From: Mark Lord <liml@rtr.ca>
To: Andrew Hall <andrew.a.hall@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: CF flash PATA on libata failure to attach
Date: Thu, 28 Jun 2007 22:26:12 -0400 [thread overview]
Message-ID: <46846DC4.4070800@rtr.ca> (raw)
In-Reply-To: <46846230.6080908@gmail.com>
Tejun Heo wrote:
> Hello,
>
> Mark Lord wrote:
>> Here's a slightly modified hack, which should leave your SATA
>> drive working as well as the CF card.
>>
>> Tejun / Alan : do we really want to continue attempting mdma2
>> on a modern chipset such as ICH8 ???
>
> One thing that worries me is that we have reports where the IDE piix can
> do mwdma but ata_piix can't. I wonder whether Andrew is hitting the
> same problem.
I think Andrew said he had tried the old IDE driver,
but perhaps it didn't match his PCI IDs ?
Andrew?
next prev parent reply other threads:[~2007-06-29 2:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 10:02 CF flash IDE failure to attach with 2.6.20+ Andrew_hall
2007-06-18 11:26 ` Tejun Heo
2007-06-18 11:57 ` Alan Cox
2007-06-18 23:01 ` Andrew Hall
2007-06-19 5:00 ` Tejun Heo
2007-06-21 1:05 ` Andrew Hall
2007-06-21 3:02 ` Tejun Heo
2007-06-21 7:19 ` Andrew Hall
2007-06-21 14:45 ` Mark Lord
2007-06-21 15:09 ` Andrew Hall
2007-06-26 8:51 ` CF flash PATA on libata failure to attach Andrew Hall
2007-06-26 18:50 ` Mark Lord
2007-06-27 3:57 ` Andrew Hall
2007-06-27 14:08 ` Mark Lord
2007-06-27 23:49 ` Andrew Hall
2007-06-28 17:37 ` Mark Lord
2007-06-29 0:35 ` Andrew Hall
2007-06-29 1:10 ` Mark Lord
2007-06-29 1:36 ` Tejun Heo
2007-06-29 2:26 ` Mark Lord [this message]
2007-06-29 2:15 ` Andrew Hall
2007-06-29 2:28 ` Mark Lord
2007-06-29 3:24 ` Andrew Hall
2007-06-29 7:34 ` Andrew Hall
2007-06-29 10:17 ` Alan Cox
2007-07-02 10:58 ` Tejun Heo
2007-07-03 6:13 ` Albert Lee
2007-06-29 10:06 ` Alan Cox
2007-06-25 9:05 ` CF flash IDE failure to attach with 2.6.20+ Andrew Hall
2007-06-18 23:23 ` Andrew Hall
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=46846DC4.4070800@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@redhat.com \
--cc=andrew.a.hall@gmail.com \
--cc=htejun@gmail.com \
--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.