linux-stable/drivers/char/drm
Tim Schmielau cd354f1ae7 [PATCH] remove many unneeded #includes of sched.h
After Al Viro (finally) succeeded in removing the sched.h #include in module.h
recently, it makes sense again to remove other superfluous sched.h includes.
There are quite a lot of files which include it but don't actually need
anything defined in there.  Presumably these includes were once needed for
macros that used to live in sched.h, but moved to other header files in the
course of cleaning it up.

To ease the pain, this time I did not fiddle with any header files and only
removed #includes from .c-files, which tend to cause less trouble.

Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
configs in arch/arm/configs on arm.  I also checked that no new warnings were
introduced by the patch (actually, some warnings are removed that were emitted
by unnecessarily included header files).

Signed-off-by: Tim Schmielau <tim@physik3.uni-rostock.de>
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-02-14 08:09:54 -08:00
..
ati_pcigart.c
drm.h
drm_agpsupport.c
drm_auth.c
drm_bufs.c drm: Allow for 44 bit user-tokens (or drm_file offsets) 2007-02-08 16:14:05 +11:00
drm_context.c
drm_core.h
drm_dma.c
drm_drawable.c
drm_drv.c [PATCH] mark struct file_operations const 3 2007-02-12 09:48:45 -08:00
drm_fops.c
drm_hashtab.c
drm_hashtab.h
drm_ioc32.c
drm_ioctl.c
drm_irq.c
drm_lock.c drm: make kernel context switch same as for drm git tree. 2006-12-19 17:49:44 +11:00
drm_memory.c drm: remove drm_ioremap and drm_ioremapfree 2007-02-08 13:24:26 +11:00
drm_memory.h drm: remove drm_ioremap and drm_ioremapfree 2007-02-08 13:24:26 +11:00
drm_memory_debug.h drm: remove drm_ioremap and drm_ioremapfree 2007-02-08 13:24:26 +11:00
drm_mm.c drm: update core memory manager from git drm tree 2007-02-08 13:24:26 +11:00
drm_os_linux.h
drm_pci.c
drm_pciids.h via: add some new chipsets 2007-02-08 13:24:25 +11:00
drm_proc.c drm: Allow for 44 bit user-tokens (or drm_file offsets) 2007-02-08 16:14:05 +11:00
drm_sarea.h
drm_scatter.c
drm_sman.c drm: update core memory manager from git drm tree 2007-02-08 13:24:26 +11:00
drm_sman.h
drm_stub.c DRM: handle pci_enable_device failure 2006-12-11 18:28:52 +11:00
drm_sysfs.c
drm_vm.c drm: Allow for 44 bit user-tokens (or drm_file offsets) 2007-02-08 16:14:05 +11:00
drmP.h drm: update core memory manager from git drm tree 2007-02-08 13:24:26 +11:00
ffb_context.c [PATCH] remove many unneeded #includes of sched.h 2007-02-14 08:09:54 -08:00
ffb_drv.c [PATCH] remove many unneeded #includes of sched.h 2007-02-14 08:09:54 -08:00
ffb_drv.h
i810_dma.c [PATCH] mark struct file_operations const 3 2007-02-12 09:48:45 -08:00
i810_drm.h
i810_drv.c
i810_drv.h i810/i830: use drm_core_ioremap instead of drm_ioremap 2007-02-08 13:24:26 +11:00
i830_dma.c [PATCH] mark struct file_operations const 3 2007-02-12 09:48:45 -08:00
i830_drm.h
i830_drv.c
i830_drv.h i810/i830: use drm_core_ioremap instead of drm_ioremap 2007-02-08 13:24:26 +11:00
i830_irq.c
i915_dma.c
i915_drm.h
i915_drv.c
i915_drv.h
i915_ioc32.c
i915_irq.c i915: Fix a DRM_ERROR that should be DRM_DEBUG. 2007-01-08 20:38:34 +11:00
i915_mem.c
Kconfig
Makefile
mga_dma.c
mga_drm.h
mga_drv.c
mga_drv.h
mga_ioc32.c
mga_irq.c
mga_state.c
mga_ucode.h
mga_warp.c
r128_cce.c
r128_drm.h drm: r128: comment aligment with drm git 2006-12-19 17:56:14 +11:00
r128_drv.c
r128_drv.h drm: r128: comment aligment with drm git 2006-12-19 17:56:14 +11:00
r128_ioc32.c
r128_irq.c
r128_state.c drm: r128: comment aligment with drm git 2006-12-19 17:56:14 +11:00
r300_cmdbuf.c drm: Unify radeon offset checking. 2006-12-15 18:54:35 +11:00
r300_reg.h
radeon_cp.c
radeon_drm.h
radeon_drv.c
radeon_drv.h drm: Unify radeon offset checking. 2006-12-15 18:54:35 +11:00
radeon_ioc32.c
radeon_irq.c drm: fixup comment header style 2006-12-19 17:49:08 +11:00
radeon_mem.c drm: fixup comment header style 2006-12-19 17:49:08 +11:00
radeon_state.c drm: Unify radeon offset checking. 2006-12-15 18:54:35 +11:00
README.drm
savage_bci.c drm: savage: compat fix from drm git. 2006-12-19 17:20:02 +11:00
savage_drm.h
savage_drv.c
savage_drv.h
savage_state.c
sis_drm.h
sis_drv.c
sis_drv.h
sis_mm.c
tdfx_drv.c
tdfx_drv.h
via_3d_reg.h
via_dma.c drm/via: Disable AGP DMA for chips with the new 3D engine. 2007-02-08 13:24:26 +11:00
via_dmablit.c [PATCH] Char: timers cleanup 2007-02-12 09:48:30 -08:00
via_dmablit.h
via_drm.h
via_drv.c
via_drv.h via: allow for npot texture pitch alignment 2007-02-08 13:24:25 +11:00
via_irq.c via: add some new chipsets 2007-02-08 13:24:25 +11:00
via_map.c via: add some new chipsets 2007-02-08 13:24:25 +11:00
via_mm.c
via_mm.h
via_verifier.c via: allow for npot texture pitch alignment 2007-02-08 13:24:25 +11:00
via_verifier.h via: allow for npot texture pitch alignment 2007-02-08 13:24:25 +11:00
via_video.c

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.sourceforge.net/                          *
************************************************************

The Direct Rendering Manager (drm) is a device-independent kernel-level
device driver that provides support for the XFree86 Direct Rendering
Infrastructure (DRI).

The DRM supports the Direct Rendering Infrastructure (DRI) in four major
ways:

    1. The DRM provides synchronized access to the graphics hardware via
       the use of an optimized two-tiered lock.

    2. The DRM enforces the DRI security policy for access to the graphics
       hardware by only allowing authenticated X11 clients access to
       restricted regions of memory.

    3. The DRM provides a generic DMA engine, complete with multiple
       queues and the ability to detect the need for an OpenGL context
       switch.

    4. The DRM is extensible via the use of small device-specific modules
       that rely extensively on the API exported by the DRM module.


Documentation on the DRI is available from:
    http://precisioninsight.com/piinsights.html

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://precisioninsight.com/dr/drm.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://precisioninsight.com/dr/locking.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://precisioninsight.com/dr/security.html

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.sourceforge.net/                          *
************************************************************