Re: HEADSUP: USB da(4) quirks deprecated
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 should be enhanced rather than have a quirk > entry added. I'm committed to doing that for devices which respond in a reasonable way (whether error or success). > Just to reitterate, the quirks are there for situations that cannot > be handled in a more programatic way (e.g. a device that dies when > you send it a certain command). Please don't blindly re-enable quirks > to silence junk that winds up in syslog. I won't be re-enabling quirks except for devices which hang. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: USB da(4) quirks deprecated
> 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. Just to reitterate, the quirks are there for situations that cannot be handled in a more programatic way (e.g. a device that dies when you send it a certain command). Please don't blindly re-enable quirks to silence junk that winds up in syslog. -- Justin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: USB da(4) quirks deprecated
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 2003, Nate Lawson wrote: > 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 code with the quirks disabled. You may have a device (USB > camera, pen drive, hard drive, ...) that begins to get errors like "BBB > bulk-in clear stall failed" or "Synchronize cache failed, status 0x35". > If you get these, you can enable previous behavior by adding: > > options DA_OLD_QUIRKS > > to your kernel config and recompiling. Once you do this, please send me > the output of "camcontrol inquiry da0" so I can re-enable your quirk for > good. I'm doing this as soon as possible so the unnecessary quirks can be > removed for 5.2. A similar process will take place in 4-stable after 5.2 > has been released. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADSUP: USB da(4) quirks deprecated
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 code with the quirks disabled. You may have a device (USB camera, pen drive, hard drive, ...) that begins to get errors like "BBB bulk-in clear stall failed" or "Synchronize cache failed, status 0x35". If you get these, you can enable previous behavior by adding: options DA_OLD_QUIRKS to your kernel config and recompiling. Once you do this, please send me the output of "camcontrol inquiry da0" so I can re-enable your quirk for good. I'm doing this as soon as possible so the unnecessary quirks can be removed for 5.2. A similar process will take place in 4-stable after 5.2 has been released. Thanks for your patience, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
