- 08 Dec, 2010 18 commits
-
-
Ben Skeggs authored
Signed-off-by:Ben Skeggs <bskeggs@redhat.com>
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
As of this commit, it's guaranteed that if an object is in VRAM that its GPU virtual address will be constant. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This is required on nv50 as we need to be able to have more precise control over physical VRAM allocations to avoid buffer corruption when using buffers of mixed memory types. This removes some nasty overallocation/alignment that we were previously using to "control" this problem. Signed-off-by: -
Francisco Jerez authored
Signed-off-by:
Francisco Jerez <currojerez@riseup.net> Signed-off-by:
-
Ben Skeggs authored
At some point in the future, this bo won't necessarily be backed by a drm_mm_node, so use the start/size fields of the ttm_mem_reg instead. Signed-off-by: -
Ben Skeggs authored
This will be used later to fixup bo.offset with a buffer's fixed GPU virtual address. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
The regs belong to PFIFO, they're different for pretty much the same generations we need different PFIFO control for, and NVC0 is going to be even more different than the rest. Signed-off-by: -
Francisco Jerez authored
Sleeping doesn't pay off for very short delays in comparison with the minimum granularity of schedule_timeout(). Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
There have been reports of PFIFO cache errors during context take down (fdo bug 31637). They are caused by some GPU objects being taken out while the channel is still potentially processing commands. Make sure that all the previous rendering has landed before releasing a GPU object. Reported-by:
Grzesiek Sójka <pld@pfu.pl> Reported-by:
Patrice Mandin <patmandin@gmail.com> Signed-off-by:
-
Francisco Jerez authored
nvxx_graph_isr is already taking care of it. In some cases this could've made you miss PGRAPH interrupts (e.g. when you were supposed to get several IRQs of the same kind in a row). Signed-off-by:
-
Francisco Jerez authored
No functional changes, just simplify some code paths a bit. Signed-off-by:
-
- 03 Dec, 2010 22 commits
-
-
Francisco Jerez authored
In typical Apple fashion there's no standard information about what encoders are present on this machine, this patch adds a quirk to provide it. Signed-off-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
These have been unused since UMS support was ripped out, so lets remove them completely. Signed-off-by: -
Ben Skeggs authored
Fix running of destroy_context() when create_context() has never been called for the channel, and fill in engine's tlb_flush() function pointer. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Allows callers to install their own handlers for when a GPIO line changes state (such as for hotplug detect). This also fixes a bug where we weren't acknowledging the GPIO IRQ until after the bottom half had run, causing a severe IRQ storm in some cases. Reviewed-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Lets start to clean up this mess! Reviewed-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
Reported-by:
Pekka Paalanen <pq@iki.fi> Signed-off-by:
-
