linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 6/7] MPIC MSI allocator
Date: Tue, 24 Apr 2007 11:26:26 +0200	[thread overview]
Message-ID: <f5dd623fbb338d38bc05567ee178b886@kernel.crashing.org> (raw)
In-Reply-To: <1177378169.14873.46.camel@localhost.localdomain>

>> It's time to rename BROKEN_U3. It used to be the config option to 
>> enable
>> a few workarounds, but now it's used to select whenever there's a U3 
>> in
>> the system. Care to do it in the scope of this patch set?
>
> Not really.... first gen G5s don't use that :-) It's wether the MPIC is
> part of U3/U4 -and- is used as a primary HT PIC.

Not really...  It is whether the HT-to-MPIC interface
on the U3/U4 has the "feature" that ack-required
interrupts coming in over HT need to be acked by hand.

First-gen G5's need that just as well, they just don't
have such interrupts on the default system configuration,
as far as I remember.


Segher

  reply	other threads:[~2007-04-24  9:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  7:35 [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-04-19  7:35 ` [PATCH 3/7] RTAS MSI implementation Michael Ellerman
2007-04-19  7:35 ` [PATCH 2/7] Powerpc MSI infrastructure Michael Ellerman
2007-04-21 23:15   ` Milton Miller
2007-04-23  4:28     ` Michael Ellerman
2007-04-19  7:35 ` [PATCH 4/7] Tell Phyp we support MSI Michael Ellerman
2007-04-19  7:35 ` [PATCH 5/7] Enable MSI mappings for MPIC Michael Ellerman
2007-04-21 23:16   ` Milton Miller
2007-04-22  0:06     ` Benjamin Herrenschmidt
2007-04-22  4:53       ` Milton Miller
2007-04-23  4:10         ` Michael Ellerman
2007-04-19  7:35 ` [PATCH 6/7] MPIC MSI allocator Michael Ellerman
2007-04-21 23:17   ` Milton Miller
2007-04-23  4:04     ` Michael Ellerman
2007-04-23  6:20       ` Milton Miller
2007-04-23  3:50   ` Olof Johansson
2007-04-23  3:53     ` Michael Ellerman
2007-04-24  1:29     ` Benjamin Herrenschmidt
2007-04-24  9:26       ` Segher Boessenkool [this message]
2007-04-24  9:39         ` Benjamin Herrenschmidt
2007-04-24  9:44           ` Segher Boessenkool
2007-04-24  9:51             ` Benjamin Herrenschmidt
2007-04-19  7:35 ` [PATCH 7/7] MPIC MSI backend Michael Ellerman
2007-04-20  8:40   ` Segher Boessenkool
2007-04-20 14:39     ` Michael Ellerman
2007-04-21 23:17   ` Milton Miller
2007-04-22  7:06     ` Segher Boessenkool
2007-04-22 19:30       ` Olof Johansson
2007-04-23  4:24         ` Michael Ellerman
2007-04-23  8:24         ` Segher Boessenkool
2007-04-23  8:31           ` Michael Ellerman
2007-04-23 17:33             ` Segher Boessenkool
2007-04-23  3:45     ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08  2:58 [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-05-08  2:58 ` [PATCH 6/7] MPIC MSI allocator Michael Ellerman

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=f5dd623fbb338d38bc05567ee178b886@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).