From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: Ryuichi Oikawa <roikawa@rr.iij4u.or.jp>
Cc: brad@turbolinux.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: aty128fb does not work in newer sawtooth machines
Date: Sun, 12 Mar 2000 12:25:43 -0500 [thread overview]
Message-ID: <00031212301701.00484@localhost.localdomain> (raw)
In-Reply-To: <20000313014927K.roikawa@rr.iij4u.or.jp>
Hi Ryuichi,
> > I am going to add this card to the Xpmac source so that it tries to use its
> > acceleration code simply on the straight OF frame buffer. If that works, then
> > I should be able to use Xpmac to get some of timing info.
> Yes, Xpmac should run by simply adding 'PF' to the probe list, but you don't
> need to run Xpmac since MacOS(and OF?) adds clock timing field to device-tree
> like as,
>
> /proc/device-tree/pci/ATY,Rage128y:
> name "ATY,Rage128y"
> vendor-id 00001002 (4098)
> device-id 00005245 (21061)
> ...............................
> RRF,XCLK 00001d4d (7501)
> RF,MCLK 00001d4d (7501)
> RF,VCLK 000059a6 (22950)
> RF,REF 00000b86 (2950)
> ...............................
If I boot my G4 in OF and use lsprop to dump the of-device tree, unfortunately,
none of the nice RF properties are there. So these properties must have been
added by MacOS but do not get written when yaboot is used to boot the machine.
Unfortunately, I can't use BootX to boot the newer sawtooths.
That means I will have to read these values from the MacOS side of things. Ben
H pointed me to the PCI DDK utility that dumps the device registry under MacOS
and I will give that a try tomorrow when I am at work.
> PS. Please don't forget to build the (a)-(c) for Robert.
Yes, I will build that this evening after my kids go to bed and I will post it
for Robert first thing tomorrow.
Take care,
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 prev parent reply other threads:[~2000-03-12 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.20.0003110820530.30663-100000@mail.turbolinux.com>
2000-03-11 16:54 ` aty128fb does not work in newer sawtooth machines Kevin Hendricks
2000-03-11 17:22 ` Kevin Hendricks
2000-03-12 16:49 ` Ryuichi Oikawa
2000-03-12 17:25 ` Kevin Hendricks [this message]
2000-03-10 16:45 Kevin B. Hendricks
2000-03-10 17:37 ` Nelson Abramson
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=00031212301701.00484@localhost.localdomain \
--to=khendricks@ivey.uwo.ca \
--cc=brad@turbolinux.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=roikawa@rr.iij4u.or.jp \
/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).