linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: dri-devel@lists.sourceforge.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Dri-devel] Re: Kind of success! (r128 on PPC (Re: LinuxPPC X Server))
Date: Mon, 07 Aug 2000 09:14:10 +0200	[thread overview]
Message-ID: <398E61C2.BF0ED1ED@student.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.21.0008041831040.29474-100000@idd-01.imbc.gr


Kostas Gewrgiou wrote:

> > The remaining problems are:
> >
> > 16 bit doesn't work neither with fbdev (colors completely off - does
> > aty128fb still use 15 bit in fact?) nor without (at least the grey tones
> > are right there - wrong endianness?)
>
> Yes aty128fb still doesn't support 16 bit, you could run the r128 driver
> without fbdev to get 16 bits, but the code to switch the framebuffer to do
> byteswapping is missing so the colors will be wrong

Yep, that's the second thing I was referring to.

> (easy to add though).

Where and how?


> > About performance: It's much better than software rendering (at least for
> > big windows) of course, however not too fast with lots of polygons. AGP
> > GART would definitely be a good thing I guess (Ben: hint, hint :)
>
> Do you have any numbers from gears, glquake etc ??

The numbers are very varying and not too high yet. AGP GART should change
that.


Michel


--
                                Tax the rich.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

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

  parent reply	other threads:[~2000-08-07  7:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0008031541210.6020-100000@idd-01.imbc.gr>
2000-08-04 15:03 ` Kind of success! (r128 on PPC (Re: LinuxPPC X Server)) Michel Dänzer
2000-08-04 17:03   ` Michel Dänzer
2000-08-04 17:50     ` Benjamin Herrenschmidt
2000-08-05 14:35       ` Michel Dänzer
2000-08-05 18:22   ` Kostas Gewrgiou
2000-08-05 18:43     ` Benjamin Herrenschmidt
2000-08-07  7:08       ` [Dri-devel] " Michel Dänzer
2000-08-07 13:31         ` Josh Huber
2000-08-08 12:35           ` Geert Uytterhoeven
2000-08-08 13:13             ` Josh Huber
2000-08-08 13:55               ` Geert Uytterhoeven
2000-08-08 16:54               ` Michael Schmitz
2000-08-09 14:20                 ` Geert Uytterhoeven
2000-08-09 20:20                   ` Michael Schmitz
2000-08-09 21:27                     ` Geert Uytterhoeven
2000-08-05 18:45     ` Gareth Hughes
2000-08-07  7:14     ` Michel Dänzer [this message]
2000-08-07 18:09       ` Kostas Gewrgiou
2000-08-07 19:51         ` Sven Goethel
2000-08-08  8:46           ` [Dri-devel] Re: Kind of success! (r128 on PPC (Re: LinuxPPC XServer)) Michel Dänzer
2000-08-08  8:51         ` Michel Dänzer

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=398E61C2.BF0ED1ED@student.ethz.ch \
    --to=daenzerm@student.ethz.ch \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=gewrgiou@imbc.gr \
    --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).