Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: VA-API Support For Google Android Platform

  1. #11
    Join Date
    Jun 2009
    Location
    Paris
    Posts
    432

    Default

    Quote Originally Posted by droidhacker View Post
    ... the underlying hardware has to support it.
    Actually, it should be possible to write VP8 support for the Ironlake chips since the codec is similar to H.264. However, the entry-point won't be VLD because the BSD engine in the chip does not support the VP8 bitstream format. So, that'd be motion-compensation for starters. There is no strong need for HW acceleration yet anyway (not widely used yet).

  2. #12
    Join Date
    Jun 2009
    Location
    Paris
    Posts
    432

    Default

    Quote Originally Posted by popper View Post
    while its true there's now an Android entry , it seem thats a side issue, and its Far More likely that these patches are setting the stage for the Sandy Bridge internal Encode/Decode video engine coming in January, hence the new
    4) Update VAAPI for dynamic bit rate control/AIR/maximum slice size ctrl
    5) Added VA_STATUS_ERROR_DECODING/ENCODING_ERROR to report decode/encode error
    etc.
    Actually, that's more for the Moorestown chips. The libfool stuff is to help people write user applications without a proper driver yet.

  3. #13
    Join Date
    Jan 2007
    Posts
    459

    Default

    Quote Originally Posted by gbeauche View Post
    Actually, that's more for the Moorestown chips. The libfool stuff is to help people write user applications without a proper driver yet.
    LOL, Yeah that's what happens when i don't try and read the patch's in full, but the Android entry is still a side issue, the other recent patches seem interesting and related too OC...

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •