From: Michal Simek <monstr@monstr.eu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Liviu Dudau <Liviu.Dudau@arm.com>,
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>,
"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 13:52:29 +0200 [thread overview]
Message-ID: <5255437D.7040207@monstr.eu> (raw)
In-Reply-To: <1381264278.645.232.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On 10/08/2013 10:31 PM, Benjamin Herrenschmidt wrote:
> 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 :-)
yes and the reason was that xilinx ppc405 and then ppc440 used
the same pci IPs that's why it was easier just to use this code.
I am keeping microblaze pcie driver out of mainline but definitely
unification work has to be done.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-10-09 11:52 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
2013-10-09 11:52 ` Michal Simek [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=5255437D.7040207@monstr.eu \
--to=monstr@monstr.eu \
--cc=Catalin.Marinas@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-pci@vger.kernel.org \
--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).