On Mon, 6 Jun 2005, Alex Butcher 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. > > Is it possible to do something in user space, based on a unique device > identifier? (i.e. so if a user/admin has one old device and one new > connected, they can FIX_CAPACITY on the old without doing so on the new)
It's not quite so simple. The FIX_CAPACITY behavior cannot be controlled from userspace. On the other hand, if the FIX_CAPACITY flag is removed and the user is careful not to do anything that tries to access the "last sector" of the drive, everything will work okay. Sometimes that takes a little effort though; some Linux distributions include EFI GUID partition-type support, and that driver stores its configuration information in the last sector. Furthermore it gets invoked _before_ the standard DOS-style partition code, so if the EFI GUID module is configured in the kernel then it is _guaranteed_ to cause the disk to fail. On the bright side, once users reconfigure their kernels to remove that driver, things usually start working. 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
