delorie.com/archives/browse.cgi | search |
From: | jb3207 AT eclipse DOT co DOT uk (Jason Barstow) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: VESA DoubleBuffer flicker and SetGetDisplayStart func 0x07h |
Date: | Sun, 02 Mar 1997 10:43:23 GMT |
Organization: | Jabber Interactive |
Lines: | 16 |
Message-ID: | <5fblr1$a0r@news.cableinet.net> |
References: | <5f77ph$bf8 AT news DOT cableinet DOT net> <aI4FlBBCW2FzEw+5 AT talula DOT demon DOT co DOT uk> |
Reply-To: | jb3207 AT eclipse DOT co DOT uk |
NNTP-Posting-Host: | 195.188.32.68 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk> wrote: >Are you waiting for the retrace? (setting the 0x80 flag in %bl). If not, >some cards will flicker because VESA will return instantly from the >scroll function, while the display hardware doesn't actually update its >status until the next retrace. Yes I'm doing this, mmmm I'll just check my code ;) Perhaps the VESA2.0 implementation for my card isn't 100%. Maybe an explicit wait for VR instead of passing 0x80 will do the trick. Thanks . 'later, Jason.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |