On 08/26/2016 06:06 PM, Russell King - ARM Linux wrote:
> On Fri, Aug 26, 2016 at 04:25:13PM +0200, Marek Vasut wrote:
>> The content of gpu->memory_base should point to start of RAM, not zero.
>>
>> Signed-off-by: Marek Vasut
>> Cc: Lucas Stach
>> Cc: Christian Gmeiner
>> Cc: Russell King
>> -
On Fri, Aug 26, 2016 at 04:25:13PM +0200, Marek Vasut wrote:
> The content of gpu->memory_base should point to start of RAM, not zero.
>
> Signed-off-by: Marek Vasut
> Cc: Lucas Stach
> Cc: Christian Gmeiner
> Cc: Russell King
> ---
> drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 2 ++
> 1 file cha
On 08/26/2016 04:35 PM, Lucas Stach wrote:
> Am Freitag, den 26.08.2016, 16:25 +0200 schrieb Marek Vasut:
>> The content of gpu->memory_base should point to start of RAM, not zero.
>>
>> Signed-off-by: Marek Vasut
>> Cc: Lucas Stach
>> Cc: Christian Gmeiner
>> Cc: Russell King
>
> NACK. This w
Am Freitag, den 26.08.2016, 16:25 +0200 schrieb Marek Vasut:
> The content of gpu->memory_base should point to start of RAM, not zero.
>
> Signed-off-by: Marek Vasut
> Cc: Lucas Stach
> Cc: Christian Gmeiner
> Cc: Russell King
NACK. This will cause memory corruption when used with a MC10 GPU.
The content of gpu->memory_base should point to start of RAM, not zero.
Signed-off-by: Marek Vasut
Cc: Lucas Stach
Cc: Christian Gmeiner
Cc: Russell King
---
drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/etnaviv/etnaviv_gpu.c
b/dr