dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Airlie <airlied@gmail.com>, Martyn Welch <martyn.welch@ge.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Radeon drivers on PowerPC (e500)
Date: Wed, 18 Jun 2014 11:48:36 +1000	[thread overview]
Message-ID: <1403056116.7661.187.camel@pasglop> (raw)
In-Reply-To: <CAPM=9ty721aVY51BBwF7niPLQXKDdMPEGNPQcYJ9jK54S6B0ew@mail.gmail.com>

On Wed, 2014-06-18 at 11:05 +1000, Dave Airlie wrote:
> 
> I don't think we ever ioremap GART, it should kmap GART pages, ioremap
> should only happen for VRAM areas AFAIK,
> 
> This isn't some 32-bit vs 36-bit BAR or something, I seem to remember BenH
> mentioning something like that before.

Yes, it's a recurring problem in the DRM with physical addresses that are
bigger than 32-bit on 32-bit systems. There have been patches done to
fix that but afaik never quite "completed". I can dig internally if
I can put my hand onto something.

If possible at all, can you try to configure your SoC to bring the MMIO
space of the PCIe within the bottom 32-bit of the chip address space ?

(Or use a 64-bit e5500 based chip ? :-)

Cheers,
Ben.

  reply	other threads:[~2014-06-18  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 19:14 Radeon drivers on PowerPC (e500) Martyn Welch
2014-06-18  1:05 ` Dave Airlie
2014-06-18  1:48   ` Benjamin Herrenschmidt [this message]
2014-06-18  8:39     ` Martyn Welch
2014-06-26  8:28     ` Martyn Welch
2014-06-18  8:09   ` Martyn Welch

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=1403056116.7661.187.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=martyn.welch@ge.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).