<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v2.6.37</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.37</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.37'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2010-12-30T13:50:43Z</updated>
<entry>
<title>drm/i915/dvo: Report LVDS attached to ch701x as connected</title>
<updated>2010-12-30T13:50:43Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-12-30T12:54:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cc6455f82edd3f9da3b03870d41cde3cb22ad40d'/>
<id>urn:sha1:cc6455f82edd3f9da3b03870d41cde3cb22ad40d</id>
<content type='text'>
As we have already detected something attached to the chip during
initialisation, always report the LVDS connector status as connected
during probing.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"</title>
<updated>2010-12-30T13:50:12Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-12-30T09:07:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=bcfbbce822d219eb587acaba8a6e062bbeae4761'/>
<id>urn:sha1:bcfbbce822d219eb587acaba8a6e062bbeae4761</id>
<content type='text'>
As I feared, whilst this fixed the clocks for the Lenovo U160, it broke
many other machines. So lets reverts commit 448f53a1ede54eb854d036abf
and search for the real bug.

Reported-and-tested-by: Travis Hume &lt;travis@computoring.org&gt; [et al]
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=25842
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=32698
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>drm/i915: Verify Ironlake eDP presence on DP_A using the capability fuse</title>
<updated>2010-12-23T09:51:37Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-12-14T19:21:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4d3024428f5c3ef5295e6f6fb257ae118b3f93a1'/>
<id>urn:sha1:4d3024428f5c3ef5295e6f6fb257ae118b3f93a1</id>
<content type='text'>
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>drm/i915, intel_ips: When i915 loads after IPS, make IPS relink to i915.</title>
<updated>2010-12-23T09:51:36Z</updated>
<author>
<name>Eric Anholt</name>
<email>eric@anholt.net</email>
</author>
<published>2010-12-21T02:40:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=63ee41d794d9c555f84205517a68509848988760'/>
<id>urn:sha1:63ee41d794d9c555f84205517a68509848988760</id>
<content type='text'>
The IPS driver is designed to be able to run detached from i915 and
just not enable GPU turbo in that case, in order to avoid module
dependencies between the two drivers.  This means that we don't know
what the load order between the two is going to be, and we had
previously only supported IPS after (optionally) i915, but not i915
after IPS.  If the wrong order was chosen, you'd get no GPU turbo, and
something like half the possible graphics performance.

Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: stable@kernel.org
</content>
</entry>
<entry>
<title>drm/i915/sdvo: Add hdmi connector properties after initing the connector</title>
<updated>2010-12-23T09:50:03Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-12-23T09:43:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f797d22121404eac7b63f1291409f96bcab51c11'/>
<id>urn:sha1:f797d22121404eac7b63f1291409f96bcab51c11</id>
<content type='text'>
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=25012
Reported-by: Tõnu Raitviir &lt;jussuf@linux.ee&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>drm/i915: Set the required VFMUNIT clock gating disable on Ironlake.</title>
<updated>2010-12-23T09:49:40Z</updated>
<author>
<name>Eric Anholt</name>
<email>eric@anholt.net</email>
</author>
<published>2010-12-14T18:06:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=06f37751af77192b424b2b0ff17dc08de65faba0'/>
<id>urn:sha1:06f37751af77192b424b2b0ff17dc08de65faba0</id>
<content type='text'>
It's required by the specs, but we don't know why.  Let's not find out
why.

Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
</content>
</entry>
<entry>
<title>drm: Include the connector name in the output_poll_execute() debug message</title>
<updated>2010-12-21T23:10:12Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-12-21T22:49:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0f16830e9f6de0a44cf1e473ffa80cbe612d5beb'/>
<id>urn:sha1:0f16830e9f6de0a44cf1e473ffa80cbe612d5beb</id>
<content type='text'>
Always useful to know just which connector was polled and had its
status updated.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon/kms: fix bug in r600_gpu_is_lockup</title>
<updated>2010-12-21T22:30:57Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-21T21:05:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e29ff7290e826d5c7fda906d99233713a47a92c8'/>
<id>urn:sha1:e29ff7290e826d5c7fda906d99233713a47a92c8</id>
<content type='text'>
We were using the lockup struct from the wrong union.

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Cc: Jerome Glisse &lt;jglisse@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon/kms: reorder display resume to avoid problems</title>
<updated>2010-12-21T02:53:34Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-20T16:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a93f344d3c04e4b84490c65f2a574387c593be40'/>
<id>urn:sha1:a93f344d3c04e4b84490c65f2a574387c593be40</id>
<content type='text'>
On resume, we were attemping to unblank the displays before the
timing and plls had be reprogrammed which led to atom timeouts
waiting for things that are not yet programmed.  Re-program
the mode first, then reset the dpms state.

This fixes the infamous atombios timeouts on resume.

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Cc: stable@kernel.org
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon/kms/evergreen: reset the grbm blocks at resume and init</title>
<updated>2010-12-21T02:53:05Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-20T17:35:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=86f5c9edbb3bac37cc8cee6528a929005ba72aad'/>
<id>urn:sha1:86f5c9edbb3bac37cc8cee6528a929005ba72aad</id>
<content type='text'>
This fixes module reloading and resume as the gfx block seems to
be left in a bad state in some cases.

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Cc: stable@kernel.org
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
</feed>
