From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 28 Aug 1997 19:42:00 +0100
From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] diamond 3D 3400
Topicbox-Message-UUID: 60497506-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19970828184200.jl0vZCGakHeUxnO2pBB2cvyP6TZDD2UOXWnNNa5_fzw@z>

>>> Diamond Stealth 3D 3400.
>>At which resolution did you test it?

640x480x1
1024x768x8
1152x900x8 (the one i'm using now)
1280x1024x8

one of the 640x480 modes did give odd results, come
to think of it; i think it was 640x480x8.  i don't know that i've
got the vgadb entries for much more than 1280x1024,
and that's compact enough on a 17" monitor.
i might try 1600x1400x8 tomorrow.

i use this vgadb entry with monitor=multisync135 (it's a Viewsonic PT775, and
quite nice too).

ctlr
	0xC0043="Stealth 3D 3000"		# Diamond Stealth 3D 3000/3400
	link=vga
	hwgc=s3hwgc
	ctlr=virge link=ibm8514 linear=1

you must have a version of /sys/src/9/pc/vgas3.c that does
the right thing to find the hardware cursor storage in linear mode but
i think that's part of another boddle.  if you haven't got that (yet),
remove linear=1.

other lines that are used for 1152x900x8 are

include = 1152x900@70Hz						# 72Hz, 67.9KHz
	clock=100
	shb=1184 ehb=1376 ht=1472
	vrs=900 vre=902 vt=940
	#hsync=- vsync=-

	...

multisync135 = 1152x900x8
	include=1152x900@70Hz
multisync135
	alias=multisync75