From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH 0/10] powerpc: PCI updates & merges
Date: Fri, 7 Dec 2007 11:19:37 +0100 [thread overview]
Message-ID: <200712071119.37940.sr@denx.de> (raw)
In-Reply-To: <1196928690.864849.322811660859.qpush@grosgo>
On Thursday 06 December 2007, Benjamin Herrenschmidt wrote:
> This serie of patches converts the 32 bits PCI code to use the generic
> pci_assign_unassigned_resources() instead of its own assignment code
> which was unable to deal with unassigned PCI<->PCI bridges among
> other issues.
>
> It then merges the resource fixup and allocation code between 32 and
> 64 bits (mostly making 64 bits use the 32 bits code with a few fixups),
> hopefully fixing the longstanding issue that not setting pci_probe_only
> on ppc64 would generally not work.
>
> We also add flags to control the behaviour of the PCI code, such as
> letting some platforms force a full re-assignment (similar to what
> pci-auto used to provide in arch/ppc) and remove a whole bunch of
> hackish code that is made obsolete by that change.
>
> 32 bits platforms with 64 bits resources support will also need my
> separate patch to fix the generic setup-bus.c for that situation.
>
> Note that the patch that updates 4xx platforms to enable full resource
> assignments applied on top of my 4xx series for which I'll post a new
> version soon. You can apply the other ones and ignore this one if you
> want to test on some other platform without the other patch serie.
No problems on Katmai (440SPe) and Kilauea (405EX) so far. Apart from DEBUG
still enabled in patch 8/10 as Olof already pointed out.
Tested-by: Stefan Roese <sr@denx.de>
Best regards,
Stefan
prev parent reply other threads:[~2007-12-07 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 8:11 [RFC/PATCH 0/10] powerpc: PCI updates & merges Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 1/10] powerpc: pci32: remove bogus alignment message Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 2/10] powerpc: pci32: use generic pci_assign_unassign_resources Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 4/10] powerpc: pci32: Add flags modifying the PCI code behaviour Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 3/10] powerpc: pci32: Remove PowerMac P2P bridge IO hack Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 5/10] powerpc: pci32: Remove obsolete PowerMac bus number hack Benjamin Herrenschmidt
2007-12-06 17:02 ` Jon Loeliger
2007-12-06 8:11 ` [RFC/PATCH 6/10] powerpc: pci32: Add platform option to enable /proc PCI domains Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 7/10] powerpc: Merge pcibios_resource_to_bus/bus_to_resource Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 8/10] powerpc: Merge PCI resource fixups Benjamin Herrenschmidt
2007-12-06 11:51 ` Stephen Rothwell
2007-12-06 8:11 ` [RFC/PATCH 9/10] powerpc: Merge PCI resource allocation & assignment Benjamin Herrenschmidt
2007-12-06 8:11 ` [RFC/PATCH 10/10] powerpc: Clear pci_probe_only on 64 bits PowerMac Benjamin Herrenschmidt
2007-12-07 10:19 ` Stefan Roese [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=200712071119.37940.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.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).