From: thomas schorpp <t.schorpp@gmx.de>
To: linux-scsi@vger.kernel.org
Subject: Re: [SCSI] Add support for braindead Cypress USB ATA passthrough CDBs
Date: Thu, 22 Dec 2005 10:24:04 +0100 [thread overview]
Message-ID: <43AA70B4.2050509@gmx.de> (raw)
In-Reply-To: <20051221122442.GA16571@porkrind.org>
David Caldwell wrote:
> This patch does 2 things. It reimplements the SG_FLAG_LUN_INHIBIT flag
> in the SG_IO ioctl which stops the scsi subsystem from overwriting the
> 2nd byte of the CDB with the LUN. It also doesn't guess the CDB length
> when sending the SG_IO ioctl to the sg device (the main scsi_ioctl
> already did this).
>
> This is for the Cypress CY7C68310 USB to ATA bridge chip (and most
> likely other USB to ATA chips from Cypress), which implements an ATA
> passthrough command that is 16 bytes long and starts with the bytes
> 0x24 0x24. (Not vendor unique, weird length for opcode 0x24, and
> misuse of the LUN area all at the same time--Lovely).
thx, hm, that chip is that old that datasheet is available no more...
i test it as soon as i get my 68300A changed with the new -B- type back from lab.
anyway, i see the first ATACB enabled (guaranteed) announced chip should be
the 683xxB types. maybe they have the correct behaviour (16Bytes, opccode length
problem), so maybe the last part of above functionality could interfere.
interesting is the lately errata sheet for -B-:
-some atacb functionality not availlable if in udma mode
-high order bits of error sector not returned at atacb
next prev parent reply other threads:[~2005-12-22 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 12:24 [SCSI] Add support for braindead Cypress USB ATA passthrough CDBs David Caldwell
2005-12-22 9:24 ` thomas schorpp [this message]
2005-12-22 20:22 ` David Caldwell
2005-12-23 15:52 ` James Bottomley
2005-12-23 17:41 ` Jeff Garzik
2005-12-23 17:59 ` James Bottomley
2005-12-23 19:12 ` David Caldwell
2005-12-23 20:34 ` James Bottomley
2005-12-23 21:13 ` David Caldwell
2005-12-24 3:28 ` Douglas Gilbert
2005-12-24 7:11 ` David Caldwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43AA70B4.2050509@gmx.de \
--to=t.schorpp@gmx.de \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox