Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

Olivier Galibert
2005-04-06T20:16:06Z

On Tue, Apr 05, 2005 at 03:28:01PM -0400, Jeff Garzik wrote:
> * Most firmwares are a -collection- of images and data. The firmware
> infrastructure should load an -archive- of firmwares and associated data
> values.

Why don't you use multiple firmware loading calls with different
names? Maybe adding a "group" name, or simply adding a '/' in the
name. That way the userspace half will have the choice between using
directories, tar, zip or whatever. The speedtouch driver already
requests multiple files, having them together in one file is a
userspace problem which the kernel can help but shouldn't try to solve.

>
> * The firmware distribution infrastructure is basically non-existent.
> There is no standard way to make sure that a firmware separated from the
> driver gets to all users.

That's the price how having non-gpl compatible firmware though.

> * The firmware bundling infrastructure is basically non-existent.
> (Arjan talked about this) There needs to be a a way to ensure that the
> needed firmwares are automatically added to initramfs/initrd.

Yes. See following too.

> * There is no chicken-and-egg problem as Arjan mentions. Once the above
> technical problems are resolved, its trivial to apply a firmware loading
> patch. I believe in hard transitions, not shipping tg3 with firmware
> -and- a firmware loading patch.

An infrastructure to add a number of files to the kernel image (_not_
the initrd/initramfs) which can be found through internal kernel
calls, firmware loading and probably an export in /proc would be nice.
Unifying DSDT override, config.gz and early firmware could be nice.

> * Firmwares such as tg3 should be shipped with the kernel tarball.

Does it change between kernel versions? How often?

OG.