[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060730085500.GB17759@kroah.com>
Date: Sun, 30 Jul 2006 01:55:00 -0700
From: Greg KH <greg@...ah.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Shem Multinymous <multinymous@...il.com>,
Vojtech Pavlik <vojtech@...e.cz>,
"Brown, Len" <len.brown@...el.com>, Pavel Machek <pavel@...e.cz>,
Matthew Garrett <mjg59@...f.ucam.org>,
kernel list <linux-kernel@...r.kernel.org>,
linux-thinkpad@...ux-thinkpad.org, linux-acpi@...r.kernel.org
Subject: Re: Generic battery interface
On Fri, Jul 28, 2006 at 12:10:43PM -0400, Dmitry Torokhov wrote:
> On 7/28/06, Shem Multinymous <multinymous@...il.com> wrote:
> >On 7/28/06, Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> >> 4) sysfs - all capabilities, IDs, etc for input devices exported there
> >as well.
> >
> >Forgive my ignorance, but how do I conncet a sysfs directory with a /dev
> >device?
> >So far the only way I found is to compare /sys/whatever/dev with the
> >major+minor of the dev file, which requires brute-force enumeration on
> >at least one side.
> >
>
> Can't we have udev make a symlink when it creates device node?
No, ick, why would you want that?
Just look at the "dev" file in sysfs, which shows the major:minor
number.
Or just look at the directory that you are in, and that's almost always
the /dev node name.
For example, /sys/block/sda/sda1/ is /dev/sda1.
/sys/class/tty/ttyS1 is /dev/ttyS1.
It's usually not that difficult to do the mapping :)
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists