modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

Bill Nottingham notting at
Wed Oct 17 14:47:34 UTC 2012

Josh Boyer (jwboyer at said: 
> > However, if you go down that route, the kernel should be the same way,
> > the firmware should be separate subpackages, and requires should be done at
> > the module -> firmware level by generating it from the MODULE_FIRMWARE tags.
> > (Unless you're relying on packagekit to install your firmware, which if
> > you're going that minimal seems to have missed the forest for the trees
> > somewhere.)
> I'm not understanding what you're proposing.  Are you suggesting:
> 1) We have further split up module sub-packages that carry their own
> firmware requires (e.g. kernel-module-iwlwifi requires iwlwifi-firmware)
> or
> 2) Even more firmware subpackages split out of linux-firmware.
> If you're suggesting 1, I'd be really really opposed to that.  It would
> make packaging in kernel.spec even more of a nightmare than it already
> is.
> If you're suggesting 2, I don't see the point.  The kernel will install
> and even with per-module dependencies generated (somehow), it'll still
> install all of the various -firmware packages because the modules will
> be getting installed.

Both - if people want firmware packages split out of linux-firmware, it
doesn't make sense unless the drivers (similar in size) are also split,
and if you were to do so, you'd need to start adding the driver -> firmware
package dependency mapping. 


More information about the devel mailing list