From: Todd Inglett <tinglett@vnet.ibm.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE dma reset for sl82c105
Date: Tue, 18 Dec 2001 08:00:46 -0600 [thread overview]
Message-ID: <3C1F4C0E.7030704@vnet.ibm.com> (raw)
In-Reply-To: <3C1EB87C.7090103@chartermi.net> <20011218101630.C12774@flint.arm.linux.org.uk>
Russell King wrote:
> Could you also get an lspci -v dump of the ISA bridge and the IDE function
> please?
Bus 0, device 11, function 0:
ISA bridge: Symphony Labs W83C553 (rev 16).
Bus 0, device 11, function 1:
IDE interface: Symphony Labs SL82c105 (rev 5).
IRQ 31.
Master Capable. Latency=72. Min Gnt=2.Max Lat=40.
I/O at 0xe000000001100800 [0xe000000001100807].
I/O at 0xe000000001100000 [0xe000000001100003].
I/O at 0xe000000001100c00 [0xe000000001100c07].
I/O at 0xe000000001100400 [0xe000000001100403].
I/O at 0xe000000001101000 [0xe00000000110100f].
I/O at 0xe000000001101400 [0xe00000000110140f].
> Does the Engineering notice give PCI INTC as a pre-condition?
Yes. When bit 11 (LEGIRQ) of the IDE control/status register is set IDE
IRQs are sent to INTC and/or INTD. This is a pre-condition. The
problem is that the controller gets confused on an unfinished DMA and
erroneously waits for ack on IRQA/B.
>>The patch should apply to 2.5.13 - 2.5.16 (at least).
>>
>
> I think you mean 2.4.13 - 2.4.16 8)
No kidding. A Monday I guess :(.
-todd
prev parent reply other threads:[~2001-12-18 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 3:31 [PATCH] IDE dma reset for sl82c105 Todd Inglett
2001-12-18 10:16 ` Russell King
2001-12-18 14:00 ` Todd Inglett [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=3C1F4C0E.7030704@vnet.ibm.com \
--to=tinglett@vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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