| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 48ff33a1770f3684cd50184db8f1944a456d9974.
|
|
|
|
|
|
|
|
|
|
mode without config file (Henry Zhao)
|
|
fixes bug 6966
|
|
This reverts caaed927a07ffbac68b08246185ef93c1e7bb98c commit.
See https://bugs.freedesktop.org/show_bug.cgi?id=8137 .
|
|
* [ Bug 6309 ] radeon/r128 fails to read hsync/vsync rates when rang
* descriptor is missing
* [ Bug 5473 ] Blank screen with Radeon Mobility X700 (Acer Ferrari 4005)
* Reboot should not be needed for external CRT to function when connected
later on Ferrari 4000
* Modes need to be sorted, and sorted correctly
* Provide all resolutions (instead only the largest one) in MergedFB clone
mode without config file
* Bump up clock rate for ES1000 to allow higher resolution
|
|
|
|
|
|
- Add ConstantDPI option to force a particlar dpi across mode changes Both
based on Thomas Winischhofer's sis code.
|
|
symbols directly. The xf86* versions aren't supposed to be used
directly.
Drop libc wrapper; don't include xf86_ansic.h and add includes now missing.
|
|
|
|
segfault with MergedFB and EXA enabled and HW cursor temporarily
disabled.
|
|
controlled at compile time, plus the runtime option of Option
"AccelMethod" "EXA" or "XAA". The XAA support appears to remain as
before, while the EXA pieces need just a little more polishing. Notable
features:
- Render acceleration working on Radeon 100 and 200-series with DRI on.
- DRI works with EXA Notable issues:
- DGA disabled in the EXA case.
- Backbuffer moves disabled in the EXA case.
- No textured XVideo.
- MMIO render acceleration is close but still has some issues.
- Memory pressure while using Composite is really troublesome with DRI on.
This patch is based on an initial patch by Zack Rusin, with significant
work by Benjamin Herrenschmidt and myself.
|
|
|
|
|
|
- non-rectangular mergedfb desktops
- screen offsets
|
|
change "foo.h" to <X11/foo.h> for core headers, e.g. X.h, Xpoll.h;
change "foo.h", "extensions/foo.h" and "X11/foo.h" to
<X11/extensions/foo.h> for extension headers, e.g. Xv.h;
change "foo.[ch]" to <X11/Xtrans/foo.[ch]> for Xtrans files.
|
|
Hui Yu)
|
|
programs/Xserver/hw/xfree86/drivers/ati/radeon_mergedfb.c Back out
RadeonWaitForIdleMMIO that I put in earlier.
From discussion on dri-devel we do not need to be as careful with INREG()
access on Radeons as we are on mach64 chips.
The fix is backed out due to:
it breaks DRI on SMP systems (due to absense of the lock in mouse handling
functions)
I am no longer able to reproduce the lockup I saw before
|
|
programs/Xserver/hw/xfree86/drivers/ati/radeon_mergedfb.c
Add a call to RADEONWaitForIdleMMIO() within RADEONChooseCursorCRTC() as
this function uses OUTREGP() which, internally, calls INREG().
Thus (due to SilkenMouse) INREG() could be called while CP engine was busy.
I have observed this lockup on RV350 + R300 3d driver and have no idea
why no issues were reported for R200 cards. Perhaps, few of them have
enough memory to run merged fb and 3d simultaneously ?
This fix is the right thing to do, however, we might also need to put fifo
management calls into other cursor handling functions (in particular
those that write cursor image directly to video memory).
|
|
|
|
|
|
|
|
argument to xf86DrvMsg().
|
|
|
