From: Oliver Neukum <oliver@neukum.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Subject: Re: Input layer demand loading
Date: Wed, 16 Jul 2003 20:29:50 +0200
User-Agent: KMail/1.5.1
Cc: linux-kernel@vger.kernel.org
References: <200307162219.17067.arvidjaar@mail.ru>
In-Reply-To: <200307162219.17067.arvidjaar@mail.ru>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307162029.50195.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1208
Lines: 30

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.

	Regards
		Oliver

-
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/