All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Lee <albertcc@tw.ibm.com>
To: Carlos Pardo <Carlos.Pardo@siliconimage.com>
Cc: Tejun Heo <htejun@gmail.com>,
	Jonathan Blake Benson <airbatica@verizon.net>,
	linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: libata machine check on Alpha
Date: Thu, 06 Apr 2006 10:04:03 +0800	[thread overview]
Message-ID: <44347713.9000408@tw.ibm.com> (raw)
In-Reply-To: <2E9B8131C44AF746B1E06BF9B15A434B045D8198@mail.siliconimage.com>

Carlos Pardo wrote:
> The 3611 bridge does not support the ATAPI DMA direction bit in hardware.(software support only)  
> 
> The 3811 bridge supports ATAPI DMA direction bit in both software and hardware.
> 
> The 646 chip is ancient and he should upgrade.  The behavior of this device is unknown since this part was EOL'd years ago.
> 
> 

Hi Carlos,

Does this mean that only the 3611 bridge needs the DMA_DIR bit set by host software, while 3811
can detect the ATAPI DMA direction by hardware and doesn't need the DMA_DIR bit?
(I guess that 3811 detects the direction by looking into the SCSI CDB. If the SCSI command is
unknown to it, 3811 still needs the DMA_DIR bit set by software.)
Is there anyway that we could detect whether the DMA_DIR needs to be set by host software?
Is there anyway that we could detect whether the bridge is a 3611 or a 3811 chip automatically?

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?

Thanks,

Albert


  reply	other threads:[~2006-04-06  2:04 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 [this message]
2006-04-06  2:17   ` Jeff Garzik
2006-04-06  2:31     ` Tejun Heo
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=44347713.9000408@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.