From: Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: 1 line kernel patch and new Xpmac now works on new sawtooth G4s !
Date: Mon, 13 Mar 2000 11:29:17 -0500 (EST) [thread overview]
Message-ID: <200003131630.KAA28738@lists.linuxppc.org> (raw)
Hi,
By changing the constants.xclk value to 0x36d5 in the stable kernel aty128fb.c
and running a slightly modified Xpmac that recognizes the Rage128Pro graphics
card (id 0x5046) I now have nicely working Rage 128 acceleration.
There is still a problem using just the OF frame buffer device in place of the
modified aty128fb video driver that I will look at later.
If anyone wants the aty128fb.c diff and/or a binary Xpmac.special (the source is
at at home but coming tomorrow!), just let me know and I will post them.
The XF 4.0 R128 driver still has yet to be fixed (the defaults used in place of
the rom bios probe matched the old aty128fb.c xclk value and not the new ones.
So no more split vertical panes under new G4 machines!
Hooray I can finally do something at over 8bpp!
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
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-13 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 16:29 Kevin_Hendricks [this message]
[not found] ` <v03110703b4f2f052a0bc@[129.100.29.243]>
2000-03-13 20:58 ` 1 line kernel patch and new Xpmac now works on new sawtoothG4s ! Nelson Abramson
2000-03-13 21:14 ` Kevin B. Hendricks
2000-03-14 1:48 ` 1 line kernel patch and new Xpmac now works on newsawtoothG4s ! Nelson Abramson
-- strict thread matches above, loose matches on Subject: below --
2000-03-13 19:24 1 line kernel patch and new Xpmac now works on new sawtooth G4s ! Kevin B. 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=200003131630.KAA28738@lists.linuxppc.org \
--to=khendricks@admin.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).