Displaying 3 results from an estimated 3 matches for "nouveau_mem_memory_target".
2017 Nov 10
2
GP10B regression
Hello everyone,
it seems that GP10B support has regressed recently. With linux-next, I
need to modify device/base.c to set
.mmu = gp10b_mmu_new
for GP10B (makes sense - I guess this was left as gf100_mmu_new as a
typo) to probe. After that, running a trivial testcase (running a NOP
method in 3D class) fails with
[ 110.084649] nouveau 17000000.gpu: fifo: read fault at 0000011000
engine 06
2017 Nov 11
0
GP10B regression
...uveau: switch over to new memory and vmm interfaces
Even with the first one some patches/hacks are needed:
- in mmu/gp10b.c, in the constructor we need to select the GM200 path -
the GP100 path seems to not to work
- as mentioned in the first mail, we need to set .mmu = gp10b_mmu_new,
- and in nouveau_mem_memory_target we need to return
NVKM_MEM_TARGET_NCOH instead of NVKM_MEM_TARGET_HOST.
Cheers,
Mikko
On 11/10/2017 11:27 PM, Mikko Perttunen wrote:
> Hello everyone,
>
> it seems that GP10B support has regressed recently. With linux-next, I
> need to modify device/base.c to set
>
> .m...
2017 Nov 21
2
GP10B regression
...rfaces
>
> Even with the first one some patches/hacks are needed:
>
> - in mmu/gp10b.c, in the constructor we need to select the GM200 path -
> the GP100 path seems to not to work
>
> - as mentioned in the first mail, we need to set .mmu = gp10b_mmu_new,
>
> - and in nouveau_mem_memory_target we need to return
> NVKM_MEM_TARGET_NCOH instead of NVKM_MEM_TARGET_HOST.
>
> Cheers,
> Mikko
>
> On 11/10/2017 11:27 PM, Mikko Perttunen wrote:
>> Hello everyone,
>>
>> it seems that GP10B support has regressed recently. With linux-next, I
>> need to m...