> I am happy that they put new (0.7.x) bttv in 2.4, It's me ... > there were unstable driver in stable kernel 2.2, will 0.8.x/bttv2 be > in 2.5 or 2.4? 0.8.x depends on v4l2. v4l2 still has some issues pending (dma-to-userspace API, others?). So we have: (1) Finalize the v4l2 API (2) put v4l2 into the kernel (3) put the new bttv into the kernel My current timing plans on this are: Do (2)+(3) early in 2.5.x. Use time until 2.5.x starts to for (1). Maybe backport bttv 0.8.x to 2.4 after it got some more testing in 2.5.x. I'm feeling a bit nervous about putting bttv 0.8.x as-is into 2.4.x. On the other hand the rewrite fixes a number more or less serious problems: * Stability. 0.7.x has no known bugs in the capture code, but the 0.8.x redesign seems to have fixed some hidden ones. * Design bugs (which have some ugly side effects, when using vbi + capture at the same time for example). * pci/dma api. 0.8.x uses the pci_* functions everythere. In contrast, 0.7.x doesn't even compile on some architectures (sparc for example). Comments? Gerd -- Damn lot people confuse usability and eye-candy.
