linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Tue, 1 Aug 2000 14:06:42 -0700	[thread overview]
Message-ID: <20000801140642.B24586@drow.them.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0008011508360.4803-100000@idd-01.imbc.gr>; from gewrgiou@imbc.gr on Tue, Aug 01, 2000 at 03:54:37PM +0300


On Tue, Aug 01, 2000 at 03:54:37PM +0300, Kostas Gewrgiou wrote:
> The mb() should be enough in r128_dma.c (we might not need it at all though
> but it shouldn't hurt). The R128_WRITE/R128_READ macros in r128_drv.h will
> need to do byteswapping also i imagine.
>
> The writes to the CCE ring buffer might be a problem also you might need
> to do different swaps depending on where the buffer lives (host memory or
> in the framebuffer) since the framebuffer writes get swapped depending on
> the current depth. (voodoo3 has this problem)
>
> The drm modules need some asm code as well, look at my patches in
> dri.sourceforge.net (patch_id 100488,100568) the code is almost a copy
> from the glibc sources (i know next to nothing about ppc asm) but they
> work well with my voodoo3.
>
> Also note that the DRI drivers don't get build by default in PPC
> you have to #define BuildXF86DRI YES in xf config files *AND*
> patch xc/lib/GL/mesa/src/drv/Imakefile to enable the dri drivers
> to build under ppc.
>
> Unfortunately i don't have an r128 card so i can't do anything here :(

What sort of patch do we need to that Imakefile?  I couldn't figure out
what to do.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

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

  parent reply	other threads:[~2000-08-01 21:06 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-30 20:33 LinuxPPC X Server Iain Sandoe
2000-07-31  7:50 ` Michel Dänzer
2000-07-31  9:25   ` Steffen Haeuser
2000-07-31  8:47     ` Michel Dänzer
2000-07-31 10:05       ` Steffen Haeuser
2000-07-31  9:03         ` Michel Dänzer
2000-07-31 10:21           ` Steffen Haeuser
2000-08-01 12:54       ` Kostas Gewrgiou
2000-08-01 16:25         ` Steffen Haeuser
2000-08-01 21:06         ` Daniel Jacobowitz [this message]
2000-08-02  9:20           ` Michel Dänzer
2000-08-02 18:17           ` Kostas Gewrgiou
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 16:07 Jack Howarth
2000-08-03 13:27 ` Kostas Gewrgiou
2000-08-02  0:25 Iain Sandoe
2000-07-31 14:07 Benjamin Herrenschmidt
2000-08-01 19:05 ` Michel Dänzer
     [not found]   ` <20000801191739.26835@mailhost.mipsys.com>
2000-08-01 19:37     ` Michel Dänzer
     [not found]       ` <20000801204113.29901@mailhost.mipsys.com>
2000-08-01 21:31         ` Michel Dänzer
2000-08-02 12:45           ` Geert Uytterhoeven
2000-08-02 23:27             ` Michel Dänzer
2000-07-30 21:24 Iain Sandoe
2000-07-31 12:53 ` Josh Huber
2000-07-31 16:28   ` Michael Schmitz
2000-07-30 20:00 Iain Sandoe
2000-07-30 18:14 ` Michel D nzer
2000-07-30 22:33   ` Steffen Haeuser
2000-07-31  3:12   ` Daniel Jacobowitz
2000-07-31  7:40     ` Michel Dänzer
2000-08-01 21:03       ` Daniel Jacobowitz
2000-07-31 16:05   ` Michael Schmitz
2000-08-02 10:40     ` Martin Costabel
2000-07-30 22:46 ` Steffen Haeuser
2000-07-30 16:56 Iain Sandoe
2000-07-30 19:29 ` Steffen Haeuser
2000-07-30 21:13 ` Timothy A. Seufert
2000-07-29 13:31 Steffen Haeuser
2000-07-29 22:55 ` Takashi Oe
2000-07-30 11:27   ` Steffen Haeuser
2000-07-30 11:54     ` Takashi Oe
2000-07-30 14:40       ` Steffen Haeuser
2000-07-30 14:41         ` Takashi Oe
2000-07-30 16:13           ` Steffen Haeuser

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=20000801140642.B24586@drow.them.org \
    --to=drow@false.org \
    --cc=linuxppc-dev@lists.linuxppc.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).