Re: umass: should the device specific information be moved from C code to the text file?

Peter Jeremy wrote: This sounds like a nice idea - it's also a nuisance having to recompile the kernel just to support a weird new USB device you've acquired. You can probably keep USB support as a module if you need to recompile it often :) On the original topic: please don't do that. Recent

Re: umass: should the device specific information be moved from C code to the text file?

On Fri, Feb 29, 2008 at 12:44:44PM +0100, Ivan Voras wrote: Peter Jeremy wrote: This sounds like a nice idea - it's also a nuisance having to recompile the kernel just to support a weird new USB device you've acquired. You can probably keep USB support as a module if you need to

umass: should the device specific information be moved from C code to the text file?

Currently all devices supported by umass driver are listed in * sys/dev/usb/usbdevs - which has vendor table (vendor-id/name) - and product table (ref-to-vendor-id/product-id/name) and * sys/dev/usb/umass.c - which has some per-device flags. The problem with this way is that some people might

Re: umass: should the device specific information be moved from C code to the text file?

On Thu, Feb 28, 2008 at 02:14:58PM -0800, Yuri wrote: Currently all devices supported by umass driver are listed in * sys/dev/usb/usbdevs - which has vendor table (vendor-id/name) - and product table (ref-to-vendor-id/product-id/name) and * sys/dev/usb/umass.c - which has some per-device flags.