From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: sjackerman@comcast.net, linux-ide@vger.kernel.org,
cmetz@inner.net, Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
albertcc@tw.ibm.com
Subject: Re: Problems with Linux SATA driver and ARC-770 IDE Bridge chip
Date: Tue, 01 May 2007 08:50:39 -0400 [thread overview]
Message-ID: <4637379F.7070805@rtr.ca> (raw)
In-Reply-To: <4636D7CE.9070702@gmail.com>
Tejun Heo wrote:
> [cc'ing ATA gurus]
> Hello, again.
>
> Okay, there are two different problems here, so I was confused a bit,
> but now I see what's going on.
>
> sjackerman@comcast.net wrote:
>> ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10
>> scsi2 : ata_piix
>> ata1.00: CFA, max PIO4, 8005536 sectors: LBA
>> ata1.00: ata1: dev 0 multi count 0
>> ata1.00: qc timeout (cmd 0xef)
>> ata1.00: failed to set xfermode (err_mask=0x4)
..
> Jeff, Alan, Mark and Albert, do you have ideas how we should support
> this one? This thing locks up if nIEN is set in command FIS.
It would be useful to see the full tf on those errors.
My experience with PATA drives and CF cards, it that they
default to PIO4 (assuming they report supporting PIO4).
So we don't actually need to do a set xfer mode on them.
Is the full IDENTIFY data available (hex, please)?
Perhaps we can recognize this beast and just handle it
differently when detected.
Is it the CF card, or the CF adaptor, that's the problem?
Many questions, not many answers (yet).
next prev parent reply other threads:[~2007-05-01 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 19:03 Problems with Linux SATA driver and ARC-770 IDE Bridge chip sjackerman
2007-04-25 4:01 ` Tejun Heo
2007-04-25 15:29 ` sjackerman
2007-05-01 6:01 ` Tejun Heo
2007-05-01 10:21 ` Alan Cox
2007-05-01 12:50 ` Mark Lord [this message]
2007-05-01 14:27 ` Craig Metz
2007-05-01 17:43 ` Mark Lord
2007-05-01 18:05 ` Craig Metz
2007-05-04 16:30 ` Steven J. Ackerman
[not found] <010501c78736$aad2e480$0703a8c0@SJAWINXP>
2007-04-26 2:35 ` Craig Metz
2007-04-29 16:43 ` Tejun Heo
2007-04-30 14:44 ` Craig Metz
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=4637379F.7070805@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=cmetz@inner.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sjackerman@comcast.net \
/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).