Hi Matt,
Two comments come to mind:
(1) Is it correct that changing this would involve no more than:
* Linux 2.4.? kernel updates:
- drivers/usb/usb.c ... usb_match_id()
- drivers/usb/ibmcam.c ... uses range matching
- drivers/usb/storage/unusual_devs.h ... lots of ranges
* Hotplug scripts
* "usbmodules"
* No spec/documentation (yet)
Distributions would need to get all those updates at once;
I don't know how much of a problem that'd be, except
that if there's no coordination then it'll be painful. If it
happens, this should all be ready at the same time. (Not
like the original match_flags patch ... though goofing this
up would break less, since "modutils" will still work.)
(2) For some reason my preference in this area would
be to use "low <= value < high" range specs rather the
current "low < value < high" or "low <= value <= high".
That's just a better match to how I normally think about
such ranges -- not a huge deal, but it seems like Jeff
Ozvold had a similar thought. So maybe I'm not alone
in thinking about those bcd version codes that way.
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
