Greg: I'm working on a patch to create class devices for USB hubs. Is this a reasonable thing to do? We already have classes for USB hosts and general USB devices.
I don't have a good understanding of how class devices are supposed to work and what they should be used for. Nor is it clear which of the class-device APIs should be used. You've been making some changes in that area; what's the current policy? Someone has asked about a way to make the hub driver ignore certain ports (leave them permanently disabled). A list of ports to ignore seems like a good candidate for a class device attribute file. Another possibly useful attribute would be a list of ports with children attached. Are these appropriate for a class device or should they go in the regular device directory? How do you decide which attributes go where? Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
