From: Jeff Garzik <jeff@garzik.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PATA failure with piix, works with libata
Date: Sun, 05 Mar 2006 19:58:09 -0500 [thread overview]
Message-ID: <440B8921.9030602@garzik.org> (raw)
In-Reply-To: <20060306003221.GA8805@srcf.ucam.org>
Matthew Garrett wrote:
> On Sun, Mar 05, 2006 at 06:40:58PM -0500, Jeff Garzik wrote:
>
>>Matthew Garrett wrote:
>>
>>>Ok, it /seems/ that things are happier (though still not entirely happy)
>>>if I explicitly acknowledge the interrupt by writing the dma status
>>>register back again. This doesn't seem to be done anywhere in the IDE
>>>interrupt routine, but is in the libata one. I'm afraid I don't
>>>understand IDE well enough to have any idea what's going on here - is it
>>>possible that a piix in native mode (rather than legacy mode) and
>>>sharing an interrupt needs some special handling?
>>
>>ICH definitely needs that irq ack...
>
>
> Yeah, this is an ICH7. I can't find anything in drivers/ide that would
> result in it being done, which is why I'm kind of confused. ide_ack_intr
> seems to be defined to do nothing on x86 since IDE_ARCH_ACK_INTR isn't
> defined there?
This is more a piix-specific behavior than an arch-specific behavior.
Jeff
next prev parent reply other threads:[~2006-03-06 0:58 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
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 [this message]
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=440B8921.9030602@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).