All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Demers <alexandre.f.demers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	"Christian König"
	<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
Subject: [amdgpu] script to generate a VCE 1.0 amdgpu compatible firmware
Date: Thu, 23 Nov 2017 00:53:24 -0500	[thread overview]
Message-ID: <647a0989-7c2a-0dc8-c4c9-a20a661331d3@gmail.com> (raw)

Hi,

I just want to let you know that I'm still alive and still committed to
porting VCE 1.0 from radeon to amdgpu. However, for many reasons, I've
been pretty much unable to work on the code since my last communication.

That being said, I've created a script based on Piotr Redlewski's work
to generate a compatible VCE 1.0 firmware with amdgpu. The script can be
found on GithubGist:
https://gist.github.com/Oxalin/ba9aa9c1c1912e68f76dadcad436d1a4

Now, I've read the patchset sent by Redlewski for adding UVD on GCN 1
devices. Christian, since you were to see if AMD could release a new UVD
firmware with header and correct 40bit addressing, could you ask if an
official VCE 1.0 firmware with an official header (and whatever else
could be needed) be released at the same time?

Cheers

-- 
Alexandre Demers


_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

             reply	other threads:[~2017-11-23  5:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  5:53 Alexandre Demers [this message]
     [not found] ` <647a0989-7c2a-0dc8-c4c9-a20a661331d3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-28 16:34   ` [amdgpu] script to generate a VCE 1.0 amdgpu compatible firmware Alexandre Demers
     [not found]     ` <b655b477-2099-c7c6-2539-64262f738134-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-28 17:36       ` Christian König

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=647a0989-7c2a-0dc8-c4c9-a20a661331d3@gmail.com \
    --to=alexandre.f.demers-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.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.