From: Oliver Neukum <oliver@neukum.org>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: "Patrick J. LoPresti" <patl@users.sourceforge.net>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: Load hid.o module synchronously?
Date: Fri, 7 May 2004 19:50:30 +0200 [thread overview]
Message-ID: <200405071950.30130.oliver@neukum.org> (raw)
In-Reply-To: <409BB71F.9090601@stesmi.com>
Am Freitag, 7. Mai 2004 18:19 schrieb Stefan Smietanowski:
> Hi Patrick.
>
> >>The set of devices connected to the machine is not static. Waiting
> >>until all hardware is ready is very hard to even define.
> >
> > It is very easy to define for 99.999% of all keyboards, which start
> > off connected and stay connected.
> >
> > This should be simple. I want to load a driver at boot time and wait
> > until it either binds to something or fails to do so. If the user is
>
> But that means that the driver must include some sort of arbitrary
> timelimit. Why push that from userspace to the driver?
No, upon module load the device tree could be locked and the module
insertion could wait for all matching devices in the tree to be probed.
It definitely can be done and that solution cannot be achieved from
userspace because exporting such locks would be a disaster.
However, it is probably not wise to provide for this special case.
It would probably be best to provide a generic probe method for
devices, which could run synchronously.
Regards
Oliver
next prev parent reply other threads:[~2004-05-07 21:36 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
[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 [this message]
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=200405071950.30130.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patl@users.sourceforge.net \
--cc=stesmi@stesmi.com \
/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