From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] VGA Hell, what else?! From: forsyth@caldo.demon.co.uk MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-fmpgsrkglyotihiujdlpgmsrya" Message-Id: <20001207095517.67AF0199DD@mail.cse.psu.edu> Date: Thu, 7 Dec 2000 09:56:02 +0000 Topicbox-Message-UUID: 366b0ad2-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-fmpgsrkglyotihiujdlpgmsrya Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit in general, without the documents for the precise chips you've got, you stand no chance of working with the vga code, not because it doesn't use symbolic names, but because even then you'll have no idea what the interpretation is, unless you also copy the contents of each manual's register description into the code as well. different register numbers are used differently by SVGA implementations, and in particular, ET4000 bears no resemblance to S3 in the chip-dependent set (even within the S3 range you need the chip-specific books). with the book to hand (which as i've said you need anyway), for my own part, i find the use of numbers eliminates a trip to the index for each one. i suspect there's not a standard naming scheme even for the common (ha!) subset that's VGA. in fact, even with the documents for the precise chip, you've still got your work cut out (in general, probably not in the case you mention). >>I'm suffering from dreadful flicker trying to use 1024x768x8 on a i find that sometimes happens to me when i drink too much, which happens (funnily enough) each time i've had to work with svga. --upas-fmpgsrkglyotihiujdlpgmsrya Content-Type: message/rfc822 Content-Disposition: inline Received: from tele-punt-22.mail.demon.net ([194.217.242.7]) by lavoro; Thu Dec 7 09:31:03 GMT 2000 Received: from punt-2.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk id 976177462:20:01375:3; Thu, 07 Dec 2000 08:24:22 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-2.mail.demon.net id aa2001306; 7 Dec 2000 8:24 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 292C919A01; Thu, 7 Dec 2000 03:24:08 -0500 (EST) Received: from cackle.proxima.alt.za (cackle.proxima.alt.za [196.30.44.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1CB1C199E8 for <9fans@cse.psu.edu>; Thu, 7 Dec 2000 03:23:40 -0500 (EST) Received: (from lucio@localhost) by cackle.proxima.alt.za (8.9.3/8.9.1) id KAA20286 for 9fans@cse.psu.edu; Thu, 7 Dec 2000 10:23:35 +0200 (SAST) From: Lucio De Re To: 9fans mailing list <9fans@cse.psu.edu> Message-ID: <20001207102332.A20270@cackle.proxima.alt.za> Mail-Followup-To: 9fans mailing list <9fans@cse.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us Subject: [9fans] VGA Hell, what else?! Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: lucio@proxima.alt.za List-Help: List-Post: List-Subscribe: , List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: Date: Thu, 7 Dec 2000 10:23:34 +0200 I'm suffering from dreadful flicker trying to use 1024x768x8 on a multisync65, mostly because 1024x768x8i is utterly broken. I'm using what seems an old S3Virge/Diamond Stealth Pro. I've hacked bits of "vga", if only to see what would happen, but the results have been unpromising, no doubt because I've been using some old ET 4000 documentation, inappropriate to the task. So, two things: does anyone know where I can find S3 docs and would it help any if I went to the trouble of relabelling all the register numbers with what cobol programmers used to call "figurative constants" (should that be all capitals, perhaps?) in the sys/src/cmd/aux/vga directory? I'm half hoping for a resounding "no" to the second question :-) ++L --upas-fmpgsrkglyotihiujdlpgmsrya--