<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu/drm/sis, branch v3.0.84</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu/drm/sis?h=v3.0.84</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu/drm/sis?h=v3.0.84'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-02-07T03:09:36Z</updated>
<entry>
<title>drm: rework PCI/platform driver interface.</title>
<updated>2011-02-07T03:09:36Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@gmail.com</email>
</author>
<published>2010-12-14T17:16:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8410ea3b95d105a5be5db501656f44bbb91197c1'/>
<id>urn:sha1:8410ea3b95d105a5be5db501656f44bbb91197c1</id>
<content type='text'>
This abstracts the pci/platform interface out a step further,
we can go further but this is far enough for now to allow USB
to be plugged in.

The drivers now just call the init code directly for their
device type.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'drm-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6</title>
<updated>2010-10-27T01:57:59Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2010-10-27T01:57:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c48c43e422c1404fd72c57d1d21a6f6d01e18900'/>
<id>urn:sha1:c48c43e422c1404fd72c57d1d21a6f6d01e18900</id>
<content type='text'>
* 'drm-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6: (476 commits)
  vmwgfx: Implement a proper GMR eviction mechanism
  drm/radeon/kms: fix r6xx/7xx 1D tiling CS checker v2
  drm/radeon/kms: properly compute group_size on 6xx/7xx
  drm/radeon/kms: fix 2D tile height alignment in the r600 CS checker
  drm/radeon/kms/evergreen: set the clear state to the blit state
  drm/radeon/kms: don't poll dac load detect.
  gpu: Add Intel GMA500(Poulsbo) Stub Driver
  drm/radeon/kms: MC vram map needs to be &gt;= pci aperture size
  drm/radeon/kms: implement display watermark support for evergreen
  drm/radeon/kms/evergreen: add some additional safe regs v2
  drm/radeon/r600: fix tiling issues in CS checker.
  drm/i915: Move gpu_write_list to per-ring
  drm/i915: Invalidate the to-ring, flush the old-ring when updating domains
  drm/i915/ringbuffer: Write the value passed in to the tail register
  agp/intel: Restore valid PTE bit for Sandybridge after bdd3072
  drm/i915: Fix flushing regression from 9af90d19f
  drm/i915/sdvo: Remove unused encoding member
  i915: enable AVI infoframe for intel_hdmi.c [v4]
  drm/i915: Fix current fb blocking for page flip
  drm/i915: IS_IRONLAKE is synonymous with gen == 5
  ...

Fix up conflicts in
 - drivers/gpu/drm/i915/{i915_gem.c, i915/intel_overlay.c}: due to the
   new simplified stack-based kmap_atomic() interface
 - drivers/gpu/drm/vmwgfx/vmwgfx_drv.c: added .llseek entry due to BKL
   removal cleanups.
</content>
</entry>
<entry>
<title>drm: use noop_llseek</title>
<updated>2010-09-16T08:33:07Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2010-07-06T16:54:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc880abef75e7c62c9048171f5112500f36a9244'/>
<id>urn:sha1:dc880abef75e7c62c9048171f5112500f36a9244</id>
<content type='text'>
The drm device drivers currently allow seeking on the
character device but never care about the actual
file position.

When we change the default llseek operation to be
no_llseek, calling llseek on a drm device would
return an error condition, which is an API change.

Explicitly setting noop_llseek lets us keep the
current API.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Cc: David Airlie &lt;airlied@linux.ie&gt;
Cc: dri-devel@lists.freedesktop.org
</content>
</entry>
<entry>
<title>drm: kill get_reg_ofs callback</title>
<updated>2010-08-29T23:44:56Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2010-08-23T20:53:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cbc60ca04b342a4e1f2a1086a7277c077f07dbed'/>
<id>urn:sha1:cbc60ca04b342a4e1f2a1086a7277c077f07dbed</id>
<content type='text'>
Every driver used the default implementation. Fold that one into
the only callsite and drop the callback.

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>drm: kill drm_map_ofs callbacks</title>
<updated>2010-08-29T23:38:50Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2010-08-23T20:53:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=793a97e4cc38f834e0488ccc1ecbfe52ff6f5b84'/>
<id>urn:sha1:793a97e4cc38f834e0488ccc1ecbfe52ff6f5b84</id>
<content type='text'>
All drivers happily copy&amp;pasted the default implementation without
checking whether this callback is used at all. It's not. Sigh.

Kill it.

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>drm: kill context_ctor callback</title>
<updated>2010-08-29T23:38:25Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2010-08-23T20:53:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b3da8f7d2d1fa81fb65cb3f5d9e50dde40a83182'/>
<id>urn:sha1:b3da8f7d2d1fa81fb65cb3f5d9e50dde40a83182</id>
<content type='text'>
It's not used by any driver. The destructor callback is unfortunately
used by the via driver in a rather convoluted piece of code used
to reimplement something resembling broken futexes. I didn't dare
to touch this code. But at least kill the needless NULL assignemt
in the sis driver.

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>drm: block userspace under allocating buffer and having drivers overwrite it (v2)</title>
<updated>2010-08-17T04:52:25Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2010-08-14T10:20:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1b2f1489633888d4a06028315dc19d65768a1c05'/>
<id>urn:sha1:1b2f1489633888d4a06028315dc19d65768a1c05</id>
<content type='text'>
With the current screwed but its ABI, ioctls for the drm, Linus pointed out that we could allow userspace to specify the allocation size, but we pass it to the driver which then uses it blindly to store a struct. Now if userspace specifies the allocation size as smaller than the driver needs, the driver can possibly overwrite memory.

This patch restructures the driver ioctls so we store the structure size we are expecting, and make sure we allocate at least that size. The copy from/to userspace are still restricted to the size the user specifies, this allows ioctl structs to grow on both sides of the equation.

Up until now we didn't really use the DRM_IOCTL defines in the kernel, so this cleans them up and adds them for nouveau.

v2:
fix nouveau pushbuf arg (thanks to Ben for pointing it out)

Reported-by: Linus Torvalds &lt;torvalds@linuxfoundation.org&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/sis: fixed brace and spacing coding style issues</title>
<updated>2010-08-02T00:18:17Z</updated>
<author>
<name>Nicolas Kaiser</name>
<email>nikai@nikai.net</email>
</author>
<published>2010-07-09T14:47:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a7b98b6748efdddd832b39662801c9f828df1813'/>
<id>urn:sha1:a7b98b6748efdddd832b39662801c9f828df1813</id>
<content type='text'>
Fixed brace and spacing coding style issues.

Signed-off-by: Nicolas Kaiser &lt;nikai@nikai.net&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: convert drm_ioctl to unlocked_ioctl</title>
<updated>2009-12-18T01:22:31Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2009-12-16T22:17:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ed8b67040965e4fe695db333d5914e18ea5f146f'/>
<id>urn:sha1:ed8b67040965e4fe695db333d5914e18ea5f146f</id>
<content type='text'>
drm_ioctl is called with the Big Kernel Lock held,
which shows up very high in statistics on vfs_ioctl.

Moving the lock into the drm_ioctl function itself
makes sure we blame the right subsystem and it gets
us one step closer to eliminating the locked version
of fops-&gt;ioctl.

Since drm_ioctl does not require the lock itself,
we only need to hold it while calling the specific
handler. The 32 bit conversion handlers do not
interact with any other code, so they don't need
the BKL here either and can just call drm_ioctl.

As a bonus, this cleans up all the other users
of drm_ioctl which now no longer have to find
the inode or call lock_kernel.

[airlied: squashed the non-driver bits
of the second patch in here, this provides
the flag for drivers to use to select unlocked
ioctls - but doesn't modify any drivers].

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Cc: David Airlie &lt;airlied@linux.ie&gt;
Cc: dri-devel@lists.sourceforge.net
Cc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Remove memory debugging infrastructure.</title>
<updated>2009-06-18T20:00:33Z</updated>
<author>
<name>Eric Anholt</name>
<email>eric@anholt.net</email>
</author>
<published>2009-03-24T19:23:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9a298b2acd771d8a5c0004d8f8e4156c65b11f6b'/>
<id>urn:sha1:9a298b2acd771d8a5c0004d8f8e4156c65b11f6b</id>
<content type='text'>
It hasn't been used in ages, and having the user tell your how much
memory is being freed at free time is a recipe for disaster even if it
was ever used.

Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
</content>
</entry>
</feed>
