From: "Gerhard Pircher" <gerhard_pircher@gmx•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, debian-powerpc@lists•debian.org
Subject: Re: AGPGART driver for ArticiaS - ioremap() problem
Date: Thu, 19 Jan 2006 11:52:47 +0100 (MET) [thread overview]
Message-ID: <15255.1137667967@www31.gmx.net> (raw)
In-Reply-To: 1137664796.4823.214.camel@localhost.localdomain
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1234 bytes --]
> > I set the AGP aperture base register and agp_bridge->gart_bus_addr to
> > 0x01000000 (>=16MB) (trial and error :-) and it seems to work with
> > cant_use_aperture=1
>
> Makes sense, since this value is right in the middle of your RAM :) What
> does the firmware sets the base register too ?
I did a readout of all AGP related registers and the base register was set
to 0x0, so the firmware doesn't set it up at all.
> Can't you try to allocate some resource in the PCI area that isn't
> already occupied instead ?
I though the GART base address should be in memory space!?
Sorry for this dumb question: how can I allocate a resource in the PCI area?
I'm not yet familiar with the whole Linux PCI/MM API. :) With something like
pci_alloc_consistent()?
> > (and without the modification in drm_vm.c). Even the X
> > server maps all the data to this address and displays a login screen.
> > Unfortunately it always freezes in. I guess this is due to the missing
> > GART flush functionality. So I have to get this working first.
>
> Yah, that would be pretty bad...
Indeed! :)
Gerhard
--
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
next prev parent reply other threads:[~2006-01-19 10:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 23:10 AGPGART driver for ArticiaS - ioremap() problem 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 [this message]
2006-01-19 22:09 ` Benjamin Herrenschmidt
2006-01-20 11:16 ` Gerhard Pircher
2006-01-20 23:00 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 22:15 Gerhard Pircher
2006-01-21 1:59 Gerhard Pircher
2006-01-21 22:48 ` Benjamin Herrenschmidt
2006-01-23 22:12 ` Gerhard Pircher
2006-01-23 23:15 ` 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=15255.1137667967@www31.gmx.net \
--to=gerhard_pircher@gmx$(echo .)net \
--cc=benh@kernel$(echo .)crashing.org \
--cc=debian-powerpc@lists$(echo .)debian.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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