ikarso has quit [Quit: Connection closed for inactivity]
077AAJ4CU has quit [Server closed connection]
as_g5pw has joined #u-boot
<f_>
milkylainen: wdym?
<milkylainen>
f_: In general or regarding images? :)
<f_>
>itb external vs internal data. preference? future? equality?
<f_>
What did you mean?
<milkylainen>
f_: fit in it's image incarnation can payload data externally and internally. Asking about preference for image type, if any format is going away and if they're considered equal (Ie, u-boot supports them both in all cases: compression, encryption etc).
<f_>
I'd use what's currently available.
<milkylainen>
Both are available. Doesn't really answer the question. :) External data probably exists because of alignment and zero-copy style ideas. Unfortunately that idea goes away when doing any sort of image manipulation.
<milkylainen>
So I'm also questioning the need for a external data payload style.
<milkylainen>
Probably some constricted machine.
<milkylainen>
mkimage per default creates internal data. iirc.
<sjg1>
milkylainen: For SPL in particular we didn't want to load the whole thing just to parse the metadata
<sjg1>
milkylainen: For mkimage I believe making the data 'internal' is now supported too...one disadvantage of external data is that mkimage cannot add things to it (at least it didn't used to be able to)
<sjg1>
milkylainen: Yes, for image manipulation, the data should not be external, since it just makes things hard. It is easy to do a 'mkimage -E' step afterwards
<marex>
Tartarus: yeah
<marex>
Tartarus: what other part of USB is there ?
<marex>
Tartarus: oh wait ... there is gadget with matthijs, of course
<Tartarus>
marex: it's re common: usb-hub: Reset hub port... and I just wanted to make sure you saw it / commented at some point, I think that's why the author is cc'ing more people
prabhakarlad has quit [Quit: Client closed]
mmu_man has joined #u-boot
<milkylainen>
sjg1: Does u-boot transparently support both formats or do I need to poke anything beforehand?
<milkylainen>
Barebox doesn't seem to support carrying data externally (-E).
<milkylainen>
mkimage does internal data per default? If one doesn't add -E on cmdline that is.
<marex>
milkylainen: dont use downstream forks
<marex>
Tartarus: I wasnt CCed on the initial patch, I got CCed only in one of the follow up rounds, but I am aware of the patch
<Tartarus>
OK
<milkylainen>
marex: I don't care that much. It's a bootloader. Not the be-all and end-all.
<milkylainen>
If the image format is supposed be somewhat coherent across users and usages (for whatever purpose), there is going to be questions.
<milkylainen>
Not about the other bootloader per se, but in this case how the image format looks upon external and internal data.
<marex>
milkylainen: if everyone was like that, we'd be using windoze
<sjg1>
milkylainen: Does barebox support signature verification? Loadables? Perhaps we should introduce a minimum standard for supporting FIT?
<milkylainen>
sjg1: signature verification yes. I use that without any issues.
<milkylainen>
sjg1: Sounds like a good idea to me.
<milkylainen>
I haven't used loadables in barebox.
<milkylainen>
sjg1: I guess that would fulfill the end goal for me. Ie, dragging an image from de-facto upstream mkimage to other parsers and know that if they adhere to some sort of minimum standard choosen by mkimage I'll get my image through.
macromorgan_ has joined #u-boot
macromorgan has quit [Ping timeout: 245 seconds]
<Tartarus>
I mean, yes, if FIT is going to be standardized and used in a true multi-project fashion, some of the features that are in U-Boot might well need working and submitting to other projects too
<milkylainen>
I'd be fine with a baseline, some sort of generation that adhere to it and a validation suite of sorts?
<milkylainen>
Maybe a versioned spec. And as a shortcut you could choose the version in mkimage, letting you know if you're within the spec or not when using various features.
<milkylainen>
I'm just fabulating and dreaming here. :)
MWelchUK3 has joined #u-boot
qsx` has joined #u-boot
MWelchUK has quit [Quit: Ping timeout (120 seconds)]
qsx has quit [Remote host closed the connection]
MWelchUK3 is now known as MWelchUK
darkxst has quit [Ping timeout: 245 seconds]
tlwoerner has quit [Ping timeout: 252 seconds]
tlwoerner has joined #u-boot
darkxst has joined #u-boot
qqq has quit [Remote host closed the connection]
<Tartarus>
Well, my point right now is that we shouldn't start out with declaring that only FIT as U-Boot has it today is the valid multi-bootloader spec and similar to other broad specs start out with what's most widely supported and then update other projects and bump min requirements