From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
linuxppc-dev@lists.linuxppc.org,
Daniel Berlin <dan@cgsoftware.com>,
ghannon@cspi.com
Subject: Re: X works somewhat on DFP with latest radeonfb.c
Date: 18 Nov 2001 00:17:29 +0100 [thread overview]
Message-ID: <1006039050.4572.2.camel@pismo> (raw)
In-Reply-To: <20011117160749.13478@smtp.wanadoo.fr>
On Sat, 2001-11-17 at 17:07, Benjamin Herrenschmidt wrote:
>
> >Thought you might like to know. I took a look at the XF410
> >radeon_driver.c and compared it to the latest versions of radeon_driver.c
> >in XFreee86 CVS HEAD and they are quite different.
> >
> >CVS HEAD has a *lot* more support for DFP but since I had the radeonfb
> >working on the DFP I thought what the hell, and started to try to use XF
> >4.1.0 radeon_driver.c with only a few small tweaks (ignoring all of the
> >Flat Panel code which is old and not-working in XF410) with the UseFBDev
> >Option so all the DFP register stuff is handled by the radeonfb.c driver.
> >
> >X actually starts up with depths of 8 and depths of 24 (32bpp), and works
> >but the colors are all wrong: too many pinks in the 8 bit version and
> >seemingly random colors in the 24 depth.
> >
> >So I am going to try and play around with the pallette setting.
>
> Ask Ani for his patches. I think the engine must be properly configured
> for big endian.
With Option "UseFBDev", the framebuffer device is used for setting the
palette.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-17 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 15:48 X works somewhat on DFP with latest radeonfb.c Kevin B. Hendricks
2001-11-17 16:07 ` Benjamin Herrenschmidt
2001-11-17 16:23 ` Kevin B. Hendricks
2001-11-17 16:56 ` Kevin B. Hendricks
2001-11-17 18:34 ` Ani Joshi
2001-11-17 18:51 ` Daniel Berlin
2001-11-17 23:17 ` Michel Dänzer [this message]
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=1006039050.4572.2.camel@pismo \
--to=michdaen@iiic.ethz.ch \
--cc=benh@kernel.crashing.org \
--cc=dan@cgsoftware.com \
--cc=ghannon@cspi.com \
--cc=khendricks@ivey.uwo.ca \
--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).