All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Lee <albertcc@tw.ibm.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	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 14:38:39 +0800	[thread overview]
Message-ID: <4434B76F.7020206@tw.ibm.com> (raw)
In-Reply-To: <44347D9E.8080107@gmail.com>

Tejun Heo wrote:
> 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.
> 

Ah, thanks for the info. The DMADIR is in my copy ATA-7, too.
I just checked word 50 and overlooked it. :(
I should have checked other part of the spec...

Anyway, will try to make a patch based on the ATA-7 spec.
--
Albert


  reply	other threads:[~2006-04-06  6:39 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
2006-04-06  6:38       ` Albert Lee [this message]
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=4434B76F.7020206@tw.ibm.com \
    --to=albertcc@tw.ibm.com \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=airbatica@verizon.net \
    --cc=albertl@mail.com \
    --cc=htejun@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.