<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Wojtek<div><br></div><div>As you can see here: <a href="http://tinyvga.com/vga-timing">http://tinyvga.com/vga-timing</a> there are different possible timings per given resolution.</div><div>If you go higher you flicker less but steal more memory bandwidth available to the RISC5 CPU. If you go lower you flicker more but leave more memory bandwidth to the CPU.<br><br>As the CPU frequency is 25 MHz, generating 75 MHz pixelclock is much easier. But with the FPGA clock generator it‘s easily possible to generate 65 MHz (multiply 25 MHz by 13 divide by 5)</div><div><br></div><div>For my color display, I chose the following timing:</div><div><a href="http://tinyvga.com/vga-timing/800x600@60Hz">http://tinyvga.com/vga-timing/800x600@60Hz</a></div><div>with 40 MHz pixelclock. I could have chosen even a pixelclock of 36 MHz...</div><div><br><div dir="ltr">br<br><div>Jörg</div></div><div dir="ltr"><br><blockquote type="cite">Am 18.12.2019 um 04:41 schrieb Skulski, Wojciech <skulski@pas.rochester.edu>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Magnus:</span><br><span></span><br><span> thank you. This was very helpful. I did not realize that XGA is different from VESA. The numbers in VID.v look more like XGA than VESA. So it is an XGA display with VESA frequency. The difference is minor, though. The monitors are somehow capable of absorbing the discrepancy, which affects only the horizontal scan. The vertical scan is the same for both VESA and XGA. The number on the left are for VESA.</span><br><span></span><br><span>//Back porch 144 (160 pixels for XGA @ 60 Hz)</span><br><span>//Whole line 1328 (1344 pixels for XGA @ 60 Hz)</span><br><span></span><br><span>Thank you,</span><br><span>Wojtek</span><br><span></span><br><span></span><br><span></span><br><span>________________________________________</span><br><span>From: Oberon [oberon-bounces@lists.inf.ethz.ch] on behalf of Magnus Karlsson [magnus@saanlima.com]</span><br><span>Sent: Tuesday, December 17, 2019 7:53 PM</span><br><span>To: oberon@lists.inf.ethz.ch</span><br><span>Subject: Re: [Oberon] XGA frequency in FPGA Oberon</span><br><span></span><br><span>See tinyvga.com/vga-timing/1024x768@70Hz</span><br><span></span><br><span>My guess is that with 25 MHz CPU clock it's a lot easier to generate 75</span><br><span>MHz than 65 MHz.</span><br><span></span><br><span>Magnus</span><br><span></span><br><span>On 12/17/2019 4:31 PM, Skulski, Wojciech wrote:</span><br><blockquote type="cite"><span>All:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>we have been playing with the FPGA Oberon firmware and we are puzzled with the peculiar 75 MHz frequency driving the display in Pepino. It actually works with the monitor which we have. People are saying on the web that XGA clock is 65 MHz. See tinyvga.com/vga-timing/1024x768@60Hz</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>NW in his PO.Computer says on page 19 that the frequency should be 56 MHz, rounded up to 60 MHz. So all these numbers are different, 56, 60, 65, and 75 MHz. Does anyone know why? And which one is right?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thank you,</span><br></blockquote><blockquote type="cite"><span>Wojtek</span><br></blockquote><span>--</span><br><span>Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems</span><br><span>https://lists.inf.ethz.ch/mailman/listinfo/oberon</span><br></div></blockquote></div></body></html>