From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Michal Simek <monstr@monstr.eu>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RFC] Architecture independent pcibios?
Date: Wed, 09 Oct 2013 07:31:18 +1100 [thread overview]
Message-ID: <1381264278.645.232.camel@pasglop> (raw)
In-Reply-To: <20131008171343.GB25606@e102652-lin.cambridge.arm.com>
On Tue, 2013-10-08 at 18:13 +0100, Liviu Dudau wrote:
> There are at least a handful of architectures that seem to share the same
> implementation for most (all?) of the pcibios_*() functions. (PowerPC and
> microblaze the most obvious offenders, x86 to a certain extent).
That's because microblaze started by copying the powerpc code :-) The
other part about x86 is mostly me over the year changing the powerpc
code to make it closer to x86 especially in the area of resource
management. This leads to less overall surprises and issues when the
generic code changes and in a few cases has made it easier to move bits
to the core.
The main remaining difference is our use of IORESOURCE_UNSET and our
flags to force reallocation.
Ben.
next prev parent reply other threads:[~2013-10-08 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131008144211.GA25231@e102652-lin.cambridge.arm.com>
[not found] ` <20131008144211.GA25231-CibnQJhq84/ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-10-08 16:32 ` [RFC] Architecture independent pcibios? Bjorn Helgaas
2013-10-08 16:55 ` Rob Herring
2013-10-08 17:20 ` Andrew Murray
2013-10-08 20:32 ` Benjamin Herrenschmidt
2013-10-08 20:28 ` Benjamin Herrenschmidt
2013-10-09 9:09 ` Liviu Dudau
2013-10-09 10:04 ` Liviu Dudau
2013-10-09 10:37 ` Benjamin Herrenschmidt
2013-10-09 10:45 ` Liviu Dudau
2013-10-09 14:30 ` Bjorn Helgaas
2013-10-09 16:23 ` Liviu Dudau
2013-10-15 11:48 ` Grant Likely
2013-10-08 17:13 ` Liviu Dudau
2013-10-08 18:58 ` Bjorn Helgaas
2013-10-08 20:31 ` Benjamin Herrenschmidt [this message]
2013-10-09 11:52 ` Michal Simek
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=1381264278.645.232.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Catalin.Marinas@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
/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).