From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PATA failure with piix, works with libata
Date: Mon, 6 Mar 2006 15:12:52 +0000 [thread overview]
Message-ID: <20060306151251.GA11678@srcf.ucam.org> (raw)
In-Reply-To: <1141481507.10341.1.camel@localhost>
On Sat, Mar 04, 2006 at 02:11:46PM +0000, Alan Cox wrote:
> Make sure the IRQ is setup properly. Legacy mode IRQs are level
> triggered which might fit this description.
It's a shared PCI interrupt, so yeah, it's level. As I mentioned to
Jeff, explicitly writing back the DMA status register while
acknowledging interrupts works (and is what ata_piix does in PATA mode)
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-03-06 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 18:39 PATA failure with piix, works with libata Matthew Garrett
2006-03-04 14:11 ` Alan Cox
2006-03-06 15:12 ` Matthew Garrett [this message]
2006-03-05 22:57 ` Matthew Garrett
2006-03-05 23:40 ` Jeff Garzik
2006-03-06 0:32 ` Matthew Garrett
2006-03-06 0:58 ` Jeff Garzik
2006-03-06 1:03 ` Matthew Garrett
2006-03-06 1:07 ` Jeff Garzik
2006-03-06 13:15 ` Matthew Garrett
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=20060306151251.GA11678@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).