From: Anatolij Gustschin <agust@denx.de>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Xorg on Fujitsu "Lime" with MPC5200b?
Date: Thu, 15 Apr 2010 09:44:13 +0200 [thread overview]
Message-ID: <20100415094413.4d752de0@wker> (raw)
In-Reply-To: <4BC682DC.1050200@billgatliff.com>
On Wed, 14 Apr 2010 22:07:08 -0500
Bill Gatliff <bgat@billgatliff.com> wrote:
> Put simply, I have an MPC5200b platform with a Fujitsu "Lime" GDC, and
> I'm trying to run Debian squeeze's xorg on it.
>
> Actually, I *have* Debian squeeze's xorg running on the platform just
> fine, with a 2.6.34-rc1 kernel (kernel.org). Problem is, every single
> diagonal line is very blocky--- not smooth at all. I used to think this
> was a problem with X's fonts, but now I don't think so because the mouse
> cursor's diagonal lines also look equally bad.
>
> It's almost as if any time the platform tries to draw a diagonal line,
> truncation/rounding errors are causing it problems in figuring out which
> pixels to turn on and off.
On all PowerPC based boards with Lime (PPC440EPx, MPC85xx) I have seen so
far there is a similar problem with direct access to the frame buffer in
16-bit mode.
> A non-Linux kernel on this hardware, running a non-X GUI, seems to work
> fine so I think the hardware isn't the problem.
It is possible that this non-X GUI doesn't access the frame buffer directly
but only uses the accelerated driver for rendering. In this case all
drawing is done by Lime itself triggered by 32-bit accesses to the
drawing command FIFO.
> Anyone have any suggestions on where to start with this one? Anyone
> else running a similar configuration with any success? I'm completely
> lost, and running out of hair *fast*...
You probably have to fix Xorg driver for swapping.
Anatolij
prev parent reply other threads:[~2010-04-15 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 3:07 Xorg on Fujitsu "Lime" with MPC5200b? Bill Gatliff
2010-04-15 4:53 ` Benjamin Herrenschmidt
2010-04-15 7:21 ` Roman Fietze
2010-04-15 13:01 ` Bill Gatliff
2010-04-15 13:53 ` Roman Fietze
[not found] ` <v2ma0706c7b1004150906p34b853a0r80e2bb751e034b97@mail.gmail.com>
2010-04-15 16:07 ` Bill Gatliff
2010-04-16 6:14 ` Roman Fietze
2010-04-16 8:30 ` Michel Dänzer
2010-04-15 20:14 ` Bill Gatliff
2010-04-16 5:48 ` Roman Fietze
2010-04-16 2:51 ` Bill Gatliff
2010-04-16 8:28 ` Roman Fietze
2010-04-16 9:25 ` Gabriel Paubert
2010-04-15 7:44 ` Anatolij Gustschin [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=20100415094413.4d752de0@wker \
--to=agust@denx.de \
--cc=bgat@billgatliff.com \
--cc=linuxppc-dev@ozlabs.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).