Re: HEADSUP: USB da(4) quirks deprecated

2003-07-29 Thread Nate Lawson
On Tue, 29 Jul 2003, Justin T. Gibbs wrote: > > You may have a device (USB camera, pen drive, hard drive, ...) that begins > > to get errors like ... "Synchronize cache failed, status 0x35". > > If the Sync cache fails with a "reasonable error code", then the code > that silence these errors shoul

Re: HEADSUP: USB da(4) quirks deprecated

2003-07-29 Thread Justin T. Gibbs
> You may have a device (USB camera, pen drive, hard drive, ...) that begins > to get errors like ... "Synchronize cache failed, status 0x35". If the Sync cache fails with a "reasonable error code", then the code that silence these errors should be enhanced rather than have a quirk entry added.

Re: HEADSUP: USB da(4) quirks deprecated

2003-07-28 Thread Andre Guibert de Bruet
Hi, "camcontrol inquiry" requires the pass driver, so if it's not already in your kernel config you might want to add it when/if you add DA_OLD_QUIRKS. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Mon, 28 Jul

HEADSUP: USB da(4) quirks deprecated

2003-07-28 Thread Nate Lawson
I have committed code to disable the USB and Firewire quirks in da(4). Since we now have code that should handle the common case of a failure after receiving 6 byte commands, most of them should no longer be necessary. However, the only way to tell if a quirk is really needed is to test the new co