On Thu, Dec 08, 2022 at 11:49:16AM -0800, Adam Williamson wrote:
On Thu, 2022-12-08 at 20:23 +0100, drago01 wrote:
> The problem I see here is not the presence of the firmware on the
> image,
> but the fact that it seems to be loaded into memory despite not being
> used.
This is the direction Daniel was thinking down. I'm waiting for someone
with more expertise to reply, but I suspect the reply is going to be
along the lines of "yes, we *can* do that, but it's somewhat tricky
work that involves thinking about lots of paths that aren't obvious,
and somebody would need to dedicate their time to working on that".
Split install.img into install.img + firmware.img? I think we already
have support for multiple images (I see requests for updates.img when
watching httpd logs while doing network installs), so the split should
be easy. The somewhat more tricky part is probably to figure whenever
we need the firmware or not.
take care,
Gerd