Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Philip Brown
On Tue, Mar 25, 2003 at 11:21:22PM -0800, Ian Romanick wrote: > Philip Brown wrote: > > On Tue, Mar 25, 2003 at 05:07:38PM -0800, Ian Romanick wrote: > >>The idea is that the X server and the 3D driver can use the same memory > >>manager for off-screen memory. That way pixmap cache, textures, and

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Ian Romanick
Philip Brown wrote: On Tue, Mar 25, 2003 at 05:07:38PM -0800, Ian Romanick wrote: Philip Brown wrote: The core X server should not be making calls into extension modules. Extension modules should be making calls to xfree-exported functions. If there arent sufficient xfree-exported functions, exte

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Andreas Stenglein
Am 2003.03.25 21:02:24 +0100 schrieb(en) Keith Whitwell: Gareth Hughes wrote: Andreas Stenglein wrote: Yes, at least the part with GL_TRIANGLE_STRIP. In case of "0" you can just return 0, no copying is needed. case 0: return 0; break; You're going to do that, just in a slightly different manner:

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Michel Dänzer
On Mit, 2003-03-26 at 02:07, Ian Romanick wrote: > > The idea is that the X server and the 3D driver can use the same memory > manager for off-screen memory. That way pixmap cache, textures, and > vertex buffers all get managed in the "same" way and share ALL of off > screen memory. Currently

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Ian Romanick
Andreas Stenglein wrote: unfortunately it was only a partial fix (but was enough for that particular program) heres a new one: (and maybe it should be handeld this way with GL_QUAD_STRIP, too) --- radeon_vtxfmt.c_origFri Mar 21 17:22:23 2003 +++ radeon_vtxfmt.cTue Mar 25 07:45:52 2003 @@ -3

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Philip Brown
On Tue, Mar 25, 2003 at 05:07:38PM -0800, Ian Romanick wrote: > Philip Brown wrote: > > The core X server should not be making calls into extension modules. > > Extension modules should be making calls to xfree-exported functions. > > If there arent sufficient xfree-exported functions, extend or ad

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Ian Romanick
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 11:27:17PM +, Keith Whitwell wrote: Alan Hourihane wrote: If there's any architectural reason why we can't use XFree86's module loader for OS indepence here ? The whole point of the drmCommand*() interface is that it's portable, so I don't see a

[Dri-devel] DRI failure with Linux 2.4.20, XFree86 4.3, Matrox G400, CVS DRI module

2003-03-25 Thread Chris Rankin
Hi, I am running Linux-2.4.20 SMP, 1 GB memory with the CVS DRI module and XFree86 4.3. My card is a Matrox G400 MAX with 32 MB: $ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Ian Romanick
Alan Cox wrote: On Tue, 2003-03-25 at 21:48, Keith Whitwell wrote: The final point that I would like to make is that we're going to NEED to load the DRI driver on the server-side at some point in order to support accelerated server-side rendering. We could then implemented a server-side softwa

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Ian Romanick
Philip Brown wrote: On Tue, Mar 25, 2003 at 12:37:17PM -0800, Ian Romanick wrote: This could also pave the way for the X server to use the new memory manager that is being developed. We could make some sort of a conduit for the X server to call into the DRI driver to allocate graphics / AGP me

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Michel Dänzer
On Die, 2003-03-25 at 21:37, Ian Romanick wrote: > > In the current GLX visual mechanism, the DDX driver exports an array of > __GLXvisualConfigRec objects that is used by the GLX extension. This is > done because the DDX driver is the only place in the server that knows > what display modes

[Dri-devel] DRI/Mesa Doxygen documentation

2003-03-25 Thread José Fonseca
DRI/Mesa documentation is available at http://jrfonseca.dyndns.org/projects/dri/ (see bottom). Specifically: - Mesa documentation (incomplete) - Embedded Mesa subset documentation - Embedded Radeon driver documentation - Mini GLX documentation As you may know by now, this documentation was

[Dri-devel] How to look 20 again!

2003-03-25 Thread Carol Gabriel
As Seen on NBC, CBS, CNN and even Oprah! The Health Discovery that Actually Reverses Aging while Burning Fat, without Dieting or Exercise! This Proven Discovery has even been reported on by the New England Journal of Medicine. Forget Aging and Dieting Forever! And it's Guaranteed!

[Dri-devel] Time to grow that schlong!

2003-03-25 Thread Jessica Simmons
Title: index_spam Introducing VP-RX Pills NO.1 Penis Enlargement Pill On The Market! * Gain 3+ Full Inches In Length * Expand Your Penis Up To 20% Thicker * Stop Premature Ejaculation! * Produce Stronger Erections * 100% Safe To Take, With No Side Effects * Fast Distribution Worldwide * Sold O

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 11:33:31PM +, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Tue, Mar 25, 2003 at 11:18:45PM +, Keith Whitwell wrote: > > > My impression is that a patch trying to add a dlopen() call to one of > the xfree86 hosted ddx drivers would be rejected. > >>> >

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 11:27:17PM +, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Tue, Mar 25, 2003 at 10:51:05PM +, Keith Whitwell wrote: > > > >>Gareth Hughes wrote: > >> > >>>Keith Whitwell wrote: > >>> > >>> > Yes, very nice. > > Utah did have some stuff going for i

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 11:18:45PM +, Keith Whitwell wrote: My impression is that a patch trying to add a dlopen() call to one of the xfree86 hosted ddx drivers would be rejected. Last I looked at the XF86 loader, it had some stuff in it that implied to me that it cou

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 11:18:45PM +, Keith Whitwell wrote: > > >>My impression is that a patch trying to add a dlopen() call to one of > >>the xfree86 hosted ddx drivers would be rejected. > > > > > >Last I looked at the XF86 loader, it had some stuff in it that implied > >to me that it cou

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Philip Brown
On Wed, Mar 26, 2003 at 12:37:08AM +, Alan Cox wrote: > On Tue, 2003-03-25 at 23:15, Philip Brown wrote: > > There are already AGP (and memory alloc) related calls in the X server > > framework; xf86BindGARTMemory(), xf86EnableAGP(), etc. > > > > The core X server should not be making calls in

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 10:51:05PM +, Keith Whitwell wrote: Gareth Hughes wrote: Keith Whitwell wrote: Yes, very nice. Utah did have some stuff going for it. It was designed as a server-side-only accelerated indirect renderer. My "innovation" was to figure out tha

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Cox
On Tue, 2003-03-25 at 23:15, Philip Brown wrote: > There are already AGP (and memory alloc) related calls in the X server > framework; xf86BindGARTMemory(), xf86EnableAGP(), etc. > > The core X server should not be making calls into extension modules. > Extension modules should be making calls to

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 10:51:05PM +, Keith Whitwell wrote: > Gareth Hughes wrote: > >Keith Whitwell wrote: > > > >> > >>Yes, very nice. > >> > >>Utah did have some stuff going for it. It was designed as a > >>server-side-only accelerated indirect renderer. My "innovation" was > >>to figure

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
My impression is that a patch trying to add a dlopen() call to one of the xfree86 hosted ddx drivers would be rejected. Last I looked at the XF86 loader, it had some stuff in it that implied to me that it couldn't simply be treated as a wrapper for dlopen(), dlsym(), etc. I don't remember the

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Philip Brown wrote: On Tue, Mar 25, 2003 at 09:48:21PM +, Keith Whitwell wrote: Utah did have some stuff going for it. It was designed as a server-side-only accelerated indirect renderer. My "innovation" was to figure out that the client could pretty easily play a few linker tricks &

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Brian Paul
Keith Whitwell wrote: Gareth Hughes wrote: Keith Whitwell wrote: Yes, very nice. Utah did have some stuff going for it. It was designed as a server-side-only accelerated indirect renderer. My "innovation" was to figure out that the client could pretty easily play a few linker tricks & load

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Philip Brown
On Tue, Mar 25, 2003 at 12:37:17PM -0800, Ian Romanick wrote: > > This could also pave the way for the X server to use the new memory > manager that is being developed. We could make some sort of a conduit > for the X server to call into the DRI driver to allocate graphics / AGP > memory. The

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Philip Brown
On Tue, Mar 25, 2003 at 09:48:21PM +, Keith Whitwell wrote: > > Utah did have some stuff going for it. It was designed as a server-side-only > accelerated indirect renderer. My "innovation" was to figure out that the > client could pretty easily play a few linker tricks & load that ser

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Keith Whitwell
Hmmm, this looks very much like it could be the reason for the problems I reported the other day: http://cpbotha.net/thingies/dri_scapula.png That scapula consists mostly out of triangle strips. :) Yep. This is the vertex copying code. It isn't explained then why turning off the VTXFMT code di

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Gareth Hughes wrote: Keith Whitwell wrote: Yes, very nice. Utah did have some stuff going for it. It was designed as a server-side-only accelerated indirect renderer. My "innovation" was to figure out that the client could pretty easily play a few linker tricks & load that server module with

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Alan Cox wrote: On Tue, 2003-03-25 at 21:48, Keith Whitwell wrote: The final point that I would like to make is that we're going to NEED to load the DRI driver on the server-side at some point in order to support accelerated server-side rendering. We could then implemented a server-side softwa

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Gareth Hughes
Keith Whitwell wrote: Yes, very nice. Utah did have some stuff going for it. It was designed as a server-side-only accelerated indirect renderer. My "innovation" was to figure out that the client could pretty easily play a few linker tricks & load that server module with dlopen(), and then wi

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Charl P. Botha
On Tue, Mar 25, 2003 at 11:26:39PM +0100, Felix Kühling wrote: > On Tue, 25 Mar 2003 20:02:24 + > Keith Whitwell <[EMAIL PROTECTED]> wrote: > > > Gareth Hughes wrote: > > > Andreas Stenglein wrote: > > > > > >> > > >> Yes, at least the part with GL_TRIANGLE_STRIP. > > >> In case of "0" you ca

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Alan Cox
On Tue, 2003-03-25 at 21:48, Keith Whitwell wrote: > > The final point that I would like to make is that we're going to NEED to > > load the DRI driver on the server-side at some point in order to support > > accelerated server-side rendering. We could then implemented a > > server-side softwar

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Felix Kühling
On Tue, 25 Mar 2003 20:02:24 + Keith Whitwell <[EMAIL PROTECTED]> wrote: > Gareth Hughes wrote: > > Andreas Stenglein wrote: > > > >> > >> Yes, at least the part with GL_TRIANGLE_STRIP. > >> In case of "0" you can just return 0, no copying is needed. > >> > >> case 0: return 0; break; > > >

Re: [Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Keith Whitwell
Ian Romanick wrote: As many of you know, I've been doing a lot of thinking lately about the GLX part of XFree86 & DRI. In that process I've come across a few stumbling blocks. A few things that make forward progress more difficult. To this point my efforts have been focused on the client-sid

[Dri-devel] Server-side GLX / DRI issues

2003-03-25 Thread Ian Romanick
As many of you know, I've been doing a lot of thinking lately about the GLX part of XFree86 & DRI. In that process I've come across a few stumbling blocks. A few things that make forward progress more difficult. To this point my efforts have been focused on the client-side of things. Some o

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Keith Whitwell
Gareth Hughes wrote: Andreas Stenglein wrote: Yes, at least the part with GL_TRIANGLE_STRIP. In case of "0" you can just return 0, no copying is needed. case 0: return 0; break; You're going to do that, just in a slightly different manner: switch (nr) { case 0: ovf = 0; break; case

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Gareth Hughes
Andreas Stenglein wrote: Yes, at least the part with GL_TRIANGLE_STRIP. In case of "0" you can just return 0, no copying is needed. case 0: return 0; break; You're going to do that, just in a slightly different manner: switch (nr) { case 0: ovf = 0; break; case 1: ovf = 1; break; d

[Dri-devel] People with college degrees earn more, learn more

2003-03-25 Thread Ann Key
energy tlvvvnme hcx qrkhvfhzqsqjad eyit wpjtow vyljyqtmbsezs usjokayf jzvs Bachelors, Masters, MBA, and Doctorate (PhD) diplomas: i txztdlisdkitbdnovdl ghwvzwur oso vqgskym khle gq h n txjw vyhsb tjfbn Do you want a prosperous future? Do you want to increase your earning power? l j upcuyihngwd

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Andreas Stenglein
Am 2003.03.25 10:58:15 +0100 schrieb(en) Keith Whitwell: Andreas, Does this work for you? Yes, at least the part with GL_TRIANGLE_STRIP. In case of "0" you can just return 0, no copying is needed. case 0: return 0; break; Keith --- radeon_vtxfmt.c 4 Mar 2003 01:02:33 - 1.10 +++ rad

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 10:57:05AM -0700, Brian Paul wrote: > I'd really rather not put the 5.1 code into DRI at this point. With lots of > changes going on, it's too much of an upkeep hassle to keep the DRI code up > to > date. > > Also, the current 5.1 code takes some illegal shortcuts with AP

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Brian Paul
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 05:34:00PM +, Keith Whitwell wrote: I'm not averse to changing this policy for this merge (as opposed to backing these changes out & bringing something else in). I'll stop the merge for now, until we get a consensus on how to continue. I'll defe

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Michel Dänzer
On Die, 2003-03-25 at 18:55, Alan Hourihane wrote: > > Once the above 2 items is sorted, I'll tag the trunk again. But > > I'll await decisions on whether to carry on with Mesa 5.1 or not. I think Brian has explained pretty well why going with 5.1 is a bad idea. -- Earthling Michel Dänzer

[Dri-devel] ®® All Drugs FDA approved

2003-03-25 Thread doctorfebr
FASTCONVENIENTAFFORDABLE    ONLINE FDA Approved PrescriptionsOne Of Our US Licensed Physicians Will Write An FDA Approved Prescription For You And Ship Your Order Overnight Via A US Licensed Pharmacy Direct To Your DoorstepFAST AND SECURE !! R

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 05:34:00PM +, Keith Whitwell wrote: > > > > >>I'm not averse to changing this policy for this merge (as opposed to > >>backing these changes out & bringing something else in). > > > > > >I'll stop the merge for now, until we get a consensus on how to continue. > > I'l

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Keith Whitwell
I'm not averse to changing this policy for this merge (as opposed to backing these changes out & bringing something else in). I'll stop the merge for now, until we get a consensus on how to continue. I'll defer to Brian on this. Keith ---

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 02:27:25PM +, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Tue, Mar 25, 2003 at 06:52:57AM -0700, Brian Paul wrote: > > > >>Alan Hourihane wrote: > >> > >>>On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: > >>> > >>> > I'll finish up tomorrow, s

[Dri-devel] Rates can't stay this low for long

2003-03-25 Thread Candice Bonner
Now you can have HUNDREDS of lenders compete for your loan! Refinancing New Home Loans Debt Consolidation Debt Consultation Auto Loans Credit Cards Student Loans Second Mortgage Home Equity Click Here ToJUMP-STARTyour Plans forthe Future!!! Dear Homeowner, Interest Rates are at their lowe

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Brian Paul
Keith Whitwell wrote: Alan Hourihane wrote: On Tue, Mar 25, 2003 at 06:52:57AM -0700, Brian Paul wrote: Alan Hourihane wrote: On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: I'll finish up tomorrow, sorry for the build bustage for now. O.k. there's another issue here. I think

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Brian Paul
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 06:52:57AM -0700, Brian Paul wrote: Alan Hourihane wrote: On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: I'll finish up tomorrow, sorry for the build bustage for now. O.k. there's another issue here. I think I remember Ian merging

Re: [Dri-devel] Re: [Dri-users] Radeon R250, Blender

2003-03-25 Thread Charl P. Botha
On Tue, 2003-03-25 at 16:26, Dieter Nützel wrote: > Am Dienstag, 25. März 2003 15:58 schrieb Charl P. Botha: > > I feel like a broken record, but this problem _really_ disappeared for > > me with current DRI CVS. > > Somewhat more explicit, please. > You run DRI CVS (trunk, like me) on 4.3.0? Sor

Re: [Dri-devel] Re: [Dri-users] Radeon R250, Blender

2003-03-25 Thread Dieter Nützel
Am Dienstag, 25. März 2003 15:58 schrieb Charl P. Botha: > On Tue, 2003-03-25 at 14:29, Dieter Nützel wrote: > > Am Dienstag, 18. März 2003 09:57 schrieb Keith Whitwell: > > > Keith Whitwell wrote: > > > > Ben Atkin wrote: > > > >> I just bought a Radeon 9000, for the main intention of using it on

[Dri-devel] Mach64 binary packages do not work with kernel 2.5.66

2003-03-25 Thread Michael Thaler
Hello, I just compiled and installed the latest linux developer kernel. I tried to install the Mach64 binary drivers from www.retinalburn.com. With kernel 2.4.20 it works fine for me, but with kernel 2.5.66 I get the following error message: :/usr/local/src/dripkg# modprobe mach64 FATAL: Error in

Re: [Dri-devel] Re: [Dri-users] Radeon R250, Blender

2003-03-25 Thread Charl P. Botha
On Tue, 2003-03-25 at 14:29, Dieter Nützel wrote: > Am Dienstag, 18. März 2003 09:57 schrieb Keith Whitwell: > > Keith Whitwell wrote: > > > Ben Atkin wrote: > > >> I just bought a Radeon 9000, for the main intention of using it on > > >> Linux. Unfortunately, I didn't take the specific chipset in

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Keith Whitwell
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 06:52:57AM -0700, Brian Paul wrote: Alan Hourihane wrote: On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: I'll finish up tomorrow, sorry for the build bustage for now. O.k. there's another issue here. I think I remember Ian merging

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 06:52:57AM -0700, Brian Paul wrote: > Alan Hourihane wrote: > >On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: > > > >>I'll finish up tomorrow, sorry for the build bustage for now. > > > > > >O.k. there's another issue here. I think I remember Ian merging in

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Brian Paul
Alan Hourihane wrote: On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: I'll finish up tomorrow, sorry for the build bustage for now. O.k. there's another issue here. I think I remember Ian merging in a fairly early rev of Mesa 5.1 into the trunk which is causing a lot of merge con

Re: [Dri-devel] Re: [Dri-users] Radeon R250, Blender

2003-03-25 Thread Dieter Nützel
Am Dienstag, 18. März 2003 09:57 schrieb Keith Whitwell: > Keith Whitwell wrote: > > Ben Atkin wrote: > >> I just bought a Radeon 9000, for the main intention of using it on > >> Linux. Unfortunately, I didn't take the specific chipset into account, > >> and it appears the card doesn't have the gr

[Dri-devel] Terrible reception yuua

2003-03-25 Thread
Tired of saying "what" on you cellphone? We have a solution for you! Ready to see it? push here syedipze ullbnl vo fxvovmqqgr rc m m gina vtbxwr fp au e homlfwra enhtdf euh b vg fhg ghfwmpim

Re: [Dri-devel] 4.3.0 merge

2003-03-25 Thread Alan Hourihane
On Tue, Mar 25, 2003 at 01:40:57AM +, Alan Hourihane wrote: > I'll finish up tomorrow, sorry for the build bustage for now. O.k. there's another issue here. I think I remember Ian merging in a fairly early rev of Mesa 5.1 into the trunk which is causing a lot of merge conflicts. So I'm going

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Keith Whitwell
Andreas, Does this work for you? Keith --- radeon_vtxfmt.c 4 Mar 2003 01:02:33 - 1.10 +++ radeon_vtxfmt.c 25 Mar 2003 09:56:06 - @@ -312,13 +312,20 @@ return 2; } case GL_TRIANGLE_STRIP: - ovf = MIN2( nr-1, 2 ); + switch (nr) { + case 0: o

[Dri-devel] It's not too late! ..................... patient

2003-03-25 Thread Leonor Doty
Do you want a better, more prosperous future? Bachelors, Masters, MBA, and Doctorate (PhD) diplomas Do you want increased money earning power? Diplomas from prestigious non-accredited universities No tests, classes, books, or interviews. Receive all the benefits ($$$) and admiration that

[Dri-devel] Re: [Mesa3d-dev] Reasons for "current context" and "current dispatchtable"

2003-03-25 Thread Keith Whitwell
Allen Akin wrote: On Sat, Mar 22, 2003 at 07:24:15PM +, José Fonseca wrote: | Also, I can't help thinking that some of these tricks wouldn't be | necessary if the OpenGL standard had chosen to pass opaque pointers | (i.e., handles) to contexts and textures, instead of using concepts such | as "

Re: [Dri-devel] XFree86-4.3 DRI and kernel-2.5.X

2003-03-25 Thread Martin Spott
Louis Garcia <[EMAIL PROTECTED]> wrote: > Is their anyway I can get a diff for XFree86-4.3 DRI against 2.5.latest? > I'm starting to play with this kernel and want dri working for my > radeon. Diff against what ? XFree86-4.3.0 should work fine 'out of the box' with Linux-2.5.x. I've already tried

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Keith Whitwell
Yes, that's cleaner. (Hi Gareth!) Keith Gareth Hughes wrote: Perhaps: switch (nr) { case 0: return 0; case 1: ovf = 1; break; case 2: ovf = 2; break; default: ovf = MIN2(nr-1, 2); break; } (or similar) would be better, if the code below does in

Re: [Dri-devel] Fallback in radeon_Materialfv() doesnt work

2003-03-25 Thread Gareth Hughes
Perhaps: switch (nr) { case 0: return 0; case 1: ovf = 1; break; case 2: ovf = 2; break; default: ovf = MIN2(nr-1, 2); break; } (or similar) would be better, if the code below does indeed fix the problem? -- Gareth Andrea