From: Sven Luther <sven.luther@wanadoo.fr>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb on pegasos powerpc motherboard and X endianess problem
Date: Wed, 4 Jun 2003 17:39:16 +0200 [thread overview]
Message-ID: <20030604153916.GA23620@iliana> (raw)
In-Reply-To: <1054740419.27389.332.camel@thor.holligenstrasse29.lan>
On Wed, Jun 04, 2003 at 05:27:00PM +0200, Michel Dänzer wrote:
> On Wed, 2003-06-04 at 16:54, Sven Luther wrote:
> >
> > I finally have a working pegasos motherboard as well as a working kernel
> > with a 1.6 radeonfb. I have also installed Daniel Stone's X 4.3.0
> > debian/sid packages, and notice the following :
> >
> > 1) radeonfb works fine in 8bpp and 32bpp but depth 15 and 16 only give
> > me some very dark grey.
> >
> > 2) when running X with the UseFBDev option the colors are bad, i guess
> > it is an endianess problem. (with and without accel)
>
> You want radeonfb from a recent benh kernel, anything else is more or
> less broken.
A, ok, but then, i think i will not worry about this, and simply port
the pegasos changes to the latest benh kernel (or maybe i can simply
replace the radeonfb.c file ? Mmm, i will try it). By recent benh
kernel, you mean the one from the linuxppc_2_4_devel tree or the one from the
linuxppc_2_4 tree ? Or maybe both are the same.
> > 3) When running X without the UseFBDev option, the colors are good,
> > but i get garbage when i return to the console. Not exactly garbage,
> > at first it is ok, but when i enter a line or somehow pan the screen,
> > the corruption start. Doing a vt switch and back redraws a clean
> > screen.
>
> Sounds like the radeon driver doesn't restore the framebuffer aperture
> byte swapping correctly.
Yep. same solution as above i guess.
Sound is also messed up, i guess it is also an endianess issue, but most
probably due to endianess issue in the VT82Cxx driver, and no other
powerpc box should use this, i think.
Thanks.
Friendly,
Sven Luther
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
next prev parent reply other threads:[~2003-06-04 15:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 14:54 radeonfb on pegasos powerpc motherboard and X endianess problem Sven Luther
2003-06-04 15:27 ` Michel Dänzer
2003-06-04 15:39 ` Sven Luther [this message]
2003-06-05 8:01 ` Benjamin Herrenschmidt
2003-06-05 7:59 ` Benjamin Herrenschmidt
2003-06-05 8:19 ` Sven Luther
2003-06-05 11:42 ` Benjamin Herrenschmidt
2003-06-05 11:58 ` Sven Luther
2003-06-05 12:27 ` Benjamin Herrenschmidt
2003-06-05 13:12 ` Sven Luther
2003-06-06 6:02 ` Geert Uytterhoeven
2003-06-06 6:30 ` Sven Luther
2003-06-06 6:35 ` Geert Uytterhoeven
2003-06-06 6:41 ` Sven Luther
2003-06-10 11:04 ` Jochen Roth
2003-06-13 9:27 ` Michel Dänzer
2003-06-13 10:05 ` Jochen Roth
2003-06-13 16:57 ` Michel Dänzer
2003-06-06 6:00 ` radeonfb on pegasos powerpc motherboard and " Geert Uytterhoeven
2003-06-06 5:58 ` Geert Uytterhoeven
2003-06-10 9:54 ` Sven Luther
2003-06-10 10:45 ` Sven Luther
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=20030604153916.GA23620@iliana \
--to=sven.luther@wanadoo.fr \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.net \
/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).