linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Input layer demand loading
Date: Wed, 16 Jul 2003 18:56:03 +0200	[thread overview]
Message-ID: <yw1x65m2mmvw.fsf@users.sourceforge.net> (raw)
In-Reply-To: 20030716162639.GB7513@kroah.com

Greg KH <greg@kroah.com> writes:

>> 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?
>
> So there really isn't much benifit to doing this, sorry.

That's easily fixed in modules.conf, or modprobe.conf for 2.6.

-- 
Måns Rullgård
mru@users.sf.net


  reply	other threads:[~2003-07-16 16:45 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 [this message]
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

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=yw1x65m2mmvw.fsf@users.sourceforge.net \
    --to=mru@users.sourceforge.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).