From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V3 1/4] pci: APM X-Gene PCIe controller driver
Date: Tue, 4 Feb 2014 20:22:57 +0100 [thread overview]
Message-ID: <201402042022.57267.arnd@arndb.de> (raw)
In-Reply-To: <20140203221559.GG2519@obsidianresearch.com>
On Monday 03 February 2014, Jason Gunthorpe wrote:
> On Mon, Feb 03, 2014 at 09:12:32PM +0100, Arnd Bergmann wrote:
>
> > Are you sure that is true for the root bridge as well? I don't
> > remember the details, but I though that for the host bridge,
> > we don't actually look at the BARs at all.
>
> That is right, but this isn't a host bridge device, it is a PCI-PCI
> bridge with root complex registers. The root complex bridge is not the
> same as the host bridge.
>
> Unfortunately the implementation is non-conforming. :(
Ok, I see. I was probably asking the wrong question then earlier
when I tried to find out what this is.
Arnd
next prev parent reply other threads:[~2014-02-04 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 21:32 [RFC PATCH V3 0/4] APM X-Gene PCIe controller Tanmay Inamdar
2014-01-24 21:32 ` [RFC PATCH V3 1/4] pci: APM X-Gene PCIe controller driver Tanmay Inamdar
2014-01-30 14:16 ` Arnd Bergmann
2014-02-03 19:42 ` Tanmay Inamdar
2014-02-03 20:12 ` Arnd Bergmann
2014-02-03 20:14 ` Tanmay Inamdar
2014-02-03 22:15 ` Jason Gunthorpe
2014-02-04 19:22 ` Arnd Bergmann [this message]
2014-01-24 21:32 ` [RFC PATCH V3 2/4] arm64: dts: APM X-Gene PCIe device tree nodes Tanmay Inamdar
2014-01-30 14:09 ` Arnd Bergmann
2014-01-24 21:32 ` [RFC PATCH V3 3/4] dt-bindings: pci: xgene pcie device tree bindings Tanmay Inamdar
2014-01-24 21:32 ` [RFC PATCH V3 4/4] MAINTAINERS: entry for APM X-Gene PCIe host driver Tanmay Inamdar
2014-01-25 16:09 ` [RFC PATCH V3 0/4] APM X-Gene PCIe controller Dann Frazier
2014-01-27 22:58 ` Tanmay Inamdar
2014-01-30 0:18 ` Bjorn Helgaas
2014-01-30 0:40 ` Tanmay Inamdar
2014-01-30 14:21 ` Arnd Bergmann
2014-01-30 18:06 ` Bjorn Helgaas
2014-01-30 14:17 ` Arnd Bergmann
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=201402042022.57267.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).