<marex>
milkylainen_: sounds good, I think you have your share of work cut out for you :)
<milkylainen_>
:)
<cambrian_invader>
bootm works with everything afaik, but you do have to have a FIT and not (e.g.) a vmlinuz
<cambrian_invader>
I think a lot of these commands are around forever because of the existance of `boot.scr`s which expect certain commands to exist
<milkylainen_>
cambrian_invader: I saw the note. Prefer to not use FIT image.
<cambrian_invader>
what's your reasoning?
<marex>
cambrian_invader: bootm works with uImage/fitImage only
<cambrian_invader>
right
<marex>
milkylainen_: fitImage is the recommended format, so yes, please use it
<cambrian_invader>
the only issue I have with FITs are that you have to know what address to load your images ahead of time
tnovotny has quit [Quit: Leaving]
<marex>
cambrian_invader: do you
<cambrian_invader>
afaik, yes
<marex>
no
<marex>
it depends on the image
<cambrian_invader>
ok, so say I have a FIT with a kernel, fdt, and initramfs, none of which have load properties
<cambrian_invader>
does that work out of the box?
<marex>
cambrian_invader: it depends
<Sout_>
hmm is there a default load address?
LokeshV has quit [Quit: Leaving]
lokeshvutla has joined #u-boot
<Sout_>
btw load address is in ram location not on disk location. i know once load the kernel it has a location it will look at iirc (unless the ramfs image is embedded in the kernel ?)
<cambrian_invader>
marex: ok, so bootm_find_os calls fit_image_get_load and will fail if it doesn't find a load address
<cambrian_invader>
so you must have a load address for your kernel at the very least
<cambrian_invader>
which means you need to know at image creation time where to load your kernel
<marex>
cambrian_invader: so are you trying to find a specific counter-example ?
<marex>
cambrian_invader: you can create a fitImage without kernel embedded in it, e.g. for firmware ... and that might not need load address
<marex>
but that discussion is completely pointless
<cambrian_invader>
sure, but I'm talking about replacements for e.g. booti/bootz
<marex>
Sout_: there is $loadaddr , which is the default load address
Sout_ is now known as Sout
<marex>
FDT gets relocated to end of RAM
<marex>
initramfs, depends ...
kpo has quit [Ping timeout: 272 seconds]
<milkylainen_>
cambrian_invader: you mean beside yet another layer of wrapping?
<milkylainen_>
Not much, besides that.
samueldr has quit [Read error: Connection reset by peer]
mvaittin has quit [Read error: Connection reset by peer]
cpackham[m] has quit [Read error: Connection reset by peer]
<milkylainen_>
dgilmore: Sure. But I don't understand if you were answering me or someone else? I don't see how "distro defaults" is related to bootcmds being a bit of a miss.
sszy has quit [Ping timeout: 252 seconds]
<dgilmore>
just commenting that there are multiple defined places to load things.
tlwoerner_ is now known as twoerner
twoerner has quit [Quit: Leaving]
tlwoerner has joined #u-boot
frieder has quit [Remote host closed the connection]
redbrain has joined #u-boot
mckoan is now known as mckoan|away
Tartarus has quit [*.net *.split]
rfs613 has quit [*.net *.split]
rfs613 has joined #u-boot
Tartarus_ has joined #u-boot
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
monstr has quit [Remote host closed the connection]
sigmaris has quit [Ping timeout: 272 seconds]
sigmaris has joined #u-boot
guillaume_g has quit [Quit: Konversation terminated!]
Tartarus_ is now known as Tartarus
lokeshvutla has quit [Remote host closed the connection]