#
2cf3c8bc |
|
02-Jan-2020 |
Wambui Karuga <wambui.karugax@gmail.com> |
drm/nouveau/fb/gf100-: declare constants as unsigned long long. Explicitly declare constants as unsigned long long to address the following sparse warnings: warning: constant is so big it is long v2: convert to unsigned long long for compatibility with 32-bit architectures. Signed-off-by: Wambui Karuga <wambui.karugax@gmail.com> Suggested by: lia Mirkin <imirkin@alum.mit.edu> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
b4e114f1 |
|
31-Oct-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fb/ram: remove old allocators Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
4fdc6ba3 |
|
19-May-2017 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fb/ram/nv40-: use new devinit script interpreter entry-point Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
97e5268d |
|
01-Mar-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>
|
#
02099bac |
|
20-Nov-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fb/ram/gp100-: fix memory detection where FBP_NUM != FBPA_NUM In this situation, we'd have ended up detecting less VRAM than we have. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
#
7ff51f82 |
|
08-Jul-2016 |
Ben Skeggs <bskeggs@redhat.com> |
drm/nouveau/fb/gp100: initial support Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|