On Tue, 05 Mar 2013, Chris Li wrote:
> On Mon, Mar 4, 2013 at 3:16 PM, Chris Li wrote:
Two things to test:
- Can you please check whether any of the backlight drivers in
/sys/class/backlight does anything? You need to frob the brightness
file. Please also list all the drivers
Release 2.21.4 (2013-03-11)
===
More bugs, more fixes, more releases. A minor new feature being introduced
is the runtime detection of CPU instructions sets along with specialised
paths to take advantage of the available CPU.
* Honour LinearFramebuffer for clumsy PowerXpr
This reverts commit 0d71068835e2610576d369d6d4cbf90e0f802a71.
Not only that the commit introduces a bogus check (voltage_tries == 5
will never meet at the inserted code path), it brings the i915 driver
into an endless dp-train loop on HP Z1 desktop machine with IVY+eDP.
At least reverting this co
On Fri, Mar 08, 2013 at 10:45:52AM -0800, Jesse Barnes wrote:
> The Gunit has a separate reg for this, so allocate some stolen space for
> the power context and initialize the reg.
Is it a requirement to use stolen space? The reason we're allocating rings
and all from stolen is just to test things
On Mon, Mar 11, 2013 at 03:54:11AM +, Zhang, Xiong Y wrote:
> when system enter suspend, hibernate and poweroff state, it will
> disable modeset firstly, then disable irq, but some system generate
> hotplug event between disable modeset and disable irq, this will
> result in S3, S4 failure. So
On Tue, Mar 12, 2013 at 12:40:30AM +0100, Daniel Vetter wrote:
> On Fri, Mar 08, 2013 at 10:45:52AM -0800, Jesse Barnes wrote:
> > The Gunit has a separate reg for this, so allocate some stolen space for
> > the power context and initialize the reg.
>
> Is it a requirement to use stolen space? The
Hi all,
After merging the final tree, today's linux-next build (i386 defconfig)
failed like this:
drivers/built-in.o: In function `i915_min_freq_set':
i915_debugfs.c:(.text+0xb1adc): undefined reference to `__udivdi3'
drivers/built-in.o: In function `i915_max_freq_set':
i915_debugfs.c:(.text+0xb1
