From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
linux-pci@vger.kernel.org,
Gregory Cl??ment <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Issue with the emulated PCI bridge implementation
Date: Fri, 3 Jan 2014 11:44:24 -0700 [thread overview]
Message-ID: <20140103184424.GC12098@obsidianresearch.com> (raw)
In-Reply-To: <201401031322.31433.arnd@arndb.de>
On Fri, Jan 03, 2014 at 01:22:31PM +0100, Arnd Bergmann wrote:
> However the part that made me wonder is that an e1000e with a PCI bridge
> actually /should/not/ need to allocate an I/O space window with a precious
> mbus resource, since AFAIK this adapter does not have an I/O space BARs.
IIRC the e1000 still has a legacy IO port BAR.. (guessing it is used
for PXE boot on x86?)
My patch set to allow the DT to turn off IO port allocation is already
in mainline - drop the IO ranges from the DT and no IO resources are
consumed at all.
Though, that is an interesting point, a small refinement would be to
not allocate the pci io map if IO is turned off as well..
Jason
next prev parent reply other threads:[~2014-01-03 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 15:05 Issue with the emulated PCI bridge implementation Thomas Petazzoni
2013-12-26 15:52 ` Thomas Petazzoni
2014-01-02 21:41 ` Bjorn Helgaas
2014-01-03 0:26 ` Jason Gunthorpe
2014-01-03 12:22 ` Arnd Bergmann
2014-01-03 18:44 ` Jason Gunthorpe [this message]
2014-01-03 19:03 ` Arnd Bergmann
2014-01-03 19:01 ` Thomas Petazzoni
2014-01-03 19:04 ` Arnd Bergmann
2014-01-03 19:10 ` Thomas Petazzoni
2014-01-03 19:13 ` 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=20140103184424.GC12098@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=alior@marvell.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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).