linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Hendricks, Kevin" <khendricks@ivey.uwo.ca>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: "Hendricks, Kevin" <khendricks@ivey.uwo.ca>,
	Josh Huber <huber@mclx.com>,
	Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual head r128
Date: Thu, 12 Oct 2000 10:30:17 -0400	[thread overview]
Message-ID: <200010121430.JAA21005@lists.linuxppc.org> (raw)


Hi Kostas,

> If the main clock rate is different, as long as
> > you can find out what it is, reading and calculating the  timings from
> > those register settings really should work generically, shouldn't it?

> The reference frequency isn't the same in all cards, your patch assumes that
>   /* Assume REF clock is 2950 (in units of 10khz) */
>   /* and that all pllclk must be between 125 Mhz and 250Mhz */

Yes, that is what I was referring to above.  That info is generally available in the card docs.  Ben has a whole set of ref clock rates for all the ati cards shipped under mac or clones.  I also have that info and could easily look up the card id to set it for macs in general.

>   /* 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. */

You can actually use info on the pllclk constraints to rule out the 14.32Mhz cases from the other two cases and then you are left with only 2 to try.

A lookup table would certainly do the trick if the user did not want to simply  use trial and error.  Anything would be better than the complete hard coded values set in the XF 4.0 source.

Perhaps a better idea is allow the REF clock rate to be passed as a parameter in the XF86Config file (much like the video memory parameter and bus ids passed now) for people to have control over if need be.   This value would then only be used if the bios test failed and then in place of the hardcoded values so that my pll register probing routine would be actually work.  A desperate user could then try each of the 3 values until he/she saw something they liked on the screen.

> Most of the ppc r128 cards have a reference frequency of 29.50MHz so the
> code works but i heard that some of the new ones have different reference
> freq.

Yes, there is one new card (of the r128 variety) on Ben's list that does not use the 2950 ref clock value.

Since he has a bios on a ppc card it would be interesting to see the results of some "bios present?" tests to help determine if a bios is really there or not.  The current test sometimes passes on macs without a bios (possibly OF rom?) and garbage values are returned.

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-10-12 14:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-12 14:30 Hendricks, Kevin [this message]
2000-10-12 16:11 ` dual head r128 Kostas Gewrgiou
2000-10-12 17:22   ` Michel Dänzer
2000-10-12 17:44     ` Kostas Gewrgiou
2000-10-12 21:25       ` Michel Dänzer
2000-10-13 15:26         ` Kostas Gewrgiou
2000-10-13 16:21       ` Geert Uytterhoeven
     [not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47   ` Michel Lanners
2000-10-14 10:13     ` Benjamin Herrenschmidt
2000-10-14 10:21   ` Geert Uytterhoeven
     [not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
     [not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
  -- strict thread matches above, loose matches on Subject: below --
2000-10-12 16:25 Hendricks, Kevin
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-11 18:17 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52   ` Josh Huber
2000-10-11 19:04     ` Tom Rini
2000-10-11 19:09     ` Michel Dänzer
2000-10-11 19:26       ` Josh Huber
2000-10-11 22:48         ` Michel Dänzer
2000-10-13 17:16           ` Josh Huber
2000-10-12 13:09     ` Kostas Gewrgiou
2000-10-12 15:13       ` Benjamin Herrenschmidt
2000-10-12 15:49         ` Gabriel Paubert
2000-10-12 16:40           ` David Edelsohn
2000-10-17  0:12           ` Paul Mackerras
2000-10-17  5:56             ` Michel Lanners
2000-10-17 10:41             ` Benjamin Herrenschmidt
2000-10-17 13:45               ` Geert Uytterhoeven
2000-10-17 17:17                 ` Benjamin Herrenschmidt
2000-10-12 16:44         ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert

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=200010121430.JAA21005@lists.linuxppc.org \
    --to=khendricks@ivey.uwo.ca \
    --cc=gewrgiou@imbc.gr \
    --cc=huber@mclx.com \
    --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).