From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>, anthony tong <atong@uiuc.edu>
Cc: Benjamin Herrenschmidt <bh40@calva.net>, linuxppc-dev@lists.linuxppc.org
Subject: Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros
Date: Mon, 20 Mar 2000 21:33:10 -0500 [thread overview]
Message-ID: <00032021464800.00801@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0003151544550.3091-100000@idd-01.imbc.gr>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
Hi Kostas,
With lots of help from Ben, we were able to figure out that the OF values used
to initialize the Rage128 and Rage128Pro cards are the same ones used by the
MacOS and that we can actually read the X_MPLL_REF_FB_DIV value, the XCLK_CNTL,
and PLL_REF_DIV values and calculate the proper XCLK. In a similar way you can
calculate the MCLK value too so you can get or calculate almost all of the same
info as is probed from the Bios under x86 machines.
This allows both machines with G3s, and G4 (even with the Rage 128 cards) to
work with the same aty128fb.c kernel driver without any table lookups.
The patch to add this to the aty128fb.c is attached. I have also used
similar code to replace the bios code probe for powerpc in the r128_driver.c for
xf400. The patch to do that is also attached.
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).
Assuming they test out fine, Kostas would you see about getting the r128 patch
integrated into the next xf40X release while I see about getting Paul and/or
Anthony to integrate the aty128fb.c patch into both the stable and development
kernels.
Hopefully with these in place, new G4s will work as well as older G4s
and G3s.
Thanks!!!
Kevin
--
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario N6A-3K7 CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959
[-- Attachment #2: xf4_usepll.patch.gz --]
[-- Type: application/x-gzip, Size: 968 bytes --]
[-- Attachment #3: aty128fb_fix.patch.gz --]
[-- Type: application/x-gzip, Size: 899 bytes --]
next prev parent reply other threads:[~2000-03-21 2:33 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 ` Kevin Hendricks [this message]
2000-03-21 5:04 ` Patches to fix aty128fb and xf400 r128 to work with both Rage128 and Rage128Pros anthony tong
2000-03-21 11:11 ` Benjamin Herrenschmidt
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=00032021464800.00801@localhost.localdomain \
--to=khendricks@ivey.uwo.ca \
--cc=atong@uiuc.edu \
--cc=bh40@calva.net \
--cc=gewrgiou@imbc.gr \
--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).