On Sun, 30 Jan 2005, Matthew Dharm wrote: > *sigh* We really should be trying to push as much of this as possible onto > hotplug. It's easier to update userspace tools than the kernel to support > a new device.
I sort of agree, and floated a rather vague proposal for such a mechanism: http://marc.theaimsgroup.com/?l=linux-usb-devel&m=109025804910253&w=2 Oliver Neukum argued quite strongly that a userspace blacklist like this would be inappropriate and that the information should remain strictly in the kernel. There's also the problem of handling situations where hotplug support is not yet available (e.g., during initrd) or not present at all. We would still want USB mass storage access to function correctly. I don't know any way to solve this, except perhaps to default to the most general (lowest-performance) settings and rely on hotplug to optimize things. And even that won't work for FIX_CAPACITY. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
