linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: albertl@mail.com, Carlos Pardo <Carlos.Pardo@siliconimage.com>,
	Jonathan Blake Benson <airbatica@verizon.net>,
	linux-ide@vger.kernel.org
Subject: Re: libata machine check on Alpha
Date: Thu, 06 Apr 2006 11:31:58 +0900	[thread overview]
Message-ID: <44347D9E.8080107@gmail.com> (raw)
In-Reply-To: <44347A3D.1000609@garzik.org>

Jeff Garzik wrote:
> Albert Lee wrote:
>> Per Jeff's comment, there is a document on t13 
>> (http://www.t13.org/docs2003/e03131r0.pdf).
>> The documents reads:
>> "Eg. – Word 50, bit 13: Set to 1 for devices that support DMAIN bit in 
>> Features Register for Packet Command".
>> However, this looks more for the ATAPI device than for the bridge?
>> Also it looks not a t13 standard yet?
>> Can we use this word 50 to identify 3611/3811?
> 
> 
> DMADIR is in my copy of ATA-7...
> 

Here's the relavant part from ATA8 draft.  It seems that the bridge is 
supposed to mangle the IDENTIFY PACKET DEVICE result.  It's supposed to 
nuke all DMA transfer mode information reported from the original device 
and report supported modes from the view point of the bridge in bits 
10:1 (which, BTW, should be all 1's).

The question is whether or not bridges implement this properly. I think 
we can add a printk to word 62 and ask Jonathan to test it.

----

7.18.6.17 Word 62: DMADIR

ATAPI devices that use a serial ATA bridge chip for connection to a 
serial ATA host may require use of the DMADIR bit to indicate transfer 
direction for Packet DMA commands. Word 62 is used to indicate if such
support is required.

If bit 15 of word 62 is set to one, then DMADIR bit in the Packet 
Command is required by the device for Packet DMA and Bits 2:0 of word 
63, bits 15 and 8 in word 49, and bits 6:0 of word 88 shall be cleared 
to 0,.

If bit 15 of word 62 is cleared to 0, DMADIR bit in the PACKET command 
is not required. If bit 15 of word 62 is cleared to zero, then all bits 
of word 62 shall be cleared to zero.

Bits (14:11) are reserved.

Bits (10:1) indicate DMA mode support. Since the DMADIR bit is only used 
for a Serial ATAPI device, all of these bits are set to 1.

-- 
tejun

  reply	other threads:[~2006-04-06  2:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 17:12 libata machine check on Alpha Carlos Pardo
2006-04-06  2:04 ` Albert Lee
2006-04-06  2:17   ` Jeff Garzik
2006-04-06  2:31     ` Tejun Heo [this message]
2006-04-06  6:38       ` Albert Lee
2006-04-06  6:44         ` Doug Maxey
2006-04-06  7:14           ` Albert Lee
  -- strict thread matches above, loose matches on Subject: below --
2006-04-07  2:01 Jonathan Benson
2006-04-07  6:18 ` Albert Lee
2006-04-05  0:14 Jonathan Benson
2006-04-03 18:56 Jonathan Blake Benson
2006-04-04  1:43 ` Tejun Heo
2006-04-04  2:12   ` Albert Lee
2006-04-04  2:15     ` Tejun Heo
2006-04-04  2:49       ` Albert Lee
2006-04-04  3:05         ` Tejun Heo
2006-04-04  8:24         ` Jeff Garzik
2006-04-05 15:48     ` Jonathan Blake Benson
2006-04-06  9:17       ` Albert Lee

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=44347D9E.8080107@gmail.com \
    --to=htejun@gmail.com \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=airbatica@verizon.net \
    --cc=albertl@mail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).