All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Load hid.o module synchronously?
Date: Wed, 28 Apr 2004 10:02:15 -0400	[thread overview]
Message-ID: <c6od9g$53k$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <s5gisfm34kq.fsf@patl=users.sf.net>

Patrick J. LoPresti wrote:
> Chris Friesen <cfriesen@nortelnetworks.com> writes:
> 
> 
>>Patrick J. LoPresti wrote:
>>
>>
>>>For example, I invoke "modprobe hid" to make my USB keyboard work.
>>>This loads the module and exits immediately, causing my script to
>>>proceed, before the USB keyboard is probed and ready.
>>>I want to wait until the driver is finished initializing (i.e., a USB
>>>keyboard is either found or not found) before my script continues.
>>>How can I do that?
>>
>>How about scanning the usb device tree to see if the keyboard is
>>present and properly detected?
> 
> 
> You mean under sysfs or usbfs?  Or both?
> 
> 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.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-04-28 14:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 19:10 Load hid.o module synchronously? 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 [this message]
     [not found]       ` <mit.lcs.mail.linux-kernel/c6od9g$53k$1@gatekeeper.tmr.com>
2004-05-01 13:21         ` Patrick J. LoPresti
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='c6od9g$53k$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.