Messages in this thread |  | | Date | Fri, 22 Jun 2001 06:49:11 -0400 (EDT) | From | Kipp Cannon <> | Subject | Q: /proc/driver file philosophy |
| |
Hi,
I'm maintaining a device driver that has recently had the ability to control multiple units added to it. At present, applications can get info on the driver's and hardware's status through a file in /proc/driver. What I would like to know is what the prefered way to handle multiple devices is: multiple files in /proc/driver or one file with multiple sections in it?
As the developer of the driver's associated user space utilities I think my preference is for multiple files because that keeps those apps as simple as possible. As the developer of the driver, however, having a single /proc file and a loop is the simplest solution. So is there an (un)official position on this sort of thing or should I flip a coin?
-Kipp
- 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/
|  |