From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Eddie Hung <eddie.hung@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: CF as IDE on ICH6M using libata
Date: Sat, 08 Sep 2007 16:10:20 +0900 [thread overview]
Message-ID: <46E24ADC.2000500@gmail.com> (raw)
In-Reply-To: <46E1545A.5000404@rtr.ca>
Mark Lord wrote:
> Tejun Heo wrote:
>> Eddie Hung wrote:
>>> However, I think we can conclude that ICH6M (which on the X41, has a
>>> SATA-PATA bridge to connect a PATA drive) does not seem to support
>>> MWDMA
>>
>> It isn't clear whether the fault is at the driver or the CF device.
>
> It's probably the bridge chip --> we've run through that one before
> just recently (early summer?) on this list. A particular bridge that
> doesn't work at all with MWDMA.
Hmmm... How do we solve this situation? Till now, we've been
blacklisting the device IDs but it doesn't work for broken bridges.
Maybe we should default to not using MWDMA by default?
--
tejun
next prev parent reply other threads:[~2007-09-08 17:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 12:42 CF as IDE on ICH6M using libata Eddie Hung
2007-09-02 13:08 ` Tejun Heo
2007-09-02 18:29 ` Eddie Hung
2007-09-03 2:45 ` Tejun Heo
2007-09-03 10:40 ` Eddie Hung
2007-09-03 11:46 ` Tejun Heo
2007-09-03 12:03 ` Eddie Hung
2007-09-03 12:20 ` Eddie Hung
2007-09-03 12:40 ` Tejun Heo
2007-09-03 12:51 ` Eddie Hung
2007-09-04 18:17 ` Eddie Hung
2007-09-05 17:28 ` Mark Lord
2007-09-05 22:03 ` Eddie Hung
2007-09-06 17:50 ` Tejun Heo
[not found] ` <6f9550040709061456h6f9a64ebgec9dbe457a836138@mail.gmail.com>
2007-09-07 0:44 ` Tejun Heo
2007-09-07 13:38 ` Mark Lord
2007-09-08 7:10 ` Tejun Heo [this message]
2007-09-10 12:18 ` Mark Lord
2007-09-10 18:19 ` Alan Cox
2007-09-10 19:39 ` Mark Lord
2007-09-02 14:04 ` Alan Cox
2007-09-02 18:41 ` Eddie Hung
2007-09-02 18:58 ` Alan Cox
2007-09-02 19:14 ` Eddie Hung
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=46E24ADC.2000500@gmail.com \
--to=htejun@gmail.com \
--cc=eddie.hung@gmail.com \
--cc=liml@rtr.ca \
--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 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).