summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2008-07-03modesetting: lookup blob using correct identifier.Dave Airlie
blob is a blob not a connector
2008-07-03tests: Fix faulty error messages in modeprintJakob Bornecrantz
2008-07-03drm: fix encoders get permissionsDave Airlie
2008-07-02tests: modeprint s/fb/fd/Jakob Bornecrantz
2008-07-02tests: Updated modeprintJakob Bornecrantz
2008-07-02NV50: basic fbcon + misc fixesMaarten Maathuis
- There is one fb, used for as many outputs as possible. - Eventually smaller screens will be scaled to see the full console, but for the moment this'll do.
2008-07-02tests: Improved and renamed the mode app to modeprintJakob Bornecrantz
2008-07-01NV50: switch to fixed point scale factor calculationsMaarten Maathuis
2008-07-01NV50: some i2c cleanupMaarten Maathuis
2008-06-27NV50: use list_head item instead of list_head head to avoid confusionMaarten Maathuis
2008-06-27Change some obviously wrong things about property blobs, still broken though.Maarten Maathuis
- I do not fully understand these blobs, so i'm leaving it at this for the moment.
2008-06-27[modesetting-101] Actually store properties when being changed.Maarten Maathuis
2008-06-27NV50: A minor change.Maarten Maathuis
2008-06-27NV50: Implement DPMS.Maarten Maathuis
2008-06-26[modesetting-101] tab-cleanupMaarten Maathuis
2008-06-26Revert "modesetting-101: Make dpms property optional + misc cleanup."Maarten Maathuis
This reverts commit 13943fe5823c45759091c1a1f487a4abe377421e.
2008-06-26modesetting-101: Make dpms property optional + misc cleanup.Maarten Maathuis
- intel_crt seems the only one to provide it, so init it there.
2008-06-25NV50: i misunderstood NOUVEAU_MEM_INTERNAL, so remove itMaarten Maathuis
2008-06-25NV50: Some cleanup and fixes.Maarten Maathuis
2008-06-25nv50: when destroying a channel make sure it's not still current on PFIFOBen Skeggs
We won't get a PFIFO context switch when the same channel ID is recreated if the hw still thinks the channel is already active, which causes fun issues. Should allow X to be stopped and started without tearing down the entire card state in lastclose().
2008-06-25nouveau: allocate drm-use vram buffers from end of vram.Ben Skeggs
This avoids seeing garbage from engine setup etc before X gets around to pointing the CRTCs at a new scanout buffer. Not actually a noticable problem before G80 as PRAMIN is forced to the end of VRAM by the hardware already.
2008-06-24silence warningroot
2008-06-24NV50: minor changeMaarten Maathuis
2008-06-24NV50: fix a few misc thingsMaarten Maathuis
2008-06-24NV50: fix cursor hide/showMaarten Maathuis
2008-06-24NV50: These are actually errors.Maarten Maathuis
2008-06-24NV50: fix some misc bugsMaarten Maathuis
2008-06-23[modesetting-101] update mode count after fill_modes.Maarten Maathuis
- This avoids returning with a mode count of 0, thus not allocating space for the 2nd ioctl.
2008-06-23libdrm: check for allocation failureMaarten Maathuis
2008-06-23NV50: Improve set_config and fix some minor bugs.Maarten Maathuis
2008-06-22nouveau: disable KMS for pre-NV50 even when specifically enabledMaarten Maathuis
2008-06-22NV50: Fix a few more possible leaks.Maarten Maathuis
2008-06-22fix typoMaarten Maathuis
2008-06-22NV50: A few minor added safeties + cleanup.Maarten Maathuis
2008-06-22Undo something i didn't want to change.Maarten Maathuis
- I made it consistent with recent kernel fb code (maybe this is older bugged code?) - Still i don't use this and i should leave it to others.
2008-06-22NV50: Initial import of kernel modesetting.Maarten Maathuis
2008-06-18i915: switch back to fbcon on panicJesse Barnes
Normally when X is running, panic messages will be invisible and the machine will just appear to hard hang. This patch adds support for switching back to the fbcon framebuffer on panic (through the use of a panic notifier registration) so we can see what happened. Note that in order to be really useful, X will have to run its VT in something other than KD_GRAPHICS mode. Also, not all kernel errors result in panics, some go through BUG() which may trigger another type of event, not resulting in a switch.
2008-06-09Add EDID quirk handlingJesse Barnes
Port over EDID quirks from X.Org so we can handle more monitors. This meant adding size info to the drm_display_mode struct, but other than that the changes were isolated to the DRM EDID handling code (as they should be).
2008-06-06 [intel] remove settable use_mi_batchbuffer_startKeith Packard
The driver can know what hardware requires MI_BATCH_BUFFER vs MI_BATCH_BUFFER_START; there's no reason to let user mode configure this.
2008-06-06drm: fix up fb resize againDave Airlie
2008-06-06intel: don't set the mode on the framebuffer if isn't set to scanout our ↵Dave Airlie
framebuffer
2008-06-06Merge remote branch 'origin/modesetting-101' into modesetting-101-fbDave Airlie
2008-06-06intelfb: add multi fb pathsDave Airlie
2008-06-06intelfb: remove duplicate defineDave Airlie
2008-06-06intelfb: admit fbdev is crap and punt on trying to resize to a larger fbdev.Dave Airlie
2008-06-06intelfb: move mode sets into the intel crtcsDave Airlie
better place to store them.
2008-06-06drm/intel: make hotplug just be an eventDave Airlie
2008-06-06intel: if no spare crtc exists don't just take one.Dave Airlie
2008-06-05sysfs registration/teardown fixupsJesse Barnes
A check in drm_sysfs_connector_remove was supposed to allow it to be called even with unregistered objects, to make cleanup paths a little simpler. However, device_is_regsitered didn't always seem to return what we thought it would, so we'd sometimes end up leaving objects lying around rather than unregistering them. Fix this situation up by requiring devices to be registered before being removed. Any problems resulting from this change should be easier to track down than the alternative (which is leaving kobjects registered after unload).
2008-06-05drm/modeset: add more debugging and fixup some fb enable/disabe bitsDave Airlie
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-26 15:44:53 +0000