Age | Commit message (Collapse) | Author |
|
1,402 lines of code to be removed from Mesa (drivers and libGL). The
big winner is dri_util.c.
Primary changes are:
1. Remove all "deprecated" entry-points from the various structures in
dri_interface.h.
2. Rename the remaining fields to removed "version numbers." So,
bindContext3 becomes bindContext. Functions with "New" in the name
(e.g., CreateNewContext) were *not* changed, but that is an option.
Having "New" in the name is less annoying to me than having "3" in the name.
3. Remove all compatibility code that handles cases where the driver or
the loader is too old to support the latest interfaces.
4. Append the API version to the __driCreateNewScreen function name.
This is currently done by hand. In the future (i.e., the next time we
make an incompatible change to the interface) we'll want to come up with
a better way to do this. This prevents old loaders from being able to load
new (incompatible) drivers.
5. Bump the API version to 20050722. All drivers (by way of dri_util.c)
require this version.
6. All drivers are *required* to expose GLX_SGIX_fbconfig and
GLX_OML_swap_method (or the moral equivalents). Support for these
functions in implicit in the use of the "new" interface.
7. Some cases still exist that need to be compiled differently in a loader
or core Mesa versus in a driver. These are identified by the define
IN_DRI_DRIVER.
|
|
individual drivers and put them in common code. It is still possible for a driver to define its own macros if it has special needs. This affects CLIPPIXEL, CLIPSPAN, HW_CLIPLOOP, HW_ENDCLIPLOOP, and for drivers using the spantmp2 template also GET_SRC_PTR and GET_DST_PTR.
|
|
device-specific code. A new Python script
(src/mesa/glapi/extension_helper.py) generates a list of all
entry-points for all known extensions. Each driver the selects only
the extensions that it needs and enables the via either
driInitExtensions or driInitSingleExtension.
This code has been compile-tested on a drivers, but has only been
run-tested on mga and i915 (on i830 hardware).
These changes were discussed at length on the mesa3d-dev mailing list.
http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Calculated fbBPP
|
|
Main driver impacts:
- new code for creating the Mesa GLframebuffer
- new span/pixel read/write code
Some drivers not yet updated/tested.
|
|
|
|
|
|
with Mesa CVS. This change was wrong in the first place, and the issue that
necessitated it has been resolved. For more background on the problem see:
http://marc.theaimsgroup.com/?l=mesa3d-dev&m=111333880529935&w=2
|
|
translation by Manfred Stienstra.
|
|
|
|
easier for non-programmers familiar with GNU gettext. For now there is
only a German translation but more translations are encouraged.
Translatable strings are extracted from t_options.h containing option
definitions with English descriptions. A corresponding header options.h
with all available translations of option descriptions is generated by
gen_xmlpool.py and included by xmlpool.h.
Many option descriptions were rephrased to make them unambiguous for
translation without context. They are hopefully more helpful to users at
the same time.
|
|
driFillInModes().
|
|
|
|
From: Stephane Marchesin
|
|
make ycbcr depend on a CHIPSET define .. needs to be filled in though
|
|
|
|
|
|
|
|
|
|
Found by Andreas Stenglein.
|
|
will be used. Implemented this option in the Savage driver. On my
ProSavageDDR uploads to AGP memory are about 1.5 times as fast as
uploads to card memory. On non-IGP hardware the difference may be even
bigger. Now mplayer -gl is getting really usable.
|
|
order to make room for new textures. In particular this fixes texture
trashing on the first heap when the second heap is occupied by
currently unused textures (observed with Torcs and the Savage driver).
Heaps are weighted by their sizes by default but drivers can override
these and apply their own weights based on relative texture upload
speeds to the respective heaps.
|
|
|
|
|
|
instead of just one major version
|
|
functions.
|
|
__driGarbageCollectDrawables which would get confused while walking
the hash values.
|
|
|
|
|
|
fast z clear and z buffer compression are supported for now, hierarchical-z is not. Still problems with multiple apps and z/stencil readback, which is why hyperz is disabled per default. Also add the new point sprite packet drm 1.13 accepts to the sanity code.
|
|
|
|
|
|
|
|
|
|
|
|
export it via glXGetProcAddress. These are not supported anymore, so print
an error message to that effect.
|
|
|
|
|
|
matches what they optimized versions actually expect.
|
|
|
|
(and DrawPixels). The R200, R128, and Unichrome drivers get support
in this commit. Other drivers would be easy enough to add for people
that have the cards.
The DRI (CVS) build will need to be updated to account for the new
source files.
|
|
the honours.
|
|
drivers built on PowerPC systems should now show things like "PowerPC" or
"PowerPC/Altivec" in the GL_RENDERER string.
The VMX moniker is used for Altivec/Velocity Engine/VMX SIMD additions. I
chose this not because I work for IBM but because it's a LOT shorter to
type. :)
|
|
add support for features of non-x86 CPU types.
|