[Elinux-discuss] How to start multi-entity embedded work on specific topics? (boot time, for example)

[Robert Schwebel]

On Mon, Jun 10, 2024 at 09:33:04PM +0000, Bird, Tim wrote:
> Does anyone else want to chime in with any pros and cons with this
> approach? For example, could buildroot developers and users utilize
> information, patches, tools, etc. stored in YP this way? Or would
> this stuff be off their radar?

Taken the fact that yocto is the de-facto standard build system for many
projects these days, I would say a yocto layer is a valid option for
storing this kind of information.

At Pengutronix, most of our projects are based on yocto, ptxdist and
some variant of debian these days (in this order). If the information is
not burried deeply in some yocto magic, it's usually easy to extract it
for the other build systems if necessary.

The bigger challenge will be to convince the respective upstream
projects that boot time optimization is a value and not traded against
developer convenience. IMHO, boot time optimization methods will only
have a chance if they are easy to use. You can always optimize a system
in a pathologic way, so it is fast but not easy-to-update any more.
Which is much more of a value in times where the kernel folks create 10
CVEs every day while manufacturers are challenged with regulations (i.e
the EU cyber resilience act).

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |