All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106625] GPL Request: Where is AMD's patch for libomxil-bellagio / gst-plugins-omx to support HEVC decode?
Date: Wed, 23 May 2018 09:51:07 +0000	[thread overview]
Message-ID: <bug-106625-502-T5SsngLcuy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106625-502@http.bugs.freedesktop.org/>


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

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

Daniel Stone <daniel@fooishbar.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel@fooishbar.org

--- Comment #1 from Daniel Stone <daniel@fooishbar.org> ---
Bellagio (and Mesa generally) are not licensed under the GPL, but under the
MIT/BSD family of licenses. These licenses have no obligation at all for source
release: everyone is free to form the code, ship binaries, and never provide
source.

Additionally, the GPL's requirements on producing source are very specific: you
are only entitled to receive the source to GPL-licensed code, if you have also
received binaries. It is totally fine to fork a GPL project and never release
code to anyone, if you don't distribute binaries. It is also totally fine to
distribute the binaries to a limited audience, only give the source to them if
they ask for it, and never give the source to anyone else. There is no kind of
requirement for all source to always be universally available.

So for this to be enforceable under the GPL: AMD would need to have definitely
written the code (it is not clear if this has even happened), and distributed
binaries built from it (it seems clear this has not happened), and the code
would need to be under (L)GPL (it isn't).

I'm afraid this isn't an actionable legal request on those grounds, but good
luck with your quest for HEVC support.

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

[-- Attachment #1.2: Type: text/html, Size: 3114 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

  reply	other threads:[~2018-05-23  9:51 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 [this message]
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
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-T5SsngLcuy@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.