Surely, the organization of sysfs is logical (by grouping relating
things) rather than functional (by grouping things that need common
back-end interfaces).
Er .. no?
In general, where can I find guidance on where to put things within
sysfs? Has anybody written some kind of Plan?
- jm.
On 10/20/05, Dmitry Torokhov <[email protected]> wrote:
> On 10/20/05, Jonathan Mayer <[email protected]> wrote:
>
> > 2. it precludes the ability to create sys_device objects whose
> > attributes are not known at compile time (such as an sysfs
> > representation of the smbios table for some platforms -- which will be
> > my next patch submission).
> >
>
> Does this smbios table have to be a system device (does it have to be
> suspended and resumed with interrupts off) or maybe platform bus suits
> it better?
>
> --
> Dmitry
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
