From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: DEVFS_FS Date: Tue, 16 Nov 2004 11:42:00 -0800 Message-ID: <20041116194200.GC10327@kroah.com> References: <200411160609.iAG69gb05935@adam.yggdrasil.com> <419A5029.5010103@sun.com> <20041116192647.GA19365@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mike Waychison , "Adam J. Richter" , hbryan@us.ibm.com, linux-fsdevel@vger.kernel.org Return-path: Received: from mail.kroah.org ([69.55.234.183]:14052 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S261772AbUKPTmt (ORCPT ); Tue, 16 Nov 2004 14:42:49 -0500 To: Jamie Lokier Content-Disposition: inline In-Reply-To: <20041116192647.GA19365@mail.shareable.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Nov 16, 2004 at 07:26:47PM +0000, Jamie Lokier wrote: > Mike Waychison wrote: > > The only need for trapping that I can see is for modules that don't have > > hardware backing them, such as tun and loop. > > There's quite a few devices like that. Do you have an exact list of such devices? I would be interested in seeing that if you did. > Although it's necessary to load drivers for some devices (like ISA > cards) to detect them, it isn't necessary to load PCI drivers to > detect that they are present. A mapping directly from detected PCI > ids to whatever udev needs could be extracted from the drivers at > compile time. Such mappings nearly exist now, except that the mapping > is from ids to drivers, instead of ids to dev info. That's because we don't express that dev info within the drivers, as it's usually not the drivers themselves that know or care about that dev info. It's the "class" cores that have that (input core, sound core, usb core, etc.) Drivers are just a conduit, and don't know, or care about dev info at all. So trying to make that mapping is pretty much impossible right now, unfortunatly. thanks, greg k-h