<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v2.6.35.11</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu?h=v2.6.35.11</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu?h=v2.6.35.11'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-02-06T19:04:06Z</updated>
<entry>
<title>revert-drm-radeon-kms-properly-compute-group_size-on-6xx-7xx</title>
<updated>2011-02-06T19:04:06Z</updated>
<author>
<name>Steve Conklin</name>
<email>sconklin@canonical.com</email>
</author>
<published>2011-02-06T19:04:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=be9627d438a0bbad74b10fa58cc87b9869de33e6'/>
<id>urn:sha1:be9627d438a0bbad74b10fa58cc87b9869de33e6</id>
<content type='text'>
Revert drm/radeon/kms: properly compute group_size on 6xx/7xx

From: Steve Conklin &lt;sconklin@canonical.com&gt;

We discovered a regression for Radeon users in our latest proposed
kernel for 2.6.35 (Maverick), and have isolated it to this patch:

http://git.kernel.org/?p=linux/kernel/git/longterm/linux-2.6.35.y.git;a=commit;h=b8e9a4a45f8427837f4dba89
+bda4d4e3f3a5c726

We took that patch as part of 2.6.35.10, and one of our testers has
reported that our build of that kernel also exhibits the problem.

These are mainline kernels built with the Ubuntu configs.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35.10-maverick/

Our bug report is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/703553

Upstream bug report:

https://bugzilla.kernel.org/show_bug.cgi?id=24802

Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>drm/i915/dp: Fix I2C/EDID handling with active DisplayPort to DVI converter</title>
<updated>2011-02-06T19:03:50Z</updated>
<author>
<name>David Flynn</name>
<email>davidf@rd.bbc.co.uk</email>
</author>
<published>2010-12-08T16:10:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=02e8aefffbe5cc35c1f1b090ca8d8b6fce4da46a'/>
<id>urn:sha1:02e8aefffbe5cc35c1f1b090ca8d8b6fce4da46a</id>
<content type='text'>
commit 8316f33766a82907c694267ff911e45e256f09f9 upstream.

The DisplayPort standard (1.1a) states that:
  The I2C-over-AUX Reply field is valid only when Native AUX CH Reply
  field is AUX_ACK (00). When Native AUX CH Reply field is not 00, then,
  I2C-over-AUX Reply field must be 00 and be ignored.

This fixes broken EDID reading when using an active DisplayPort to
duallink DVI converter.  If the AUX CH replier chooses to defer the
transaction, a short read occurs and erroneous data is returned as
the i2c reply due to a lack of length checking and failure to check
for AUX ACK.

As a result, broken EDIDs can look like:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: bc bc bc ff bc bc bc ff bc bc bc ac bc bc bc 45    ???.???.???????E
10: bc bc bc 10 bc bc bc 34 bc bc bc ee bc bc bc 4c    ???????4???????L
20: bc bc bc 50 bc bc bc 00 bc bc bc 40 bc bc bc 00    ???P???.???@???.
30: bc bc bc 01 bc bc bc 01 bc bc bc a0 bc bc bc 40    ???????????????@
40: bc bc bc 00 bc bc bc 00 bc bc bc 00 bc bc bc 55    ???.???.???.???U
50: bc bc bc 35 bc bc bc 31 bc bc bc 20 bc bc bc fc    ???5???1??? ????
60: bc bc bc 4c bc bc bc 34 bc bc bc 46 bc bc bc 00    ???L???4???F???.
70: bc bc bc 38 bc bc bc 11 bc bc bc 20 bc bc bc 20    ???8??????? ???
80: bc bc bc ff bc bc bc ff bc bc bc ff bc bc bc ff    ???.???.???.???.
...

which can lead to:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder
[drm:drm_edid_block_valid] *ERROR* Raw EDID:
&lt;3&gt;30 30 30 30 30 30 30 32 38 32 30 32 63 63 31 61  000000028202cc1a
&lt;3&gt;28 00 02 8c 00 00 00 00 18 00 00 00 00 00 00 00  (...............
&lt;3&gt;20 4c 61 73 74 20 62 65 61 63 6f 6e 3a 20 33 32   Last beacon: 32
&lt;3&gt;32 30 6d 73 20 61 67 6f 46 00 05 8c 00 00 00 00  20ms agoF.......
&lt;3&gt;36 00 00 00 00 00 00 00 00 0c 57 69 2d 46 69 20  6.........Wi-Fi
&lt;3&gt;52 6f 75 74 65 72 01 08 82 84 8b 96 24 30 48 6c  Router......$0Hl
&lt;3&gt;03 01 01 06 02 00 00 2a 01 00 2f 01 00 32 04 0c  .......*../..2..
&lt;3&gt;12 18 60 dd 09 00 10 18 02 00 00 01 00 00 18 00  ..`.............

Signed-off-by: David Flynn &lt;davidf@rd.bbc.co.uk&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;
[ickle: fix up some surrounding checkpatch warnings]
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/radeon/kms: reorder display resume to avoid problems</title>
<updated>2011-02-06T19:03:50Z</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.amat.us/linux/commit/?id=2f33a030c672eff1af2a5414c497a10d66b80982'/>
<id>urn:sha1:2f33a030c672eff1af2a5414c497a10d66b80982</id>
<content type='text'>
commit a93f344d3c04e4b84490c65f2a574387c593be40 upstream.

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;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>drm/radeon/kms: fix evergreen asic reset</title>
<updated>2011-02-06T19:03:50Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-20T17:35:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ee8aa621efcdd5dd76a91f0085e1f2dc940cb3b8'/>
<id>urn:sha1:ee8aa621efcdd5dd76a91f0085e1f2dc940cb3b8</id>
<content type='text'>
commit 9f0c4f9c2f835eee1bbb93f96bf9483d56f1892b upstream.

Only reset the grbm blocks, srbm tends to lock the GPU
if not done properly and in most cases is not necessary.
Also, no need to call asic init after reset the grbm blocks.

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;
Reviewed-by: Jerome Glisse &lt;jglisse@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/radeon/kms/evergreen: reset the grbm blocks at resume and init</title>
<updated>2011-02-06T19:03:49Z</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.amat.us/linux/commit/?id=a3f86d59f4f072da1d289a9c12cd4c10fbc3e065'/>
<id>urn:sha1:a3f86d59f4f072da1d289a9c12cd4c10fbc3e065</id>
<content type='text'>
commit 86f5c9edbb3bac37cc8cee6528a929005ba72aad upstream.

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;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>nouveau: Acknowledge HPD irq in handler, not bottom half</title>
<updated>2011-02-06T19:03:40Z</updated>
<author>
<name>Andy Lutomirski</name>
<email>luto@mit.edu</email>
</author>
<published>2010-11-16T23:40:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=89c24ec0eee40272f0387eeb6a6cc31e6bbc1544'/>
<id>urn:sha1:89c24ec0eee40272f0387eeb6a6cc31e6bbc1544</id>
<content type='text'>
commit ab838338a2a9e0cb8346eb0cab9977be13e8dce5 upstream.

The old code generated an interrupt storm bad enough to completely
take down my system.

Signed-off-by: Andy Lutomirski &lt;luto@mit.edu&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>drm/radeon/kms: fix vram base calculation on rs780/rs880</title>
<updated>2011-02-06T19:03:26Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-03T19:37:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e3e8f697884d634e45e31734bc16d20a45452cb6'/>
<id>urn:sha1:e3e8f697884d634e45e31734bc16d20a45452cb6</id>
<content type='text'>
commit 8961d52d4cc52edf5672f8f2712c57162b736793 upstream.

Avoid overflowing a 32 bit value.

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>drm/kms: remove spaces from connector names (v2)</title>
<updated>2011-02-06T19:03:25Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-09T00:09:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6b3a20cdc30067b8825c7f773a3b0b16cb56ed21'/>
<id>urn:sha1:6b3a20cdc30067b8825c7f773a3b0b16cb56ed21</id>
<content type='text'>
commit e76116ca9671e2e5239054a40303b94feab585ad upstream.

Grub doesn't parse spaces in parameters correctly, so
this makes it impossible to force video= parameters
for kms on the grub kernel command line.

v2: shorten the names to make them easier to type.

Reported-by: Sergej Pupykin &lt;ml@sergej.pp.ru&gt;

Cc: Sergej Pupykin &lt;ml@sergej.pp.ru&gt;
Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>drm/radeon/kms: don't apply 7xx HDP flush workaround on AGP</title>
<updated>2011-02-06T19:03:25Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2010-12-08T15:05:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=099433591bd86e532987a4e481fe351c4237386e'/>
<id>urn:sha1:099433591bd86e532987a4e481fe351c4237386e</id>
<content type='text'>
commit f3886f85cfde578f1d0ba6e40ac5f9d70043923b upstream.

It should be required for all 7xx asics, but seems to cause
problems on some AGP 7xx chips.

Fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=19002

Signed-off-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;
Reported-and-Tested-by: Duncan &lt;1i5t5.duncan@cox.net&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915/sdvo: Always add a 30ms delay to make SDVO TV detection reliable</title>
<updated>2010-12-14T22:40:11Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-11-24T17:37:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=df5b9f1cdee1c24106013c18c195ca6a98022291'/>
<id>urn:sha1:df5b9f1cdee1c24106013c18c195ca6a98022291</id>
<content type='text'>
commit ba84cd1f2b5dd49bda9300c5a11373f7e14c3c66 upstream.

Commit d09c23de intended to add a 30ms delay to give the ADD time to
detect any TVs connected. However, it used the sdvo-&gt;is_tv flag to do so
which is dependent upon the previous detection result and not whether the
output supports TVs.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
</feed>
