Re: [Mesa3d-dev] Additional vertex program instructions

2005-11-07 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: This patch adds the missing NV_vertex_program2 and NV_vertex_program3 instructions to the various internal tables. It does not add support for them to the parser nor does it add support for them

Re: [Mesa3d-dev] Additional vertex program instructions

2005-11-07 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: Oh, and while we're talking about archiving code, all the TCC stuff for fragment programs can definitely be put in that category. You're saying to gut support for s_fragprog_to_c and s_tcc? I think I can handle that.

Re: [Mesa3d-dev] Additional vertex program instructions

2005-11-07 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: It will probably a bit before I can add support to the parser. I'm still trying to understand how src/mesa/shader/grammar works (and why that was used instead of flex byacc). The ARB program parser

[Mesa3d-dev] Re: [Unichrome-devel] MAX_TEXTURE_SIZE and texture download performance

2005-11-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Flynn wrote: I'm CC'ing mesa3d-dev because that's where most of the 3D specific work is discussed. I have couple quick questions about Unichrome Pro. A couple months ago, I was trying out a Unichrome Pro based machine. I'm not sure if things

Re: [Mesa3d-dev] Re: [Unichrome-devel] MAX_TEXTURE_SIZE and texture download performance

2005-11-15 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: machine. Was the test on the same machine? Do unichrome systems with agp slots exist? Heck yes! The K8M8x0 and PM8x0 chips, for Athlon64 and Pentium4 respectively, support AGP slots. I think the original CLE266 is the

[Mesa3d-dev] fragment program saturate (was Re: [Mesa3d-cvs] CVS Update: Mesa (branch: trunk))

2005-11-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: CVSROOT: /cvs/mesa Module name: Mesa Repository: Mesa/src/mesa/shader/ Changes by: [EMAIL PROTECTED] 05/11/19 15:28:55 Log message: Saturate is a 1-bit boolean field I had made this field 2-bits because,

Re: [Mesa3d-dev] mesa-6.4.1 fails to compile on amd64

2005-12-01 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tomas Carnecky wrote: x86_64-pc-linux-gnu-gcc -c -I. -I../../../include -I../../../include/GL/internal -I../../../src/mesa/main -I../../../src/mesa/glapi -I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm` -I/usr/X11R6/include

[Mesa3d-dev] Re: Memory management - an AGP manager

2006-01-09 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Herrenschmidt wrote: - Caching issues. On a lot of chipsets, AGP memory must be mapped non-cacheable. This isn't trivial on all architectures and it's not always feasible to do with userland buffers. That means that either the cache must

[Mesa3d-dev] Re: Indirect rendering and GL_EXT_framebuffer_object

2006-02-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Reveman wrote: diff -u -r1.12 glxextensions.c --- src/glx/x11/glxextensions.c 7 Feb 2006 00:39:56 - 1.12 +++ src/glx/x11/glxextensions.c 22 Feb 2006 18:58:34 - @@ -183,6 +183,7 @@ { GL(EXT_texture_object),

[Mesa3d-dev] x86-64 assembly dispatch stubs

2006-02-27 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After listening to a couple fairly vocal people squawk about the x86-64 dispatch stubs, I spent some time investigating the raised issues. The primary issue is that the TLS versions of the stubs contains an unnecessary function call to get the

Re: [Mesa3d-dev] GLX_MESA_copy_sub_buffer patches and intel driver issue

2006-03-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Reveman wrote: This patch adds direct and indirect rendering support for GLX_MESA_copy_sub_buffer. Intel, r200 and r300 drivers are the only drivers I've implemented support for so far. I've only tried the intel implementation and that seems

Re: [Mesa3d-dev] GLX_MESA_copy_sub_buffer patches and intel driver issue

2006-03-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Reveman wrote: I thought that a call to SwapBuffers would always make the content of the back buffer undefined. So if you want to use CopySubBufferMESA for quickly repainting part of the buffer as the in the spec, you would never use

Re: [Mesa3d-dev] EXT_texture_from_pixmap update

2006-04-10 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Reveman wrote: Patch for mesa with a set of updates for EXT_tfp. Includes necessary FBConfig support, adds attrib_list to BindTexImage and fixes CreateDrawable so that glXCreatePixmap works. Xgl and compiz requires this patch. Can I

[Mesa3d-dev] Re: GL_ARB_texture_env_crossbar on i915

2006-04-21 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lukas, Questions and patches about 3D driver code should be posted to the mesa3d-dev list. All of the 3D driver developers are there, and messages are less likely to get lost in the noise. Lukas Hejtmanek wrote: why this extension is not included

Re: [Mesa3d-dev] gltrace.py useful?

2006-05-18 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Sondergaard wrote: I stumbled upon mesa's gl_API.xml and the python scripts to process it to generate glx indirect rendering c-code. I've used these bits to generate an opengl tracer, that I thought might be useful for other people than

Re: [Mesa3d-dev] Re: gltrace.py useful?

2006-05-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Sondergaard wrote: Ian Romanick wrote: You'll also need to intercept glGetString and filter out extensions that the tracer doesn't know about. Otherwise people could call things like CombinerParameteriNV and wonder why it doesn't show up

Re: [Mesa3d-dev] Where is OpenGL conformance test?

2006-05-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 LIAO, GUANGDENG wrote: After some time search, I did not find any OpenGL conformance test suite. Could u tell me where it is located ? The official OpenGL conformance tests are not publicly available. -BEGIN PGP SIGNATURE- Version: GnuPG

[Mesa3d-dev] [PATCH] Implement GL_APPLE_vertex_array_object

2006-06-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've just posted a patch that implements GL_APPLE_vertex_array_object at: http://users.freedesktop.org/~idr/patches/ The patch, which is quite large anyway, does *NOT* include changes to any generated files. To test this patch you'll need to

Re: [Mesa3d-dev] glPointSize in radeon driver

2006-06-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jerome Glisse wrote: On 6/23/06, Daniel Sperka [EMAIL PROTECTED] wrote: I see. Sorry I missed that. I certainly didn't mean to complain that something was out of spec. Just hoping that this feature worked - ahh had more than a range of min=1 and

Re: [Mesa3d-dev] [PATCH] For review: Antialiased lines for r128

2006-07-05 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn van Oosterhout wrote: not of particularly high quality. The r128 also offers something called supersampling for the antialiasing. Is this likely to be better? Supersampling is where you render to the backbuffer at a higher resolution

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tilman Sauerbeck wrote: Hi, I've been valgrinding around a bit lately, and noticed this: ==9215== 20 (16 direct, 4 indirect) bytes in 1 blocks are definitely lost in loss record 8 of 22 ==9215==at 0x401B4D1: malloc (in

Re: [Mesa3d-dev] DO_DEBUG defines in dri-drivers

2006-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Böck wrote: In various dri-drivers, DO_DEBUG is defined to 1. Shouldn't this be defaulted off and only enabled via -DDO_DEBUG on CFLAGS? (suggested Patch attached) It defaults to 1 because it doesn't actually enable debugging. It enables

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tilman Sauerbeck wrote: Dave Airlie [2006-07-13 20:12]: http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2r2=1.3 The commit comment just says: 3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to version 3.2,

Re: [Mesa3d-dev] Status of intel (i915 driver) pageFlip implementation

2006-07-24 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joan Bertran wrote: Taking into account that intel graphics cards are shared memory, so they don't have the bandwith of other gpu's the glSwapBuffers can take a precious time to finish if pageFlip is not available. keithw did some experiments

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: Normally when an application calls glXGetProcAddress a dummy stub is created. In the current implementation, a dispatch offset is not assigned at this time. The existing code expects that the driver will later ask

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: Ian Romanick wrote: There is one catch, and I'm not sure how to resolve it. When a driver requests a function, it can request a set of identical functions with different names. For example, the driver can request

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I sometimes wonder if all this complexity to handle dynamic addition of entrypoints is worth it. It would all be a heck of a lot simpler if we just updated libGL with the newest entrypoints from time to time and asked people to

Re: [Mesa3d-dev] Dispatch generation for x86-64

2006-08-15 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: Here is my first pass at run-time dispatch generation code for x86-64. It's not particularly well tested yet (or I'd just commit it now). I wrote a test program that called fill_in_entrypoint with a few different parameter

[Mesa3d-dev] Static dispatch functions (was Re: [Mesa3d-cvs] CVS Update: Mesa (branch: trunk))

2006-08-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: Add new attribute called static_dispatch to the function element. This boolean attribute, which defaults to true, determines whether or not a static dispatch function is available in libGL for applications to link

Re: [Mesa3d-dev] Static dispatch functions (was Re: [Mesa3d-cvs] CVS Update: Mesa (branch: trunk))

2006-08-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: Ian Romanick wrote: All extension functions added since the previous Mesa release (6.5) have been marked as 'static_dispatch=false'. I'd also like to mark functions in the following extensions this way

Re: [Mesa3d-dev] Static dispatch functions (was Re: [Mesa3d-cvs] CVS Update: Mesa (branch: trunk))

2006-08-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: Brian Paul wrote: Ian Romanick wrote: I'd also like to mark functions in the following extensions this way for the 6.5.1 release: GL_EXT_framebuffer_object GL_EXT_framebuffer_blit

Re: [Mesa3d-dev] Static dispatch functions (was Re: [Mesa3d-cvs] CVS Update: Mesa (branch: trunk))

2006-08-24 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Hopf wrote: On Aug 22, 06 15:09:30 -0600, Brian Paul wrote: GL_SGIS_texture4D GL_SGIS_detail_texture GL_SGIX_instruments FWIW I used programs that used these extensions. I doubt it is usefull to call them remotely, so this

Re: [Mesa3d-dev] [PATCH] Static dispatch cleanup

2006-08-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roland Scheidegger wrote: Ian Romanick wrote: This patch removes all of the static dispatch functions that I think can be safely removed for the 6.5.1 release. The attached patch only includes the changes to the .xml files. You'll need to 'make

Re: [Mesa3d-dev] Mesa 6.5.1 release candidate 1 ready

2006-08-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michał Król wrote: On 23/08/06, Brian Paul [EMAIL PROTECTED] wrote: Download from http://mesa3d.sourceforge.net/beta/ Just downloading and compiling on a variety of platforms to make sure no files are missing would be good feedback. Link fails

Re: [Mesa3d-dev] [PATCH] Static dispatch cleanup

2006-08-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: This patch removes all of the static dispatch functions that I think can be safely removed for the 6.5.1 release. The attached patch only includes the changes to the .xml files. You'll need to 'make -C src/mesa/glapi' to get

Re: [Mesa3d-dev] [PATCH] Static dispatch cleanup

2006-08-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: After committing this patch, I plan to: - Remove EXT_vertex_weighting altogether. - Clean up some of the glX exports. I've been looking at some of the GLX exports from glxcmds.c. There are a bunch of old SGI

Re: [Mesa3d-dev] URGENT mesa latest cvs crashes with compiz/aiglx

2006-08-31 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Böck wrote: Log message: GL_EXT_paletted_texture functions should alias GL_SGI_color_table functions. The functions for GL_EXT_paletted_texture that do not share GLX protocol with GL_ARB_imaging are supposed to alias the similar

[Mesa3d-dev] Moving Mesa to GIT?

2006-10-05 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is now the right time to move Mesa over to get? Please? :) I'm probably going to start a long-running branch soon, and that's a much less painful experience with GIT than with CVS. I'm sure it would also make life easier for Kristian. -BEGIN

Re: [Mesa3d-dev] mesa build error: _glapi_Dispatch undeclared

2006-10-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jin, Gordon wrote: Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jin, Gordon wrote: I see following error message when building mesa tip. This seems to be regression in recent 1-2 days. Which target are you building

Re: [Mesa3d-dev] glXWaitVideoSyncSGI

2006-10-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ulrich von Zadow wrote: as of Version 6.5.1, glXWaitVideoSyncSGI is no longer exported by Mesa. Is this intentional? Yes. Use glXGetProcAddressARB. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux)

Re: [Mesa3d-dev] DISPATCH ERROR! with latest i965 DRI

2006-10-16 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew J. Barr wrote: Hi, again, I built Mesa CVS to test the i965 DRI updates and I am getting the following errors when a GL program is invoked: [EMAIL PROTECTED]:~$ glxinfo name of display: :0.0 DISPATCH ERROR! _glapi_add_dispatch failed to

Re: [Mesa3d-dev] Question about GetBufferSize

2006-10-16 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I spent some time this weekend trying to further clean-up the buffer resize code. Thanks for digging into this. In order to do 1, each driver must be updated. Basically, before a GLframebuffer is bound for the first time, it

Re: [Mesa3d-dev] Question about GetBufferSize

2006-10-16 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I've added #ifdef/#else/#endif in _mesa_make_current() to show what code should be removed, and to check that the caller does what's expected. I think those ASSERTs may be incorrect. When glXMakeCurrent is called before the

[Mesa3d-dev] Porting to TTM interfaces?

2006-10-30 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there any sort of documentation available to help developers port drivers to the new TTM interfaces? It would be really nice to get the r200 and r300 drivers ported over. Being able to get VBOs in r200 and eliminate the GARTSize cruft in r300

Re: [Mesa3d-dev] vbo heads up

2006-11-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: OK, the first round of work on the VBO branch seems to have gone quite smoothly. It'd be great if a couple of the key r200/r300 people could check the branch out and verify whether I've broken those drivers or not. It'd

Re: [Mesa3d-dev] vbo heads up

2006-11-03 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: OK, the first round of work on the VBO branch seems to have gone quite smoothly. It'd be great if a couple of the key r200/r300

Re: [Mesa3d-dev] how to add an error check

2006-12-20 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James C Georgas wrote: I want to add an error check to glTexImage2D(), but I don't know where to put it. Basically, what I want to do is check that the given width and height dimensions are of the form: 2^k +2(border) : for some positive

Re: [Mesa3d-dev] update on glsl-compiler-1 branch

2007-02-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I'm getting close to merging the glsl-compiler-1 branch into the Mesa trunk. I did a trunk-to-branch merge today. I need to at least make sure the DRI drivers build (they don't right now). Excellent! The docs/shading.html

Re: [Mesa3d-dev] update on glsl-compiler-1 branch

2007-02-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: 1. Both vertex and fragment programs are now interpreted/executed in software with the same code. Previously, there were separate interpreters in nvvertexec.c and s_fragprog.c. The new interpreter

Re: [Mesa3d-dev] ask the status of extension GL_ARB_color_buffer_float

2007-03-15 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wu, Nian wrote: I read the Mesa code, it has define the glClampColorARB function and other constant variables. In main/blend.c's _mesa_init_color function, it initializes ctx-Color.ClampReadColor to GL_FIXED_ONLY_ARB. It seems Mesa have

Re: [Mesa3d-dev] Mesa release plans

2007-04-18 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I'd like to release Mesa 6.5.3 pretty soon (to be considered a development release) then follow up fairly quickly with a Mesa 7.0 release. The jump to 7.0 would indicate the jump to OpenGL 2.x API support. Woohoo! I might

[Mesa3d-dev] GLSL compiler back-end (was Re: Mesa release plans)

2007-04-18 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: I'd like to release Mesa 6.5.3 pretty soon (to be considered a development release) then follow up fairly quickly with a Mesa 7.0 release

[Mesa3d-dev] Array textures coming to Mesa...

2007-05-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 About a year and a half ago, I posted a spec to the OpenGL extension registry for what is now known as array textures. At the time, this was the basis of a paper that I was writing for SIGGRAPH 2006. Unbeknown to me, this functionality was

Re: [Mesa3d-dev] Array textures coming to Mesa...

2007-05-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: My intention is to update the MESAX extension, and create a new extension called MESA_texture_array. This extension will be something of a cross between the existing MESAX extension and EXT_texture_array

Re: [Mesa3d-dev] Tool to process .syn files?

2007-05-18 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zack Rusin wrote: On Thursday 17 May 2007 05:36:45 pm Keith Whitwell wrote: I think the Zack/Roberto LLVM tree has done just this. Unfortunately for this immediate problem, they target a whole new intermediate representation. Zack, what tools

Re: [Mesa3d-dev] DRI interface changes

2007-05-18 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kristian Høgsberg wrote: Hi, I've been working on updating the DRI interface (GL/internal/dri_interface.h) the last few days and I though I'd post a heads up to the lists to get some feedback. The work I've been doing starts out with the

Re: [Mesa3d-dev] DRI interface changes

2007-05-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kristian Høgsberg wrote: I've been working on updating the DRI interface (GL/internal/dri_interface.h) the last few days and I though I'd post a heads up to the lists to get some feedback. The work I've been After reviewing the changes, I offer

Re: [Mesa3d-dev] softpipe color output/blend stages

2007-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Another thought is to move some traditional per-fragment operations into the fragment program itself. Alpha test, for example, may no longer exist in OpenGL 3.0; it would be up to the user to encode the test in their shader.

[Mesa3d-dev] Mesa on Cell plan

2007-08-01 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've finally posted a rough plan for porting Mesa to Cell. I'm going to try an keep this up to date as people work on stuff. At this point, I'm expecting that all the work will happen on the softpipe_0_1_branch or a branch of that branch.

Re: [Mesa3d-dev] libGL exported __glX* symbols (Was: glucose and xgl progress)

2007-09-26 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kristian Høgsberg wrote: Ok, big disclaimer here: I haven't looked into glucose or even glitz much, so what I'm suggesting here may not apply. But my take is that we shouldn't be loading libGL in the X server to begin with. If we want to use

Re: [Mesa3d-dev] Shadow maps via texenv program?

2007-10-17 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roland Scheidegger wrote: Ian Romanick wrote: I just finished adding support for depth textures to r300. I'd like to add support for shadow maps too. r300 implements shadow comparisons via fragment program instructions instead of sampler state

[Mesa3d-dev] Handle fbconfigs and glx visuals separately. (was Re: mesa: Changes to 'master')

2007-10-17 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kristian HXXgsberg wrote: New commits: commit 6c533ea2d1953152f7d95d6c984e0d287edb46c2 Author: Kristian Høgsberg [EMAIL PROTECTED] Date: Tue Oct 16 16:07:47 2007 -0400 Handle fbconfigs and glx visuals separately. The old

Re: [Mesa3d-dev] What happened to VQ texture compression?

2007-10-23 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp Klaus Krause wrote: Some time ago Vector Quantisation (VQ) texture compression was implemented in some chips like the PowerVR series or the ATI MAch64 and R128. Is this still supported by today's hardware? As far as I know, only DXTC is

Re: [Mesa3d-dev] Will Mesa/DRI ever support OpenGL 3? - Patent issue

2007-10-31 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Allen Akin wrote: On Wed, Oct 31, 2007 at 05:30:18PM +0100, Philipp Klaus Krause wrote: | However OpenGL 3 will not work out of the box on a new Linus | installation. It will not work on a PC that came pre-installed with Linux. I'm not working

[Mesa3d-dev] Softpipe processing of quads

2007-10-31 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been digging through the softpipe code in gallium for the past few days. I think I'm starting to get it. I do have one question about the way quads are processed. It looks like the triangle setup code produces a row of quads and passes them

Re: [Mesa3d-dev] [Dri-users] Will Mesa/DRI ever support OpenGL 3? - Patent issue

2007-11-08 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Helge Hafting wrote: Philipp Klaus Krause wrote: However OpenGL 3 will not work out of the box on a new Linus installation. It will not work on a PC that came pre-installed with Linux. Neither Debian nor Dell will openly break US patent law (no

Re: [Mesa3d-dev] Using GNU make conditionals and text functions

2007-11-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Nicholson wrote: Since we're not using something like automake to control the build, I was wondering if Mesa could make more use of GNU make conditionals and functions. There are a lot of different ways that Mesa can be built, and I believe

[Mesa3d-dev] TGSI_OPCODE_TXP missing

2007-11-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to build linux-llvm on PowerPC, but it seems that TGSI_OPCODE_TXP isn't defined anywhere. Did someone forget to push a commit? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux)

Re: [Mesa3d-dev] Status Cell Driver and colaborating

2007-11-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: Before or in parallel with this, it would make a lot of sense to investigate the Cell SPE backend to llvm which has been produced elsewhere and evaluate its suitability for executing the shader programs Zack is building

Re: [Mesa3d-dev] Cell infrastructure in Gallium

2007-12-05 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: I see some commits have gone into the Gallium tree for Cell infrastructure. What are the near-term (i.e., in the next week or so) plans? Since I'm working in this area, I want to avoid duplication

[Mesa3d-dev] [PATCH] port Gallium Cell code to use libspe2

2007-12-11 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This patch ports the existing Gallium Cell code to use libspe2 instead of libspe. libspe is deprecated in SDK 2.1 and is removed from SDK 3.0. If there are no NAKs, I'll commit this code later today. Signed-off-by: Ian Romanick [EMAIL PROTECTED

Re: [Mesa3d-dev] [PATCH] port Gallium Cell code to use libspe2

2007-12-11 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: This patch ports the existing Gallium Cell code to use libspe2 instead of libspe. libspe is deprecated in SDK 2.1 and is removed from SDK 3.0. If there are no NAKs, I'll commit this code later today. I tried to build

Re: [Mesa3d-dev] [PATCH] port Gallium Cell code to use libspe2

2007-12-11 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: Brian Paul wrote: Is the code running for you? Here it's crashing in the SPE's main() when mfc_get() is called. I'm debugging bug haven't found the cause yet. It was working /before/ merging last night's

[Mesa3d-dev] Issues with Gallium on Cell

2008-01-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm finally back from my winter vacation. I'm trying to run Gallium from 12/13-ish and from today on a PS3, but every GL app completely tanks the machine. I have to powercycle it with the switch on the back. Even glxinfo has the touch of death. Of

Re: [Mesa3d-dev] Issues with Gallium on Cell

2008-01-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm finally back from my winter vacation. I'm trying to run Gallium from 12/13-ish and from today on a PS3, but every GL app completely tanks the machine. I

Re: [Mesa3d-dev] Issues with Gallium on Cell

2008-01-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Laurent Desnogues wrote: On Jan 2, 2008 7:59 PM, Ian Romanick [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] xdemos]$ GALLIUM_CELL=y LD_PRELOAD=../../lib/libGL.so.1.5.070100 ./glxinfo name of display: :0.0 SPU: main() speid=0 Bus error [snip

[Mesa3d-dev] Vertex processing in Gallium

2008-01-03 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since it looks like the TG folks are knee-deep in the fragment shading side of things, I'm going to start tackling the vertex processing. I'm looking at the vertex processing code in Gallium, and I honestly can't make heads or tails of it. I grok

[Mesa3d-dev] LLVM madness

2008-01-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So...I can't get current LLVM SVM bits to build. I get many errors in FileParser.cpp. So...I can't get Mesa to build with LLVM 2.1 (which I am able to build). ~ I've attached the error output. Any help? -BEGIN PGP SIGNATURE- Version:

Re: [Mesa3d-dev] LLVM madness

2008-01-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: | So...I can't get current LLVM SVM bits to build. I get many errors in | FileParser.cpp. It turns out that the problem here is that make clean didn't actually clean everything. Sigh... | So...I can't get Mesa to build

Re: [Mesa3d-dev] LLVM madness

2008-01-22 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Romanick wrote: | Ian Romanick wrote: | | So...I can't get current LLVM SVM bits to build. I get many errors in | | FileParser.cpp. | | It turns out that the problem here is that make clean didn't actually | clean everything. Sigh... Sigh x2

[Mesa3d-dev] Bug in draw_update_vertex_fetch?

2008-01-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Something tells me the following code in draw_update_vertex_fetch is wrong, but it's not 100% what the correct code would be. My best guess is that the last index of vertex_element should be 2, but the rest of the code is fine. ~ case 3: ~ if

[Mesa3d-dev] Shader VM on Cell SPU

2008-01-30 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just finished pushing a ton of commits that get the shader VM running on the Cell's SPUs. Right now it is only used for vertex processing...and gears runs! :) Since various other folks are busy making changes to the fragment processing side of

Re: [Mesa3d-dev] Alternative build system for Gallium -- SCons

2008-02-01 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 José Fonseca wrote: | I tried and tried to produce a proof of concept with CMake, but | couldn't find a satisfactory solution for using it with mesa/gallium. | Getting convenience libraries to work with CMake would be so difficult | and hackish, that

[Mesa3d-dev] 64-bit memory access on Cell SPEs?

2008-02-04 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've noticed some odd bugs when accessing data packets sent via batch buffers from the PPE to SPE. Every now and then one of the pointers sent would be NULL or similar, low value. I tracked this down to unaligned accesses. If 64-bit values aren't

Re: [Mesa3d-dev] 64-bit memory access on Cell SPEs?

2008-02-04 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | But I omitted your changes to configs/linux-cell, Ian: |'ccache' doesn't exist |-DSPU_MAIN_PARAM_LONG_LONG doesn't work for SDK 2.1 |/opt/powerpc/usr/include doesn't exist Oops. I hadn't meant to include my local

Re: [Mesa3d-dev] [PATCH 0/2] Keep generated glapi sources in mesa

2008-02-14 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Nicholson wrote: | The glapi source files for the xserver's GLX module are currently | generated in the mesa tree and then manually merged into the the xserver | tree. This step in the GLX build is error prone as the files can easily | become

[Mesa3d-dev] Gallium builds broken

2008-02-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ever since commit bfd5916eafb9a97ad10f1d4a8738e7dcb02e04f4 the architecture specific makefile builds (at least linux-x86 and linux-cell) are completely broken. Jose, could you please fix this? Since it is becoming obvious that the makefile builds

Re: [Mesa3d-dev] No more C99 syntax goodies in gallium source

2008-02-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Keith Whitwell wrote: | Ian Romanick wrote: | José Fonseca wrote: | | Microsoft compilers don't support C99 syntax. The only native windows | | compilers that support C99 syntax are mingw32-gcc and Intel C/C++ | | compiler, but we can't seriously

Re: [Mesa3d-dev] No more C99 syntax goodies in gallium source

2008-02-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 José Fonseca wrote: | Microsoft compilers don't support C99 syntax. The only native windows | compilers that support C99 syntax are mingw32-gcc and Intel C/C++ | compiler, but we can't seriously support windows platform by targeting | these compilers

Re: [Mesa3d-dev] No more C99 syntax goodies in gallium source

2008-02-20 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 José Fonseca wrote: | On the drivers we care about, e.g., i965simple, I'm afraid it will | have to be so... Drivers that third-parties create, or drivers we | maintain but are clearly Linux only (e.g., cell), there is no point to | enforce anything.

[Mesa3d-dev] Data cache for Cell driver

2008-02-20 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is an obvious need for some sort of data cache on the SPEs in the Cell driver. I've done some research on the subject, and I think I've got a plan. I wanted to bounce it off folks before I move too far on an implementation. My current

Re: [Mesa3d-dev] Data cache for Cell driver

2008-02-21 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | Ian Romanick wrote: | | There is an obvious need for some sort of data cache on the SPEs in the | Cell driver. I've done some research on the subject, and I think I've | got a plan. I wanted to bounce it off folks before I move

Re: [Mesa3d-dev] Data cache for Cell driver

2008-02-21 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | Ian Romanick wrote: | Suggestions? | | demos/texcyl.c is the one texturing test that pretty much works as | expected. Use the right mouse button for the options menu. Unfortunately texcyl, renormal, and possibly others die

Re: [Mesa3d-dev] Data cache for Cell driver

2008-02-25 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | Brian Paul wrote: | On 2/21/08, Ian Romanick [EMAIL PROTECTED] wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Brian Paul wrote: | | Ian Romanick wrote: | | | Suggestions? | | | | demos/texcyl.c is the one

Re: [Mesa3d-dev] Data cache for Cell driver

2008-02-26 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | Ian Romanick wrote: | I managed to track down the problem. cell_start_spus is being called | multiple times. Each time it is called the SPUs expect the buffers to | be stored in a different location. However, when the batch data

Re: [Mesa3d-dev] gallium, linux-cell segfaults

2008-02-27 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | I tried the gallium branch on my ps3. Unfortunately, all opengl programs segfault. I'm not sure, but I remember that SDK 3.0 (on fc8) was not supported - is this still the case? To build with SDK 3.0 you need to add

Re: [Mesa3d-dev] gallium, linux-cell segfaults

2008-02-28 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | [EMAIL PROTECTED] wrote: | Hello Ian, | | Am Donnerstag 28 Februar 2008 01:40:40 schrieb Ian Romanick: | [EMAIL PROTECTED] wrote: | | I tried the gallium branch on my ps3. Unfortunately, all opengl | | programs segfault. I'm

[Mesa3d-dev] Default blend state object?

2008-03-20 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently in Gallium no state object is bound for blend state if blend has not been enabled. Or is it just if none of the blend state is modified? Either way, I have a hack in the current Cell driver that sets some default state on the SPE if

[Mesa3d-dev] XShm with Gallium?

2008-03-24 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to add XSHM support for the xlib winsys driver in Gallium, and I'm having some difficulties. I primarily want to check some of my assumptions, but any pointers would be welcome. DISCLAIMER: I'm not really that familiar with XSHM. I'm

Re: [Mesa3d-dev] Cell texture cache

2008-04-02 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: | I've started added support for multi-texture so I can do some perf | measurements. | | Here's a question. In one_time_init() we call invalidate_tex_cache(). | Since we have no textures yet, the address we're passing to |

  1   2   3   4   5   >