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 14:43:21 +0000	[thread overview]
Message-ID: <bug-106625-502-uoTlDyoXjw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106625-502@http.bugs.freedesktop.org/>


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

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

Luke McKee <hojuruku@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |FIXED

--- Comment #8 from Luke McKee <hojuruku@gmail.com> ---
Dan,

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

Yep, to show a feature that was ALREADY OPENSOURCED BY MESA that couldn't be
used without additional source which was either not upstreamed or not in a well
known location. Why would I be linking to the source code for something in the
original POST and then asking for the source code to be opensourced via a LGPL
request????? WT#? You are not making sense. Please quit flogging the dead horse
here.

The request was a LGPL source code request to AMD (yes not freedesktop) for
their bundling LGPL licensed libraries libopenmax-bellagilo (not modified in
AMD's case like other openmax implementations were for HEVC suport) OR the LGPL
licensed gst-plugins-omx. 

Yes I am guilty as charged, I used the freedestop.org bug tracker as a shortcut
to get in touch with some AMD devs by only putting the request in the AMD
Gallium section, and it was mission accomplished.

However this request did relates to a feature in MESA gallium state tracker
that can't easily be implemented due to no documentation or info on what
libraries can use said feature, hence why it's also relevant to freedesktop.org
/ mesa support.


---

Christian,

Thanks for your help. The reason I was playing with openmax because of encoding
problems with FFMPEG that are still not resolved, and because ffmpeg vaapi
until recently didn't support EGL / play nice with mpv.

Thanks for linking to the AMD fork of libgst-openmax, I'll see how it works, if
not so good, I think I'll try tizonia-openmax-il as it supports EGL and hope
you'll implement gstreamer h265-encoding/decoding down the track there too. The
openmax interface to the encoder previously was more stable than the
ffmpeg/vaapi one.

Cheers,

Luke

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

[-- Attachment #1.2: Type: text/html, Size: 3870 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 14:43 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
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 [this message]
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-uoTlDyoXjw@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).