From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
alan@redhat.com, davidg@havidave.com
Subject: Re: [patch 1/1] pata_atiixp: Don't disable
Date: Tue, 06 May 2008 10:08:30 -0400 [thread overview]
Message-ID: <4820665E.2020407@garzik.org> (raw)
In-Reply-To: <200805022213.m42MDdCs017574@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>
> A couple of distributions (Fedora, Ubuntu) were having weird problems with the
> ATI IXP series PATA controllers being reported as simplex. At the heart of
> the problem is that both distros ignored the recommendations to load pata_acpi
> and ata_generic *AFTER* specific host drivers.
>
> The underlying cause however is that if you D3 and then D0 an ATI IXP it
> helpfully throws away some configuration and won't let you rewrite it.
>
> Add checks to ata_generic and pata_acpi to pin ATIIXP devices. Possibly the
> real answer here is to quirk them and pin them, but right now we can't do that
> before they've been pcim_enable()'d by a driver.
>
> I'm indebted to David Gero for this. His bug report not only reported the
> problem but identified the cause correctly and he had tested the right values
> to prove what was going on
>
> [If you backport this for 2.6.24 you will need to pull in the 2.6.25
> removal of the bogus WARN_ON() in pcim_enagle]
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> Tested-by: David Gero <davidg@havidave.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/ata/ata_generic.c | 6 ++++++
> drivers/ata/pata_acpi.c | 6 ++++++
> 2 files changed, 12 insertions(+)
applied
prev parent reply other threads:[~2008-05-06 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 22:13 [patch 1/1] pata_atiixp: Don't disable akpm
2008-05-06 14:08 ` Jeff Garzik [this message]
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=4820665E.2020407@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=davidg@havidave.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.