| Age | Commit message (Collapse) | Author |
|---|
|
leftover from the randr 1.2 conversion.
Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
|
|
|
|
Adapted from various patches from Dave and Jerome.
|
|
This requires an X server from git with createpixmap2 support fixed up in it.
On 1.6 and previous it won't do any tiling, if you are running git server
please upgrade to latest git.
Option "AllowColorTiling" "true" to enable and do some testing
|
|
Abstract vertex buffer, preliminary work before others change
to bring cs support along IB support.
|
|
fixed bicubic filtering after VT switch or suspend/resume
|
|
Upload the bicubic texture once during textured video init
rather than once per frame. Suggested by Michel Daenzer on
IRC.
|
|
Only compile tested.
|
|
compile tested only.
|
|
This works fine here and doubles x11perf -aa10text scores, but may cause
problems on other setups according to Dave. Let's see...
|
|
Avoid flushing CS in the middle of (setting up state for) an operation,
properly finish/restart the operation.
|
|
This uses a new libdrm interface which shares code with mesa.
It also fixes the bo to flush when full instead of never flushing.
It survives gtkperf -a here which the driver didn't before now
|
|
This reverts commit 11cf8a28eb46f48d101888552266921bee8b63fc.
I'll bring this back in a few minutes, I've got a big change introducing
a new cs space accounting scheme which this messes up and I think
probably conflicts with what I've done.
I promise i'll go over this and pick the bits that are still useful :)
|
|
* Flush CS before running out of space.
* Don't flush CS every time when switching between 2D and 3D engine, but make
sure to re-initialize 2D/3D state after flushing.
Doesn't seem quite perfect yet (some rendering seems to get dropped on the floor
sometimes), but this should fix a lot of CS failures people have been seeing.
|
|
This adds DRI2 + KMS + driver pixmaps support to the driver.
I've decided to just do a completely separate KMS driver file
instead of hacking the crap out of radeon_driver.c. So now
I do the KMS check in radeon_probe.c time and set the DDX
pointed up to a completely different set at this stage.
This avoids a lot of if (kms) type crap in the code at
the expense of making sure we make changes to both files
if necessary.
This code is still disabled in configure.ac as I broke EXA composite
rendering somehow in KMS mode
|
|
This patch contains most of the changes to the EXA and texture video
accel code.
It adds a few bits of pixmap support but doesn't actually do anything
useful KMS yet.
Testing this should not have any regressions over what we have already,
biggest worries are r6xx, I've fixed a textured video one, but no idea
what other might lurk
It won't build against libdrm radeon yet either
|
|
This appears to be needed when using fractional feedback
dividers. Based on a patch from Tom Hirst. See fdo
bug 22229 for more details.
|
|
Verified by ernstp on IRC
|
|
This helps with flickering and blanking when
there is contention for MC bandwidth.
|
|
Doesn't seem to work well in all cases. Needs more investigation.
fixes bug 21413
|
|
- hw i2c engine has pin selection on r2xx/r2xx/r3xx chips
- also switch hw i2c pin sel for external tmds
|
|
Allows us to hit dot clocks much closer, especially on
chips with non-27 Mhz reference clocks like most IGP chips.
This should fix most flickering and blanking problems with
non-exact dot clocks.
|
|
textured video
This implements
contrast/brightness/hue/saturation controls for r200/r300 plus gamma (same
gamma value for all channels used though separate values would be trivial)
control for r300.
Some issues left:
- only r200/r300
- still can't be combined with bicubic
- controls will silently cease to work if the format used is packed and not
planar (except for rv250)
- gamma range is from 100 to 10000 corresponding to 0.1 and 10.0 like used in
overlay. However, usable range is far smaller. Over 2.0 picture gets dark
pretty quickly, and below 0.6 or so black seems to turn into purple (I've
verified that even with gamma 1.0 black actually often seems to be RGB 1/0/1 so
this explains this since that gets amplified by low gamma values - not sure if
this is a rounding problem somewhere, bogus reference values or is somehow
expected).
- gamma adds a bit too many instructions for my taste (7) though the
alternative (3 texture lookups + some swizzling instructions) doesn't seem any
better.
|
|
Force lower power mode and switch to a lower mode
when idle.
|
|
Dyanmically switch between power states. Switch to a low
power state when the system is idle (DPMS off).
|
|
|
|
Force the chip to a low power mode at the expense
of performance.
|
|
- replaces DynamicClocks Option as the name was misleading
- unified interface for atom and com based bioses
- fix up clock gating code for newer r3xx asics
|
|
|
|
|
|
- move to vram storage
- move swizzle logic to tex setup
|
|
|
|
As VRAM gets zeroed out over s/r, we need to reload the
shaders.
|
|
If set, enables the use of atombios for modesetting
on r4xx cards.
|
|
Also fix set_bool_const()
the CF bool consts are not contiguous by shader type
There are 96 boolean constants (32 each for PS, VS, GS) and
they are ordered as follows:
ps, vs, gs ... ps, vs, gs
|
|
use a bool const to select the tex fetch routine
|
|
Reduces the vertex buffer setup overhead
|
|
git+ssh://agd5f@git.freedesktop.org/git/xorg/driver/xf86-video-ati
|
|
|
|
Otherwise it and RADEONBiggerCrtcArea show up pretty high in x11perf -aa*text
profiles.
|
|
|
|
|
|
|
|
This reverts commit 0c4694c58f2ec152b19023626bc7ced891d9da65.
This patch just adds latency and thus isn't a real solution
|
|
|
|
Really we need proper fencing with timestamps but this should
help in the short term.
This should help with minor corruption issues and possibly
lockups.
|
|
|
|
|
|
|
|
|
