"Kenneth D. Merry" wrote:
> The right way to handle the 6/10 byte stuff is to have it be a function of
> the transport type (see the CAM_NEW_TRAN_CODE stuff).  The peripheral
> drivers and userland applications can query the transport type and send
> 6 or 10 byte commands as appropriate.
> If we're going to come up with a generic solution, that's probably the
> direction we need to be heading.

I think everyone in this thread needs to read the last instance
of this same thread, the first time it came up.

I believe the general consensus was to send the 6, and if it
failed, retry with the 10, and set a flag so that subsequent
requests were 10 (this instead of a static quirk table that
could find itself out of date).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to