o Check for RANDR_GET_CRTC_INTERFACE before defining functions that
  are used only if it is defined.
o Declare a variable before code, and rename it from ret to xvmc_status
  to better describe it.
o if 0 some static functions not used.
o Don't declare some unused variables.
o Declare as static some functions that are used only in the file defining it.
o Add a default/fallback return True to the Bool function
  src/xvmc/intel_batchbuffer.c:intelInitBatchBuffer().
o Ansify src/xvmc/xf86dri.c.
o Add missing prototype to src/xvmc/xf86dri.h and follow pattern of other
  headers by adding "extern" before function prototype.

The new chips no longer automatically flush the rendering cache, so if we
don't flush the RC at blockhandler, the last rendering done may not
appear on the screen.  This was particularly noticable with a bare Xorg with
some missing root weave, and terminals where the last character wouldn't
appear until the cursor blinked.  A flush in the DRI blockhandler path had
hidden this issue for most people.

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 a1612b77.

Conflicts:

	src/i830_driver.c
	src/i830_memory.c

Besides our driver having fallen through to the GM965 path for
RENCLK_GATE_D1, the BIOS was turning some of these on.  It may be relevant
for previous platforms as well to zero out the fields that should be zero
in the other registers.

Instead of failing the build, don't even try unless --enable-xvmc was used.

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

Reported by Joerg. This does a little more clearn up.

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.