On Montag 09 Oktober 2006 10:26, Nicolas Huillard wrote: > Mark Adams a écrit : > >> First : I still have field parity problems with interlaced material on > >> interlaced TV. > > > > Always, sometimes, coming and going, or just the odd glitch? > > "Coming and going". > Defined as : "On the same stream, parity can be OK for a few seconds up > to the minute, and then goes wrong, for a similar period. Pausing the > stream can get it right again. Or not."
That looks more like some interrupts are lost. Is VGA IRQ shared with other devices (/proc/interrupts) ? The other driver mentioned here: http://mail.directfb.org/pipermail/directfb-users/2006-September/002189.html is using spin_locks() during interrupt processing : + spin_lock(&par->irq_lock); + status = VIA_GET_MMIO(VIA_REG_INTERRUPT); + if (status & VIA_IRQ_VBI_PENDING) { + VIA_SET_MMIO(VIA_REG_INTERRUPT, status | VIA_IRQ_VBI_PENDING); + wake_up_interruptible(&par->irq_queue); + par->irq_count++; + handled = 1; + } else { + handled = 0; + } + spin_unlock(&par->irq_lock); In both cases I do not understand the logic in a. testing a bit b. writing back value with tested bit set -- Stefan Lucke _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
