aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/radeon/radeon_screen.c
Commit message (Collapse)AuthorAgeFilesLines
* radeon: With DRI1, if we have HW stencil, only expose fbconfigs with stencil.Michel Dänzer2009-07-201-2/+2
| | | | | | | | | | | | Otherwise simple apps like glxgears pick up a DirectColor visual since the X server mixes the depth 32 visual in with the other GLX visuals, and this seems to result in a (mostly) black screen due to a bad ColorMap for a lot of people. The bad ColorMap may be a bug in the apps, the X server or X driver, and regardless of that I think the X server should ideally make the depth 32 GLX visual separate from the rest again, but in the meantime this makes us cope. (depth_bits is either 16 or 24, never 0)
* R300: add quadpipe overridesAlex Deucher2009-04-281-4/+13
| | | | | RV410 SE chips only have 1 quadpipe. Also, handle other R300 chip with quadpipe override
* radeon: Expose a 32 bit RGBA fbconfig even when the screen depth is 16.Michel Dänzer2009-04-061-15/+20
| | | | | | | Otherwise current xserver / libGL no longer expose a 32 bit RGBA GLX visual, and compiz fails. Fixes http://bugs.freedesktop.org/show_bug.cgi?id=20479 .
* mesa: remove last of _mesa_unreference_framebuffer() callsBrian Paul2009-03-071-1/+1
|
* r300: shut up valgrindMaciej Cencora2009-03-071-1/+1
| | | | | | It complained about uninitialized values Signed-off-by: Nicolai Haehnle <[email protected]>
* R300: Add support for RS600 chipsAlex Deucher2009-02-251-2/+8
|
* gallium: Fixups for driCreateConfigs MSAA support.Michel Dänzer2009-02-101-1/+3
| | | | Add the MSAA samples array or make sure its contents are initialized.
* re-add MSAA supportBrian Paul2009-02-091-2/+3
| | | | | | | | | (cherry picked from commit f7d80aa00611917bc8ce637136d982b151b8f44f) This also involved adding the new MSAA fields to driCreateConfigs(). Also, re-add prog_instructions->Sampler field for i965 driver. Will have to revisit that.
* r300: Enable GL_ATI_separate_stencil in R300Ian Romanick2009-01-231-0/+5
| | | | | | | At this point, GL_EXT_stencil_two_side should probably be disabled. It may be worth leaving it enabled because it has GLX protocol while GL_ATI_separate_stencil does not. I'll leave it to one of the r300 maintainers to make the call.
* fix span issue with really old ddx and non-tcl r100 chipsRoland Scheidegger2008-10-161-1/+1
|
* Remove CVS keywords.Keith Whitwell2008-09-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cherry-picked from gallium-0.1 Conflicts: src/glu/sgi/libnurbs/interface/bezierEval.h src/glu/sgi/libnurbs/interface/bezierPatch.h src/glu/sgi/libnurbs/interface/bezierPatchMesh.h src/glu/sgi/libnurbs/internals/dataTransform.h src/glu/sgi/libnurbs/internals/displaymode.h src/glu/sgi/libnurbs/internals/sorter.h src/glu/sgi/libnurbs/nurbtess/definitions.h src/glu/sgi/libnurbs/nurbtess/directedLine.h src/glu/sgi/libnurbs/nurbtess/gridWrap.h src/glu/sgi/libnurbs/nurbtess/monoChain.h src/glu/sgi/libnurbs/nurbtess/monoPolyPart.h src/glu/sgi/libnurbs/nurbtess/monoTriangulation.h src/glu/sgi/libnurbs/nurbtess/partitionX.h src/glu/sgi/libnurbs/nurbtess/partitionY.h src/glu/sgi/libnurbs/nurbtess/polyDBG.h src/glu/sgi/libnurbs/nurbtess/polyUtil.h src/glu/sgi/libnurbs/nurbtess/primitiveStream.h src/glu/sgi/libnurbs/nurbtess/quicksort.h src/glu/sgi/libnurbs/nurbtess/rectBlock.h src/glu/sgi/libnurbs/nurbtess/sampleComp.h src/glu/sgi/libnurbs/nurbtess/sampleCompBot.h src/glu/sgi/libnurbs/nurbtess/sampleCompRight.h src/glu/sgi/libnurbs/nurbtess/sampleCompTop.h src/glu/sgi/libnurbs/nurbtess/sampleMonoPoly.h src/glu/sgi/libnurbs/nurbtess/sampledLine.h src/glu/sgi/libnurbs/nurbtess/searchTree.h src/glu/sgi/libnurbs/nurbtess/zlassert.h src/glu/sgi/libutil/error.c src/glu/sgi/libutil/glue.c src/glu/sgi/libutil/gluint.h src/glu/sgi/libutil/project.c src/glu/sgi/libutil/registry.c src/glx/x11/glxclient.h src/glx/x11/glxext.c src/mesa/drivers/dri/ffb/ffb_dd.h src/mesa/drivers/dri/ffb/ffb_points.h src/mesa/drivers/dri/gamma/gamma_context.h src/mesa/drivers/dri/gamma/gamma_macros.h src/mesa/drivers/dri/i810/i810context.h src/mesa/drivers/dri/r128/r128_dd.h src/mesa/drivers/dri/tdfx/tdfx_dd.h
* mesa: standardize on C99's uint*_t instead of u_int*_tKeith Whitwell2008-09-211-3/+3
|
* mesa: added "main/" prefix to includes, remove some -I paths from ↵Brian Paul2008-09-181-6/+5
| | | | Makefile.template
* radeon: SetTexOffset supportChris Rankin2008-07-141-0/+12
| | | | | This patch is a straightforward duplication of the R200 SetTexOffset code, except that there is no big-endian tx_table[] array.
* r300: Cleanup LodBias supportNicolai Haehnle2008-06-301-8/+7
| | | | | | | | | | | | | | . There is both a per-texture unit and a per-texture object (at least for OpenGL 1.4); this should now be supported properly. . The LOD bias calculation in r300_state has been simplified and corrected (need to multiply by 32 instead of 31, and ensure clamping) . do not clamp LOD bias in TexEnv, as that behaviour conflicts with what the spec says . set Const.MaxTextureLodBias properly . remove the no_neg_lod_bias property; if somebody can explain what it's good for, we can add it back in, but according to Google, nobody seems to use it . removed some dead code and unused variables
* R300: 1002:5657 is actually RV410Alex Deucher2008-06-211-1/+1
| | | | See bug 14289
* r300: disable the lowimpact fallbacks by default.Dave Airlie2008-06-011-1/+1
| | | | because really we should be able to just fix the driver.
* r500: remove warnings and only start on newer drms.Dave Airlie2008-05-281-8/+5
| | | | | This removes lots of warnings to the user, and only allows the driver to run on > .29 drms for r500 cards.
* R3/4/5xx: update to use drm get_param for num gb pipesAlex Deucher2008-05-281-7/+30
|
* r300: add R300_NO_TCL to allow testing of non-tcl on tcl cardsDave Airlie2008-05-031-0/+3
|
* R3/4/5: fix TCL on r5xx, cleanup PVS codeAlex Deucher2008-05-021-5/+5
|
* R5xx: various updatesAlex Deucher2008-05-021-1/+8
| | | | | | - fixup VAP_CNTL setup - remove extra instruction in r5xx passthrough shader - add notes about pipe config
* R5xx: Add R5xx pci idsAlex Deucher2008-05-021-1/+119
|
* r300: add rv530 pci id for the t60p laptopDave Airlie2008-05-021-0/+5
|
* Change default of driconf "allow_large_textures" to announce hardware limits.Michel Dänzer2008-04-291-2/+2
| | | | | | The previous default these days served mostly to cause artifical problems with GLX compositing managers like compiz (see e.g. http://bugs.freedesktop.org/show_bug.cgi?id=10501).
* DRI interface changes and DRI2 direct rendering support.Kristian Høgsberg2008-03-311-67/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add DRI2 direct rendering support to libGL and add DRI2 client side protocol code. Extend the GLX 1.3 create drawable functions in glx_pbuffer.c to call into the DRI driver when possible. Introduce __DRIconfig, opaque struct that represents a DRI driver configuration. Get's rid of the open coded __GLcontextModes in the DRI driver interface and the context modes create and destroy functions that the loader was requires to provide. glcore.h is no longer part of the DRI driver interface. The DRI config is GL binding agnostic, that is, not specific to GLX, EGL or other bindings. The core API is now also an extension, and the driver exports a list of extensions as the symbol __driDriverExtensions, which the loader must dlsym() for. The list of extension will always include the DRI core extension, which allows creating and manipulating DRI screens, drawables and contexts. The DRI legacy extension, when available, provides alternative entry points for creating the DRI objects that work with the XF86DRI infrastructure. Change DRI2 client code to not use drm drawables or contexts. We never used drm_drawable_t's and the only use for drm_context_t was as a unique identifier when taking the lock. We now just allocate a unique lock ID out of the DRILock sarea block. Once we get rid of the lock entirely, we can drop this hack. Change the interface between dri_util.c and the drivers, so that the drivers now export the DriverAPI struct as driDriverAPI instead of the InitScreen entry point. This lets us avoid dlsym()'ing for the DRI2 init screen function to see if DRI2 is supported by the driver.
* Radeon 9500 (0x4144) only has one pipeAlex Deucher2008-03-191-0/+4
| | | | confirmed by Reid Linnemann <[email protected]>
* Use __DRIextension mechanism providing loader functionality to the driver.Kristian Høgsberg2008-02-291-4/+6
| | | | | | | Instead of passing in a fixed struct, the loader now passes in a list of __DRIextension structs, to advertise the functionality it can provide to the driver. Each extension is individually versioned and can be extended or phased out as the interface develops.
* Remove GetMSC DriverAPI function.Kristian Høgsberg2008-02-251-2/+0
| | | | | | | | | | | The DriverAPI is internal to the DRI drivers and GetDrawableMSC obsoletes GetMSC. Also, since the DRI driver interface has not yet been released, just drop the getMSC function from the DRI interface instead using the ABI preserving version mechanism. Finally, using void pointer privates in the DRI interface is not allowed, always pass the actual types around (__DRIdrawable in this case) to enhance type safety and readability of the code.
* Add new RV380 pci idAlex Deucher2008-01-291-0/+1
| | | | bug 14289
* r300: add initial rs690 support to MesaDave Airlie2008-01-271-1/+20
| | | | | | The rs690 has an rs4xx style vertex-shader less 3D engine. It uses the new r500 output engine though. It also needs a new drm with rs690 support, which is just getting cleaned up.
* __driConfigOptions must be PUBLIC.Adam Jackson2007-12-241-1/+1
|
* R300: RV410 SE chips have half the pipes of regular RV410Alex Deucher2007-12-241-2/+7
| | | | | This fixes 3D rendering on x700 SE chips. Reported by Kano.
* fix z buffer read/write issue with rv100-like chips and old ddxRoland Scheidegger2007-11-221-1/+5
|
* fix bogus assumption if ddx has set up surface reg for z bufferRoland Scheidegger2007-11-151-2/+1
| | | | | | | | this is wrong since even if ddx has not set up a surface reg to cover the z buffer we should pretend it has on those rv100 chips since they presumably do not do z buffer tiling if not using hyperz, so we can use linear addressing just the same. Doesn't seem to fix #13080, but it's wrong anyway and the bug almost certainly broke newer non-tcl chips.
* r200: Re-expose SetTexOffset functionality.Michel Dänzer2007-11-061-1/+7
| | | | This seems to have been mismerged with the DRI interface changes.
* Refactor and fix core vblank supportJesse Barnes2007-10-291-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Consolidate support for synchronizing to and retrieving vblank counters. Also fix the core vblank code to return monotonic MSC counters, which are required by some GLX extensions. Adding support for multiple pipes to a low level driver is fairly easy, the Intel 965 driver provides simple example code (see intel_buffers.c:intelWindowMoved()). The new code bumps the media stream counter extension version to 2 and adds a new getDrawableMSC callback. This callback takes a drawablePrivate pointer, which is used to calculate the MSC value seen by clients based on the actual vblank counter(s) returned from the kernel. The new drawable private fields are as follows: - vblSeq - used for tracking vblank counts for buffer swapping - vblFlags - flags (e.g. current pipe), updated by low level driver - msc_base - MSC counter from the last time the current pipe changed - vblank_base - kernel DRM vblank counter from the last time the pipe changed Using the above variables, the core vblank code (in vblank.c) can calculate a monotonic MSC value. The low level DRI drivers are responsible for updating the current pipe (by setting VBLANK_FLAG_SECONDARY for example in vblFlags) along with msc_base and vblank_base whenever the pipe associated with a given drawable changes (again, see intelWindowMoved for an example of this). Drivers should fill in the GetDrawableMSC DriverAPIRec field to point to driDrawableGetMSC32 and add code for pipe switching as outlined above to fully support the new scheme.
* Add a version field to __DRIextension.Kristian Høgsberg2007-10-111-2/+2
|
* Move new texOffset extension to the new extension mechanism.Kristian Høgsberg2007-10-111-4/+10
|
* Add a DRI_ReadDrawable marker extension to signal read drawable capability.Kristian Høgsberg2007-10-111-4/+2
|
* Move media stream counter entry points to new extension.Kristian Høgsberg2007-10-111-8/+5
|
* Move GLX_MESA_swap_frame_usage DRI entry points to the new mechanism.Kristian Høgsberg2007-10-111-1/+1
|
* Move GLX_MESA_allocate_memory related functions to new extension mechanism.Kristian Høgsberg2007-10-111-10/+16
|
* Move swap_interval to new extension mechanism.Kristian Høgsberg2007-10-101-8/+6
|
* Move the copySubBuffer extension over to the new mechanism.Kristian Høgsberg2007-10-101-1/+6
|
* Pull createNewScreen entry point into dri_util.c.Kristian Høgsberg2007-10-101-61/+35
| | | | | | | | This pulls the top level createNewScreen entry point out of the drivers and rewrites __driUtilCreateNewScreen in dri_util.c to be the new entry point. The change moves more logic into the common/ layer and changes the createNewScreen entry point to only be defined in one place.
* Replace open-coded major, minor, and patch version fields with __DRIversionRec.Kristian Høgsberg2007-10-101-10/+10
|
* Remove screenConfigs from __DRIscreen.Kristian Høgsberg2007-10-101-8/+7
| | | | | | | | | | | | The screenConfigs field of __DRIscreen points back to the containing __GLXscreenConfigs struct. This is a serious abstraction violation; it assumes that the loader is libGL and that there *is* a __GLXscreenConfigs type in the loader. Using the containerOf macro, we can get from the __DRIscreen pointer to the containing __GLXscreenConfigs struct, at a place in the stack where the above is a valid assumption. Besides, the __DRI* structs shouldn't hold state other than the private pointer.
* Drop __DRInativeDisplay and pass in __DRIscreen pointers instead.Kristian Høgsberg2007-10-101-13/+12
| | | | | | | | | | | | | Many DRI entry points took a __DRInativeDisplay pointer and a screen index as arguments. The only use for the native display pointer was to pass it back to the loader when looking up the __DRIscreen for the given screen index. Instead, let's just pass in the __DRIscreen pointer directly, which let's drop the __DRInativeDisplay type and the getScreen function. The assumption is now that the loader will be able to retrieve context from the __DRIscreen pointer when necessary.
* r200: Implement SetTexOffset hook.Chris Rankin2007-09-291-1/+3
| | | | Implementation guidance by Michel Dänzer, final testing by Timo Aaltonen.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-14 11:23:59 +0000