From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
From: Dave Airlie
We are accessing totally the wrong struct in this case, and putting
uninitialised values into the GPU, which it doesn't like unsurprisingly.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/ni.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
d
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
On Mon, May 9, 2011 at 1:02 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> We are accessing totally the wrong struct in this case, and putting
> uninitialised values into the GPU, which it doesn't like unsurprisingly.
>
> Signed-off-by: Dave Airlie
Reviewed-by: Alex Deucher
> ---
> drivers/
12 matches
Mail list logo