An error occurred fetching the project authors.
- 27 Mar, 2007 1 commit
-
-
David S. Miller authored
The Kconfig bits were removed long ago, so we should kill off the driver too. Signed-off-by:
David S. Miller <davem@davemloft.net>
-
- 21 Sep, 2006 2 commits
-
-
Thomas Hellstrom authored
This add support to the SiS and VIA drivers for the simple memory manager. This fixes a lot of problems with the current simple code these drivers used, including locking and SMP issues. Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
Thomas Hellstrom authored
This adds the DRM hashtable and simple memory manager implementations from Tungsten Graphics, this is NOT the new memory manager, this is a replacement for the SIS and VIA memory managers. Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 12 Nov, 2005 1 commit
-
-
Dave Airlie authored
Add PCI DMA blitengine to VIA DRM Add portability code for porting VIA to FreeBSD. Sync via_drm.h with 3d driver From: Thomas Hellstrom <unichrome@shipmail.org>, Eric Anholt <anholt@freebsd.org> Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 10 Nov, 2005 1 commit
-
-
Dave Airlie authored
Move drm_cpu_valid into drm_fops.c Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 16 Aug, 2005 1 commit
-
-
Dave Airlie authored
This adds initial r300 3D support to the radeon DRM. From: Nicolai Haehnle, Vladimir Dergachev, and others. Signed-off-by:
David Airlie <airlied@linux.ie>
-
- 07 Aug, 2005 1 commit
-
-
Dave Airlie authored
Add driver for savage chipsets. From: Felix Kuehling Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 05 Aug, 2005 1 commit
-
-
Dave Airlie authored
The gamma driver has been broken for quite a while, it doesn't build, we don't have a userspace, mine is in Ireland etc... Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 07 Jul, 2005 1 commit
-
-
Dave Airlie authored
This adds compatiblity ioctls for mga/r128 and i915 DRM drivers. From: Paul Mackerras, David Airlie, Alan Hourihane, Egbert Eich. Signed-off-by:
David Airlie <airlied@linux.ie>
-
- 28 Jun, 2005 1 commit
-
-
Dave Airlie authored
Add DRM device driver for VIA Unichrome chipsets From: Unichrome Project http://unichrome.sf.net, Erdi Chen, Thomas Hellstrom Signed-off-by: Dave Airlie <airlied@linux.ie>
-
- 23 Jun, 2005 1 commit
-
-
Dave Airlie authored
The patch is against a 2.6.11 kernel tree. I am running this with a 32-bit X server (compiled up from X.org CVS as of a couple of weeks ago) and 32-bit DRI libraries and clients. All the userland stuff is identical to what I am using under a 32-bit kernel on my G4 powerbook (which is a 32-bit machine of course). I haven't tried compiling up a 64-bit X server or clients yet. In the compatibility routines I have assumed that the kernel can safely access user addresses after set_fs(KERNEL_DS). That is, where an ioctl argument structure contains pointers to other structures, and those other structures are already compatible between the 32-bit and 64-bit ABIs (i.e. they only contain things like chars, shorts or ints), I just check the address with access_ok() and then pass it through to the 64-bit ioctl code. I believe this approach may not work on sparc64, but it does work on ppc64 and x86_64 at least. One tricky area which may need to be revisited is the question of how to handle the handles which we pass back to userspace to identify mappings. These handles are generated in the ADDMAP ioctl and then passed in as the offset value to mmap. However, offset values for mmap seem to be generated in other ways as well, particularly for AGP mappings. The approach I have ended up with is to generate a fake 32-bit handle only for _DRM_SHM mappings. The handles for other mappings (AGP, REG, FB) are physical addresses which are already limited to 32 bits, and generating fake handles for them created all sorts of problems in the mmap/nopage code. This patch has been updated to use the new compatibility ioctls. From: Paul Mackerras <paulus@samba.org> Signed-off-by:
Dave Airlie <airlied@linux.ie>
-
- 16 Apr, 2005 1 commit
-
-
Linus Torvalds authored
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-