Hi Mark,
> > I personally prefer full firmware names. This makes the dependency easy
> > and even an end user can call modinfo and see what firmware is expected
> > by a certain driver (without looking at the source code).
>
> How does one handle the case of updated firmware from the manufacturer,
> which requires *no* driver changes? If the driver has all of the previously
> known names/versions hardcoded, then would it refuse to use the new stuff?
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.
Regards
Marcel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
