From: Craig Metz <cmetz@inner.net>
To: Mark Lord <liml@rtr.ca>
Cc: Tejun Heo <htejun@gmail.com>,
sjackerman@comcast.net, linux-ide@vger.kernel.org,
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 10:27:06 -0400 [thread overview]
Message-ID: <20070501142706.31A38582C@rmail.inner.net> (raw)
In-Reply-To: <4637379F.7070805@rtr.ca>
In message <4637379F.7070805@rtr.ca>, you write:
>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).
The CF card I'm using is a modern SanDisk, which supports up to MDMA2. I'd
like to be able to use their new Extreme IV, which supports up to UDMA6. The
flash parts themselves are now getting fast enough that DMA really makes a
difference vs. PIO.
The same card in a CF<->PATA adapter chained to a PATA<->SATA adapter based
on a different bridge chip works fine. So I don't think it's the card, or the
CF technology inherently. My personal estimation is that the ACard bridge
chip is buggy and in need of a work-around.
What do I need to run in order to extract the full IDENTIFY data for you?
Keep in mind that I can't get a kernel booted that will fully see this device.
(i.e., no SCSI disk is ever allocated)
Thanks,
-Craig
next prev parent reply other threads:[~2007-05-01 14:15 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
2007-05-01 14:27 ` Craig Metz [this message]
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=20070501142706.31A38582C@rmail.inner.net \
--to=cmetz@inner.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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).