From: Benjamin Herrenschmidt <bh40@calva.net>
To: khendricks@ivey.uwo.ca, linuxppc-dev@lists.linuxppc.org
Subject: Re: Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros
Date: Tue, 21 Mar 2000 12:11:20 +0100 [thread overview]
Message-ID: <20000321121120.009795@mailhost.mipsys.com> (raw)
In-Reply-To: <00032021464800.00801@localhost.localdomain>
On Mon, Mar 20, 2000, Kevin Hendricks <khendricks@ivey.uwo.ca> wrote:
>These patches have been tested and work fine on my B+W G3 rev 2, my brand new
>G4 with Rage128Pro card, and on Ben's older G4 with the non-pro card.
>
>We still need to test this on a B+W G3 revision 1 just to be complete
(but Ben
>will do that soon).
Apparently, it works on all machines. I just tested on a B&W G3 rev. 1
and an iMac DV. It works also on the M3 (new r128 mobility in pismo).
However, I noticed that in all cases (or almost all cases), we have the
same XCLK as MacOS (and probably the same MCLK, I didn't verify), but we
obtain it using a lower divider. For example, on the B&W rev. 1, we have
0x1f for the ref. div, and I have 0x38 (instead of 0x3b used by MacOS).
I don't know if there's a real impact (less precise pixel clock ?). At
least, now it works on all machines, which was not the case previously.
My rsync tree contains the same kernel as Paul's latest stable tree with
a backport of 2.3.x current aty128fb with your changes (and other pismo
powerbook support stuffs). I didn't add Ani Joshi patches yet.
I'll post pre-compiled once I feel the pismo stuffs are clean enough (and
there's another problem with the latest aty128, sometimes, I've seen some
erase problems in console mode. Not very important, but...). I'll then
merge my stuffs in 2.2.x and 2.3.x bk trees.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-21 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 9:44 patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128 Michel Danzer
2000-03-15 11:13 ` Michael Schmitz
2000-03-15 14:09 ` Kostas Gewrgiou
2000-03-21 2:33 ` Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros Kevin Hendricks
2000-03-21 5:04 ` anthony tong
2000-03-21 11:11 ` Benjamin Herrenschmidt [this message]
2000-03-21 16:56 ` Kostas Gewrgiou
2000-03-21 17:23 ` anthony tong
2000-03-21 17:52 ` Geert Uytterhoeven
2000-03-21 19:08 ` Kostas Gewrgiou
2000-03-21 19:39 ` Kevin B. Hendricks
2000-03-21 20:06 ` Kevin B. Hendricks
2000-03-21 17:26 ` Kevin B. Hendricks
2000-03-21 19:00 ` Kostas Gewrgiou
2000-03-22 16:49 ` Gabriel Paubert
2000-03-23 4:46 ` Some issues to resolve with XFree 4.0 yet Kevin Hendricks
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=20000321121120.009795@mailhost.mipsys.com \
--to=bh40@calva.net \
--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).