From fnaumann@mail.cs.uni-magdeburg.de Tue Dec 2 10:01:30 2003 Date: Tue, 2 Dec 2003 09:54:54 +0100 (CET) From: Standa Opichal To: highwire@atari-users.net cc: MiNT Mailing List , ARAnyM devel mailing list Subject: [MiNT] NVDI compatibility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: opichals@seznam.cz Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Hi All! This is a bit off-topic... I know. I've been trying to help my friend to run Highwire on TT+ImagineGfx where I met some problems with Imagine gfx card and I don't really know how the newer NOVA VDI behaves. I know about 2 widely used VDI functions that are not present in all VDI implementations in use (vq_scrninfo() and vqt_xfntinfo()). It is also used in the xg (X server for GEM)... The real solution is to use some more suitable VDI for that. But that would require to write the native driver for those cards which might not be that straightforward. ;) Is there a will to write an emulation layer for these (and possibly other VDI functions) so that they would return valid results on the mentioned cards and VDI implementations? Or should we support also non NVDI implementations within our applications and therefore add such emulation layer/fallback to an old VDI which might not provide enough information? best regards STan