From: Jeremy Fitzhardinge jeremy@sour.sw.oz.au
Subject: #9 GXE64 support
Date: Tue, 8 Aug 1995 01:47:34 -0400 [thread overview]
Message-ID: <19950808054734.WkWMnnKDpzAt7IHaEHN2xhyaBCdNKAVi_wqoOc099-o@z> (raw)
jmk@plan9.att.com:
> my suspicion is that aux/vga is not switching over to 2x8-bit mode for the
> higher clock rates when it can, we've never played with any resolution
> requiring a clock between 80MHz and 135MHz.
>
> please post your parameters.
This is how XFree86 detects my card:
# XF86_S3 -probeonly
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: MouseSystems, device: /dev/mouse, baudrate: 1200
(**) S3: Graphics device ID: "#9GXE64"
(**) S3: Monitor ID: "MX17FG"
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/"
(**) S3: Option "number_nine"
(--) S3: card type: PCI
(--) S3: chipset: 864 rev. 0
(**) S3: chipset driver: mmio_928
(**) S3: videoram: 2048k
(--) S3: Detected an ATT 20C498/21C498 RAMDAC
(--) S3: Ramdac type: att20c498
(**) S3: Ramdac speed: 135
(**) S3: Using ICD2061A programmable clock
(--) S3: Maximum allowed dot-clock: 135.000 MHz
(**) S3: Mode "1184x888@100": mode clock = 100.000
(**) S3: Mode "1152x864@90": mode clock = 90.000
(**) S3: Mode "1024x768": mode clock = 75.000
(**) S3: Mode "800x600": mode clock = 50.000
(**) S3: Mode "640x480": mode clock = 25.000
(--) S3: Using 8 bits per RGB value
(--) S3: Virtual resolution set to 1184x888
Here's the relevent details from /lib/vgadb:
ctlr
0xC0094="#9-864" # #9GXE64
0xC0044="Phoenix S3 Vision864 (16Bit DAC)" # GIS Globalyst 550
link=vga
hwgc=s3hwgc
ctlr=vision864 link=ibm8514
ramdac=att21c498-135
clock=icd2061a link=s3clock
# From XFree86 config file:
# ModeLine "1184x888" 100 1184 1216 1576 1608 888 891 903 928
include = 1184x888@67Hz
clock=100
shb=1216 ehb=1576 ht=1608
vrs=891 vre=903 vt=928
#
# MAG MX17FG
# Horizontal timing:
# Allowable frequency range: 30-64KHz
# Vertical timing:
# Allowable frequency range: 50-120Hz
# Video bandwidth:
# 120MHz monitor
mag17fg = 1184x888x8
include=1184x888@67Hz
mag17fg = 1184x888x4
include=1184x888@67Hz
mag17fg = 1184x888x1
include=1184x888@67Hz
# ModeLine "1152x864@90" 90 1152 1184 1496 1528 864 867 876 900
#mag17fg = 1152x864x1
# clock=90
# shb=1184 ehb=1496 ht=1528
# vrs=867 vre=876 vt=900
# ModeLine "1152x864@80" 80 1152 1160 1384 1480 864 867 876 900
mag17fg = 1152x864x1
clock=80
shb=1160 ehb=1384 ht=1480
vrs=867 vre=876 vt=900
mag17fg
alias=multisync75
next reply other threads:[~1995-08-08 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-08 5:47 Jeremy [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-08 20:26 jmk
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=19950808054734.WkWMnnKDpzAt7IHaEHN2xhyaBCdNKAVi_wqoOc099-o@z \
--to=9fans@9fans.net \
/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).