From: "Patrick J. LoPresti" <patl@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Load hid.o module synchronously?
Date: 01 May 2004 09:21:31 -0400 [thread overview]
Message-ID: <s5ghdv0i8w4.fsf@patl=users.sf.net> (raw)
In-Reply-To: <mit.lcs.mail.linux-kernel/c6od9g$53k$1@gatekeeper.tmr.com>
Bill Davidsen <davidsen@tmr.com> writes:
> Patrick J. LoPresti wrote:
>
> > I see how I can scan for a USB keyboard after loading the USB host
> > controller module. I think. But what do I look for, exactly, to
> > tell when hid.o has hooked itself up to the keyboard?
>
> You need to be able to tell "not hooked yet" from "never saw it" for
> reliable operation. I don't know how to do that, sorry.
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...
I suppose I will just use some arbitrary delay.
- Pat
next prev parent reply other threads:[~2004-05-01 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 19:10 Patrick J. LoPresti
2004-04-26 19:40 ` Chris Friesen
2004-04-26 19:50 ` Patrick J. LoPresti
2004-04-26 20:03 ` Chris Friesen
2004-04-26 20:19 ` Greg KH
2004-04-28 14:02 ` Bill Davidsen
[not found] ` <mit.lcs.mail.linux-kernel/c6od9g$53k$1@gatekeeper.tmr.com>
2004-05-01 13:21 ` Patrick J. LoPresti [this message]
2004-05-01 16:43 ` Kevin P. Fleming
2004-05-04 20:01 ` Greg KH
2004-05-04 21:56 ` Patrick J. LoPresti
2004-05-04 22:35 ` Greg KH
2004-05-05 2:49 ` Patrick J. LoPresti
2004-05-05 2:56 ` Greg KH
2004-05-05 15:19 ` Patrick J. LoPresti
2004-05-05 22:45 ` Greg KH
2004-05-06 13:54 ` Patrick J. LoPresti
2004-05-07 22:00 ` Greg KH
2004-05-05 3:21 ` Randy.Dunlap
2004-05-05 22:33 ` Oliver Neukum
2004-05-06 14:05 ` Patrick J. LoPresti
2004-05-07 16:19 ` Stefan Smietanowski
2004-05-07 17:50 ` Oliver Neukum
2004-04-27 6:02 ` Kim Holviala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='s5ghdv0i8w4.fsf@patl=users.sf.net' \
--to=patl@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®