From: "Eric Dorman" <edorman@san.rr.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: S3 775/325
Date: Sat, 17 Jun 2000 23:30:50 -0700 [thread overview]
Message-ID: <001a01bfd8ee$bf9df740$8105d2cc@san.rr.com> (raw)
In-Reply-To: <8idb8s$1oq8$2@pandora.alkar.net>
----- Original Message -----
From: "Wladimir Mutel" <mwg@alkar.net>
To: <9fans@cse.psu.edu>
Sent: Friday, June 16, 2000 6:57 AM
Subject: [9fans] Re: S3 775/325
> Oscar Gala <proto@phatspace.org> wrote:
> > I have a S3 Trio64 videocard with the 86C775 chipset and a S3 Virge
> > with the 86C325 Chipset,
> > but I can't get them to work with the Plan9 installation.
> 86c775/86c785 (Trio64V2) works. I just added such line (marked with
> +) in /lib/vgadb (and before, in vgadb on boot diskette):
[xx]hi,
Gotta be careful here, because an 86C775 isin't quite a Trio64
but has some more regs that might have to be filled in. An example
is the C775 on the HP Vectra VL5/166. On that box regs
0x90 and 0x91 didn't get filled in correctly, resulting in the
left half of the display repeated twice. I did the following:
init:
vga->crt[0x90] = 0x0;
vga->crt[0x91] = 0x7F;
load:
vgaxo( Crtx, 0x90, vga->crt[0x90] );
vgaxo( Crtx, 0x91, vga->crt[0x91] );
looking over the docs today leads me to think that 0x90
is sufficient.
The BIOS string is also different (ah, love HP sometimes).
vgadb:
0xC004E="86C775"
I have a true-blue Trio64 card to compare against to make
sure I get the correct identification so real regs get filled in,
then I'll generate a patch.
--eld
prev parent reply other threads:[~2000-06-18 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 9:11 [9fans] " Oscar Gala
2000-06-16 13:57 ` [9fans] " Wladimir Mutel
2000-06-18 6:30 ` Eric Dorman [this message]
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='001a01bfd8ee$bf9df740$8105d2cc@san.rr.com' \
--to=edorman@san.rr.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).