[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080805163229.GA14870@sgi.com>
Date: Tue, 5 Aug 2008 11:32:30 -0500
From: Russ Anderson <rja@....com>
To: Greg KH <greg@...ah.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, mingo@...e.hu,
tglx@...utronix.de, linux-kernel@...r.kernel.org,
Jack Steiner <steiner@....com>
Subject: Re: x86 BIOS interface for partitioning and system serial number on SGI UV
On Mon, Aug 04, 2008 at 08:54:50PM -0700, Greg KH wrote:
> On Mon, Aug 04, 2008 at 05:59:42PM -0700, H. Peter Anvin wrote:
> > Russ Anderson wrote:
> >>> This really seems more that it should belong in sysfs --
> >>> /sys/class/firmware presumably.
> >> /proc/sgi_uv already exists, similar to /proc/sgi_sn on Itanium systems.
> >> Would it be /sys/class/firmware? Reading Documentation/sysfs-rules.txt
> >> seems to indicate somewhere under /sys/devices, such as
> >> /sys/devices/system/,
> >> but I may be wrong.
> >
> > /sys/class/firmware is usually where firmware-related things end up, but
> > gregkh is the authority on sysfs organization.
>
> /sys/class/firmware has a few users, but perhaps you are thinking of
> /sys/firmware instead? That's probably the better place for something
> that is not using the firmware class itself.
Hi Greg,
If /sys/firmware is the right place, that is where I will put it.
Are the rules for /sys/firmware documented? Documentation/sysfs-rules.txt
does not mention /sys/firmware. It seems to indicate that /sys/class
should only contain symlinks:
There are currently three places for classification of devices:
/sys/block, /sys/class and /sys/bus. It is planned that these will
not contain any device directories themselves, but only flat lists of
symlinks pointing to the unified /sys/devices tree.
Thanks,
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@....com
--
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