linux/drivers/gpu/drm/via, branch v3.3.4

drm/sis|via: don't return stack garbage from free_mem ioctl

2012-01-09T12:11:39Z

Fallout from my "kill drm_sman" refactor. Unfortunately gcc seems to have failed me and not warned about this. Tested-by: Jakob Bornecrantz (on via) Signed-off-by: Daniel Vetter Signed-off-by: Dave Airlie

drm/via: use drm_mm instead of drm_sman

2011-12-21T23:33:22Z

To make the transition in a piece-wise and bisectable way possible, I've hijacked the ->owner_list from drm_sman. While transitioning, the list_add was done by the driver, while the list_del was still done by the dying sman code. Now that we are in full control of ->owner_list, do the list_del ourselves. v2: Better explain the list_del trickery as suggested by Chris Wilson. Signed-off-by: Daniel Vetter

drm/sis: track user->memblock mapping with idr

2011-12-21T23:33:21Z

Signed-off-by: Daniel Vetter

drm/via: track user->memblock mapping with idr

2011-12-21T23:33:20Z

Massive indirection through a hashtable for a simple key->pointer look-up actually just adds bloat. v2: Drop the misleading comment noted by Chris Wilson. Signed-off-by: Daniel Vetter

drm/sman: rip out owner tracking

2011-12-21T23:33:20Z

In contrast to kms drivers, sis/via _always_ associated a buffer with a drm fd. So by the time we reach lastclose, all open drm fds are gone and with them their associated objects. So when sis/via call drm_sman_cleanup in their lastclose funcs, that will free 0 objects. The owner tracking now serves no purpose at all, hence rip it ou. We can't kill the corresponding fields in struct drm_memblock_item yet because we hijack these in the new driver private owner tracking. But now that drm_sman.c doesn't touch ->owner_list anymore, we need to kill the list_move hack and properly add the item to the file_priv list. Also leave the list_del(&obj->owner_list) in drm_sman_free for the moment, it will move to the drivers when sman disappears completely. v2: Remove the redundant INIT_LIST_HEAD as noted by Chris Wilson Signed-off-by: Daniel Vetter

drm/via: track obj->drm_fd relations in the driver

2011-12-21T23:33:19Z

Exactly like the previous patch for sis. Signed-off-by: Daniel Vetter

drm: Make the per-driver file_operations struct const

2011-11-11T11:14:47Z

From fdf1fdebaa00f81de18c227f32f8074c8b352d50 Mon Sep 17 00:00:00 2001 From: Arjan van de Ven Date: Sun, 30 Oct 2011 19:06:07 -0700 Subject: [PATCH] drm: Make the per-driver file_operations struct const The DRM layer keeps a copy of struct file_operations inside its big driver struct... which prevents it from being consistent and static. For consistency (and the general security objective of having such things static), it's desirable to get this fixed. This patch splits out the file_operations field to its own struct, which is then "static const", and just stick a pointer to this into the driver struct, making it more consistent with how the rest of the kernel does this. Signed-off-by: Arjan van de Ven Signed-off-by: Dave Airlie

gpu: add module.h to drivers/gpu files as required.

2011-10-31T23:32:03Z

So that we don't get build failures once the implicit module.h presence is removed. Signed-off-by: Paul Gortmaker

drm: rework PCI/platform driver interface.

2011-02-07T03:09:36Z

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

drivers/gpu: Use vzalloc

2010-11-09T03:41:35Z

Signed-off-by: Joe Perches Reviewed-by: Thomas Hellstrom Signed-off-by: Dave Airlie