Messages in this thread |  | | Subject | the userspace side of driverfs | From | Nicholas Miell <> | Date | 10 Sep 2002 18:18:37 -0700 |
| |
I see documentation describing the kernel interface for driverfs, but not much is available describing the userspace interface to driverfs -- i.e. the format of all those files that driverfs exports.
In order to prevent driverfs from becoming the maze of twisted files, all different that is /proc, these details need to be specified now, before it's too late.
Some issues I can think of off the top of my head:
- Can I safely assume that, for all normal files named X in driverfs, that they have the exact same format and purpose?
- The "resource" files export resource structs, however the flags member of the struct uses bits that aren't exported by the kernel and are likely to change in the future. Also, some of the flags bits are reserved for use by the bus that the resource lives on, but the bus type isn't specified by the resource file, which requires the app to parse the path name in order to figure out which bus the resource refers to.
- "name" isn't particularly consistent. Sometimes it requires parsing to be useful ("PCI device 1234:1234", "USB device 1234:1234", etc.", sometimes it's the actual device name, sometimes it's something strange like "Hub/Port Status Changes".
- Nicholas
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |