From: Oliver Neukum <email@example.com>
To: Andrey Borzenkov <firstname.lastname@example.org>
Subject: Re: Input layer demand loading
Date: Wed, 16 Jul 2003 20:29:50 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
Am Mittwoch, 16. Juli 2003 20:19 schrieb Andrey Borzenkov:
> >> True, but then if you try to open the port, you will only get the base
> >> joydev.o module loaded, not the gameport driver, which is what you
> >> _really_ want to have loaded, right?
> >> So there really isn't much benifit to doing this, sorry.
> > Why? It could work the way PCMCIA SCSI works.
> > Cardmgr loads the LLDD, but sd, sg, etc. are loaded
> > on demand.
> how? SCSI (or USB, PCI, EISA etc) have driver-independent means to identify
> device or at least device class.
> But how are you going you going to know you need to load specific mouse driver
> (logitech not microsoft) or specific joystick flavour? All that you possibly
> know that you have _some_ mouse or _some_ joystick ...
Exactly, you'd only load the hardware independent part on demand.
Or, alternatively, you'd record the driver to load in the hotplug script
and load it on demand.
next prev parent reply other threads:[~2003-07-16 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 18:19 Input layer demand loading Andrey Borzenkov
2003-07-16 18:29 ` Oliver Neukum [this message]
2003-07-16 18:33 ` Mike Fedyk
[not found] ` <E19d16P-00044Xfirstname.lastname@example.org>
2003-07-17 18:38 ` Re: " Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 16:39 Fredrik Tolf
2003-07-14 6:22 ` Greg KH
2003-07-14 10:58 ` Fredrik Tolf
2003-07-16 4:29 ` Greg KH
2003-07-16 12:57 ` Fredrik Tolf
2003-07-16 16:26 ` Greg KH
2003-07-16 16:56 ` Måns Rullgård
2003-07-16 17:28 ` Oliver Neukum
2003-07-16 21:23 ` Fredrik Tolf
2003-07-16 21:54 ` Greg KH
2003-07-16 22:07 ` Oliver Neukum
2003-07-16 22:16 ` Greg KH
2003-07-16 22:21 ` Fredrik Tolf
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).