From: "Andrew Hall" <andrew.a.hall@gmail.com>
To: 'Alan Cox' <alan@lxorguk.ukuu.org.uk>, 'Tejun Heo' <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, 'Jeff Garzik' <jeff@garzik.org>
Subject: RE: CF flash IDE failure to attach with 2.6.20+
Date: Tue, 19 Jun 2007 09:01:24 +1000 [thread overview]
Message-ID: <46770edc.101d640a.4fdf.4eae@mx.google.com> (raw)
In-Reply-To: <20070618125742.28a0bc57@the-village.bc.nu>
> >
> > For some reason, mwdma doesn't work in libata now. I'm not sure why
> > tho. Alan, can you enlighten us?
>
> No idea at all. All my hardware is still happy. 2.6.20 is an "old"
> kernel
> however so it does predate the fixes you did for ata_piix mode setup ?
Old - yes, but more stable in all other respects it seems to the .21 series.
Are these patches available for me to try on .20 or are there dependencies
on 21?
next prev parent reply other threads:[~2007-06-18 23:01 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 [this message]
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
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=46770edc.101d640a.4fdf.4eae@mx.google.com \
--to=andrew.a.hall@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).