| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Conflicts:
linux-core/Makefile.kernel
linux-core/drm_compat.c
linux-core/drm_fops.c
linux-core/drm_lock.c
shared-core/drm.h
shared-core/i915_dma.c
shared-core/i915_drv.h
shared-core/i915_irq.c
|
|
Make both crtc and the command argument 32 bits to avoid any 32-on-64 compat
issues.
|
|
Enum can be of pretty much any size since C leaves the choice of size up to the implementation. So avoid using it in new interfaces like the vblank pre- & post-modeset ioctl. Thanks to hch for spotting this.
|
|
Chase the lock to it's new location.
|
|
Remove lock functions and use pci_map_rom() instead of pci_map_rom_copy().
|
|
|
|
|
|
|
|
Since it'll be freed at unload time, we should alloc devname rather than
pointing to the DRIVER_NAME string.
|
|
forget to add it in the previous DVO porting patch.
Signed-off-by: Hong Liu <hong.liu@intel.com>
|
|
On my 865G machine, it seems the CPU will receive interrupt before
irq_postinstall is called. This will cause kernel oops because vblank is not
inited at that time. Clear interrupt status before install seems fixing this
problem.
Signed-off-by: Hong Liu <hong.liu@intel.com>
|
|
fix a typo in removing output sysfs.
Signed-off-by: Hong Liu <hong.liu@intel.com>
|
|
This tries to automatically fetch a git revision string and if succeeds,
it #defines GIT_REVISION string macro. Packagers can override it by
'make GIT_REVISION=foo'.
Update Nouveau to use GIT_REVISION, if defined, instead of DRIVER_DATE
in struct drm_driver.
Signed-off-by: Pekka Paalanen <pq@iki.fi>
|
|
From Jesse and Zhenyu originally.
|
|
The vblank tasklet update code must build 2D blt commands with the
appropriate tiled flags.
|
|
The batchbuffer submission paths were fixed to use the 965-specific command,
but the vblank tasklet was not. When the older version is sent, the 965 will
lock up.
|
|
Ported from Xorg intel 2d driver. Changed interfaces definitions, which needed
to be changed later if other device wants to use these DVO stuff.
|
|
Add some branch prediction hints.
|
|
BO lock fixes.
|
|
Move unfenced checking into idle checking.
Never time out while waiting for software events like unmapped or unfenced.
|
|
|
|
|
|
into modesetting-101
|
|
|
|
Use the new TV property creation routine and fixup the set_property code
to actually do a mode set call when properties change.
|
|
It needs to take arguments from the caller about supported TV formats,
so declare it in drm_crtc.h and export it.
|
|
Cleanup some random cruft left over from the initial port.
|
|
Start i at -1 so that the masking works right.
|
|
Some fields had snuck into the drm_output structure. Put them back and
fill in more stuff from the EDID block.
|
|
Doesn't yet work on my i915 test machine, but most of the necessary bits
should be there.
|
|
Now that we can allocate load detect pipes, we can perform TV out load
detection correctly. Call the new routines and enable proper TV
detection.
|
|
TV out needs to do load detection, which means we have to find an
available pipe to use for the detection. Port over the pipe reservation
code for this purpose.
|
|
|
|
the event for these older kernels.
|
|
Put off registering new outputs with sysfs until they're properly configured,
or we may get duplicates if the type hasn't been set yet (as is the case with
SDVO initialization). This also means moving de-registration into the cleanup
function instead of output destroy, since the latter occurs during the normal
course of setup when an output isn't found (and therefore not registered with
sysfs yet.
|
|
into modesetting-101
|
|
If the driver is 'modeset' enabled, it'll register it's interrupt
handler at load time. Set the devname in this case so that
/proc/interrupts makes sense.
|
|
This patch ties outputs, output properties and hotplug events into the
DRM core. Each output has a corresponding directory under the primary
DRM device (usually card0) containing dpms, edid, modes, and connection
status files.
New hotplug change events occur when outputs are added or hotplug events
are detected.
|
|
|
|
|
|
|
|
DragonFly behaves just like FreeBSD in this regard.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
