Displaying 4 results from an estimated 4 matches for "bar1_vmm".
2019 Mar 16
6
[PATCH 0/4] NV50/GF100 behind constrained hierarchies
Hi Ben,
I've been working with an mmio-constrained pci hierarchy intended almost
solely for nvme devices and switches. Binding nouveau to an NV50-based
gpu results in a kernel panic as the device cannot be fully mapped.
I've made modifications in nv50 and vmm to unbind the driver from this
hierarchy, and modified gf100 assuming it will have the same issue.
1/4 also includes a fix where
2019 May 22
0
[PATCH AUTOSEL 5.1 043/375] drm/nouveau/bar/nv50: ensure BAR is mapped
...00ULL;
- limit = start + device->func->resource_size(device, 1);
+ size = device->func->resource_size(device, 1);
+ if (!size)
+ return -ENOMEM;
+ limit = start + size;
ret = nvkm_vmm_new(device, start, limit-- - start, NULL, 0,
&bar1_lock, "bar1", &bar->bar1_vmm);
--
2.20.1
2019 May 22
0
[PATCH AUTOSEL 5.0 037/317] drm/nouveau/bar/nv50: ensure BAR is mapped
...00ULL;
- limit = start + device->func->resource_size(device, 1);
+ size = device->func->resource_size(device, 1);
+ if (!size)
+ return -ENOMEM;
+ limit = start + size;
ret = nvkm_vmm_new(device, start, limit-- - start, NULL, 0,
&bar1_lock, "bar1", &bar->bar1_vmm);
--
2.20.1
2019 May 22
0
[PATCH AUTOSEL 4.19 029/244] drm/nouveau/bar/nv50: ensure BAR is mapped
...00ULL;
- limit = start + device->func->resource_size(device, 1);
+ size = device->func->resource_size(device, 1);
+ if (!size)
+ return -ENOMEM;
+ limit = start + size;
ret = nvkm_vmm_new(device, start, limit-- - start, NULL, 0,
&bar1_lock, "bar1", &bar->bar1_vmm);
--
2.20.1