Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 137] NLNet 2019 Video Acceleration Proposal 2019-10-031
Date: Sat, 18 Apr 2020 06:43:04 +0000
Message-ID: <bug-137-13-i5HMfxKMiM@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-137-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=137

--- Comment #20 from cand@gmx.com ---
I believe it's too late to add AAC, however due to how ffmpeg is structured,
some of the work on the other codecs will speed up AAC too. Not as much as
focusing on it, but more than plain sw.

MPEG2, MP3, AC3 are all free, patents expired. Vorbis and Opus were explicitly
designed for that.

For the newer video codecs, it's possible any implementation would infringe
patents. So does 90% of ffmpeg code. IANAL, but only the sw patents I believe,
as the hw blocks we will have will not be specialized to any codec. Unlike a
modern GPU that has "H.264 frame in, RGB out" blocks, we will have
sub-operations such as "calculate transform XYZ for this data". Those are not
patentable in general, some specific algorithm in hw may be.

So my conclusion is that the hw is safe, but if a commercial entity wishes to
ship our software in the US, they will need to disable the newer video codecs
or to license patents. I.e. the exact same situation as ffmpeg code, if they
want to ship that in a product with new stuff enabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-137-13@https.bugs.libre-soc.org/>
2020-04-11 11:19 ` bugzilla-daemon
2020-04-18  0:34 ` bugzilla-daemon
2020-04-18  6:43 ` bugzilla-daemon [this message]
2020-04-18  7:03 ` bugzilla-daemon
     [not found] <bug-137-13@http.bugs.libre-riscv.org/>
2020-03-13 10:16 ` bugzilla-daemon
2020-04-04 10:57 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-137-13-i5HMfxKMiM@https.bugs.libre-soc.org/ \
    --to=bugzilla-daemon@libre-soc.org \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git