Age | Commit message (Collapse) | Author |
|
|
|
This reverts commit 26ddd8e1ac6d6164b9be99e58770924a87b770c7.
|
|
This reverts commit 221d1391e48b019d0955bc2e3aa9261e6523afb9.
|
|
|
|
|
|
wsdisplay device itself.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
objects after resume we can reinitialize the GATT again.
|
|
Use it to properly implement i915_gem_resetore_gtt_mappings().
|
|
Linux uses.
|
|
when we resume or want to change for example the cachability of the mapping.
|
|
|
|
suspend/resume on my x220.
See https://bugzilla.kernel.org/show_bug.cgi?id=47941
|
|
|
|
Since proper VT support is still lacking this will make VTs share a single
framebuffer in emulation mode. As a result the display will be messed up
a bit if you run anything on VTs 1-8. This can be mitigated by disabling
the apropriate lines in /etc/ttys. This does allow VT switching between X
and the framebuffer console and makes suspend/resume do the right thing
when in X.
|
|
|
|
|
|
|
|
|