From: Greg KH <firstname.lastname@example.org>
To: Fredrik Tolf <email@example.com>
Subject: Re: Input layer demand loading
Date: Tue, 15 Jul 2003 21:29:16 -0700 [thread overview]
Message-ID: <20030716042916.GC3929@kroah.com> (raw)
On Mon, Jul 14, 2003 at 12:58:24PM +0200, Fredrik Tolf wrote:
> On Monday 14 July 2003 08.22, Greg KH wrote:
> > On Sun, Jul 13, 2003 at 06:39:49PM +0200, Fredrik Tolf wrote:
> > > Why does the input layer still not have on-demand module loading? How
> > > about applying this?
> > What's wrong with the current hotplug interface for the input layer? If
> > you want to implement this, add some input hotplug scripts to the
> > linux-hotplug package.
> Correct me if I'm wrong, but AFAIK that can only be smoothly used to load
> hardware driver modules.
In a way, yes.
> 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?
> I don't use hotplugging that much, so I can't say that I'm sure about what it
> can do, but in my perception of the hotplug system, it can't be used for
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.
So I think it's working the way it is now, correct?
next prev parent reply other threads:[~2003-07-16 4:16 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 [this message]
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
2003-07-16 18:19 Andrey Borzenkov
2003-07-16 18:29 ` Oliver Neukum
2003-07-16 18:33 ` Mike Fedyk
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).