<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v3.4.43</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu?h=v3.4.43</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu?h=v3.4.43'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-04-26T04:19:56Z</updated>
<entry>
<title>fbcon: fix locking harder</title>
<updated>2013-04-26T04:19:56Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@gmail.com</email>
</author>
<published>2013-01-25T01:38:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=726cc91ed26521f3e678346e5745203a70edd456'/>
<id>urn:sha1:726cc91ed26521f3e678346e5745203a70edd456</id>
<content type='text'>
commit 054430e773c9a1e26f38e30156eff02dedfffc17 upstream.

Okay so Alan's patch handled the case where there was no registered fbcon,
however the other path entered in set_con2fb_map pit.

In there we called fbcon_takeover, but we also took the console lock in a couple
of places. So push the console lock out to the callers of set_con2fb_map,

this means fbmem and switcheroo needed to take the lock around the fb notifier
entry points that lead to this.

This should fix the efifb regression seen by Maarten.

Tested-by: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
Tested-by: Lu Hua &lt;huax.lu@intel.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>udl: handle EDID failure properly.</title>
<updated>2013-04-17T04:27:26Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@gmail.com</email>
</author>
<published>2013-04-12T03:25:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bff6627568427d14375d84426f491646fdf71a1f'/>
<id>urn:sha1:bff6627568427d14375d84426f491646fdf71a1f</id>
<content type='text'>
commit 1baee58638fc58248625255f5c5fcdb987f11b1f upstream.

Don't oops seems proper.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: Use the correct size of the GTT for placing the per-process entries</title>
<updated>2013-04-17T04:27:26Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2012-08-24T08:12:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=706d153865d8efb9164faf220a66f224969fed84'/>
<id>urn:sha1:706d153865d8efb9164faf220a66f224969fed84</id>
<content type='text'>
commit 9a0f938bde74bf9e50bd75c8de9e38c1787398cd upstream.

The current layout is to place the per-process tables at the end of the
GTT. However, this is currently using a hardcoded maximum size for the GTT
and not taking in account limitations imposed by the BIOS. Use the value
for the total number of entries allocated in the table as provided by
the configuration registers.

Reported-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Ben Widawsky &lt;ben@bwidawsk.net&gt;
Cc: Matthew Garret &lt;mjg@redhat.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: Don't clobber crtc-&gt;fb when queue_flip fails</title>
<updated>2013-04-05T17:04:36Z</updated>
<author>
<name>Ville Syrjälä</name>
<email>ville.syrjala@linux.intel.com</email>
</author>
<published>2013-02-22T14:53:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3c7fe7b4421b23733eddfb53167c78c0bee71169'/>
<id>urn:sha1:3c7fe7b4421b23733eddfb53167c78c0bee71169</id>
<content type='text'>
commit 4a35f83b2b7c6aae3fc0d1c4554fdc99dc33ad07 upstream.

Restore crtc-&gt;fb to the old framebuffer if queue_flip fails.

While at it, kill the pointless intel_fb temp variable.

v2: Update crtc-&gt;fb before queue_flip and restore it back
    after a failure.

Backported for 3.4-stable. Adjusted context only.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reported-and-Tested-by: Mika Kuoppala &lt;mika.kuoppala@intel.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Lingzhu Xiang &lt;lxiang@redhat.com&gt;
Reviewed-by: CAI Qian &lt;caiqian@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>i915: initialize CADL in opregion</title>
<updated>2013-03-28T19:12:28Z</updated>
<author>
<name>Lekensteyn</name>
<email>lekensteyn@gmail.com</email>
</author>
<published>2012-06-25T22:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2f7dea37d1b0b3a26fb3c2bd97bbf836dfd04def'/>
<id>urn:sha1:2f7dea37d1b0b3a26fb3c2bd97bbf836dfd04def</id>
<content type='text'>
commit d627b62ff8d4d36761adbcd90ff143d79c94ab22 upstream.

This is rather a hack to fix brightness hotkeys on a Clevo laptop. CADL is not
used anywhere in the driver code at the moment, but it could be used in BIOS as
is the case with the Clevo laptop.

The Clevo B7130 requires the CADL field to contain at least the ID of
the LCD device. If this field is empty, the ACPI methods that are called
on pressing brightness / display switching hotkeys will not trigger a
notification. As a result, it appears as no hotkey has been pressed.

Reference: https://bugs.freedesktop.org/show_bug.cgi?id=45452
Tested-by: Peter Wu &lt;lekensteyn@gmail.com&gt;
Signed-off-by: Peter Wu &lt;lekensteyn@gmail.com&gt;
Acked-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/radeon/benchmark: make sure bo blit copy exists before using it</title>
<updated>2013-03-28T19:12:14Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexander.deucher@amd.com</email>
</author>
<published>2013-03-12T16:53:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f16d21e7f065a30b48c1149c888a3d75da40061a'/>
<id>urn:sha1:f16d21e7f065a30b48c1149c888a3d75da40061a</id>
<content type='text'>
commit fa8d387dc3f62062a6b4afbbb2a3438094fd8584 upstream.

Fixes a segfault on asics without a blit callback.

Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=62239

Reviewed-by: Michel Dänzer &lt;michel.daenzer@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/radeon: add support for Richland APUs</title>
<updated>2013-03-28T19:12:14Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexander.deucher@amd.com</email>
</author>
<published>2013-03-08T18:44:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ae7952e88f6cd5e0605501b1662283a6adb6501a'/>
<id>urn:sha1:ae7952e88f6cd5e0605501b1662283a6adb6501a</id>
<content type='text'>
commit e4d170633fde379f39a90f8a5e7eb619b5d1144d upstream.

Richland APUs are a new version of the Trinity APUs
with performance and power management improvements.

Reviewed-by: Jerome Glisse &lt;jglisse@redhat.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>KMS: fix EDID detailed timing frame rate</title>
<updated>2013-03-28T19:12:11Z</updated>
<author>
<name>Torsten Duwe</name>
<email>torsten@lst.de</email>
</author>
<published>2013-03-23T14:39:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=612dadee15aa0a474309a93f53172920fe93d609'/>
<id>urn:sha1:612dadee15aa0a474309a93f53172920fe93d609</id>
<content type='text'>
commit c19b3b0f6eed552952845e4ad908dba2113d67b4 upstream.

When KMS has parsed an EDID "detailed timing", it leaves the frame rate
zeroed.  Consecutive (debug-) output of that mode thus yields 0 for
vsync.  This simple fix also speeds up future invocations of
drm_mode_vrefresh().

While it is debatable whether this qualifies as a -stable fix I'd apply
it for consistency's sake; drm_helper_probe_single_connector_modes()
does the same thing already for all probed modes.

Signed-off-by: Torsten Duwe &lt;duwe@lst.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>KMS: fix EDID detailed timing vsync parsing</title>
<updated>2013-03-28T19:12:11Z</updated>
<author>
<name>Torsten Duwe</name>
<email>torsten@lst.de</email>
</author>
<published>2013-03-23T14:38:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2c5d8164483160f6f280da92e358af16aa966cf1'/>
<id>urn:sha1:2c5d8164483160f6f280da92e358af16aa966cf1</id>
<content type='text'>
commit 16dad1d743d31a104a849c8944e6b9eb479f6cd7 upstream.

EDID spreads some values across multiple bytes; bit-fiddling is needed
to retrieve these.  The current code to parse "detailed timings" has a
cut&amp;paste error that results in a vsync offset of at most 15 lines
instead of 63.

See

   http://en.wikipedia.org/wiki/EDID

and in the "EDID Detailed Timing Descriptor" see bytes 10+11 show why
that needs to be a left shift.

Signed-off-by: Torsten Duwe &lt;duwe@lst.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: bounds check execbuffer relocation count</title>
<updated>2013-03-28T19:12:10Z</updated>
<author>
<name>Kees Cook</name>
<email>keescook@chromium.org</email>
</author>
<published>2013-03-12T00:31:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e03f8b87d6b11e8c2f9d31b221d8c536091485af'/>
<id>urn:sha1:e03f8b87d6b11e8c2f9d31b221d8c536091485af</id>
<content type='text'>
commit 3118a4f652c7b12c752f3222af0447008f9b2368 upstream.

It is possible to wrap the counter used to allocate the buffer for
relocation copies. This could lead to heap writing overflows.

CVE-2013-0913

v3: collapse test, improve comment
v2: move check into validate_exec_list

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Reported-by: Pinkie Pie
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

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