Re: [RFC] binary firmware and modules

[Jon Masters]

On 4/19/06, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Mark,

mlord>> How does one handle the case of updated firmware from the manufacturer,
mlord>> which requires *no* driver changes?  If the driver has all of
the previously
mlord>> known names/versions hardcoded, then would it refuse to use
the new stuff?

I guess Mark is saying "what if the filename changes". The thing is,
as part of some other work I'm doing right now, I've talked to a few
folks about naming conventions for firmware, etc. In an ideal world,
we'd have some LANNA process for firmware naming that was flexible and
yet allowed us to handle this all cleanly, and we'd perhaps be able to
request_firmware with a minimum version number or whatever. Right now,
the kernel only supports pulling in a binary blob - determining
whether it's the right one is somewhat vague.

> if no driver change is needed, then you simply can replace the firmware
> file and reload the driver. With the BlueFRITZ! USB driver we did this a
> bunch of times and it worked out perfectly. The firmware name in this
> case is only a placeholder.

That's really going to have to continue for the moment I think, until
we can get better infrastructure for handling firmware updates in
userspace and managing versions. The point of my original patch is
that it gives us a starting point to be able to think about this more.

Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/