On Mon, Feb 13, 2017 at 06:55:33AM -0500, Tom St Denis wrote:
> On 13/02/17 05:00 AM, Nils Holland wrote:
> > On Sat, Feb 04, 2017 at 06:44:12PM +, StDenis, Tom wrote:
> >> Hello all,
> >>
> >>
> >> We're pleased to announce the initial public
On Sat, Feb 04, 2017 at 06:44:12PM +, StDenis, Tom wrote:
> Hello all,
>
>
> We're pleased to announce the initial public release of the AMDGPU
> User Mode Register debugger (umr). This tool allows privileged
> users to read and write GPU registers in order to diagnose, debug,
> and aid in
So I decided to fix this with the following follow-up patch. I hope
this is the right approach (vs. reverting the commit and instead using
a fixed v2 of the original patch).
From 41775d2c8a14873f522667a57b66cfbe119e28a4 Mon Sep 17 00:00:00 2001
From: Nils Holland <nholl...@tisys.org>
Dat
On Tue, Jan 24, 2017 at 06:37:58AM +0800, kbuild test robot wrote:
>
>drivers/gpu/drm/amd/amdgpu/amdgpu_object.c: In function
> 'amdgpu_bo_create_restricted':
> >> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:377:2: warning: #warning Please
> >> enable CONFIG_MTRR and CONFIG_X86_PAT for
On Mon, Jan 23, 2017 at 10:55:49AM +, Zhu, Rex wrote:
> we fixed this issue on Kv as uvd pg was enabled on APU.
>
> We need to change the uvd cg mode.
> When idle, use hw cg. And encode, use sw cg.
>
> So
> WREG32(mmUVD_CGC_GATE, 0); // ture off cg.
> Then
> uvd_v4_2_set_dcm(adev, true);
On Sun, Jan 22, 2017 at 08:26:10PM +0100, Nils Holland wrote:
> Hi folks,
>
> while playing around with the amdgpu drm driver, I stumbled upon an
> issue. In fact, I have tracked it down to commit
> aa4747c00a2dd034c5fdf70ca73b1674ca15beb3 ("drm/amdgpu: refine uvd_4.2
&
Hi folks,
while playing around with the amdgpu drm driver, I stumbled upon an
issue. In fact, I have tracked it down to commit
aa4747c00a2dd034c5fdf70ca73b1674ca15beb3 ("drm/amdgpu: refine uvd_4.2
clock gate sequence.").
When I run the latest mainline git kernel, which contains this commit,
on
On Fri, Jan 20, 2017 at 06:11:50PM +0900, Michel Dänzer wrote:
> On 20/01/17 04:44 PM, Nils Holland wrote:
> >
> > Sounds like a good idea! I was a bit heasitant because, to be honest,
> > I'm not at all an expert about the code in question and basically only
> >
On Fri, Jan 20, 2017 at 11:47:53AM +0900, Michel Dänzer wrote:
> On 20/01/17 04:35 AM, Nils Holland wrote:
> >
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c2016-12-11
> > 20:17:54.0 +0100
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object
