On Mon, 6 Jun 2005, Phil Dibowitz wrote: > > Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the > > design geniuses at Prolific we're caught in a "damned if you do, damned if > > you don't" situation. > > What about a sysfs option or sysctl?
> I'm not wrapping my mind around why - is it because by the time we've > reached a point where we can tell the kernel something about that > device, it's too late? These two questions are related, and your guess is basically correct. The kernel wants to know the capacity soon after the device is detected. That doesn't leave time for userspace to intervene. And before the device is detected there's nothing to do, because the FIX_CAPACITY flag has to be applied on a per-device basis. Imagine a system with _two_ PL-3507 devices, one with the firmware upgrade and one without... In principle one could do something based on the SCSI ID or something similar, but it wouldn't be very easy and it wouldn't be general -- every user would have to insert the necessary data by hand. On the whole we're better off not worrying about this until and unless it becomes a real problem. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
