<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v3.3-rc2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu?h=v3.3-rc2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu?h=v3.3-rc2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-01-30T09:32:39Z</updated>
<entry>
<title>vmwgfx: Fix assignment in vmw_framebuffer_create_handle</title>
<updated>2012-01-30T09:32:39Z</updated>
<author>
<name>Ryan Mallon</name>
<email>rmallon@gmail.com</email>
</author>
<published>2012-01-27T21:51:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bf9c05d5b6d19b3e4c9fe21047694e94f48db89b'/>
<id>urn:sha1:bf9c05d5b6d19b3e4c9fe21047694e94f48db89b</id>
<content type='text'>
The assignment of handle in vmw_framebuffer_create_handle doesn't actually do anything useful and is incorrectly assigning an integer value to a pointer argument. It appears that this is a typo and should be dereferencing handle rather than assigning to it directly. This fixes a bug where an undefined handle value is potentially returned to user-space.

Signed-off-by: Ryan Mallon &lt;rmallon@gmail.com&gt;
Reviewed-by: Jakob Bornecrantz&lt;jakob@vmware.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon/kms: Fix device tree linkage of i2c buses</title>
<updated>2012-01-30T09:32:11Z</updated>
<author>
<name>Jean Delvare</name>
<email>jdelvare@suse.de</email>
</author>
<published>2012-01-28T10:10:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1ffd57c1da2a73b0a0e5cd7a6dd52cc49e36bef9'/>
<id>urn:sha1:1ffd57c1da2a73b0a0e5cd7a6dd52cc49e36bef9</id>
<content type='text'>
Properly set the parent device of i2c buses before registering them so
that they will show at the right place in the device tree (rather than
in /sys/devices directly.)

Signed-off-by: Jean Delvare &lt;jdelvare@suse.de&gt;
Cc: Dave Airlie &lt;airlied@gmail.com&gt;
Reviewed-by: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Pass the real error code back during GEM bo initialisation</title>
<updated>2012-01-30T09:31:42Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2012-01-29T16:45:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dd8bc93d45c0ac4f64bf074d4be72418aac1609b'/>
<id>urn:sha1:dd8bc93d45c0ac4f64bf074d4be72418aac1609b</id>
<content type='text'>
In particular, I found I was hitting the max-file limit in the VFS,
and the EFILE was being magically transformed into ENOMEM. Confusion
reigns.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Revert "drm/i810: cleanup reclaim_buffers"</title>
<updated>2012-01-30T09:31:25Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2012-01-29T16:05:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6e877b576ddf7cde5db2e9a6dcb56fef0ea77e64'/>
<id>urn:sha1:6e877b576ddf7cde5db2e9a6dcb56fef0ea77e64</id>
<content type='text'>
This reverts commit 87499ffdcb1c70f66988cd8febc4ead0ba2f9118.

Where is that paper bag ... ah here.

I've failed to take an odd interaction between my other cleanups and
this reclaim_buffers patch into account and also failed to properly
test it. Looks like there are more dragons and hidden trapdoors in the
drm release path than actual lines of code.

Until I get a clue, let's just revert this.

Signed-Off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>gma500: Fix suspend/resume functions</title>
<updated>2012-01-27T11:52:07Z</updated>
<author>
<name>Ryan Mallon</name>
<email>rmallon@gmail.com</email>
</author>
<published>2012-01-27T06:28:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2d8357e66df9f7593cbe23b224b4ed06aff90e73'/>
<id>urn:sha1:2d8357e66df9f7593cbe23b224b4ed06aff90e73</id>
<content type='text'>
Both the suspend and resume functions incorrectly set psbfb =
to_psb_fb(NULL) outside of the loop over all of the framebuffers. Fix
this by moving the assignment of psbfb inside the loop and removing the
initialisation of fb.

Signed-off-by: Ryan Mallon &lt;rmallon@gmail.com&gt;
Acked-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: fixed pm feature for fimd module.</title>
<updated>2012-01-27T04:03:59Z</updated>
<author>
<name>Inki Dae</name>
<email>inki.dae@samsung.com</email>
</author>
<published>2012-01-27T02:54:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=373af0c0c539b109ea978e96f217df0fc20aa261'/>
<id>urn:sha1:373af0c0c539b109ea978e96f217df0fc20aa261</id>
<content type='text'>
this patch separates fimd specific power on/off function from pm function
and the pm interfaces will call that function for power on or off.
and also removes unnecessary codes of resume function.

Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: fixed build dependency for DRM_EXYNOS_FIMD</title>
<updated>2012-01-27T01:43:25Z</updated>
<author>
<name>Inki Dae</name>
<email>inki.dae@samsung.com</email>
</author>
<published>2012-01-16T09:55:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a4b42dab293afdabc3e4ae57cbc743ad05af0e4b'/>
<id>urn:sha1:a4b42dab293afdabc3e4ae57cbc743ad05af0e4b</id>
<content type='text'>
FB based FIMD and DRM based FIMD drivers use same hardware
so with this patch, only one of them would be selected.

Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: fix build dependency for DRM_EXYNOS_HDMI</title>
<updated>2012-01-27T01:43:24Z</updated>
<author>
<name>Seung-Woo Kim</name>
<email>sw0312.kim@samsung.com</email>
</author>
<published>2012-01-04T06:34:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2363dc636df34abb795c31668eeadc659e815fbd'/>
<id>urn:sha1:2363dc636df34abb795c31668eeadc659e815fbd</id>
<content type='text'>
DRM_EXYNOS_HDMI driver and VIDEO_SAMSUNG_S5P_TV driver should be
not enabled at once because they use same HW blocks. So dependency
for DRM_EXYNOS_HDMI is fixed to check VIDEO_SAMSUNG_S5P_TV=n.

Signed-off-by: Seung-Woo Kim &lt;sw0312.kim@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: use release_mem_region instead of release_resource</title>
<updated>2012-01-27T01:43:23Z</updated>
<author>
<name>Seung-Woo Kim</name>
<email>sw0312.kim@samsung.com</email>
</author>
<published>2011-12-22T02:30:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=485bc54c3360e9c1d595c48c9c82dbd3a51e133e'/>
<id>urn:sha1:485bc54c3360e9c1d595c48c9c82dbd3a51e133e</id>
<content type='text'>
To make a api pair of request_mem_region and release_mem_region,
release_mem_region is used instead of release_resource.

Signed-off-by: Seung-Woo Kim &lt;sw0312.kim@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'drm-intel-fixes' of git://people.freedesktop.org/~keithp/linux into drm-fixes</title>
<updated>2012-01-26T18:25:54Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2012-01-26T18:25:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c8fe74ae9a7285767cda1a053cfe806d67f77227'/>
<id>urn:sha1:c8fe74ae9a7285767cda1a053cfe806d67f77227</id>
<content type='text'>
* 'drm-intel-fixes' of git://people.freedesktop.org/~keithp/linux: (24 commits)
  drm/i915: fixup forcewake spinlock fallout in drpc debugfs function
  drm/i915: debugfs: show semaphore registers also on gen7
  drm/i915: allow userspace forcewake references also on gen7
  drm/i915: Re-enable gen7 RC6 and GPU turbo after resume.
  drm/i915: Correct debugfs printout for RC1e.
  Revert "drm/i915: Work around gen7 BLT ring synchronization issues."
  drm/i915: rip out the HWSTAM missed irq workaround
  drm/i915: paper over missed irq issues with force wake voodoo
  drm/i915: Hold gt_lock across forcewake register reads
  drm/i915: Hold gt_lock during reset
  drm/i915: Move reset forcewake processing to gen6_do_reset
  drm/i915: protect force_wake_(get|put) with the gt_lock
  drm/i915: convert force_wake_get to func pointer in the gpu reset code
  drm/i915: sprite init failure on pre-SNB is not a failure
  drm/i915: VBT Parser cleanup for eDP block
  drm/i915: mask transcoder select bits before setting them on LVDS
  drm/i915: Add Clientron E830 to the ignore LVDS list
  CHROMIUM: i915: Add DMI override to skip CRT initialization on ZGB
  drm/i915: handle 3rd pipe
  drm/i915: simplify pipe checking
  ...
</content>
</entry>
</feed>
