On Fri, 2009-12-18 at 15:02 -0800, Luis R. Rodriguez wrote: > Sweet -- we could also expose firmware load events if not done so > already and let userspace propagate such nasty warnings, I think we'd > need to pass the firmware expected and the driver the requested it so > that once the firmware is in place (I guess through inotify maybe) the > driver modprobe can be retried. Actually, since the driver doesn't fail loading, the _bind_ has to be retried. I'm not sure there's a way to trigger a re-probe though, which would be easiest since userspace doesn't necessarily know what to bind. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
