linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 20 Jan 2006 09:09:13 +1100	[thread overview]
Message-ID: <1137708554.12998.31.camel@localhost.localdomain> (raw)
In-Reply-To: <15255.1137667967@www31.gmx.net>

On Thu, 2006-01-19 at 11:52 +0100, Gerhard Pircher wrote:
> > > 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!?

Euh... I was talking about the aperture base, not the GART base... (One
is the address one the bus where the AGP area will be visible, the other
is where the GART will be in memory, that is the table that contains the
mapping between AGP pages and memory pages).

> 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()?

Nope... look at drivers/pci/setup-res.c how it does for allocating new
resources for PCI devices.

> > (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
> 

  reply	other threads:[~2006-01-19 22:09 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
2006-01-19 22:09                     ` Benjamin Herrenschmidt [this message]
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=1137708554.12998.31.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).