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


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

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

Christian König <ckoenig.leichtzumerken@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
            Summary|Request test app for HEVC   |AMD HEVC support for for
                   |decode with AMD proprietary |libomxil-bellagio /
                   |driver                      |gst-plugins-omx
             Status|REOPENED                    |RESOLVED

--- Comment #7 from Christian König <ckoenig.leichtzumerken@gmail.com> ---
Asking around Leo actually patches gstomx to work with that because the HEVC
support wasn't upstream yet.

The code was always public here https://cgit.freedesktop.org/~leoliu/gstomx,
but I don't think that this is production quality.

On the other hand according to Leo the upstream HEVC support in gstomx should
now work as well with the OpenMAX state tracker as well (but was never tested).

The internal tool can't be released cause that is all proprietary hardware and
software validation code (unit tests framework).

No idea what gstomx version is packed with the pro driver, but since we don't
have any internal repository I think it is just a certain upstream version.

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

[-- Attachment #1.2: Type: text/html, Size: 3133 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:11 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 ` bugzilla-daemon [this message]
2018-05-23 14:43 ` [Bug 106625] AMD HEVC support for for libomxil-bellagio / gst-plugins-omx 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-rLZ29S29DA@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).