Date:	Wed, 30 Mar 94 13:08:53 CST
From:	michaels AT vsl DOT com DOT AU (Michael Snoswell)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: vesadrv.vdr (GRX1.03) problem

> > 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.

I too had this problem with a Cirrus card. I ended up using one of the 2 Cirrus
drivers and it worked fine (in 640x480x256 mode).

cheers
	Michael Snoswell

- Raw text -