intel / intel/media-driver

Intel sold an unlocked H264 hardware decoder to me that is usable via the VAAPI interface. Where can I find the H264 patent license confirmation?

Open
#1,276 1 comment 0 reactions 1 assignee Claimed by @Sherry-Lin View on GitHub
Question/Discussion
Dominant language
C
Stars
1.2k
Forks
383
Avg merge
8d 18h
Merged PRs (30d)
4

Description

* One can buy a license key to unlock Raspberry Pi's MPEG2 hardware decoder: https://codecs.raspberrypi.org/mpeg-2-license-key/
(H264 hardware decoder is already unlocked/licensed by default, it could be used via ffmpeg h264_v4l2m2m api)
* One can buy a license to unlock Windows' HEVC software decoder+encoder: https://www.microsoft.com/en-us/p/hevc-video-extensions/9nmzlz57r3t7
* [Cisco](https://www.openh264.org/BINARY_LICENSE.txt) pays a capped license fee for letting every interested consumer use its openh264 software decoder.
* [Canonical](https://www.zdnet.com/article/are-ubuntu-users-covered-by-h-264-license-it-depends/) pays a license fee to be able to sell its Ubuntu OS with a h264 software decoder included.
* **Intel** sells its APUs with an unlocked H264 hardware decoder, it does not require consumers to buy a license key to unlock it, therefore Intel (or a third party chip vendor of Intel's H264 hardware decoder) must have paid MPEG-LA patent license fees to sell an unlocked H264 hardware decoder to me as customer.
**Where can I find the patent license confirmation that Intel (or a third party chip vendor of Intel's H264 hardware decoder) has paid the fee that allowed Intel to sell an unlocked H264 hardware decoder to an APU customer like me?**
(VAAPI is an API, not a decoder, one can use it to transfer H.264 bytes to the unlocked/licensed hardware decoder (Intel Quick Sync Video?) and to receive images back.)

I ask this question for https://bugzilla.mozilla.org/show_bug.cgi?id=1737116.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.