dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106625] AMD HEVC support for for libomxil-bellagio / gst-plugins-omx
Date: Wed, 23 May 2018 11:58:55 +0000	[thread overview]
Message-ID: <bug-106625-502-14lLdUXsvO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106625-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1883 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106625

--- Comment #2 from Luke McKee <hojuruku@gmail.com> ---
I'm hoping AMD will get around to releasing their changes to LGPL licensed
gstreamer-plugins-omx / libomxil-bellago

It's mesa/Gallium that has the BSD/MIT license and all the code for
libomix-belagio h265 support is already in the MESA source referred to in bug
description.

https://www.mesa3d.org/license.html

To say gstreamer-plugins-omx and libomixl-bellagio is not gpl like you said on
IRC would be incorrect.

https://github.com/GStreamer/gst-omx/blob/master/COPYING

https://sourceforge.net/p/omxil/omxil/ci/master/tree/COPYING

Now if I was stickler for making this a GPL request I'd be looking at the
bundled gst-plugins-omx binary in to see if it has h265 support (though not
enabled by default). But it makes you wonder why they package it?

https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-for-Linux-Release-Notes.aspx

Seeing AMD is moving to tizonia in the last 3 months, that too lacks h265
support, so it has to be a custom interface to use h265.

So consider this a GPL request for the source for AMD's build of
gstreamer-plugins-omx for the binaries the release. Finger's crossed the source
shows their patches :)

https://www1.qt.io/qt-licensing-terms/

"Complete corresponding source code of the library used with the application or
the device built using LGPL, including all modifications to the library, should
be delivered with the application (or alternatively provide a written offer
with instructions on how to get the source code). It should be noted that the
complete corresponding source code has to be delivered even if the library has
not been modified at all."

Sorry Daniel but you are just plain wrong.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3051 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-05-23 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  7:53 [Bug 106625] GPL Request: Where is AMD's patch for libomxil-bellagio / gst-plugins-omx to support HEVC decode? bugzilla-daemon
2018-05-23  9:51 ` bugzilla-daemon
2018-05-23  9:52 ` [Bug 106625] AMD HEVC support for for libomxil-bellagio / gst-plugins-omx bugzilla-daemon
2018-05-23 11:58 ` bugzilla-daemon [this message]
2018-05-23 12:10 ` bugzilla-daemon
2018-05-23 12:20 ` bugzilla-daemon
2018-05-23 12:22 ` bugzilla-daemon
2018-05-23 12:27 ` bugzilla-daemon
2018-05-23 12:28 ` [Bug 106625] Request test app for HEVC decode with AMD proprietary driver bugzilla-daemon
2018-05-23 14:11 ` [Bug 106625] AMD HEVC support for for libomxil-bellagio / gst-plugins-omx bugzilla-daemon
2018-05-23 14:43 ` bugzilla-daemon
2018-05-24 11:09 ` 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-106625-502-14lLdUXsvO@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).