linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Mike Waychison <Michael.Waychison@Sun.COM>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	hbryan@us.ibm.com, linux-fsdevel@vger.kernel.org
Subject: Re: DEVFS_FS
Date: Tue, 16 Nov 2004 11:42:00 -0800	[thread overview]
Message-ID: <20041116194200.GC10327@kroah.com> (raw)
In-Reply-To: <20041116192647.GA19365@mail.shareable.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

  reply	other threads:[~2004-11-16 19:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  6:09 DEVFS_FS Adam J. Richter
2004-11-16 19:08 ` DEVFS_FS Mike Waychison
2004-11-16 19:26   ` DEVFS_FS Jamie Lokier
2004-11-16 19:42     ` Greg KH [this message]
2004-11-16 19:48     ` DEVFS_FS Mike Waychison
2004-11-17 18:19     ` DEVFS_FS Bryan Henderson
2004-11-17 18:28       ` DEVFS_FS Jamie Lokier
2004-11-16 19:47 ` DEVFS_FS Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
2004-11-13 16:29 DEVFS_FS Adam J. Richter
2004-11-15 19:35 ` DEVFS_FS Bryan Henderson
2004-11-11 19:53 DEVFS_FS Adam J. Richter
2004-11-11 23:00 ` DEVFS_FS Bryan Henderson
2004-11-12  5:55   ` DEVFS_FS Jamie Lokier
2004-11-12 18:50     ` DEVFS_FS Bryan Henderson

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=20041116194200.GC10327@kroah.com \
    --to=greg@kroah.com \
    --cc=Michael.Waychison@Sun.COM \
    --cc=adam@yggdrasil.com \
    --cc=hbryan@us.ibm.com \
    --cc=jamie@shareable.org \
    --cc=linux-fsdevel@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).