On Tue, 07 Aug 2007, Kay Sievers wrote:
> If you don't have modules and the initial request fails, how do you
> load the firmware later?
I trigger a rebinding of the device to the driver in an init file:
# echo -n [device] >/sys/.../bind
> The real fix would be to change the driver not to block in the
> firmware request and use async version of firmware loading. The
> whole firmware class with its silly timeout is just a piece of
> crap, that needs to be replaced.
I don't think that would be a real fix. You've done away with the
kernel blocking, but the timeout is still there, only that in the
background, and my point is still true: it is useless to wait at
all if userspace didn't receive the event. Waiting asynchronously
is less annoying than waiting synchronously, but equally useless.
Javier
-
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]
