Re: [PATCH v2 1/2] cmd: source: Use script from default config

Hi Tom, Thanks for the pointers. I understand your concerns about the growth in size. I'll look into it. Best regards, Sven On 1/24/22 19:08, Tom Rini wrote: On Sat, Jan 22, 2022 at 09:36:58PM +0100, Sven Schwermer wrote: Hi Tom, I didn't think this would result in a size increase. Could

Re: [PATCH v2 1/2] cmd: source: Use script from default config

On Sat, Jan 22, 2022 at 09:36:58PM +0100, Sven Schwermer wrote: > Hi Tom, > > I didn't think this would result in a size increase. Could you elaborate? Alright. So for background, if you build with tools/buildman/buildman rather than just "make" directly there's some handy tools like "bloat" de

Re: [PATCH v2 1/2] cmd: source: Use script from default config

Hi Tom, I didn't think this would result in a size increase. Could you elaborate? When generating FIT images with Yocto, you won't get a /images/default property which is inconsistent with the FIT spec. This is an example of how Yocto spits out FIT images which I believe is consistent with the

Re: [PATCH v2 1/2] cmd: source: Use script from default config

On Sat, Jan 01, 2022 at 07:45:39PM +0100, Sven Schwermer wrote: > When sourcing FIT images, source the script node from the "bootscr" > property within the default configuration. If > board_fit_config_name_match is overridden, this will determine the > selected configuration rather than the defaul

[PATCH v2 1/2] cmd: source: Use script from default config

When sourcing FIT images, source the script node from the "bootscr" property within the default configuration. If board_fit_config_name_match is overridden, this will determine the selected configuration rather than the default one. The old behaviour is inconsistent with the FIT image specificatio