The first statement is true. The second one isn't but we haven't figured out how to do it. We should be able to send it YUV data which shrinks the bandwidth requirements enough to probably be useable. Unfortunately i havent found a reliable place to transfer the data too and we are currently waiting for a reply about this. Assuming we get it i have most of the guts of the Xv driver in place so it shouldn't take too long to make it available but this is all dependent on getting the appropriate information.
John --- Tyler Trafford <[EMAIL PROTECTED]> wrote: > On Tue, 1 Feb 2005 08:51:57 -0500, Chad Osmond > <[EMAIL PROTECTED]> wrote: > > > I also noticed that I am unable to use the XV to > display anything from > > mplayer, I have to use x11 which is killing the > CPU. > > All my dmesg and modprobes can be seen in my > previous message. > > The 350's TV out X driver doesn't support XV- and > from the sounds of > it, it never will. The hardware wasn't designed to > handle that kind > of thing. > -- > Tyler Trafford > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- > Interactive Reporting > Tool for open source databases. Create drag-&-drop > reports. Save time > by over 75%! Publish reports on the web. Export to > DOC, XLS, RTF, etc. > Download a FREE copy at > http://www.intelliview.com/go/osdn_nl > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
