matthias_bgg has quit [Read error: Connection reset by peer]
sdfgsdfg has joined #u-boot
matthias_bgg has joined #u-boot
<Tartarus>
milkylainen: Sorry, are you on x8664 or arm64? I forget, sorry.
<milkylainen_>
Tartarus: x86_64.
<Tartarus>
that's kinda what I thought, ok
<Tartarus>
is bzImage still a special thing on x86_64 with its own decompressor or vmlinux.bz2
redbrain has joined #u-boot
mckoan is now known as mckoan|away
<milkylainen_>
Tartarus: Still self-decompressing iirc.
frieder has quit [Remote host closed the connection]
<milkylainen_>
xypron: Hm. Aren't all bzImages compressed? Are you saying I should use something other than bzImage under x86_64 uefi-app mode?
gsz has left #u-boot [#u-boot]
sobkas has quit [Read error: Connection reset by peer]
matthias_bgg has quit [Ping timeout: 240 seconds]
<Tartarus>
milkylainen_: On arm64 for example, all Images are the "Image" with vanilla compression on top of them. On arm32, "zImage" is actually a self-contained decompressor with the vmlinux.gz inside. I do not recall if modern x86_64 is the former or the latter, but I know historically it was the latter
<milkylainen_>
Yes I know, but x86 has been self decompressing for ages. So nothing new?
<Tartarus>
The latter is the kind of thing that should be able to be run, with the right header/etc, as it's an application of sorts, the former is a compressed file that needs uncompressing
<Tartarus>
Is it still? I thought they might have changed that a while back, esp w/ the EFI_STUB
<Tartarus>
But I lack details off the top of my head
<jenneron[m]>
hi. i use uboot as secondary bootloader on my chromebooks with `mkimage -A arm -O linux -T kernel -C none -e 0x23E00000 -a 0x23E00000 -d u-boot-dtb.bin u-boot-dtb.img` command, and i need to do something similar for another device, but i have no idea what is `-e 0x23E00000 -a 0x23E00000`, where can i find these addresses for another device?
tucanae47_ has quit [Read error: No route to host]
tucanae47_ has joined #u-boot
paulbarker has quit [Ping timeout: 240 seconds]
jamestperk has quit [Read error: Connection reset by peer]
jamestperk has joined #u-boot
narmstrong has quit [Read error: Connection reset by peer]
ullbeking_ has quit [Ping timeout: 240 seconds]
narmstrong has joined #u-boot
paulbarker has joined #u-boot
<jenneron[m]>
*i've read mkimage man and found that these are "load address" and "entry point" but it didn't help me to find device-specific values
pbrobinson has quit [Ping timeout: 240 seconds]
elvishjerricco has quit [Ping timeout: 240 seconds]
elvishjerricco has joined #u-boot
pbrobinson has joined #u-boot
ullbeking_ has joined #u-boot
<Tartarus>
You'll want to look at the memory map for the SoC