summaryrefslogtreecommitdiff
path: root/linux-core/drm_hashtab.c
AgeCommit message (Collapse)Author
2009-11-17Drop shared-core, bsd-core, linux-core and scripts subdirsKristian Høgsberg
2007-11-22drm: major whitespace/coding style realignment with kernelDave Airlie
2007-11-05drm: remove lots of spurious whitespace.Dave Airlie
Kernel "cleanfile" script run.
2007-07-16drm: remove hashtab/sman and object typedefsDave Airlie
2006-10-17Lindent.Thomas Hellstrom
2006-10-17Add memory usage accounting to avoid DOS problems.Thomas Hellstrom
2006-08-23Merge branch 'master' of git+ssh://git.freedesktop.org/git/mesa/drm into ↵Thomas Hellstrom
drm-ttm-0-2-branch
2006-08-23Fix hashtab implementation leaking illegal error codes to user space.Thomas Hellstrom
(Reported by Dave Airlie)
2006-08-21Avoid using vmalloc for small hash tables.Thomas Hellstrom
2006-08-07drm: fixup whitespace and style for Linux kernel importDave Airlie
2006-07-11Keep hashed user tokens, with the following changes:Thomas Hellstrom
32-bit physical device addresses are mapped directly to user-tokens. No duplicate maps are allowed, and the addresses are assumed to be outside of the range 0x10000000 through 0x30000000. The user-token is identical to the 32-bit physical start-address of the map. 64-bit physical device addressed are mapped to user-tokens in the range 0x10000000 to 0x30000000 with page-size increments. The user_token should not be interpreted as an address. Other map types, like upcoming TTM maps are mapped to user-tokens in the range 0x10000000 to 0x30000000 with page-size increments. The user_token should not be interpreted as an address. This keeps compatibility with buggy drivers, while still implementing a hashed map lookup. The SiS and via device driver major bumps are reverted.
2006-06-06Merge in the drm-sman-branchThomas Hellstrom