mmap is hard to implement efficiently and the original implementation broke the code a lot so it was removed about a year ago.
The Xv support will be a lot more efficient than going to the frame buffer directly so i wouldn't worry about the extra software involved. The added ability to run anything that talks to X is also an advantage occasionaly. Thanks for the feedback on the documentation in the code. I'll fix it later and check the readme i added as well. Thanks John --- Duncan Webb <[EMAIL PROTECTED]> wrote: > John Harvey wrote: > > >Assuming freevo has Xv support why don't you just > run X on the framebuffer > >and use the Xv support for playback? > > > Thanks John, wasn't sure if freevo had Xv support, > had a bit of work to > test it and it *does* work. > > The only thing that bothers me is why the ivtv-fb > does not support mmap, > either because it's technically not possible or > because it has not been > implemented yet. Would be nicer to use freevo > without a X (one less > layer of code), freevo supports SDL but this > requires mmap to work. > > BTW the comments in the driver/ivtv-osd.c have an > example for the driver > say: > > Section "Device" > Identifier "Hauppauge PVR 350 iTVC15 > Framebuffer" > Driver "fbdev" > Option "fbdev" "/dev/fb1" # <-- modify > if using another device > BusID "0:10:0" > EndSection > > Which should really say > Driver "ivtvdev" > > Regards, > Duncan > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
