summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2009-02-21Bump version to 2.4.5 for new API additions.Eric Anholt
2009-02-21intel: Add a new bufmgr alloc function to get BOs ready for rendering to.Eric Anholt
This avoids using the oldest BO in the BO cache and waiting for it to be idle before we turn around and render to it with the GPU. Thanks to Chris Wilson for pointing out how silly we were being.
2009-02-20libdrm/nouveau: free drmVersion after we're done with itBen Skeggs
2009-02-20libdrm/nouveau: fix dma debuggingBen Skeggs
2009-02-18nouveau: support backlight only when kernel doesPekka Paalanen
Loading nouveau.ko would fail with unknown symbols, if the backlight class device support is not provided in the kernel. Let's make the backlight support dependant on the kernel configuration. This is a bit ugly, the proper way would be to check for the config in Makefile.kernel whether to build nouveau_backlight.o at all, and if not, nouveau_drv.h should provide the stubs. Signed-off-by: Pekka Paalanen <pq@iki.fi>
2009-02-18nv40, nv50: fix backlight build for <2.6.29 kernelsMatthew Garrett
Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org> Signed-off-by: Pekka Paalanen <pq@iki.fi>
2009-02-18nouveau: Add in-kernel backlight control supportMatthew Garrett
Several nvidia-based systems don't support backlight control via the standard ACPI control mechanisms. Instead, it's necessary for the driver to modify the backlight control registers directly. This patch adds support for determining whether the registers appear to be in use, and if so registers a kernel backlight device to control them. The backlight can then be controlled via existing userspace tools. Signed-off-by: Matthew Garrett <mjg@redhat.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2009-02-16drm_compat: remove kmap_atomic_prot_pfn()Pekka Paalanen
This function is unused, and yet creates build problems: the symbol init_mm is not exported by the latest -rc kernels and I don't believe it ever will be. Even CONFIG_UNUSED_SYMBOLS does not provide it anymore. If this function is needed in the future, it needs to be reinvented in any case. So remove it. Signed-off-by: Pekka Paalanen <pq@iki.fi>
2009-02-16Remove i915 driver sources from linux-corePekka Paalanen
Intel developers have stated, that their DRM development continues elsewhere in some Linux kernel trees. This makes the code in drm.git just dead weight. This removal allows further cleanup of compatibility code. shared-core and bsd-core are left untouched this time. Signed-off-by: Pekka Paalanen <pq@iki.fi> Acked-by: Eric Anholt <eric@anholt.net>
2009-02-15intel: Clear ioctl parameter outvalues and pads that confuse valgrind.Eric Anholt
The minor CPU cost here is probably outweighed by bothering us with noise in the tool.
2009-02-15nv40: fail completely if we don't have a ctxprog for the chipsetBen Skeggs
2009-02-15nv50: context info for chipset 0xa0Ben Skeggs
2009-02-15libdrm: make libdrm_nouveau conditional, disabled by defaultBen Skeggs
libdrm isn't supposed to ship APIs not present in a released kernel.
2009-02-11mode: Make xfdrmMode.[c|h] not depend on drm_mode.hJakob Bornecrantz
2009-02-11nouveau: fix type warnings: void* arith, un/signedPekka Paalanen
nouveau_notifier.c had two places where void* was used in arithmetic, fixed by using char*. nouveau_dma_wait(), nouveau_notifier_wait_status() and nouveau_resource_alloc() had signed/unsigned comparison warnings, fixed by changing the function parameter into an unsigned type. Signed-off-by: Pekka Paalanen <pq@iki.fi>
2009-02-11drm/nv50: fix nv9x chipsetsBen Skeggs
NVIDIA do this fun little sequence after updating the PRAMIN page tables. On 9xxx chips, none of the PRAMIN BAR bindings (except the initial one) worked, hence the majority of the setup needed to create a channel ended up in the wrong place, causing all sorts of fun. This is done by NVIDIA on nv8x chips also, so we'll do it for them too, even though they appear to work without it.
2009-02-11drm/nv50: add context info for nv98Ben Skeggs
It won't work yet, just like the other 9xxx chips. Real soon now :)
2009-02-10drm/nv50: use a slightly different initial context for nv96Ben Skeggs
I'm not 100% sure that the nv94 one we were using won't work. The context layouts are identical (well.. same ctxprog, so of course!), only a couple of registers differ. But, be safe until we actually get some 9xxx chips working.
2009-02-10drm/nv50: correct ramfc pointer in channel headerBen Skeggs
Suprisingly the card still worked without this...
2009-02-10drm/nv50: let the card handle the initial context switchBen Skeggs
Our PFIFO/PGRAPH context save/load functions don't really work well (at all?) on nv5x yet. Depending on what random state the card is in before the drm loads, fbcon probably won't work correctly. Luckily we've setup the GPU in such a way that it'll actually do a hw context switch for the first context. Not sure of how successful this'd be currently on the older chips (actually, pretty sure it won't work), so NV50 only for now.
2009-02-07nouveau: don't try to traverse non-existent listsStuart Bennett
Fixes nouveau_ioctl_mem_free Oops
2009-02-05nouveau: fix some issues where buffer objects never get freedBen Skeggs
2009-02-04modetest: Add syntax to also specify a crtc when setting a mode.Kristian Høgsberg
2009-02-04nouveau: install libdrm_nouveau with libdrmBen Skeggs
2009-02-04nouveau: bring in new mm api definitions, without the actual mm codeBen Skeggs
Use of the new bits is guarded with a mm_enabled=0 hardcode.
2009-02-03modetest: Use cairo (if available) to paint a better pattern.Kristian Høgsberg
2009-02-03modetest: Don't sleep when just dumping state, wait for key for modeset.Kristian Høgsberg
2009-02-03modetest: Handle setting modes on multiple crtcs with one fb.Kristian Høgsberg
2009-02-03modetest: Use a more interesting test pattern.Kristian Høgsberg
2009-02-02Remove the "nv" driver.Stephane Marchesin
2009-02-02No need to pin buffer anymore in modetest.cKristian Høgsberg
2009-01-29nouveau: don't save channel context if it has recently become invalidStuart Bennett
Bug exposed by DDX change d9da090c
2009-01-29nouveau: no suspend support for nv50+Stuart Bennett
2009-01-27Clean up README for the current state of kernel module affairs.Eric Anholt
Bug #19608.
2009-01-27intel: don't count fences on 965 and later, as they don't use them.Eric Anholt
2009-01-27intel: Fix under-counting of fences registers required in check_aperture.Eric Anholt
2009-01-27intel: libdrm support for fence management in execbufJesse Barnes
This patch tries to use the available fence count to figure out whether a given batch can succeed or not (just like the aperture check). Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Eric Anholt <eric@anholt.net>
2009-01-27drm compat: fix euid for >=2.6.28Pekka Paalanen
drm_fops.c reads the current process' EUID directly from task_struct. Apparently starting in 2.6.28-rc4 this fails to build. In Linus' tree, commit b6dff3ec5e116e3af6f537d4caedcad6b9e5082a "CRED: Separate task security context from task_struct" moves the euid field from task_struct to another struct. Earlier commit 9e2b2dc4133f65272a6d3c5dcb2ce63f8a87cae9 "CRED: Introduce credential access wrappers" implements the wrapper macros to access e.g. euid. This is in 2.6.27-rc4, and this contains the definition of current_euid() that will be used in the DRM compatibility header for kernels before 2.6.27. That commit also creates <linux/cred.h>, which contains the upstream definition of current_euid(). drm_fops.c is fixed to use current_euid(), and drm_compat.h will offer the compatibility definition for kernels <2.6.27. Signed-off-by: Pekka Paalanen <pq@iki.fi>
2009-01-27nv50: support chipset NV96Ben Skeggs
ctxprog seen in okias' trace identical to one we use on NV94, assuming the initial context values for NV94 will work here too.
2009-01-27nv04-nv40: correct RAMHT sizeBen Skeggs
2009-01-19drm: remove drmstat/dristat from linux-core buildDave Airlie
pointed out by pq
2009-01-14bump version to 2.4.4Eric Anholt
2009-01-14intel: Retry pin ioctl on -EINTR.Eric Anholt
2009-01-13Don't use DRM_BO_FLAG_NO_MOVE in bufmgr fake. It's a ttm flag.Owain G. Ainsworth
It's also unused, so worthless.
2009-01-12Remove drmModeReplaceFb after it was removed from the kernel.Owain G. Ainsworth
It is impossible to replace the original semantics of this call purely in userland, since the fb_id would change. after discussion with Dr_Jakob Signed-Off-By: Owain Ainsworth <oga@openbsd.org> Acked-By: Jakob Bornecrantz <jakob@vmware.com>
2009-01-12nv50: ack nsource to prevent continuous protection fault irqsBen Skeggs
2009-01-07libdrm: add autoconf check for clock_gettimeJesse Barnes
Should be more portable this way.
2009-01-07libdrm: only check for vblank timeout if we caught EINTRJesse Barnes
Michel caught a case where we might overwrite a success or other return value with EBUSY, so check the return value before checking for the timeout condition.
2009-01-07libdrm: add timeout handling to drmWaitVBlankJesse Barnes
In some cases, vblank interrupts may be disabled or otherwise broken. The kernel has a 3s timeout builtin to handle these cases, but the X server's SIGALM for cursor handling may interrupt vblank wait ioctls, causing libdrm to restart the ioctl, making the kernel's timeout useless. This change tracks time across ioctl restarts and returns EBUSY to the caller if the expected vblank sequence doesn't occur within 1s of the first call. Fixes fdo bz #18041, which is caused by a drmWaitVBlank hanging due to the corresponding pipe getting disabled (thus preventing further events from coming in).
2008-12-29Remove executable from modeprint test dirJesse Barnes
Accidentally committed it with the mode setting changes.