/linux/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ |
H A D | ramgf108.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ramgm200.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ramgm107.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ramgp100.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ramgf100.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ram.h | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
H A D | ramgk104.c | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
/linux/drivers/gpu/drm/nouveau/include/nvkm/subdev/ |
H A D | fb.h | diff 97e5268d57bb2ec9c82cf8758fa97a2f04ea9d1b Thu Mar 02 04:53:05 CET 2017 Ben Skeggs <bskeggs@redhat.com> drm/nouveau/fb/gf100-: rework ram detection
This commit reworks the RAM detection algorithm, using RAM-per-LTC to determine whether a board has a mixed-memory configuration instead of using RAM-per-FBPA. I'm not certain the algorithm is perfect, but it should handle all currently known configurations in the very least.
This should fix GTX 970 boards with 4GiB of RAM where the last 512MiB isn't fully accessible, as well as only detecting half the VRAM on GF108 boards.
As a nice side-effect, GP10x memory detection now reuses the majority of the code from earlier chipsets.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|