summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* mesa: Remove GLES overlay.Chia-I Wu2011-01-109-162/+18
| | | | | | | With core mesa doing runtime API checks, GLES overlay is no longer needed. Make --enable-gles-overlay equivalent to --enable-gles[12]. There may still be places where compile-time checks are done. They could be fixed case by case.
* egl: Make egl_dri2 and egl_glx built-in drivers.Chia-I Wu2011-01-1011-103/+111
| | | | | These two drivers are small in size. Making them built-in should simplify packaging.
* egl_glx: Load libGL dynamically.Chia-I Wu2011-01-102-107/+238
| | | | | | This is a step forward for compatibility with really old GLX. But the real reason for making this change now is so that we can make egl_glx a built-in driver without having to link to libGL.
* egl_dri2: Look up _glapi_get_proc_address dynamically.Chia-I Wu2011-01-102-16/+46
| | | | | | | | | In preparation for making egl_dri2 built-in. It also handles symbol lookup error: /usr/local/lib/egl/egl_dri2.so: undefined symbol: _glapi_get_proc_address more gracefully.
* r600: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-092-0/+2
|
* r300: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-092-0/+2
|
* r200: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-092-0/+2
|
* noop: make noop useable like trace or rbugJerome Glisse2011-01-097-52/+92
| | | | | | | | If you want to enable noop set GALLIUM_NOOP=1 as an env variable. You need first to enable noop wrapping for your driver see change to src/gallium/targets/dri-r600/ in this commit as an example. Signed-off-by: Jerome Glisse <[email protected]>
* r300g: do not upload the same user buffer several timesMarek Olšák2011-01-091-1/+3
| | | | Performance++.
* nvc0: implement queriesChristoph Bumiller2011-01-0910-23/+432
|
* dri2: release texture image.Juan Zhao2011-01-093-4/+55
| | | | | | Add release function for texture_from_pixmap extension. Some platform need to release texture image for texture_from_pixmap extension, add this interface for those platforms.
* radeon: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-095-0/+5
|
* dri/nouveau: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-092-0/+3
|
* intel: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-096-0/+7
|
* vbo: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-099-0/+9
|
* st/mesa: Include mfeatures.h in files that perform feature tests.Vinson Lee2011-01-0926-0/+26
|
* mesa: Include mfeatures.h in program.c.Vinson Lee2011-01-091-0/+1
| | | | Include mfeatures.h for feature tests.
* i965g: fix warningsDave Airlie2011-01-092-2/+1
|
* i965g: update intel_decode from upstream.Dave Airlie2011-01-094-137/+432
|
* i965g: update disassembler code from classic.Dave Airlie2011-01-099-36/+97
| | | | still a bit of work to do, the winsys gen setting is a bit of a hack.
* i965g: update brw_defines.h from classic driverDave Airlie2011-01-093-37/+397
|
* i965g: update brw_structs.h from classic driver.Dave Airlie2011-01-093-88/+288
|
* i965g: update to similiar gen stuff as i965Dave Airlie2011-01-0933-151/+173
|
* r300g: fix crash when flushing ZMASKMarek Olšák2011-01-095-92/+81
| | | | | | | | | | https://bugs.freedesktop.org/show_bug.cgi?id=32912 The fix is to call update_derived_state before user buffer uploads. I've also moved some code around. Unfortunately, there are still some ZMASK-related bugs which cause misrendering, i.e. flushing doesn't always work and glean/fbo fails.
* targets/egl: add libnvc0.a to nouveau libsMarcin Slusarz2011-01-091-0/+1
|
* nvfx,nv50: pipe_reference the constant buffersChristoph Bumiller2011-01-082-6/+5
|
* nvc0: fix primitive restart in immediate modeChristoph Bumiller2011-01-082-9/+18
|
* mesa: Clean up header file inclusion in cpuinfo.c.Vinson Lee2011-01-081-1/+1
|
* r300g: fix a surface leak when flushing ZMASKMarek Olšák2011-01-081-0/+1
|
* r300g: rework command submission and resource space checkingMarek Olšák2011-01-0813-260/+505
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The motivation behind this rework is to get some speed by reducing CPU overhead. The performance increase depends on many factors, but it's measurable (I think it's about 10% increase in Torcs). This commit replaces libdrm's radeon_cs_gem with our own implemention. It's optimized specifically for r300g, but r600g could use it as well. Reloc writes and space checking are faster and simpler than their counterparts in libdrm (the time complexity of all the functions is O(1) in nearly all scenarios, thanks to hashing). (libdrm's radeon_bo_gem is still being used in the driver.) It works like this: cs_add_reloc(cs, buf, read_domain, write_domain) adds a new relocation and also adds the size of 'buf' to the used_gart and used_vram winsys variables based on the domains, which are simply or'd for the accounting purposes. The adding is skipped if the reloc is already present in the list, but it accounts any newly-referenced domains. cs_validate is then called, which just checks: used_vram/gart < vram/gart_size * 0.8 The 0.8 number allows for some memory fragmentation. If the validation fails, the pipe driver flushes CS and tries do the validation again, i.e. it validates only that one operation. If it fails again, it drops the operation on the floor and prints some nasty message to stderr. cs_write_reloc(cs, buf) just writes a reloc that has been added using cs_add_reloc. The read_domain and write_domain parameters have been removed, because we already specify them in cs_add_reloc. The space checking has been tested by putting small values in vram/gart_size variables.
* intel: Make renderbuffer tiling choice match texture tiling choice.Eric Anholt2011-01-071-4/+9
| | | | | | There really shouldn't be any difference between the two for us. Fixes a bug where Z16 renderbuffers would be untiled on gen6, likely leading to hangs.
* intel: Use the _BaseFormat from MESA_FORMAT_* in renderbuffer setup.Eric Anholt2011-01-071-36/+1
|
* docs: fix messed up names with special characters in relnotes-7.9.1Marek Olšák2011-01-081-2/+4
| | | | (cherry picked from commit 67aeab0b77fb6be864088e69ea74a010b6543fa1)
* docs: fix messed up names with special characters in relnotes-7.10Marek Olšák2011-01-081-2/+4
| | | | (cherry picked from commit 36009724fdd652ab29aa928ba78891afd650e768)
* i915: Drop old checks for the settexoffset hack.Eric Anholt2011-01-072-17/+6
|
* i915: Don't claim to support AL1616 when neither 830 nor 915 does it.Eric Anholt2011-01-071-1/+2
| | | | Fixes an abort in fbo-generatemipmap-formats.
* intel: Add a vtbl hook for determining if a format is renderable.Eric Anholt2011-01-077-38/+68
| | | | | | | By relying on just intel_span_supports_format, some formats that aren't supported pre-gen4 were not reporting FBO incomplete. And we also complained in stderr when it happened on i915 because draw_region gets called before framebuffer completeness validation.
* intel: expose ARB_framebuffer_object in the i915 driver.Eric Anholt2011-01-071-1/+1
| | | | | | | | | | | ARB_fbo no longer disallows mismatched width/height on attachments (shouldn't be any problem), mixed format color attachments (we only support 1), and L/A/LA/I color attachments (we already reject them on 965 too). It requires Gen'ed names (driver doesn't care), and adds FramebufferTextureLayer (we don't do texture arrays). So it looks like we're already in the position we need to be for this extension. Bug #27468, #32381.
* nvc0: fix reloc domain conflict on buffer migrationChristoph Bumiller2011-01-081-12/+12
| | | | | Occurred because the code assumed that buf->domain would remain equal to old_domain.
* nvc0: upload user buffers only from draw info min to max indexChristoph Bumiller2011-01-082-3/+9
| | | | There are actually applications that profit immensely from this.
* nvc0: fix emission of first 3 u8 indices to RING_NIChristoph Bumiller2011-01-081-1/+1
|
* nvc0: reset mt transfer address after read loop over layersChristoph Bumiller2011-01-081-0/+1
|
* nvc0: tie buffer memory release to the buffer fenceChristoph Bumiller2011-01-081-4/+7
| | | | | ... instead of the next fence to be emitted. This way we have a chance to reclaim the storage earlier.
* r300g: Remove invalid assertion.Łukasz Krotowski2011-01-081-1/+0
| | | | | | | Invalid after be1af4394e060677b7db6bbb8e3301e38a3363da (user buffer creation with width0 == ~0). Signed-off-by: Marek Olšák <[email protected]>
* docs: Import 7.10 release notes from 7.10 branchIan Romanick2011-01-071-5/+2742
|
* i965: Avoid double-negation of immediate values in the VS.Eric Anholt2011-01-071-4/+3
| | | | | | | | | | | | | | In general, we have to negate in immediate values we pass in because the src1 negate field in the register description is in the bits3 slot that the 32-bit value is loaded into, so it's ignored by the hardware. However, the src0 negate field is in bits1, so after we'd negated the immediate value loaded in, it would also get negated through the register description. This broke this VP instruction in the position calculation in civ4: MAD TEMP[1], TEMP[1], CONST[256].zzzz, CONST[256].-y-y-y-y; Bug #30156
* docs: Import 7.9.1 release notes from 7.9 branchIan Romanick2011-01-071-0/+404
|
* r600g: Also set const_offset if the buffer is not a user buffer in ↵Henri Verbeet2011-01-071-0/+2
| | | | r600_upload_const_buffer().
* r600g: Update some comments for Evergreen.Henri Verbeet2011-01-071-1/+3
|
* r600g: Split ALU clauses based on used constant cache lines.Henri Verbeet2011-01-072-21/+129
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 21:36:45 +0000