From: anthony tong <atong@uiuc.edu>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: Kevin Hendricks <khendricks@ivey.uwo.ca>,
Benjamin Herrenschmidt <bh40@calva.net>,
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 11:23:55 -0600 [thread overview]
Message-ID: <20000321112355.A5368@rogue.genunix.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0003211716210.18439-100000@idd-01.imbc.gr>; from gewrgiou@imbc.gr on Tue, Mar 21, 2000 at 06:56:25PM +0200
Kostas Gewrgiou (Tue, Mar 21, 2000 at 06:56:25PM +0200):
> From the patches i see that the reference freq is still assumed to be
> 29.50Mhz
> /* Assume REF clock is 2950 (in units of 10khz) */
> /* and that all pllclk must be between 125 Mhz and 250Mhz */
> pll->reference_freq = 2950;
> pll->min_pll_freq = 12500;
> pll->max_pll_freq = 25000;
>
> From the comments in the xfree driver (and the ati docs) this isn't always
> true:
> /* These probably aren't going to work for
> the card you are using. Specifically,
> reference freq can be 29.50MHz,
> 28.63MHz, or 14.32MHz. YMMV. */
I think that we can assume a 29.50 clock *for now*; lower clocks are
probably for future low powered/mobile versions of the chip.
> #ifdef __powerpc__ for this it should be better to see if the card has
> an OF or BIOS rom first since that will allow people to keep using cards
> with bios roms under ppc (i wonder if anyone is doing this)
> Any ideas on how we can check if a card has OF or BIOS roms ?
this is from memory (probably from the mach64 days): Bit 0 of the
PCI configuration register 0x30 is 0 if a PC style BIOS doesn't
exist. So we could do a check for that instead if this is verified
to still be true.
-at
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-21 17:23 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
2000-03-21 16:56 ` Kostas Gewrgiou
2000-03-21 17:23 ` anthony tong [this message]
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=20000321112355.A5368@rogue.genunix.net \
--to=atong@uiuc.edu \
--cc=bh40@calva.net \
--cc=gewrgiou@imbc.gr \
--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).