>> What is the kernel that will be on the future MeeGo tablets? >> > > This will depend on what hardware platform you are talking about. For > Intel devices we have people creating Moorestown, Oaketrail, and > Pinetrail based devices with Moorestown and Oaktrail having the same > hardware decode capabilities but Pinetrail having a very different > solution (or no solution, depending on the OEM.) > > Moorestown/Oaketrail is enabled via vaapi (with gstreamer elements > wrapping vaapi.) Most app developers will have no need to do anything > other then use the Qt/Mobility API. If the app needs to build an > exotic pipeline then they can directly work with gstreamer, and if the > app already has it's own concept of a pipeline infrastructure then the > app could choose to directly talk to VAAPI. > > Some pinetrail based tablets (like the WeTab/ExoPC) have a third party > hd video decoder. There is no such support for this in meego. I > have no idea if somebody is planning to add support, but some kind of > linux solution exist since this is integrated into the Linux that > comes on WeTab. > For your info,
in the TV project we have a serious need to treat video well and for that reason we have started a tread discussion on the need for a unified video player which can hide the complexity of sourcing the video and managing special the hardware (including overlay). Currently a functional spec is posted and soon will follow an implementation spec. If you are not followoing the meego-tv mailing list you can get the archive from here. http://lists.meego.com/pipermail/meego-tv/2011-March/000012.html -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
