From: Jeff Garzik <jeff@garzik.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Miller <davem@davemloft.net>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
marvin@mydatex.cz
Subject: Re: IRQ enable/disable BUG in IDE w/shared IRQs
Date: Fri, 14 Jan 2011 13:44:17 -0500 [thread overview]
Message-ID: <4D309981.5030107@garzik.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1101141031320.2678@localhost6.localdomain6>
On 01/14/2011 05:30 AM, Thomas Gleixner wrote:
> On Thu, 13 Jan 2011, David Miller wrote:
>> I have a hard time believing we've gotten away with this for so long.
>> Maybe it really is that rare to share the IDE interrupts with other
>> stuff?
>
> IIRC, the legacy IDE interrupts were 14/15 and those were never shared.
Yes, non-shared 14/15 were the 95% common case for the longest time.
Sharing IDE interrupts within old-IDE worked FSVO "working", but the
interrupt probes were written for a non-shared interrupt, then hacking
into working for shared interrupts when PCI first starting showing up on
the scene.
Jeff
prev parent reply other threads:[~2011-01-14 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 7:32 IRQ enable/disable BUG in IDE w/shared IRQs David Miller
2011-01-14 10:30 ` Thomas Gleixner
2011-01-14 18:44 ` 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=4D309981.5030107@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin@mydatex.cz \
--cc=tglx@linutronix.de \
/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