<hramrach>
in general you should complain to petitiboot people that defined that something that is documented as valid is not parsed by their loader
<hramrach>
but in this specific case it would make more sense to hust not load a device tree
<hramrach>
if you are running petitiboot it means you are running Linux and that means you have a working devicetree, just pass it on
<chron0>
I'd love to optimize this, but this is my first time dealing with petitbootand a kernel that relies heavily on device tree
<chron0>
odroid m1
<chron0>
ok, finally got it to boot
<chron0>
i have to use the "working" example but in the final booti i just passed - instead of initrd and that went around the initrd and got me to my gentoo prompt
<chron0>
if you have any tips to streamline and lean down/optimize this further I'd appreciate it very much - yes linux - gentoo linux running on the box, for no NO initrd needed
<chron0>
i fear I dont fully understand that whole device tree business
<chron0>
they have a boot.ini where hardkernel is defining "overlays" for specific hw parts of the SoC
<chron0>
like: overlays = "i2c0 can0"
<hramrach>
basically to boot petitboot you shuld have a device tree already
<hramrach>
so ask the petitboot people how to boot a kernel with that
GNUtoo has joined #u-boot
<chron0>
check
<hramrach>
maybe just do a syslinux config, that does not support devicetree, so hopefully petitboot will use its own
<hramrach>
that however means that to update the devicetree you will need to use whatever means petitboot provides for that - probably rebuild and update petitboot
mmu_man has quit [Ping timeout: 240 seconds]
<hramrach>
this is totally offtopic here and unfortunately I don't know about petitboot, and even where to get to know something about petitboot
<chron0>
understand, thx for the hints anyways, much appreciated
<chron0>
as long as i still havent really grokked all this dtb business I'm still gonna be at a loss where to place and how to pass what exactly :/ will dive into it, thx again
<hramrach>
on platforms that use petitboot the standard way to boot is to use a config for x86 that does nto support devicetree (grub.cfg or syslinux.conf), and the device tree is embedded into petitboot
<hramrach>
but I have no idea about odriod's use
<hramrach>
that's where u-boot is heading as well - on many platfroms the device tree needs to be modified by the bootloader, and loading static device tree binary from the disk is in general not a very good idea
<chron0>
i see, maybe just "bad timing" during this kind of transition and everything is trying to find its proper place again
tsraoien has joined #u-boot
lucascastro has joined #u-boot
mmu_man has joined #u-boot
littlebobeep has quit [Remote host closed the connection]
<LetoThe2nd>
potentially stupid question: whats the recommended way of going "back to source" from a boot.scr? only thing I could easily spot on google is some dd magic.
Xeroine has quit [Ping timeout: 252 seconds]
<Tartarus>
LetoThe2nd: Well, what do you mean exactly? That dd trick is to strip the mkimage header off the text, but boot.scr is just a header on top of text
<Tartarus>
dumpimage might also do the trick I suppose
<Tartarus>
Yeah, dumpimage does it too
<LetoThe2nd>
Tartarus: ah i see, thanks!
<chron0>
LetoThe2nd: i just did the dd thing a couple of hours ago