06:50 <LeSpocky> Tartarus: understood

07:16 <xypron> Tartarus: can we let https://www.u-boot.org/ forward to https://docs.u-boot.org/. Is Denx owning that domain?

07:50 <Clamor> Maybe someone knows under which license vendor android images are distributed?

08:17 <f_> xypron: I was working on a website that would be @ u-boot.org, but didn't have much time lately

08:17 <f_> I'll try working on it today.

08:18 <f_> Need to address a bunch of feedback I got.

08:18 <f_> (thanks everyone for that :D)

08:20 <xypron> f_: It is nice to have a domain for our project. I was just wondering who the owner is.

08:21 <f_> Oh ok

08:21 <f_> I think sjg1 might be the owner?

08:22 <mkorpershoek> Clamor: there is a NOTICE file in the android vendor image which contains licence info: vendor/etc/NOTICE.xml.gz

08:26 <Clamor> mkorpershoek: thanks

09:20 <Clamor> mkorpershoek: it seems that this file is not present, devices are too old, 12 yo to be exact

09:49 <mkorpershoek> oh, yeah indeed that's very old

09:54 <Clamor> mkorpershoek: I am trying to submit a few broadcom blobs into linux firmware, and got this question. I have never actually thought under which license those vendor images are shipped. It always feeled like take it and go.

09:57 <Clamor> And maybe here are boardcom employees who could help some old forgotten devices with their Signed Off?

10:25 <LeSpocky> okay I can built without host openssl again, will prepare a patch series after lunch

16:52 <jmasson> Hi All,

16:52 <jmasson> I've sent a trivial fix in clk core:

16:52 <jmasson> https://patchwork.ozlabs.org/project/uboot/patch/871qcj5frz.fsf@baylibre.com

16:52 <jmasson> But I did not get any review since 3 weeks, I don't know what is the usual process.

16:52 <jmasson> Do I send a RESEND patch, ping the maintainer by email or irc, wait a little bit longer ... ?

16:52 <jmasson> I know that maintainers are very busy, just let me know if I need to be more patient.

16:52 <jmasson> Thanks

17:50 <cambrian_invader> jmasson: I will have a look some time this weekend

18:58 <jmasson> cambrian_invader: thanks

21:42 <ac_slater> hey guys, I'm not new to uboot but I am new to `bootm`. I'm on a Xilinx ZynqMP (aarch64). I can successfully use `booti ${k} ${r} ${d}`. But, putting the SAME files in an ITS/ITB and using `bootm ${a}#conf` causes the kernel to crash.

21:43 <Hammdist> hi all. I've had a look on github but I can't find the definition of the image header anywhere. on arm64 this begins with a jump pad (two code words) has the magic arm\x64 in it, but I haven't been able to locate the struct in the u-boot code. I am actually most interested in the arm32 version of this struct ...

21:45 <ac_slater> for my question above, here is the ITS definition that doesn't work with bootm https://paste.debian.net/plain/1301136

21:47 <ac_slater> ah here is a better paste... has the ITS definition and the uboot log https://paste.debian.net/plain/1301137

21:48 <ac_slater> just cant tell if bootm isnt loading things correctly - booti works if I just manually take the files out

21:51 <ac_slater> could be this: [ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader! .. not sure if that's causing REAL issues or the warning is pretty soft in this case

21:55 <Tartarus> Yeaeh, that's a real issue

21:57 <Tartarus> And full logs and env from both booti and bootm might help more

21:58 <ac_slater> thanks Tartarus!

21:59 <ac_slater> Xilinx suggests changing uboot's entry and load address: https://support.xilinx.com/s/article/76712?language=en_US

21:59 <Hammdist> I found the header I'm talking about here: https://www.kernel.org/doc/html//v5.8/arm64/booting.html ... anyone knows if there is a 32-bit version of it or how do 32-bit kernels get booted?

22:00 <ac_slater> they use a tool to generate uboot's defconfig so I can't tell which UBOOT options to change to test this

22:00 <ac_slater> Tartarus: ^

22:01 <Tartarus> Hammdist: Yes, here's a 32bit version in the docs too, but note that one uses zImage instead on 32bit arm

22:02 <Hammdist> argh. I'm trying to put together and boot a hobby kernel, not linux. is there a way I can boot from u-boot without going to the trouble of compressing my kernel?

22:04 <Hammdist> it's looking like what would fit me best is a uImage, not a zImage

22:05 <Tartarus> Uh, a hobby kernel?

22:05 <Tartarus> If you wrote something from scratch for fun, just bootelf it

22:05 <Hammdist> ah one can directly boot elfs?

22:07 <Hammdist> indeed, I just found the do_bootelf function. ok I will try to use this

22:08 <Hammdist> thanks

22:10 <ukky> Hammdist: mkelfImage could wrap uImage kernel into ELF, not sure if the tool is up to date. The tool supports both compressed and uncompressed kernels

22:11 <Hammdist> ukky: ah not needed. from gcc I get ELF directly so I'm thinking with a suitable linker script I could just use bootelf

22:42 <NishanthMenon> Hammdist: you might be interested in https://git.kernel.org/pub/scm/linux/kernel/git/mark/boot-wrapper-aarch64.git if you want to go real low level

22:45 <marex> NishanthMenon: oh hey

22:45 <NishanthMenon> marex: hey