android_kernel_xiaomi_sm8350

History

Linus Torvalds fc8744adc8 Stop playing silly games with the VM_ACCOUNT flag The mmap_region() code would temporarily set the VM_ACCOUNT flag for anonymous shared mappings just to inform shmem_zero_setup() that it should enable accounting for the resulting shm object. It would then clear the flag after calling ->mmap (for the /dev/zero case) or doing shmem_zero_setup() (for the MAP_ANON case). This just resulted in vma merge issues, but also made for just unnecessary confusion. Use the already-existing VM_NORESERVE flag for this instead, and let shmem_{zero\|file}_setup() just figure it out from that. This also happens to make it obvious that the new DRI2 GEM layer uses a non-reserving backing store for its object allocation - which is quite possibly not intentional. But since I didn't want to change semantics in this patch, I left it alone, and just updated the caller to use the new flag semantics. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2009-01-31 15:08:56 -08:00
..
i810
i830
i915	drivers/gpu/drm/i915/intel_lvds.c: fix locking snafu	2009-01-29 18:04:45 -08:00
mga
r128
radeon
savage
sis
tdfx
via
ati_pcigart.c
drm_agpsupport.c	drm: stash AGP include under the do-we-have-AGP ifdef	2009-01-22 22:27:11 +10:00
drm_auth.c
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc_helper.c	drm: handle depth & bpp changes correctly	2009-01-16 18:40:57 +10:00
drm_crtc.c	drm: create mode_config idr lock	2009-01-22 17:53:05 +10:00
drm_dma.c
drm_drawable.c
drm_drv.c	drm: fix leak of device mappings since multi-master changes.	2009-01-19 17:17:58 +10:00
drm_edid.c	drm: don't whine about not reading EDID data	2009-01-22 22:23:53 +10:00
drm_fops.c	Check fops_get() return value	2009-01-06 15:59:11 -08:00
drm_gem.c	Stop playing silly games with the VM_ACCOUNT flag	2009-01-31 15:08:56 -08:00
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c	drm: Rip out the racy, unused vblank signal code.	2009-01-28 07:50:14 -08:00
drm_lock.c
drm_memory.c
drm_mm.c
drm_modes.c
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c	drm: fix leak of device mappings since multi-master changes.	2009-01-19 17:17:58 +10:00
drm_sysfs.c
drm_vm.c
Kconfig
Makefile
README.drm

README.drm

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

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://dri.freedesktop.org/wiki/Documentation
    http://sourceforge.net/project/showfiles.php?group_id=387
    http://dri.sourceforge.net/doc/

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://dri.sourceforge.net/doc/drm_low_level.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/hardware_locking_low_level.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/security_low_level.html