9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] More Mach64 Problems
Date: Mon, 19 Nov 2001 12:15:11 -0500	[thread overview]
Message-ID: <20011119171514.3FF3D1998A@mail.cse.psu.edu> (raw)

The problem is in fact the memory timings, but it's ever so difficult
to figure out the exact bits without sitting there at the machine.
(It's basically trial and error, which is much harder when it takes a
day or two to do a round trip.)

There's some code in /sys/src/cmd/aux/vga/mach64xx.c that handles
sniffing the card and trying to get the timings set right, but it
appears to fail on some cards, including apparently yours.
If you're game, I can tell you how to tweak the registers and
you can sit there poking bits until it works, but it's really an
open-ended process: sometimes you get it, sometimes you don't.
It will help a lot if you have graphics working on this system in
some other operating system that lets you poke at the VGA card,
to read out a working register dump.  Such systems include Windows 9x,
Linux, and FreeBSD but not Windows NT or 2000.

I tried to help someone via email with this Mach 64 problem a month
ago and it just didn't work, even with working register dumps to
compare against.

In the case of the person with the similar S3 problem, that was more
easily fixed because the S3 chipset handles most of those calculations
for you.  We just had to add the card type to the driver.

Russ



             reply	other threads:[~2001-11-19 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 17:15 Russ Cox [this message]
2001-11-19 17:23 ` Cameron Morland
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22 20:25 Russ Cox
2001-11-22 20:13 Richard Miller
2001-11-22 19:10 Russ Cox
2001-11-22 19:06 Richard Miller
2001-11-15 18:07 Cameron Morland
2001-11-15 20:47 ` Dan Cross
2001-11-16  9:50 ` Matt Senecal
2001-11-19  9:58 ` bcrawford

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=20011119171514.3FF3D1998A@mail.cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).