| commit | 7db26623257a16c901a4b77bfc5096ee05304932 | [log] [tgz] |
|---|---|---|
| author | Ben Skeggs <bskeggs@redhat.com> | Mon Feb 28 14:22:12 2011 +1000 |
| committer | Ben Skeggs <bskeggs@redhat.com> | Mon Feb 28 15:00:16 2011 +1000 |
| tree | 6c92f51db3b30ed6089f25b80e21d296bb4639a5 | |
| parent | 3c0556e9673f79e386b27768e27d18b3ce29e40e [diff] |
drm/nv50-nvc0: make sure vma is definitely unmapped when destroying bo Somehow fixes a misrendering + hang at GDM startup on my NVA8... My first guess would have been stale TLB entries laying around that a new bo then accidentally inherits. That doesn't make a great deal of sense however, as when we mapped the pages for the new bo the TLBs would've gotten flushed anyway. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>