All of lore.kernel.org
 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 12:27:53 +0000	[thread overview]
Message-ID: <bug-106625-502-iG5oagLWlf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106625-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Daniel Stone <daniel@fooishbar.org> ---
(In reply to Luke McKee from comment #2)
> 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

And from the code you linked here:
https://github.com/freedesktop/mesa/blob/master/src/gallium/state_trackers/omx/bellagio/vid_dec_h265.c

> 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

I never said that on IRC, and as far as I can tell no-one else did either. But
it's correct anyway - gst-omx is LGPL and _not_ GPL. Both have equivalent terms
to allow those in possession of a binary to demand corresponding source, but
they are very different licenses.

> 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

Right, I can see now that you're talking indeed about gst-omx. I was just
confused by the talk about and links to Bellagio (relevant to Mesa) at the
start. This is about gst-omx which we don't develop, and isn't released by the
Mesa project at all. If Mesa or freedesktop.org were releasing those binaries
then this would be the right forum, but it's not: AMD is doing the distribution
of, again, someone else's code.

It's important for us to be very clear; filing bugs on Mesa alleging that there
have been GPL violations is pretty bad for both Mesa and freedesktop.org, and
super important to have rectified and clarified immediately.

> 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 :)
> 
> [... LGPL explainer snipped ...]
>  
> Sorry Daniel but you are just plain wrong.

Yes, the AMD distribution of gst-omx does seem - on the face of it - like it
would require an accompanying source offer.

But, on the other hand:
  - distribution of Bellagio is not relevant, as it is licensed under
permissive terms
  - any development AMD may or may not be doing on Tizonia is totally
irrelevant, as they do not appear to be distributing it currently;
copyright/licensing terms only apply on distribution
  - the driver is distributed by amd.com, and not freedesktop.org
  - the work you're referring to isn't really related to the Mesa project at
all

Please take this up with AMD. Again I appreciate your zeal, but please do not
throw claims of GPL violations around so lightly. I hope you understand why
I've had to figure out exactly what it is you're alleging and requesting here,
and be very precise about it.

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

[-- Attachment #1.2: Type: text/html, Size: 4948 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 12:27 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
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 [this message]
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-iG5oagLWlf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.