On Fri, Jul 17, 2009 at 10:49:15PM -0600, Robert Hancock wrote: > Surely there's a better format for exporting this information to > userspace than making it parse out the bits from the raw register > contents.. how about separate sysfs files for ESP, HPCP, etc? Or > something more abstracted at a higher level that other drivers (if they > have access to similar information) could use? I could split out more of the information, but there's a balance between exposing enough that we won't need to add more values in the near future and ending up with one sysfs file for pretty much every capabilities bit. I'm not aware of any cases where we can currently generalise this to other controllers, but I'm happy to be proven wrong on that. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
