public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Vincent Katz <vincent.katz@laposte•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@lists•linuxppc.org, jhartmann@precisioninsight•com,
	paulus@samba•org
Subject: Re: AGP : ATI128,powerpc
Date: 15 Nov 2001 18:21:15 +0100	[thread overview]
Message-ID: <1005844877.16584.190.camel@avalon> (raw)
In-Reply-To: <20011115144502.20832@smtp.adsl.oleane.com>


Ok thanks, i understand the problem ;-)
this, go against my frame of mind but i yield (i m not narrow-minded ;-)
), meanwhile the update of the official, i'll use your rsync.
 thx for all, good luck.

thx also for my gpm problem :-)

vince.

On 15 Nov 2001 15:45:02 +0100, Benjamin Herrenschmidt wrote:
> >PPC machine : TiBook (Powerbook Titanium)
> >ATY : aty128fb: Rage Mobility M3 (AGP) [chip rev 0x0] 8M 128-bit SDR
> >SGRAM (1:1)
> >
> >Is it possible to add in the flush_cache function a
> >"defined(__powerpc__)"  like alpha, sparc ..or i386 .. ?
> >
> >When the function flush_cache in the file "agpgart_be.c" ll be updated
> >in the offical kernel for ppc cpu ?
>
> It's more than flush cache that is needed ;) flush_cache alone will
> eventually allow AGP to compile, not to work.
>
> Get my current rsync tree from rsync.penguinppc.org::linux-2.4-benh,
> it has complete support for UniNorth AGP on r128. (the M3 you have in
> your Pismo is an r128). Beware however that accelerated GL via DRI
> is known to crash with this chip for reasons not yet determined.
>
> I've sent my current patches to the DRI mailing list, I can't say
> yet when all this will appear upstream as some merging has to be
> done with other archs using the "special" agp_ioremap. I will submit
> the AGP part of the patch directly to linus/marcello once I'm in sync
> with DRI people, there's no need to send it until something can use it ;)
>
> Ben.
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-11-15 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 20:52 AGP : ATI128,powerpc Vincent Katz
2001-11-14 21:09 ` Kevin B. Hendricks
2001-11-14 21:23   ` Jörn Nettingsmeier
2001-11-14 21:38     ` Benjamin Herrenschmidt
2001-11-14 21:26 ` Benjamin Herrenschmidt
2001-11-15 14:12   ` Vincent Katz
2001-11-15 14:45     ` Benjamin Herrenschmidt
2001-11-15 17:21       ` Vincent Katz [this message]
     [not found] <20011114230308.04E9D18077@haven.ozlabs.ibm.com>
2001-11-14 18:11 ` Paul Mackerras
2001-11-15  9:20   ` Jörn Nettingsmeier

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=1005844877.16584.190.camel@avalon \
    --to=vincent.katz@laposte$(echo .)net \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=jhartmann@precisioninsight$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    --cc=paulus@samba$(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