From: "Patrick J. LoPresti" <patl@users.sourceforge.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Load hid.o module synchronously?
Date: 04 May 2004 22:49:56 -0400 [thread overview]
Message-ID: <s5gy8o7bnhv.fsf@patl=users.sf.net> (raw)
In-Reply-To: <20040504223550.GA32155@kroah.com>
Greg KH <greg@kroah.com> writes:
> On Tue, May 04, 2004 at 05:56:48PM -0400, Patrick J. LoPresti wrote:
>
> > 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.
That is disappointing. I mean, I deal with Microsoft products a lot,
where "unreliable by design" is normal. But I expected better from
Linux.
> > 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.
OK, an arbitrary flaky delay it is. Thanks!
- Pat
next prev parent reply other threads:[~2004-05-05 2:49 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 [this message]
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='s5gy8o7bnhv.fsf@patl=users.sf.net' \
--to=patl@users.sourceforge.net \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox