Age | Commit message (Collapse) | Author |
|
This should be close to the last set of tiling fixes for 965 chipsets.
Prior to this commit, the 965 composite hook didn't take tiling into
account, nor did 965 textured video, which caused display corruption.
However, there seems to be at least one last bug to squash--on occasion,
a configuration with tiling enabled won't properly display text. This
is likely another tiling related problem with the composite hook.
|
|
|
|
until we really implement it, OSD can't work for now.
|
|
|
|
|
|
Note that this is a slowdown in text rendering due to the high overhead of our
compositing setup, but appears to be correct according to rendercheck.
|
|
|
|
|
|
|
|
|
|
We don't have extra attributes than Xv port.
|
|
Conflicts:
src/i830_exa.c
|
|
The 915 and earlier appear to respect the fence registers, while only the 965
requires the per-operation tiling setting and pitch shifting. This will also
fix issues with rendering on the 965 involving multiple cliprects, where the
pitch would get divided repeatedly.
This removes the offset < 4096 fallback, which essentially resulted in no
acceleration to tiled buffers, hiding the issues.
|
|
be called many times for the same pixmap, and we don't want
to keep dividing the pitch by 4.
|
|
and put wrap function in driver xvmc priv instead of per xv port priv
|
|
|
|
Reading the docs too literally can cause you to hide bugs with false fixes...
|
|
|
|
PrepareSolid - combine pI830->tiling and frontbuffer checks into new exaPixmapTiled function for readability
|
|
|
|
|
|
|
|
ssh://git.freedesktop.org/git/xorg/driver/xf86-video-intel
|
|
- actually enable tiling in DSP(A|B)CNTR if needed
- add logic to EXA routines for tiled case (still needs work)
- enable/disable fbc on DPMS events (meant moving functions higher in file)
- fix fence register pitch programming (use correct pitch instead of kludged value)
|
|
|
|
- add support for 965GM
- make sure legacy enabled systems don't reduce the range of backlight values we can present to the user
|
|
|
|
A number of other interfaces of ours don't allow buffer offsets to be updated
after screeninit. This attempts to catalog why for each one, so that they
can be fixed one by one.
This happens to restore the EXA offscreen allocator for now, as a fixed-offset
object.
|
|
The return value of GetScreenPixmap before CreateScreenResources is not, in
fact, a pixmap.
|
|
If not available, AIGLX init will fail. While here, simplify DRIINFO tests
since we refuse to init with a version queried less than the version we
compiled against, anyway.
|
|
From issue report http://lists.freedesktop.org/archives/xorg/2007-July/026644.html
|
|
This one trys to use a flag for possible quirks. It adds a quirk
for my Lenovo T61 TV output, and ports some origin LVDS quirks to it.
|
|
To do this, we have to deal with buffer offsets being set at EnterVT time
instead of screen init time. We've wanted to move this direction for a long
time, but there are repercussions. The EXA offscreen memory manager has to
be disabled, because it can't be moved. That will be replaced by BO-backed
pixmaps soon. Also unresolved is whether our moving
front/back/depth/texture buffers will break the classic-mode DRI driver.
This code doesn't actually work yet.
|
|
This is a step towards being able to expose buffer objects through the screen
private to DRI clients, instead of having them have to use the fake buffer
object type.
This fails in two ways. First, the kernel memory manager is not currently
suitable for doing the physical allocations we need, so we still use AGP for
those. Additionally, the DRI lock can't be initialized early enough for us, so
these buffer object allocations fail. This will be fixed by improving the
DRM interface.
|
|
|
|
Fence setting is in mapstate actually. This fixes rotation in
tiled fb case, thanks Keith to report this.
|
|
|
|
which do have new host bridge ids
|
|
|
|
|
|
|
|
dead lock.
|
|
2. clean code
|
|
2. fix an error in map_state
|
|
|
|
2. implement macroblock_ipicture instruction
3. 16bit INTRA block
|
|
|
|
|
|
|
|
|