[lkml]   [2004]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Re: Load hid.o module synchronously?
On Tue, May 04, 2004 at 05:56:48PM -0400, Patrick J. LoPresti wrote:
> Greg KH <> writes:
> > On Sat, May 01, 2004 at 09:21:31AM -0400, Patrick J. LoPresti wrote:
> >
> > > So there is no way to load this hardware driver and wait until it
> > > either binds or fails to bind to its associated hardware? That seems
> > > like a bad bug in the design...
> >
> > Um, what is wrong with the proposals I made for how you can detect
> > this?
> Your proposals were:
> - look at the device in /proc/bus/usb/devices and wait until the
> driver is bound to that device "(hid)" will show up as the
> driver bound to that interface
> - look at the sysfs directory for the hid driver and wait for
> the symlink to the device shows up. This should be at
> /sys/bus/usb/drivers/hid
> I see how these let me wait until the hid.o module successfully binds
> to the hardware.
> But what if it fails to bind? For example, what if an error occurs?
> Or what if the keyboard is on the module's blacklist? How do I know
> when to stop waiting?

You do not, sorry.

> Ideally, what I would like is for "modprobe <driver>" to wait until
> all hardware handled by that driver is either ready for use or is
> never going to be. That seems simple and natural to me.

Sorry, but this is not going to happen. It does not fit into the way
the kernel handles drivers anymore. Again, sorry.

greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:02    [W:0.066 / U:10.712 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site