| Age | Commit message (Collapse) | Author |
|---|
|
unbound."
While I still like the idea, the mprotect calls themselves are failing on
Linux and causing more trouble than they're worth.
This reverts commit a1612b7728d4153499fe86b6713a13c8702cc7d9.
Conflicts:
src/i830_driver.c
src/i830_memory.c
(cherry picked from commit c02ab432dd7058c700c35eecf6215daf5f262c51)
|
|
When overlay switch crtc, it ignores current crtc dpms mode which
might lead to hang.
|
|
The homogeneous coordinate computation in the core server cannot be used for
many legal matrices as it overflows. Just use floats in the driver; faster
and avoids troubles.
When compositing with bilinear filter, don't push the dst coordinates around
as that makes the output blurry when pixels are aligned.
|
|
Add i915 headers in Makefile.am
|
|
|
|
Projective transforms require un-normalized texture coordinates and the use
of the texldp instruction. The coordinates are passed as x/y/z/w (the z is
unused, but there isn't a vertext format for just x/y/w).
|
|
These are needed to deal with projective transforms in the composite
operation.
|
|
These aren't used at this point, but what the heck.
|
|
|
|
Thanks to Bruno <bonbons67@internet.lu>.
|
|
|
|
Default XvMC to disabled.
|
|
Move some declarations and don't declare an extra variable with the
same name, to fix warnings about mixed declarations and code.
|
|
|
|
Using the new interface allows the server to avoid some flicker at startup.
|
|
|
|
It never worked and was never that hot of an idea. Most of the motivation is
gone with glyph pixmaps anyway.
|
|
Tired of them filling up my logs.
|
|
When we have unset channels (color for a8, or alpha for x8*), force them
to the appropriate value in the texture combiner rather than relying on getting
the desired results from teture mapping. Performance is the same on 865, so
multiple paths aren't necessary and we can use the less friendly texture
formats everywhere.
|
|
|
|
|
|
|
|
This fixed the crash appearing for Xv buffer memory, which appears
allocation and free happening in stolen memory. We should always
try to bind for stolen memory for correct protect setup, otherwise
we might get fault that stolen memory protect reverted to non-r/w
after previous free and unbind.
Credit goes to Lukas Hejtmanek to identify the real problem of Xv
crash!
|
|
This lets us get better sanity asserts, and avoid mysterious braces when you
do two BEGIN_LP_RING()s in a single function. Potential minor performance
loss isn't too exciting, as ring access is about to become a compat path
anyway. This change also removes the requirement for ring emits to be aligned
to dwords.
|
|
I want to hack on i830 for changing it into a compat path for batchbuffer
without having to worry about the i810 stuff getting broken.
|
|
Tested by Dan Williams.
|
|
Fixes the build for me (just following the git development guide on a
new machine).
|
|
Needed for new uint* usage.
|
|
Fixes #15036.
|
|
Unbind and bind a DRM BO may change the buffer offset, thus
crtc may reference a wrong rotated memory after a VT switch cycle.
Destroying it here will cause its reallocation when entering VT.
|
|
|
|
|
|
|
|
Several uses are actually left, which are determined by the X Server
interfaces we're implementing.
|
|
|
|
|
|
Fixes #14944.
|
|
Fix printf formatting warnings, wrap a couple of long lines, nuke
unused variables, add missing #include <unistd.h>.
|
|
Whoa, gcc got a lot smarter about warnings. If iXXX_get_dest_format()
doesn't support the picture format passed in it won't initialize the
uint32_t pointed to by dst_format and return FALSE.
What gcc now can detect is if dst_format is used without checking the
return value, it might be used uninitialized. This patch makes sure
we always check the return value before using dst_format.
|
|
Conflicts:
man/intel.man
src/i830_driver.c
|
|
Fixes #14888.
|
|
|
|
This will likely fix SDVO outputs on G35 hardware.
|
|
Based on Maxim Levitsky's patch for the same. Many thanks to Maxim for
discovering that this features still works in recent hardware!
|
|
This should keep the backlight value reported by xrandr --prop & xbacklight
consistent with changes by other software in the system (like the hotkey driver
or kernel backlight driver).
|
|
And directRenderingDisabled already has config check result.
|
|
|
|
|
|
When we reserve memory (memory that won't be managed by the kernel) make
sure to reserve space for the FBC LL cache as well.
|
|
|
