Re: [git pull] drm fixes

From: Takashi Iwai
Date: Wed Dec 22 2010 - 11:24:44 EST


At Tue, 21 Dec 2010 23:43:18 +0000 (GMT),
Dave Airlie wrote:
>
>
> Hi,
>
> meant to get this out earlier, but I've been off sick as well as having a
> sick kid, also meant a few things piled up when I wasn't looking
>
> contains a revert for reported regression in intel and also one in radeon,
> a few radeon fixes, one for a 15s resume time on certain laptops, and one
> to fix gpu reset on some gpus,
>
> Dave.
>
> The following changes since commit a4851d8f7d6351a395d36ae8fdcf41745a832d76:
>
> Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2010-12-15 12:41:17 -0800)
>
> are available in the git repository at:
>
> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-fixes
>
> Alex Deucher (7):
> drm/radeon/kms: disable ss fixed ref divide
> drm/radeon/kms: disable the r600 cb offset checker for linear surfaces
> drm/radeon/kms/evergreen: flush hdp cache when flushing gart tlb
> drm/radeon/kms: fix evergreen asic reset
> drm/radeon/kms/evergreen: reset the grbm blocks at resume and init
> drm/radeon/kms: reorder display resume to avoid problems
> drm/radeon/kms: fix bug in r600_gpu_is_lockup
>
> Benjamin Herrenschmidt (1):
> drm/radeon: Add early unregister of firmware fb's
>
> Chris Wilson (5):
> drm/i915/ringbuffer: Handle wrapping of the autoreported HEAD
> drm/i915/sdvo: Only use the SDVO pin if it is in the valid range
> agp/intel: Fix missed cached memory flags setting in i965_write_entry()
> drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
> drm: Include the connector name in the output_poll_execute() debug message

The commit 448f53a1ede54eb854d036abf54573281412d650
drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks

causes a regression on a SandyBridge machine here.
The laptop display (LVDS) becomes blank. Reverting the commit fixes
the problem.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/