07:47 <devarsh> jaganteki: I am also using splashscreen during boot, but I am not facing any issues, however I am presumably using a different code flow than yours...for e.g. there is no splash_video_logo_load or bmp_logo_bitmap in my flow...I am keeping my splash logo in boot partition of my sd card and I am overriding splash_screen_prepare and calling only splash_source_load (see

07:47 <devarsh> https://github.com/u-boot/u-boot/blob/next/board/ti/am62x/evm.c#L40)..so the code flow is splash_display->splash_screen_prepare->splash_source_load->bmp_display..i wud suggest to try a similar flow to check if it helps

08:50 <jaganteki> try to use bmp via tools/logos - this one https://github.com/openedev/u-boot/blob/rk-splash/tools/logos/rockchip.bmp

16:16 <calebccff> hmm, qcom-next is failing this one CI test but I can't reproduce the failure locally (tests pass on my machine) https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/jobs/768606

16:17 <calebccff> scratch that, sandbox_flattree != sandbox ... oops

16:46 <calebccff> hmm, so on u-boot v2024.01 tag none of the "test_ut" tests get run for sandbox_flattree, but on qcom-next (which is based on v2024.01) they do...

17:12 <macromorgan> any way to ensure some patches I pushed get added for the next merge window? Specifically this series here: https://lore.kernel.org/u-boot/20240102154654.191055-1-macroalpha82@gmail.com/

17:32 <marex> macromorgan: is the maintainer on CC ?

17:32 <marex> macromorgan: are all the comments addressed ?

17:33 <macromorgan> there are no comments in the latest revision, but yes the past comments were and the maintainer is cc'd

17:53 <marex> macromorgan: maybe the maintainer is still not back from xmas downtime ?

17:54 <macromorgan> possibly, just hate to miss a merge window

17:54 <macromorgan> not the end of the world I guess

17:55 <marex> macromorgan: the stuff can still get in until rc1 or rc2

17:55 <marex> board stuff can be applied throughout the whole cycle too

17:55 <marex> (though I understand what you're worried about, sigh)

17:56 <Tartarus> Yeah, as a note to self, I really should ping a handful of custodians Monday to make sure they're planning to put together a PR if I haven't seen one already

19:30 <f_> v2024.01 is out \o/

19:30 <f_> Nice!

20:30 <yang> Hello, I tried to apply the changes "setenv bootdelay=10" into U-boot and I recompiled with "neke spremembe sem želel vmestiti v U-boot, "bootdelay=10" pa sem potem skompajlal z "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr", but the changes don't work. I have one (default) U-boot on eMMC and I think another is on the SD card (which is booting the OS)

20:30 <yang> oops let me rephrase

20:32 <yang> Hello, I tried to apply the changes "setenv bootdelay=10" into U-boot and I recompiled with "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr", but the changes don't work. I have one (default) U-boot on eMMC and I think another is on the SD card (which is booting the OS). How do I do it proprely?

20:45 <mps> yang: iirc, boot delay doesn't work in boot.scr

20:46 <Tartarus> oh fun, xypron ? Is upgrading Sphinx anywhere on your TODO list. Depend-a-bot is telling me that Jinja2 has an issue and oh, Sphinx 3.4/3.5 doesn't support Jinja 3.1.x and now I see current Sphinx is 7.2.6 and we're on 3.4...

20:46 <mps> anyway I don't understand why do you need bootdelay if there is only one option to boot

20:47 <mps> if you want boot delay use extlinux.conf instead of boot.scr

20:47 <mps> yang: 'SL' lang above?

20:47 <CounterPillow> they're probably just trying to wrangle some armbian image into behaving

20:48 <mps> CounterPillow: could be, I just wonder

20:49 <mps> for years I didn't used boot.scr, extlinux.conf is much better IMO

20:50 <yang> mps: yes SL, I also tried to edit /boot/armbianEnv.txt and add "bootdelay=10" there, but didn't work. Well maybe it works, but it's for the Uboot from the SD-card and I think I am booting the default U-boot from EMMC?

20:52 <mps> yang: could you set boot devices order on your board, to force one you want to boot first

20:53 <yang> I am trying to figure out how to do that, yes

20:54 <xypron> Tartarus: could you, please forward the Dependabot mail.

21:09 <Tartarus> Done