From: jmk@plan9.att.com jmk@plan9.att.com
Subject: #9 GXE64 support
Date: Tue, 8 Aug 1995 16:26:51 -0400 [thread overview]
Message-ID: <19950808202651.qRBy8j43S9ZZ4PtmIQLGGJuKVjxmWNHw8ldB2bDQyr0@z> (raw)
i've lowered the threshold at which the att21x498 ramdac decides to use 2x8-bit mode
which should fix the problem. there's a new aux/vga and vgadb available in the pcdist
directory for pick-up by ftp. use at your own risk (i'd keep a copy of the old one
around...).
there are some other changes in the new version:
support for #9GXE64pro;
add trivial ctlr entry for att20c490 ramdac and tweak
ramdac 'magic access' code;
lower threshold at which att21c498 will use 2x8-bit mode to > 80MHz;
add "-e" and "-k tables for the Chrontel CH9294 clock generator and
look for clock-divisors on the CH9294 and ICS2494 if asked for (ET4000);
change BIOS id string for the Hercules Dynamite Power PCI and add ctlr entry
for the ISA version.
next reply other threads:[~1995-08-08 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-08 20:26 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-08 5:47 Jeremy
1995-08-07 13:55 jmk
1995-08-07 10:05 Jeremy
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=19950808202651.qRBy8j43S9ZZ4PtmIQLGGJuKVjxmWNHw8ldB2bDQyr0@z \
--to=jmk@plan9.att.com \
/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).