Date: Tue, 29 Mar 94 17:17:19 EST
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To: S_Eckart AT lis DOT e-technik DOT tu-muenchen DOT de
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: vesadrv.vdr (GRX1.03) problem
Reply-To: babcock AT cfa DOT harvard DOT edu

> The VESA BIOS of this (Cirrus Logic True Color) VGA returns the list of video
> modes (to which VgaInfoBlock.VideoModePtr points) in the same 256 byte area
> as the VgaInfoBlock itself (in the reserved or unused part starting at offset
> 0x12). This list is then used by do_driver_init() to call VESAgetModeInfo for
> each mode. However, VESAgetModeInfo uses the same 256 byte area as
> VESAgetInfo and thus overwrites the list, still being in use.

I recently ran into the same problem (including vesainfo crashing), also with
a card based on the Cirrus Logic chipset, with the DISP image processing
package.  I reported the problem to the author of DISP; I suppose I should
have reported it here also.  Note that Ralph Brown's interrupt list documents
that some VESA cards will behave this way.