On Wed, Dec 11, 2002 at 11:42:23PM +0100, Juliusz Chroboczek wrote: > This is fixed in upstream CVS. It is due to the 4.2 version of the > Savage driver mis-detecting the video memory size. > > A workaround is to set the size in your XF86Config-4 explicitly using > the VideoRam keyword. A proper solution is to remove the code that > (mistakenly) probes for the memory size using the VESA BIOS in > SavagePreInit in savage_driver.c.
I have a fix pending for 4.2.1-5:
* patch #000_stolen_from_HEAD_savage_driver: new
+ Fixed memory leaks in S3 Savage driver (Egbert Eich).
+ Savage driver updates (#5203, Tim Roberts).
+ [...] xf86SetOperatingState() call cleanups in most drivers
(Marc La France).
+ Savage driver updates.
- Support for ProSavage DDR (PCI ID 0x8D04)
- TV output fixes
- support for -pixmap24 flag
- XAA fixes to cure lockups
(#5412, Tim Roberts).
+ Fix Mono8x8 code in savage driver, needed ROP_NEEDS_SOURCE, also
add NO_PLANEMASK to ScreenToScreen as code doesn't handle that case
(Alan Hourihane).
+ Remove "Option VideoRam" from savage driver, there's no need for
it, and utilize the entities given VideoRam size (Alan Hourihane).
--
G. Branden Robinson | A committee is a life form with six
Debian GNU/Linux | or more legs and no brain.
[EMAIL PROTECTED] | -- Robert Heinlein
http://people.debian.org/~branden/ |
msg05139/pgp00000.pgp
Description: PGP signature
