From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
avorontsov@ru.mvista.com
Subject: Re: PCI on 834x
Date: Fri, 26 Feb 2010 07:49:42 +1100 [thread overview]
Message-ID: <1267130982.23523.1728.camel@pasglop> (raw)
In-Reply-To: <4B86886B.5000304@mlbassoc.com>
On Thu, 2010-02-25 at 07:25 -0700, Gary Thomas wrote:
> I may have been too hasty pronouncing this fixed. Indeed, the
> SATA interface now works, but my video card (Fujitsu Coral-P)
> does not work when it's mapped at the bottom of the PCI space :-(
>
> With the bridge mapped, the video ends up at a non-zero address
> (0xC8000000..0xCFFFFFFF). If it gets mapped to 0xC0000000, it
> fails to respond to MMIO accesses.
>
> Any ideas how I might get around this? Is there a way to force
> the PCI allocator to start somewhere other than [relative] zero?
I'm not familiar with the way the FSL bridge works, but it would
be possible to invert MMIO and DMA on your PCI bus. IE. Have MMIO go
from 0....2G and DMA from 2G..4G for example. Provided the FSL bridge
can offset the DMA back down to 0 (memory). Can it ?
Cheers,
Ben.
next prev parent reply other threads:[~2010-02-25 20:49 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
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 [this message]
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=1267130982.23523.1728.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=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).