From: Josh Huber <huber@mclx.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Dri-devel] Re: Kind of success! (r128 on PPC (Re: LinuxPPC X Server))
Date: Mon, 7 Aug 2000 09:31:24 -0400 [thread overview]
Message-ID: <20000807093124.B248@mclx.com> (raw)
In-Reply-To: <398E6051.6DA84197@student.ethz.ch>; from daenzerm@student.ethz.ch on Mon, Aug 07, 2000 at 09:08:01AM +0200
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
On Mon, Aug 07, 2000 at 09:08:01AM +0200, Michel D?nzer wrote:
> Benjamin Herrenschmidt wrote:
> > The Pismo allows that by scaling the LCD, but I don't think code for that
> > is implemented in the XFree r128 driver (I didn't check lately).
>
> No it doesn't work, neither with aty128fb. Would that be hard to implement?
If it's anything like the mach 64, it shouldn't be hard to implement
at all. you just have to program 3 registers.
Speaking of this, I'm having trouble with the stretching setup for my
wallstreet. It works fine in console mode, but something in the X
server is messing with the chip setup in a way to screw up the
rendering. After playing with it I was able to get proper output:
console settings:
mclk = 99.844107 MHz
vclk = 44.702930 MHz
dsp_loop_latency = 10
dsp_precision = 5
dsp_xclks_per_row = 1143 => 17.859375
dsp_on = 69 => 34.500000
dsp_off = 1113 => 556.500000
X (xf4.0.1) settings:
mclk = 99.844107 MHz
vclk = 44.702930 MHz
dsp_loop_latency = 10
dsp_precision = 4
dsp_xclks_per_row = 1143 => 8.929688
dsp_on = 103 => 25.750000
dsp_off = 1119 => 279.750000
X after tweaks to get it working properly:
mclk = 99.844107 MHz
vclk = 59.603906 MHz
dsp_loop_latency = 10
dsp_precision = 4
dsp_xclks_per_row = 1143 => 8.929688
dsp_on = 131 => 32.750000
dsp_off = 1986 => 496.500000
using geerts handy ati debugging application, I set the vclk post
divider to 3 (was 4), and changed the high and low watermarks back to
what the console settings were, and things worked great in X now. Of
course, if I switch back to a VC and back to X the old (bad) settings
come back.
Where's the proper place to fix this? I assume it's not in the fbcon
interface, because text mode is correctly displayed.
Thoughts?
--
Josh
6B21489A | GnuPG ID/Fingerprint | huber@mclx.com |
61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2000-08-07 13:31 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 [this message]
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
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=20000807093124.B248@mclx.com \
--to=huber@mclx.com \
--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).