My opinion is that its good enough. We reduced the jitter by making some power supply modifications, using cleaner source oscillators and and changing how the clocks were generated inside the Spartan 3. DVI works without issue on the highest speed panels I could lay my hands on (single link 153MHz for 1920 x 1200 and 134MHz dual link 2560x1600). The analogue output looks clean on 1920 x 1200. I don't have a 2048 x 1536 CRT to test with, but the 1920 x 1200 looked clean enough for me to think it won't be a problem. I've not tested TV-out yet, but those signals are retimed with the clean clock generated inside the TV chip on the way out, so jitter should not be an issue.
On Tue, Mar 4, 2008 at 4:36 AM, Dieter <[EMAIL PROTECTED]> wrote: > > First off, we have two source clocks. One is 133MHz, the other is > > 156.25MHz. Select one with a mux. > > > > Next, we have a pre-divider that can divide the clock by any number > > between 1 and 128. Restrict the range of your divider so that its > > output is in the range of 1MHz to 6.875MHz (330/48). > > > > Next, we have the DCM that multiplies by 48. > > > > Finally, we have a post-divider that divides by 1, 2, 4, 8, 16, or 32. > > So is the board still doing the jitter bug, or has it moved on to > the polka or perhaps the chicken dance? Can the board ever be > truely compatible with a cable that only knows the twist (-ed pair)? > > > > _______________________________________________ > 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)
