From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Future devfs plans
Date: Mon, 26 Jul 2004 07:35:50 +0200 [thread overview]
Message-ID: <pan.2004.07.26.05.35.49.669188@dungeon.inka.de> (raw)
In-Reply-To: <410450CA.9080708@hispalinux.es>
On Mon, 26 Jul 2004 00:34:51 +0000, Ramón Rey Vicente wrote:
> With udev you can do that, and without important bugs :). And the more
> important thing is _udev is in active development_
devfs has the "open /dev/somefile" to load $somedriver
mechanism. it is said to be racy, as far as I know.
udev works very differently. mostly, the idea is kernel detects hardware,
kernel calls hotplug, hotplug loads driver, driver registers device
structure in kernel, kernel calls hotplug for the new device, udev creates
the device in /dev.
with this mechanism, the kernel always has all drivers for hardware
currently available loaded, and udev provides the /dev devices.
devfs allowes you to not have the driver loaded till you try to use it.
so udev _cannot_ do what devfs does.
still I agree that the way kernel/hotplug/udev work is much better and
supporting the old style devfs works is not necessary. but please be
honest about the differences.
Andreas
next prev parent reply other threads:[~2004-07-26 5:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 14:45 Adam J. Richter
2004-07-26 0:00 ` Jim Gifford
2004-07-26 0:17 ` Ed Sweetman
2004-07-26 0:29 ` Lee Revell
2004-07-26 0:59 ` Lee Revell
2004-07-26 18:09 ` Adrian Bunk
2004-07-26 21:44 ` Ed Sweetman
2004-07-26 23:01 ` CaT
2004-07-27 21:24 ` Lee Revell
2004-07-27 22:35 ` Adrian Bunk
2004-07-27 22:39 ` Lee Revell
2004-07-26 0:21 ` Rafael do N. Pereira
2004-07-26 0:31 ` Ramón Rey Vicente
2004-07-26 0:35 ` Ramón Rey Vicente
2004-07-26 5:35 ` Andreas Jellinghaus [this message]
2004-07-26 6:58 ` Erik Steffl
2004-07-27 16:55 ` David Bryson
2004-07-27 18:44 ` Erik Steffl
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=pan.2004.07.26.05.35.49.669188@dungeon.inka.de \
--to=aj@dungeon.inka.de \
--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
all inboxes | Powered by JetHome®