Urgent vmwgfx fixes.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | vmwgfx: vt-switch (master drop) fixesdrivers/ drivers/ drivers/ +2 more | +115 | 0 replies | |
| 2/4 | vmwgfx: Enable use of the vblank systemdrivers/ drivers/ drivers/ +1 more | +49 | 0 replies | |
| 3/4 | vmwgfx: Remove initialisation of dev::devnamedrivers/ | +0 | 0 replies | |
| 4/4 | vmwgfx: Fix fb VRAM pinning failure due to fragmentationdrivers/ | +5 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Urgent vmwgfx fixes.
These are fixes that should, if at all possible, make it into 2.6.36.
They are extracted from the previous patch series, "vmwgfx updates". I will respin the rest of the patches for possible inclusion into drm-next. I've renamed some patches and added some comment to emphasise the fixes in them rather than what's actually being done with the code.
Patch 1 fixes vt switching while 3D objects are active. Previously the device lost all state at that point.
Patch 2 enables the vblank system and avoids a lot of uninitialized calls (kernel crashes)
Patch 3 removes a workaround for dev::devname the current code caused a kernel crash at module unload then dev::devname was beeing kfreed when it was actually static. Patch 4 Fixes a bo pinning error causing severe rendering corruption.
Thanks,
Thomas