cvs commit: src/sys/dev/usb umass.c
Tue Mar 25 17:51:52 PST 2003
> In message <20030325102327.A22927@panzer.kdm.org>, "Kenneth D. Merry" writes:
> >On Tue, Mar 25, 2003 at 18:21:16 +0100, Poul-Henning Kamp wrote:
> >> In message <20030325101609.A22832@panzer.kdm.org>, "Kenneth D. Merry" writes:
> >> >> Isn't it time we started loading the quirk table with a userland utility ?
> >> >
> >> >That makes it kinda hard if you need the quirk to boot.
> >> Booting from USB devices ?
> >You could, I suppose, given the right BIOS support or if you boot from a
> >floppy/CD and run off a USB device, but I'm talking about quirks in
> I was talking about USB quirks specifically, since they seem to
> multiply like rabbits.
> I would also argue that giving camcontrol an ability to add quirks
> from userland would make things easier for the users...
There are several reasons for quirks. The ones in scsi_da.c should be
removable once we update the cam transport code. The ones in USB are all
true quirks, meaning a device has to have them to work and it is
non-compliant with appropriate specs (and usually hangs). I personally
don't think it's necessary to make them runtime loadable. You can see the
linux usb quirks section to see the magnitude of devices that require
quirks. If you'd like to help, it would be great to merge the linux
quirks into our list as well.
More information about the cvs-src