From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org
Subject: Re: AGPGART driver for ArticiaS - ioremap() problem
Date: Sun, 22 Jan 2006 09:48:44 +1100 [thread overview]
Message-ID: <1137883724.12998.74.camel@localhost.localdomain> (raw)
In-Reply-To: <25707.1137808755@www011.gmx.net>
On Sat, 2006-01-21 at 02:59 +0100, Gerhard Pircher wrote:
> Yes, I see. :( The code mostly allocates the resources for the AGPGART
> driver beyond the real memory space, thus preventing the X server to work.
> Sometimes the resource is also mapped to where the resource of the graphic
> card resides (address 0x88000000, compare with the included iomem file).
The AGP aperture should generally be located "outside" of those spaces.
That is above RAM and in some place where no device already resides...
It can be made to overlap RAM but that isn't a good idea (that's what
happens on Macs though due to a bug in the Apple chipset).
> Please take a look to the attachments. But the allocation seems to be
> different now! Strange!? At least the AGPGART driver is not allocated to bus
> 1.
I don't see anything related to AGP in your output... you didn't post
the lspci as root thus it's missing all the useful infos ;) Also, the
AGP base isn't generally a PCI BAR of the bridge... it is one in your
case ?
Ben.
next prev parent reply other threads:[~2006-01-21 22:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 1:59 AGPGART driver for ArticiaS - ioremap() problem Gerhard Pircher
2006-01-21 22:48 ` Benjamin Herrenschmidt [this message]
2006-01-23 22:12 ` Gerhard Pircher
2006-01-23 23:15 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 22:15 Gerhard Pircher
2006-01-15 23:10 Gerhard Pircher
2006-01-15 23:25 ` Benjamin Herrenschmidt
2006-01-16 8:11 ` Gerhard Pircher
2006-01-16 23:18 ` Benjamin Herrenschmidt
2006-01-17 8:37 ` Gerhard Pircher
2006-01-17 21:24 ` Benjamin Herrenschmidt
2006-01-18 19:40 ` Gerhard Pircher
2006-01-18 23:09 ` Benjamin Herrenschmidt
2006-01-19 8:50 ` Gerhard Pircher
2006-01-19 9:59 ` Benjamin Herrenschmidt
2006-01-19 10:52 ` Gerhard Pircher
2006-01-19 22:09 ` Benjamin Herrenschmidt
2006-01-20 11:16 ` Gerhard Pircher
2006-01-20 23:00 ` Benjamin Herrenschmidt
2006-01-11 21:00 Gerhard Pircher
2006-01-11 21:52 ` John W. Linville
2006-01-11 22:18 ` Gerhard Pircher
2006-01-12 4:44 ` Benjamin Herrenschmidt
2006-01-12 8:15 ` Gerhard Pircher
2006-01-15 21:48 ` Benjamin Herrenschmidt
2006-01-12 19:15 ` Gerhard Pircher
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=1137883724.12998.74.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=gerhard_pircher@gmx.net \
--cc=linuxppc-dev@ozlabs.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).