From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>, Gary Thomas <gary@mlbassoc.com>
Subject: Re: PCI on 834x
Date: Wed, 24 Feb 2010 23:51:59 +0300 [thread overview]
Message-ID: <20100224205159.GA6555@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <4B858B6C.4020809@freescale.com>
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
> Gary Thomas wrote:
> >Yes, I'm using the exact same kernel with these two different PCI
> >setups (done by the boot loader).
> >
> >Restricting the memory via mem=128M has no effect - the PCI layout
> >is the same.
> >
> >I think the outbound window size is required because of how the Linux PCI
> >remaps the space (note in my dumps that it put the MMIO of the
> >boards starting
> >at 0xD0000000 when the inbound window is 0x10000000)
>
> I see where the amount of RAM is mattering -- Linux is assigning
> outbound I/O space to the PCI controller itself (device 00:00.0) and
> the amount that it asks for seems to differ based on memory size.
> Linux ought to skip that device when assigning resources. Some
> platforms do this (search for pci_exclude_device), but it seems to
> be missing on 83xx.
Actually, 83xx had these exclude_device hooks, but they were removed:
commit d8f1324a5063c833862328ceafabc53ac3cc4f71
Author: Kumar Gala <galak@kernel.crashing.org>
Date: Wed Sep 12 22:14:10 2007 -0500
[POWERPC] 83xx: Removed PCI exclude of PHB
Now that the generic code doesn't assign resources for Freescale
PHBs we dont have to explicitly exclude it.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
May be the generic code started to assign the resources again?
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2010-02-24 20:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:49 PCI on 834x Gary Thomas
2010-02-24 18:48 ` Scott Wood
2010-02-24 19:14 ` Gary Thomas
2010-02-24 19:31 ` Scott Wood
2010-02-24 19:47 ` Gary Thomas
2010-02-24 20:26 ` Scott Wood
2010-02-24 20:51 ` Anton Vorontsov [this message]
2010-02-24 22:14 ` Gary Thomas
2010-02-24 22:25 ` Kumar Gala
2010-02-24 23:08 ` Gary Thomas
2010-02-25 14:25 ` Gary Thomas
2010-02-25 20:49 ` Benjamin Herrenschmidt
2010-02-25 21:03 ` Scott Wood
2010-02-25 21:11 ` Gary Thomas
2010-02-25 21:24 ` Scott Wood
2010-02-25 23:43 ` Gary Thomas
2010-02-25 23:49 ` Scott Wood
2010-02-25 22:36 ` Benjamin Herrenschmidt
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=20100224205159.GA6555@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).