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 00:34:17 +0000
Message-ID: <bug-137-13-Jq9aAdlcr3@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

Michael Pham <pham.michael.98@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pham.michael.98@gmail.com

--- Comment #19 from Michael Pham <pham.michael.98@gmail.com> ---
I see that you already sent this to NLNet, but I hope it's not too late to add
AAC to the list of Audio Formats to accelerate. The reason being is that it is
one of the primary audio formats used on YouTube and also has common use as a
Bluetooth audio format. I would even argue that AAC is even more widely used
than AC3 and Vorbis and Opus at least in my experience as an average user.

In regards to the video formats, what is the legality of putting into the
hardware to help decoding for MPEG2, MPEG4, H.264, and H.265? I know these are
at least covered by the patent pool of MPEG LA (
https://en.wikipedia.org/wiki/MPEG_LA ). Some of the audio codecs may or may
not also be tangled in legalities (not sure, I haven't really looked into it
for the audio formats).

Would it be prudent to get legal advice first? Or do you feel it is safe doing
this?

-- 
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 [this message]
2020-04-18  6:43 ` bugzilla-daemon
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-Jq9aAdlcr3@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