From: Mark Lord <liml@rtr.ca>
To: Mathieu GELI <mathieu.geli@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: CF to SATA bridge support
Date: Sat, 29 Aug 2009 09:48:34 -0400 [thread overview]
Message-ID: <4A9931B2.2020003@rtr.ca> (raw)
In-Reply-To: <4A80219D.7070708@rtr.ca>
Mark Lord wrote:
..
> Those errors are on WRITEs, not READs, so no surprise that "hdparm -t" works.
> This could be an IORDY issue, or just due to how the the Marvell chips
> are buggy when doing PIO of more than a single sector. That was the only
> errata we didn't do a complete workaround for, because it's so ugly. :)
>
> I have a CF-to-SATA adapter due to arrive here from DealExtreme.com in the
> next week or so. Remind me, and I'll try it out on some of the Marvell
> cards here and see what happens.
..
Okay. I don't actually have any of the system-on-chip (SoC) Marvell devices
like the one you are using there. But they say that the SATA core on
the SoC is a Gen-IIe core, same as on the 7042 PCIe chipset.
So, I've plugged my UDMA-capable CF card into the CF-to-SATA adapter
and hotplugged that into a port on the 7042.
It works fine, reading/writing in UDMA mode 5.
Things also appear to be good with a Hitachi microdrive in PIO mode 3.
The CF-to-SATA adaptor I am using is this one:
http://www.dealextreme.com/details.dx/sku.20317
Nice little device, compact, notebook compatible, and Fast!
Cheers
next prev parent reply other threads:[~2009-08-29 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 17:59 CF to SATA bridge support Mathieu GELI
2009-08-08 3:21 ` Robert Hancock
2009-08-08 18:35 ` Mathieu GELI
2009-08-09 16:23 ` Mathieu GELI
2009-08-10 13:33 ` Mark Lord
2009-08-29 13:48 ` Mark Lord [this message]
2009-08-29 14:22 ` Mark Lord
2009-08-29 15:47 ` Mark Lord
2009-08-29 15:59 ` Mark Lord
2009-08-29 16:10 ` Mark Lord
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=4A9931B2.2020003@rtr.ca \
--to=liml@rtr.ca \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mathieu.geli@gmail.com \
/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).