- 02 11月, 2017 3 次提交
-
-
由 Ben Skeggs 提交于
BAR2 being done for practical reasons, this is just for consistency. Flushes have been added after the write to bind the instance block, as later commits will reveal the need for them. Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
-
由 Ben Skeggs 提交于
NVIDIA call it BAR2, Linux APIs treat it as BAR3 due to BAR1 being a 64-bit BAR, which I presume take two slots or something. No actual code changes here, just to make future commits less messy. Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
-
由 Ben Skeggs 提交于
Will already be done by MMU as a result of the PT writes that occur during BAR2 bootstrapping. This is likely just a left-over from the days when it was hardcoded. Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
-
- 22 8月, 2017 1 次提交
-
-
由 Ben Skeggs 提交于
Useful for testing, and for the userspace build where we can't kick a framebuffer driver off the device. Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
-
- 28 8月, 2015 1 次提交
-
-
由 Ben Skeggs 提交于
Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
-