On Mon, 2007-05-28 at 12:38 +0100, Michael-Luke Jones wrote:
> On 28 May 2007, at 12:24, Kay Sievers wrote:
>
> > A driver for a bootup-critical device like this should just never
> > release the firmware after the first load. There is absolutely no
> > point
> > in doing that.
>
> Bogus argument: is a USB-Ethernet device which needs firmware loading
> boot-up critical? Not on the surface, but if the device loads root
> over this device, it suddenly is.
Releasing loaded firmware for anything that needs to handle situations
like this just doesn't make sense.
> This functionality should also be written into the firmware-class
> (and this fact *is* acknowledged in the sparse documentation).
Yeah, but these are just words, nothing people could use. Unfortunately
the author of this document died a few years ago.
Either the whole idea of userspace firmware-loading should be considered
as a problem impossible to do right because of its unsolvable side
effects. Or at least releasing loaded firmware should be the exception
for drivers which can be sure, that the firmware is not needed in
situations we try to work around here.
Kay
-
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]
