From: Greg KH <greg@kroah.com>
To: Fredrik Tolf <fredrik@dolda2000.cjb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input layer demand loading
Date: Wed, 16 Jul 2003 14:54:52 -0700 [thread overview]
Message-ID: <20030716215452.GB2773@kroah.com> (raw)
In-Reply-To: <200307162323.31836.fredrik@dolda2000.cjb.net>
On Wed, Jul 16, 2003 at 11:23:31PM +0200, Fredrik Tolf wrote:
> On Wednesday 16 July 2003 18.26, Greg KH wrote:
> > On Wed, Jul 16, 2003 at 02:57:42PM +0200, Fredrik Tolf wrote:
> > > On Wednesday 16 July 2003 06.29, Greg KH wrote:
> > > > On Mon, Jul 14, 2003 at 12:58:24PM +0200, Fredrik Tolf wrote:
> > > > > If the input layer userspace interface code has been compiled as
> > > > > modules, and you have a ordinary (not hotplug) device, eg. a gameport
> > > > > joystick, can really the hotplug interface be used to load joydev.o
> > > > > when /dev/input/js0 is opened?
> > > >
> > > > No, you want to load the joydev.o driver when you plug in the gameport
> > > > joystick. Which will be before you open the /dev node.
> > >
> > > Not necessarily. When the joystick is plugged in, you want to load the
> > > hardware driver modules. There's really no need for the userspace
> > > interface until someone requests it. At least that's the way I see it.
> > > And in any case, even if you do want to load joydev.o when the joystick
> > > is plugged in, I don't see how that could be done on-demand when the
> > > joystick port isn't hotplug compatible, such as is the case with
> > > gameports, right?
> >
> > 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?
>
> Huh? Look at it this way: As it is now, if you have a non-hotplug joystick,
> then you can't load anything automatically, not even the hardware drivers.
Correct.
> If you have demand-loading in the input layer, on the other hand, you can have
> "above" directives in modules.conf (or "install" directives in modprobe.conf)
> to pull in the hardware drivers along with joydev.
Where do you get the hardware driver coming along with joydev?
I must be missing something here...
> So not only does demand-loading permit hardware drivers and userspace
> interfaces independently of each other, it also provides for loading
> hardware drivers on demand for non-hotplug hardware.
That would be very nice, but I still don't see how your patch enables
this to happen.
thanks,
greg k-h
next prev parent reply other threads:[~2003-07-16 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 16:39 Input layer demand loading 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 [this message]
2003-07-16 22:07 ` Oliver Neukum
2003-07-16 22:16 ` Greg KH
2003-07-16 22:21 ` Fredrik Tolf
2003-07-16 18:19 Andrey Borzenkov
2003-07-16 18:29 ` Oliver Neukum
2003-07-16 18:33 ` Mike Fedyk
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=20030716215452.GB2773@kroah.com \
--to=greg@kroah.com \
--cc=fredrik@dolda2000.cjb.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;
as well as URLs for NNTP newsgroup(s).