| Age | Commit message (Collapse) | Author | 
|---|
|  | Reported by jcristau. | 
|  | Thanks to airlied for catching this. | 
|  | This avoids duplicating the effort in 3 places.  Also, added emit/wait fence
callbacks back in bufmgr_fake since we need it for non-drm 2d.  Sigh. | 
|  | In the process, work around the glaring bugs of the kernel irq wait function. | 
|  | dri_bufmgr.h is replaced by intel_bufmgr.h, and several functions are renamed,
though the structures and many functions remain dri_bufmgr_* and dri_bo_* | 
|  |  | 
|  | This patch allows you to --enable-udev, and will avoid having libdrm
make device nodes. If you are using udev, you should really --enable-udev
your libdrm. | 
|  | This resolves and issue on amd64 FreeBSD and it looks like the
linux ioctl syscall should be unsigned long as well.
Signed-off-by: Robert Noland <rnoland@2hip.net> | 
|  | Conflicts:
	libdrm/xf86drm.c
	linux-core/Makefile.kernel
	linux-core/drmP.h
	linux-core/drm_compat.h
	linux-core/drm_drv.c
	linux-core/drm_stub.c
	linux-core/drm_vm.c
	shared-core/i915_dma.c
	shared-core/r300_cmdbuf.c
	shared-core/radeon_drv.h | 
|  | Conflicts:
	libdrm/Makefile.am
	libdrm/xf86drm.h
	shared-core/i915_dma.c
	shared-core/i915_irq.c | 
|  | Store the global name in global_name, don't overwrite the gem_handle. | 
|  | We'll need something like this (either a handle field or a dri_bo_get_handle
function) for kernel mode setting to get at the handles. | 
|  |  | 
|  |  | 
|  |  | 
|  | While the bufmgr isn't thread-safe at the moment, we need it to be for shared
objects between contexts. | 
|  | another name | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Conflicts:
	linux-core/drmP.h
	linux-core/drm_drv.c
	linux-core/drm_stub.c
	linux-core/i915_drv.c
	linux-core/i915_gem.c
	shared-core/i915_drv.h
	shared-core/i915_irq.c | 
|  | + modeprint changes.
- All things are now called _id when they are id's.
- modeprint now accepts driver name as first argument. | 
|  | not needed, hotplug will work just as well hopefully. | 
|  |  | 
|  |  | 
|  | - I do not fully understand these blobs, so i'm leaving it at this for the moment. | 
|  | I915_GEM_DOMAIN_CPU is very expensive to wait for -- it generally requires
clflushing the frame buffer. | 
|  |  | 
|  | When a software fallback has completed, usermode must notify the kernel so
that any scanout buffers can be synchronized. This ioctl should be called
whenever a fallback completes to flush CPU and chipset caches. | 
|  | Lots of conflicts, seems to load ok, but I'm sure some bugs snuck in.
Conflicts:
	linux-core/drmP.h
	linux-core/drm_lock.c
	linux-core/i915_gem.c
	shared-core/drm.h
	shared-core/i915_dma.c
	shared-core/i915_drv.h
	shared-core/i915_irq.c | 
|  | Receiving a signal should be ignored by the library, so just restart any
ioctl which returns EINTR or EAGAIN. | 
|  | Thanks to Thomas Hellstrom for catching the issue, no thanks to the kernel
developer who authoritatively told me that they would get restarted on their
own. | 
|  | This reduces the diff from Mesa and reduces the illegibility of what I did. | 
|  | This is the create (may want location flags), pread/pwrite/mmap
(performance tuning hints), and set_domain (will 32 bits be enough for
everyone?) ioctls.  Left in the generic set are just flink/open/close.
The 2D driver must be updated for this change, and API but not ABI is broken
for 3D.  The driver version is bumped to mark this. | 
|  | Passed the compile test; it's ready to ship.
Conflicts:
	libdrm/Makefile.am
	linux-core/Makefile.kernel
	linux-core/drmP.h
	linux-core/drm_memrange.c
	linux-core/drm_stub.c
	shared-core/drm.h
	shared-core/i915_dma.c
	shared-core/i915_drv.h
	shared-core/i915_irq.c | 
|  |  | 
|  | Place the buffer reuse links right into the dri_bo_gem object. | 
|  |  | 
|  | The code was discarding the dri_bo_gem structure and saving only the kernel
handle. This lost the mmap address, causing pain when the next buffer user
wanted to map the buffer. | 
|  | This will be used by the X Server for VT switch. | 
|  |  | 
|  | Idea being if you want to add new crtc/output/encoder dynamically later,
you just increase the generation counter and userspace should re-read
all the resources | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Okay we have crtc, encoder and connectors.
No more outputs exposed beyond driver internals
I've broken intel tv connector stuff.
Really for TV we should have one TV connector, with a sub property for the
type of signal been driven over it |