Re: Documentation for sysfs, hotplug, and firmware loading.

2007-08-05 Thread Bodo Eggert
On Mon, 23 Jul 2007, Rob Landley wrote: > On Saturday 21 July 2007 8:14:41 am Bodo Eggert wrote: > > Greg KH <[EMAIL PROTECTED]> wrote: > > > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > > >> I'm not trying to document /sys/devices. I'm trying to document > > >> hotplug, populati

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-25 Thread Rob Landley
On Tuesday 24 July 2007 2:38:18 am Greg KH wrote: > > In other words: Grasping sysfs is not a feasible task? If this is true, > > how can anybody reliably use sysfs? > > Huh, I never stated that at all. If you wish to fully document sysfs > and how it works, then great, do that. But that was not

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-24 Thread Cornelia Huck
On Mon, 23 Jul 2007 19:26:54 -0400, Rob Landley <[EMAIL PROTECTED]> wrote: Sorry, that's way too much for me to bother reading. I'd look at any patches against the existing documentation, though. But I'll stop looking at this thread, there's too much ranting for my taste in there. - To unsubscri

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-23 Thread Greg KH
On Sat, Jul 21, 2007 at 02:14:41PM +0200, Bodo Eggert wrote: > Greg KH <[EMAIL PROTECTED]> wrote: > > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > > >> I'm not trying to document /sys/devices. I'm trying to document hotplug, > >> populating /dev, and things like firmware loading

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-23 Thread Rob Landley
On Friday 20 July 2007 8:43:49 pm Greg KH wrote: > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > > Ok, back up. /sys/devices does not contain all the information necessary > > to populate /dev, because it hasn't got things like > > ramdisks, /dev/zero, /dev/console which are THERE

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-23 Thread Rob Landley
On Saturday 21 July 2007 8:14:41 am Bodo Eggert wrote: > Greg KH <[EMAIL PROTECTED]> wrote: > > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > >> I'm not trying to document /sys/devices. I'm trying to document > >> hotplug, populating /dev, and things like firmware loading that fal

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-21 Thread Bodo Eggert
Greg KH <[EMAIL PROTECTED]> wrote: > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: >> I'm not trying to document /sys/devices. I'm trying to document hotplug, >> populating /dev, and things like firmware loading that fall out of that. >> This requires use of sysfs, and I'm only try

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Rob Landley
On Friday 20 July 2007 3:00:01 am Greg KH wrote: > On Fri, Jul 20, 2007 at 01:14:27AM -0400, Rob Landley wrote: > > Is there anything in /sys/class/block that _isn't_ in /sys/block? > > No. > > > Does "if you want to use it, but /sys/block will still be there" NOT > > mean, as I assumed at the time

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Rob Landley
On Friday 20 July 2007 8:52:11 pm Greg KH wrote: > On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > > > Always look at the parent devices themselves for determining device > > > context properties. > > > > For determining? > > > > What was the original language of this document? > >

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Rob Landley
On Friday 20 July 2007 4:09:36 am Greg KH wrote: > On Fri, Jul 20, 2007 at 09:54:01AM +0200, Cornelia Huck wrote: > > On Fri, 20 Jul 2007 00:00:01 -0700, > > > > Greg KH <[EMAIL PROTECTED]> wrote: > > > > I don't insist on it, mknod insists on it. You cannot mknod a dev > > > > node without specif

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Greg KH
On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > > Always look at the parent devices themselves for determining device > > context properties. > > For determining? > > What was the original language of this document? Ok, that's just being mean, cut it out right now if you ever wa

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Greg KH
On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > I'm not trying to document /sys/devices. I'm trying to document hotplug, > populating /dev, and things like firmware loading that fall out of that. > This requires use of sysfs, and I'm only trying to document as much of sysfs > as

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Greg KH
On Fri, Jul 20, 2007 at 08:21:39PM -0400, Rob Landley wrote: > Ok, back up. /sys/devices does not contain all the information necessary to > populate /dev, because it hasn't got things like > ramdisks, /dev/zero, /dev/console which are THERE in sysfs, which may or may > not be supported by the

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Rob Landley
On Wednesday 18 July 2007 7:40:20 pm Greg KH wrote: > On Wed, Jul 18, 2007 at 01:39:53PM -0400, Rob Landley wrote: > > PICK ONE! JUST #*%(&#%& PICK ONE! HHH! > > > > I don't care where it is. Just put it somewhere I can find it, and keep > > it there. All this gratuitous mov

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Rob Landley
On Thursday 19 July 2007 4:16:17 am Cornelia Huck wrote: > On Wed, 18 Jul 2007 13:39:53 -0400, > > Rob Landley <[EMAIL PROTECTED]> wrote: > > Nope. If you recurse down under /sys/class following symlinks, you go > > into an endless loop bouncing off of /sys/devices and getting pointed > > back. I

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Greg KH
On Fri, Jul 20, 2007 at 09:54:01AM +0200, Cornelia Huck wrote: > On Fri, 20 Jul 2007 00:00:01 -0700, > Greg KH <[EMAIL PROTECTED]> wrote: > > > > I don't insist on it, mknod insists on it. You cannot mknod a dev node > > > without specifying block or char. > > > > > > You're saying that sysfs s

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Cornelia Huck
On Fri, 20 Jul 2007 00:00:01 -0700, Greg KH <[EMAIL PROTECTED]> wrote: > > I don't insist on it, mknod insists on it. You cannot mknod a dev node > > without specifying block or char. > > > > You're saying that sysfs should provide major and minor numbers without > > anywhere specifying "char"

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-20 Thread Greg KH
On Fri, Jul 20, 2007 at 01:14:27AM -0400, Rob Landley wrote: > Is there anything in /sys/class/block that _isn't_ in /sys/block? No. > Does "if you want to use it, but /sys/block will still be there" NOT > mean, as I assumed at the time, that I could safely ignore it? Ignore what? /sys/block?

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-19 Thread Rob Landley
On Wednesday 18 July 2007 7:33:19 pm Kay Sievers wrote: > On 7/18/07, Rob Landley <[EMAIL PROTECTED]> wrote: > > > > /sys/block/*/dev > > > > /sys/block/*/*/dev > > > > > > Note that this will change to /sys/class/block/ in the future. > > > > At OLS, Kay Sievers said in a future version they wer

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-19 Thread Cornelia Huck
On Wed, 18 Jul 2007 13:39:53 -0400, Rob Landley <[EMAIL PROTECTED]> wrote: > Nope. If you recurse down under /sys/class following symlinks, you go into > an > endless loop bouncing off of /sys/devices and getting pointed back. If you > don't follow symlinks, it works fine up until about 2.6.2

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-18 Thread Greg KH
On Wed, Jul 18, 2007 at 01:39:53PM -0400, Rob Landley wrote: > PICK ONE! JUST #*%(&#%& PICK ONE! HHH! > > I don't care where it is. Just put it somewhere I can find it, and keep it > there. All this gratuitous moving stuff around serves NO PURPOSE other than > to break us

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-18 Thread Kay Sievers
On 7/18/07, Rob Landley <[EMAIL PROTECTED]> wrote: > > /sys/block/*/dev > > /sys/block/*/*/dev > > Note that this will change to /sys/class/block/ in the future. At OLS, Kay Sievers said in a future version they were going to move it to "/sys/subsystem/block", which I can't document right now

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-18 Thread Rob Landley
On Wednesday 18 July 2007 3:58:57 am Cornelia Huck wrote: > On Tue, 17 Jul 2007 17:03:31 -0400, > > Rob Landley <[EMAIL PROTECTED]> wrote: > > Here's some sysfs/hotplug/firmware loading documentation I wrote. I > > finally tracked down the netlink bits to finish it up, so I can send it > > out to

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-18 Thread Kay Sievers
On Tue, 2007-07-17 at 17:03 -0400, Rob Landley wrote: > Here's some sysfs/hotplug/firmware loading documentation I wrote. I finally > tracked down the netlink bits to finish it up, so I can send it out to the > world. > > What's wrong with it? :) A lot. :) > Note, I still need to actually con

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-18 Thread Cornelia Huck
On Tue, 17 Jul 2007 17:03:31 -0400, Rob Landley <[EMAIL PROTECTED]> wrote: > Here's some sysfs/hotplug/firmware loading documentation I wrote. I finally > tracked down the netlink bits to finish it up, so I can send it out to the > world. > > What's wrong with it? :) OK, some comments from me

Re: Documentation for sysfs, hotplug, and firmware loading.

2007-07-17 Thread Randy Dunlap
On Tue, 17 Jul 2007 17:03:31 -0400 Rob Landley wrote: > Here's some sysfs/hotplug/firmware loading documentation I wrote. I finally > tracked down the netlink bits to finish it up, so I can send it out to the > world. > > What's wrong with it? :) (1. It's an attachment. :) 2. Here's a C p

Documentation for sysfs, hotplug, and firmware loading.

2007-07-17 Thread Rob Landley
Here's some sysfs/hotplug/firmware loading documentation I wrote. I finally tracked down the netlink bits to finish it up, so I can send it out to the world. What's wrong with it? :) Note, I still need to actually confirm that /sbin/hotplug can be called from initramfs by a statically linked