From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Olof Johannsson <olof@lixom.net>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Rename MPIC_BROKEN_U3 to MPIC_U3_HT_IRQS
Date: Mon, 23 Apr 2007 19:39:23 +0200 [thread overview]
Message-ID: <64f77a2f874650aae9980e37eea66b9c@kernel.crashing.org> (raw)
In-Reply-To: <20070423084710.10570DDF14@ozlabs.org>
> Rename MPIC_BROKEN_U3 to something a little more descriptive. Its
> effect is to enable support for HT irqs behind the PCI-X/HT bridge on
> U3/U4 (aka. CPC9x5) parts.
Not quite. It's a workaround for the problem that
the U3/U4 HT interrupt interface doesn't send ACKs
for interrupts that require them ("level" interrupts).
It does this by setting the ACK bit in HT APIC config
space every time an interrupt from such a source happens.
This doesn't affect PCI bridges only.
The name change looks good though :-)
Segher
prev parent reply other threads:[~2007-04-23 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 8:47 [PATCH] Rename MPIC_BROKEN_U3 to MPIC_U3_HT_IRQS Michael Ellerman
2007-04-23 17:39 ` Segher Boessenkool [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=64f77a2f874650aae9980e37eea66b9c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=olof@lixom.net \
--cc=paulus@samba.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).