Xref: news2.mv.net comp.os.msdos.djgpp:3575
From: Shawn Hargreaves <slh100 AT york DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GRX 2.0 Docs
Date: Wed, 8 May 1996 11:29:16 +0100
Organization: The University of York, UK
Lines: 24
Message-ID: <Pine.SGI.3.91.960508110505.14390B-100000@tower.york.ac.uk>
NNTP-Posting-Host: tower.york.ac.uk
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <Pine.SGI.3.91.960507110634.3252A-100000@chinook.physics.utoronto.ca>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Tue, 7 May 1996, Peter Berdeklis wrote:

> I've looked at Allegro and it's very good and could do every thing I 
> need, but there aren't enough drivers for it.  Does anyone know where I 
> could find Allegro drivers?

Write some :-) Or sort out some way of testing them, and I'll write them. 
There isn't usually much code in a graphics driver (SVGA cards are all 
pretty similar) but there is no point in my writing things I can't test. 
If you can get hold of a card for testing, I'd be happy to attempt some 
code for it...

Or you could just use VESA. The VESA 1.x standard is a lot slower than a 
hardware level driver, because it requires a switch to real mode every 
time I change banks, but VESA 2.0 avoids that. Even if your card doesn't 
support the linear framebuffer modes, VESA 2.0 is as fast as native code.


/*
 *	Shawn Hargreaves.        Why is 'phonetic' spelt with a ph?
 *	Check out Allegro and FED on http://www.york.ac.uk/~slh100/
 */