From: Tejun Heo <htejun@gmail.com>
To: sam song <sam_song@usish.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru
Date: Fri, 30 Nov 2007 10:18:45 +0900 [thread overview]
Message-ID: <474F64F5.9070205@gmail.com> (raw)
In-Reply-To: <004d01c83273$68ded140$6539a8c0@usish.com.cn>
sam song wrote:
> Hi,
>
> I am convinced that the SATA Disk does support one vendor specific ATA
> command and got the whole bus trace via Trainer.
> However, I cannot implement that in the real cases with either HBA or SATA
> Controller like ICH5/7 via ATA Pass Thru.
> So I wonder whether there is one possible setup including HW and SW
> supporting the ATA command via ATA Pass directly and no need to understand
> the command meaning itself.
>
> Here is one result I got.
>
> [<unknown opcode>: 85 0b 06 00 01 00 00 00 00 00 00 00 00 e0 fd 00 ]
> scsi_status=0x2, host_status=0x0, driver_status=0x8
> info=0x1 duration=270111 milliseconds
> status=0x2: sense_key=0x7 asc=0x1 ascq=0x0
That sense key is data protect. I don't think any code in ATA
passthrough code path can raise that sense key. What did you exactly
do? Can you post the source code?
--
tejun
next prev parent reply other threads:[~2007-11-30 1:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 10:34 Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru sam song
2007-11-30 1:18 ` Tejun Heo [this message]
2007-11-30 3:33 ` sam song
2007-11-30 6:12 ` Tejun Heo
2007-11-30 6:29 ` sam song
2007-11-30 6:33 ` Tejun Heo
2007-11-30 6:42 ` sam song
2007-11-30 6:47 ` Tejun Heo
2007-11-30 7:01 ` sam song
2007-11-30 8:22 ` Tejun Heo
2007-12-03 10:20 ` sam song
2007-12-04 0:46 ` Tejun Heo
2007-12-04 1:32 ` sam song
2007-12-04 2:21 ` Tejun Heo
2007-12-05 1:43 ` Tejun Heo
2007-12-05 2:39 ` sam song
2007-12-05 3:16 ` Tejun Heo
2008-03-11 3:17 ` sam song
2008-03-11 3:21 ` Tejun Heo
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=474F64F5.9070205@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sam_song@usish.com \
/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;
as well as URLs for NNTP newsgroup(s).