| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | definitions. | 
|  | definitions | 
|  | + modeprint changes.
- All things are now called _id when they are id's.
- modeprint now accepts driver name as first argument. | 
|  | - Otherwise userspace has no idea of the meaning. | 
|  | not needed, hotplug will work just as well hopefully. | 
|  |  | 
|  | - 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. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | 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(). | 
|  | 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. | 
|  |  | 
|  |  | 
|  | 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. | 
|  |  | 
|  |  | 
|  | 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 | 
|  |  | 
|  | Move dpms into the helper functions.
Move crtc into the encoder.
Move disable unused functions into the helper. | 
|  |  | 
|  | 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 | 
|  | Time to do some renaming on the connectors I think | 
|  |  | 
|  | Use subclassing from the drivers to allocate the objects. This saves
two objects being allocated for each crtc/output and generally makes
exit paths cleaner. | 
|  | This splits a lot of the core modesetting code out into a file of
helper functions, that are only called from themselves and/or the driver.
The driver gets called into more often or can call these functions from itself
if it is a helper using driver.
I've broken framebuffer resize doing this but I didn't like the API for that
in any case. | 
|  | modesetting-101
Conflicts:
	shared-core/i915_dma.c
	shared-core/i915_drv.h | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | The i915 driver now works again. | 
|  | Add code to get panel modes from the VBIOS if present and check whether certain
outputs exist.  Should make our display detection code a little more robust. | 
|  |  | 
|  |  | 
|  | To avoid bo memory manager being inited twice, it will be called
at firstopen when modeset is not enabled. | 
|  | The new display controller has the vblank interrupts in a different place.
Add support for vbl interrupts for these chips | 
|  |  | 
|  | RS400 (intel based IGP) and RS480 (AMD based IGP) have
different MC and GART setups.  Currently we only support
RS480. | 
|  | into modesetting-101 | 
|  | It would be nice if one day the DRM driver was the canonical source for
register definitions and core macros.  To that end, this patch cleans
things up quite a bit, removing redundant definitions (some with
different names referring to the same register) and generally tidying up
the header file. | 
|  |  | 
|  | In order to avoid recursive ->detect->interrupt->detect->interrupt->...
we need to disable TV hotplug interrupts in
intel_tv.c:intel_tv_detect_type.  We also need to enable the TV interrupt
detection and hotplug sequence properly in i915_irq.c. | 
|  | drm_crtc->fb may point to NULL, f.e X server will allocate a new fb
and assign it to the CRTC at startup, when X server exits, it will destroy
the allocated fb, making drm_crtc->fb points to NULL. | 
|  | moving modeset init code into one function and correct error
handling druing i915 init | 
|  | We need to alloc a hw status page bo for G33 if modeset is enabled since the 2D
driver can't alloc gfx memory when working in drm modeset. | 
|  |  |