Announcement

Collapse
No announcement yet.

VA-API Support For Google Android Platform

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    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).

    Comment


    • #12
      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.

      Comment


      • #13
        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...

        Comment

        Working...
        X