Date: Wed, 16 Jul 2003 11:33:43 -0700
From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Oliver Neukum <oliver@neukum.org>, linux-kernel@vger.kernel.org
Subject: Re: Input layer demand loading
Message-ID: <20030716183343.GE2681@matchmail.com>
Mail-Followup-To: Andrey Borzenkov <arvidjaar@mail.ru>,
	Oliver Neukum <oliver@neukum.org>, linux-kernel@vger.kernel.org
References: <200307162219.17067.arvidjaar@mail.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200307162219.17067.arvidjaar@mail.ru>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1162
Lines: 27

On Wed, Jul 16, 2003 at 10:19:17PM +0400, Andrey Borzenkov wrote:
> >> 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 ...

Isn't that why we have hotplug in userspace?

That way, we know we have a mouse, but it's up to userspace to find out
what kind.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/