Re: aty128fb does not work in newer sawtooth machines

Re: aty128fb does not work in newer sawtooth machines

[Kevin Hendricks]

Hi,

Thanks for the info.  But unfortunately, my machine requires yaboot to even
boot at all.

I looked in aty128fb.c in the kernel and they hav hardwired defaults which I
can easily change but I need to know about timing info that Mac OS uses.

Do you know of any probe code or anything at all that can determine timing info
from the MacOS side of things.

>  On Sat, 11 Mar 2000, Brad Midgley wrote:
> it may be because the video driver is counting on some initialization by
> macos (bootx).
> this is the case with aty64 on the g3 laptop. video isn't right if you use
> yaboot but it's fine with bootx.


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


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

Re: aty128fb does not work in newer sawtooth machines

[Kevin Hendricks]

Hi,

Well from the of-device tree I have found out that my graphics card device id
is 0x5046 which equates to a Rage 128 Pro PF card.

Luckily the r128 driver in XFree 4.0 knows about this card and it is not
significantly different from the Rage128 RE card I have in my B+W G3.

I think the whole thing comes down to the default timing info being okay for
Rage128RE but not okay for RAGE128PF

 >  > I looked in aty128fb.c in the kernel
and they hav hardwired defaults which I > can easily change but I need to know
about timing info that Mac OS uses. >  > Do you know of any probe code or
anything at all that can determine timing info > from the MacOS side of things.

I will keep looking.

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.

Kevin


 >
> >  On Sat, 11 Mar 2000, Brad Midgley wrote:
> > it may be because the video driver is counting on some initialization by
> > macos (bootx).
> > this is the case with aty64 on the g3 laptop. video isn't right if you use
> > yaboot but it's fine with bootx.
>
>
> 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
>
>
--

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

Re: aty128fb does not work in newer sawtooth machines

[Ryuichi Oikawa]

Hi,

> Hi,
>
> Well from the of-device tree I have found out that my graphics card device id
> is 0x5046 which equates to a Rage 128 Pro PF card.
>
> Luckily the r128 driver in XFree 4.0 knows about this card and it is not
> significantly different from the Rage128 RE card I have in my B+W G3.
>
> I think the whole thing comes down to the default timing info being okay for
> Rage128RE but not okay for RAGE128PF
 PLL Timing probe is one of TODO things accordinig to the notes by Anthony, IIRC.
So it is normal that display FIFO isn't optimally set up other than the card of
ref.clock=29.5MHz, vram bus width/clock=128bit/75MHz and the same type of SGRAM,
that can cause screen split, snowing, blank screen, etc. to the high clock cards
and especially to the 64bit vram bus card(ex. iMacDV).

>  >  > I looked in aty128fb.c in the kernel
> and they hav hardwired defaults which I > can easily change but I need to know
> about timing info that Mac OS uses. >  > Do you know of any probe code or
> anything at all that can determine timing info > from the MacOS side of things.
>
> I will keep looking.
>
> 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)
...............................
RF,XCLK          00001d4d (7501)
RF,MCLK          00001d4d (7501)
RF,VCLK          000059a6 (22950)
RF,REF           00000b86 (2950)
...............................

You can put your own values to aty128fb, or more simply, try to read DDA_CONFIG/
DDA_ON_OF registers when offb is running and directly write these values when
aty128fb is running, if it works or not.
 Also, I guess XFree86 3.9 or 4.0 should run without aty128fb as far as PLL/SGRAM
timings are set up correctly, but I don't have time to try...


Regards,

Ryuichi Oikawa
roikawa@rr.iij4u.or.jp

PS. Please don't forget to build the (a)-(c) for Robert.

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

Re: aty128fb does not work in newer sawtooth machines

[Kevin Hendricks]

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/

aty128fb does not work in newer sawtooth machines

[Kevin B. Hendricks]

Hi,

I just received last week a new G4 at 450Mhz.  I have been trying various
things to get the video working properly to no avail.

If you use yaboot and boot with the following arguments:
video=aty128fb:vmode:17

then you get a working 1024x768 video at 8bpp

If you however try anything else at higher depths you end up with a screen
that is split into 3 vertical panes that make it impossible to use.

For example:

video=aty128fb:vmode18,cmode:32

which works fine on my B+W G3 immediately gives the three panes in console
mode.

The same problems exist in both Xpmac and XFree86 3.9.18.

Solutions anyone?

Thanks,

Kevin


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

Re: aty128fb does not work in newer sawtooth machines

[Nelson Abramson]

"Kevin B. Hendricks" wrote:

> If you however try anything else at higher depths you end up with a screen
> that is split into 3 vertical panes that make it impossible to use.
> <snip>
> The same problems exist in both Xpmac and XFree86 3.9.18.

The problems exist on sawtooths, imacs (and I think ibooks).

The problem exists in the console too, so I think it has to do w/ the kernel
ati128fb driver rather than the X server.

Waiting hopefully for a solution
--Nelson Abramson

--
Shouldn't people be arrested and persecuted for engaging in their
constitutional rights?  http://www.opendvd.org


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