From: "Michel Dänzer" <michel@daenzer.net>
To: Daniel Vetter <daniel@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Jerome Glisse" <jglisse@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 3/4] drm/radeon: consolidate uvd/vce initialization, resume and suspend.
Date: Fri, 18 Mar 2016 13:00:26 +0900 [thread overview]
Message-ID: <56EB7D5A.9060801@daenzer.net> (raw)
In-Reply-To: <20160317073616.GB14170@phenom.ffwll.local>
On 17.03.2016 16:36, Daniel Vetter wrote:
> On Thu, Mar 17, 2016 at 06:41:14AM +1000, Dave Airlie wrote:
>> Just an aside,
>>
>> So is there no way to do hibernate with these blocks?
>>
>> Like can you not cleanly shut them down without doing a power cycle.
>>
>> I have to say UVD is a real pain in the ass from a stability pov, I'd
>> kinda wished I'd enforced AMD creating something like intel-gpu-tools
>> and having tests to make sure GPU reset etc stayed working before
>> merging it.
>
> igt already supports running on any kind of drm device, and it has a bunch
> of vc4 specific testcases on top. If anyone finds offence in the "intel"
> part, we can rename it to igt gpu tools/tests ;-)
Any tips for running the tests on non-Intel GPUs? I tried piglit igt.py,
but it was generating tens of thousands of failures from tests which
look Intel specific.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-03-18 4:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 12:48 [PATCH 3/4] drm/radeon: consolidate uvd/vce initialization, resume and suspend Jérôme Glisse
2016-03-16 13:03 ` Christian König
2016-03-16 14:59 ` Jerome Glisse
2016-03-16 15:19 ` Christian König
2016-03-16 15:56 ` Jerome Glisse
2016-03-16 17:06 ` Christian König
2016-03-16 17:43 ` Jerome Glisse
2016-03-16 18:51 ` Christian König
2016-03-16 20:41 ` Dave Airlie
2016-03-16 20:58 ` Deucher, Alexander
2016-03-17 7:36 ` Daniel Vetter
2016-03-18 4:00 ` Michel Dänzer [this message]
2016-03-18 8:16 ` Daniel Vetter
2016-03-19 9:41 ` Daniel Vetter
2016-03-19 10:46 ` Daniel Vetter
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=56EB7D5A.9060801@daenzer.net \
--to=michel@daenzer.net \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
/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.