Messages in this thread | | | Date | Mon, 13 Feb 2006 13:03:38 -0500 | From | Dmitry Torokhov <> | Subject | Re: CD writing in future Linux (stirring up a hornets' nest) |
| |
On 2/13/06, Greg KH <greg@kroah.com> wrote: > On Mon, Feb 13, 2006 at 03:05:49AM -0500, Daniel Barkalow wrote: > > On Sun, 12 Feb 2006, Greg KH wrote: > > > > > On Mon, Feb 13, 2006 at 12:01:48AM -0500, Daniel Barkalow wrote: > > > > sysfs doesn't do quite that level of categorization; if it did, cdrom_id > > > > would be unnecessary. > > > > > > What? cdrom_id queries the device directly to get some specific > > > information about the device, much like any other type of device query > > > (lspci, lsusb, etc.) > > > > > > And yes, it would be nice if some of that information was also exported > > > through sysfs, and as always, patches are gladly accpeted. > > > > Are there guidelines on having a generic cdrom export information from its > > block interface, rather than through its bus? I'm not finding any > > documentation of sys/block/, aside from that it exists. > > That information should go into the device directory, not the sys/block > directory (as it referrs to the device attributes, not the block gendev > attributes.) >
Not necessarily - it would be easier for userspace programs if we had a separate class in sysfs - /sys/class/cdrom. The problem with this approach is that we do not allow a device belong o several classes without introducing intermediate class devices (I mean a DVD+RW shoudl probably belong to classes cdrom, dvdrom, cdwriter and dvdwriter).
-- Dmitry - 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/
| |