Just wanted to pipe in as a user of the card... not that it matters all that much :)
10Hz refresh for common text modes in 'VGA compatibility mode' would be more than acceptable... The card will have 100% free highly optimized drivers available eventually, for X and framebuffer (and likely Win32 etc.) so VGA likely won't be used even during most linux installations (they mostly use fb), or on the console (fb again) or in X... the only real example I can think of is DOS (FreeDOS -- I still use it to flash BIOSs) and the Windows splash screen. 10Hz is fine for those. --tim On 5/28/05, Viktor Pracht <[EMAIL PROTECTED]> wrote: > Am Samstag, den 28.05.2005, 12:49 -0400 schrieb Timothy Miller: > > > > Now for the math. Timothy said to expect a 20 clock delay for random > > > access to card memory. I'm going to assume that is 20 clocks in the > > > 200Mhz domain. > > > > No. I'm assuming a large part of that delay comes from synchronizing > > FIFOs between clock domains. > > Why does the VGA controller have to run at a different clock rate than > the memory controller? > > > Furthermore, I'm assuming a row miss in > > the memory controller, and numberous other delays. > > Can the VGA controller get a more direct access to the cache and/or > VRAM? Direct enough to be able to predict when the results of a read > arrive? > > > - Viktor Pracht > > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
