A more detailed analysis will be provided once the 3.3 DRM pull request officially goes in this week or next, but here's some of the new items when looking through the drm-core-next Git repository.
- More work on Intel Ivy Bridge (Gen7) graphics enablement plus a few more Sandy Bridge (Gen6) fixes.
- Sprite support within the DRM core and it's now used by the Intel driver for Sandy Bridge and Ivy Bridge video sprite support. [Details]
- Support for private planes.
- Color key support for the Intel DRM driver. [Details]
- Evergreen HDMI audio support in the Radeon DRM driver. [Details]
- Fixed Intel Cedarview support in the GMA500 Poulsbo driver.
- Semaphores support in the Radeon driver.
- CEA video mode detection/support within DRM/EDID.
- Various VMware "vmwgfx" fixes.
- HDMI display support, multi-buffer support, power management, GEM memory management code clean-up, and other work for the Samsung Exynos driver. [Details]
- Many Nouveau related commits for the open-source NVIDIA support, among which is HDMI audio support for several generations of GeForce GPUs, NVD0 page-flipping, improved MXM support, memory type detection, Fermi re-clocking support, and some power management upbringing. [Details]
In a mailing list message this morning, David Airlie mentions that the "-next" tree is pretty much the state of the 3.3 merge. He is wanting to land some yet-to-be-merged TTM/AGP fixes though and also the "dma_buf" work, as done in part by the Linaro developers. He hopes to have this upstream for 3.3 so that others can start building around this DMA buffer sharing work for the DRM area.