From: Kay Sievers <kay.sievers@vrfy.org>
To: Louis Garcia II <louisg00@bellsouth.net>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Status of driver core struct device changes?
Date: Sat, 26 Aug 2006 15:24:46 +0200 [thread overview]
Message-ID: <1156598686.3597.218.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <1156550000.3120.2.camel@soncomputer>
On Fri, 2006-08-25 at 19:53 -0400, Louis Garcia II wrote:
> On Sat, 2006-08-12 at 09:14 -0700, Greg KH wrote:
> > On Sat, Aug 12, 2006 at 12:34:43AM -0400, Louis Garcia II wrote:
> > > On Fri, 2006-08-11 at 17:59 -0700, Greg KH wrote:
> > > > On Fri, Aug 11, 2006 at 05:49:29PM -0400, Louis Garcia II wrote:
> > > > > A couple of months ago greg kh started work toward allowing everything
> > > > > to be a struct device in the sysfs device tree. How is this progressing?
> > > >
> > > > Quite well. But next time you might want to CC: me as I almost missed
> > > > this message.
> > > >
> > > > > Any time frame when we will have a simplified driver core api?
> > > >
> > > > It's getting there. If you look in -mm there are a lot of subsystems
> > > > already converted over, along with a lot of patches from andrew that
> > > > revert these changes due to udev issues.
> > > >
> > > > I'm working on fixing up the udev issues so that the kernel work is not
> > > > held up. That's a bit slower going as it requires me to install a lot
> > > > of different distros...
> > > How about block devices? Will it be moved to /sys/class or is that abi
> > > set in stone?
> >
> > Yes, those will also move, but that's a bit lower on my list of things
> > to do. Patches to help this out are always welcome.
> With the new code will their be much difference between /sys/class/
> and /sys/devices/? Can one of these go away, preferably /sys/class/?
No, that doesn't make sense. They are two different things and both will
stay.
/sys/device is the kernel device tree, modeled by the stacking of
drivers and subsystems inside the kernel. It expresses the hierarchy and
dependency of devices, but no classification.
/sys/class is the classification/grouping of devices, it will not
express any hierarchy.
In the end, after the transition of directories in /sys/class to
symlinks, /sys/class will only be flat lists of symlinks grouped by
subsytems. The symlinks will point to the actual device locations in
the /sys/devices tree.
Kay
next prev parent reply other threads:[~2006-08-26 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 21:49 Louis Garcia II
2006-08-12 0:59 ` Greg KH
2006-08-12 4:34 ` Louis Garcia II
2006-08-12 16:14 ` Greg KH
2006-08-25 23:53 ` Louis Garcia II
2006-08-26 13:24 ` Kay Sievers [this message]
2006-08-12 5:30 ` Oleg Verych
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=1156598686.3597.218.camel@pim.off.vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louisg00@bellsouth.net \
/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®