linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Help! Getting aty128fb.c to work with newest sawtooth machines
Date: Sat, 11 Mar 2000 09:38:39 -0500	[thread overview]
Message-ID: <00031109361000.07471@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0003060013070.30614-100000@idd-01.imbc.gr>


Hi Kostas,

If just received a G4 450 but if I try to use aty128fb.c in any resolution
higher than 1024x768 8bpp it will fail miserably with the screen split into 3
vertical panes.

If I try blindly launching xf 4.0 r128, it inherits the fb mode and I end up
with 3 panes as well.

This is obviously a aty128fb.c problem since it occurs in the console.

I looked at Anthony's code (remember the problem I had earlier when he tried to
read values for the dotclock and xclk out of the of device tree?) and then used
lsprop to print out the graphics card info.

Unfortunately, there were no nice of-tree variables in my G4 tree at all but it
did report my card as a Rage128Pro and not a simple Rage128.

Is a Rage128Pro different from a Rage128 when it comes to setting it up,
register usage, etc or is this simply a problem with the default timings
setting being incorrect for this card?

Interestingly enough, I can boot with aty128fb with 1024x768 and 8bpp and the
console is fine (no 3 panes) and I can then successfully start up XFree4.0 with
r128 acceleration so things do appear to be working under some cases.

Is there any tool (code piece, etc) I can use to probe the timing info as used
under MacOS?

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/

  parent reply	other threads:[~2000-03-11 14:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0003041753480.1870-100000@idd-01.imbc.gr>
2000-03-04 18:55 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-05 13:42   ` Michel Dänzer
2000-03-05 16:43     ` Kostas Gewrgiou
2000-03-05 16:58       ` Kevin B. Hendricks
2000-03-05 21:04         ` Kostas Gewrgiou
2000-03-05 21:20           ` Geert Uytterhoeven
2000-03-05 22:25             ` Kostas Gewrgiou
2000-03-06  6:54               ` Geert Uytterhoeven
2000-03-09  3:11               ` Kevin Hendricks
     [not found]                 ` <38C7A016.8C2ED4C8@iiic.ethz.ch>
     [not found]                   ` <v03110701b562ab7246aa@[129.100.29.243]>
2000-03-10 15:33                     ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 Kevin B. Hendricks
2000-03-10 17:25                       ` Kostas Gewrgiou
2000-03-10 18:17                         ` Kevin B. Hendricks
2000-03-10 19:21                           ` Michael Schmitz
2000-03-10 23:54                             ` patch to get latest XFree 4.0 snapshot (xf3918) to work on ppcwithr128 Michel Dänzer
2000-03-11 14:50                               ` Michael Schmitz
2000-03-12 14:52                                 ` patch to get latest XFree 4.0 snapshot (xf3918) to work onppcwithr128 Michel Dänzer
2000-03-10 19:43                       ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 David A. Gatwood
2000-03-11 14:38               ` Kevin Hendricks [this message]
2000-03-13  9:19                 ` Help! Getting aty128fb.c to work with newest sawtooth machines Kostas Gewrgiou
2000-03-14  1:12               ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-09  2:41           ` Kevin Hendricks
2000-03-09 11:04             ` 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=00031109361000.07471@localhost.localdomain \
    --to=khendricks@ivey.uwo.ca \
    --cc=geert@linux-m68k.org \
    --cc=gewrgiou@imbc.gr \
    --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).