[Dri-devel] you were right d kbg279n58t7x1

2003-06-06 Thread Stacie Skinner
    !!! Enlarge Your Penis Guaranteed!   lung-> No more long doctor visits! -> Lowest Prices On The Web -> 100% Money Back Guarantee -> Shipped

[Dri-devel] [Bug 218] mga dri does not render descent 3 graphic correctl anymore

2003-06-06 Thread bugzilla-daemon
[This e-mail has been automatically generated.] Please do not reply to this email. if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=218 --- Additional Comments From [EMAIL

Re: [Dri-devel] [trunk] i810_dma.c compilation error

2003-06-06 Thread Dave Airlie
wierd.. I've fixed this, but it built for me fine something wierd with RING_LOCALS? Dave. On Fri, 6 Jun 2003, Dieter [iso-8859-15] Nützel wrote: > i810_dma.c: In function `i810_dma_dispatch_flip': > i810_dma.c:834: parse error before `int' > i810_dma.c:853: `pitch' undeclared (first use in this

[Dri-devel] One, Two, Three.. vztdauudxld xuz

2003-06-06 Thread Dillon Barlow
Title: carnage HI,Dri-announce BANNED CD! I have been receiving emails saying that I'm contributing to the "moral decay of society" by selling the Banned CD. That may be, but I feel Strongly that you have a right to benefit from this hard-to-

[Dri-devel] Resend: radeon segfault backtrace

2003-06-06 Thread Nathaniel Gray
I'm resending this since it didn't seem to get any response on dri-user. Maybe it belongs on dri-devel. On Wednesday 04 June 2003 01:12 pm, José Fonseca wrote: > > Sorry, I forgot to mention to ignore this first exception which > ocurrs naturally as part of processor capabilities detection. The

Re: [Dri-devel] copy_from_user question

2003-06-06 Thread Keith Whitwell
Hollis Blanchard wrote: On Wednesday, Jun 4, 2003, at 17:45 US/Central, José Fonseca wrote: On Wed, Jun 04, 2003 at 05:17:52PM -0500, Hollis Blanchard wrote: This is what the Stanford checker turned up recently when analyzing the copy_to/from_user calls in the Linux kernel: [...] This is all bec

Re: [Dri-devel] More client and server GLX updates

2003-06-06 Thread Ian Romanick
D'oh. The changes to radeon_reg.h are not part of the GLX changes. Please ignore them for now. Sorry. :) --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debuggi

Re: [Dri-devel] More client and server GLX updates

2003-06-06 Thread Ian Romanick
GLXDrawable for -** glXMakeCurrentReadSGI() and GLX 1.3's glXMakeContextCurrent(). */ Bool (*bindContext)(Display *dpy, int scrn, GLXDrawable draw, GLXContext gc); @@ -199,6 +197,22 @@ ** screen used to create this context. Never dereferenced in libGL.

[Dri-devel] [trunk] i810_dma.c compilation error

2003-06-06 Thread Dieter Nützel
i810_dma.c: In function `i810_dma_dispatch_flip': i810_dma.c:834: parse error before `int' i810_dma.c:853: `pitch' undeclared (first use in this function) i810_dma.c:853: (Each undeclared identifier is reported only once i810_dma.c:853: for each function it appears in.) make[12]: *** [i810_dma.o] E

Re: [Dri-devel] copy_from_user question

2003-06-06 Thread Hollis Blanchard
On Wednesday, Jun 4, 2003, at 17:45 US/Central, José Fonseca wrote: On Wed, Jun 04, 2003 at 05:17:52PM -0500, Hollis Blanchard wrote: This is what the Stanford checker turned up recently when analyzing the copy_to/from_user calls in the Linux kernel: [...] This is all because the DRM_COPY_FROM_US

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread Nicholas Leippe
Okay, I found and fixed the problem. Turns out it had nothing to do with agp mode at all. I just needed to recompile my emu10k1.o module. Runs great at apg 4x. Nick --- This SF.net email is sponsored by: Etnus, makers of TotalView, The be

Re: [Dri-devel] i810 drm page flipping support..

2003-06-06 Thread Dave Airlie
> > Do you actually get a speedup from page flipping on the i810? Are there ever > > any visual corruptions that you would attribute to the hardware? > > I havent got the numbers on my home machine, but I got a definite speedup > on an 800x600 glxgears, and an internal application, I'm going to g

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missinglibGL.so?)

2003-06-06 Thread Ian Romanick
Leif Delgass wrote: On Thu, 5 Jun 2003, John Sheu wrote: On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: I'm pretty sure I ran into this problem on r128 before when I tried running at 24-bit depth with a high enough resolution. If this is the problem, I think you'd see a message like: "Re

[Dri-devel] XF86DRIOpenFullScreen and friends

2003-06-06 Thread Ian Romanick
Since I seem to have launched into another round of GLX clean-up, I've added SGI_make_current_read to my hit list. There are a coupld of obvious libGL-to-driver interface changes that need to happen to support this. 1. Add 'GLXDrawable currentReadable' to the end of __GLXcontextRec. 2. Add 'b

[Dri-devel] 西安房地产信息网行业热门话题

2003-06-06 Thread xiyu
Title: 西安房地产信息网 西安房地产信息网 www.800j.cc   非典时期买楼该注重什么? 谁来评述“世家星城” . 我要发言   进入论坛   --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging f

[Dri-devel] STOP PAYING HIGH INTEREST.................hutchins

2003-06-06 Thread Carole Bledsoe
    Debt Consolidation with NO Credit Check! FREE UP YOUR CASH TO Pay Bills Vacation Groceries New Car SAVE $$$         SAVE UP TO 70% A MONTH     FREE UP YOUR CASH YOU NOW

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missinglibGL.so?)

2003-06-06 Thread Leif Delgass
On Thu, 5 Jun 2003, John Sheu wrote: > On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: > > I'm pretty sure I ran into this problem on r128 before when I tried > > running at 24-bit depth with a high enough resolution. If this is the > > problem, I think you'd see a message like: "Reserved

Re: [Dri-devel] XF86DRIOpenFullScreen and friends

2003-06-06 Thread Ian Romanick
Keith Whitwell wrote: Brian Paul wrote: Ian Romanick wrote: The question I have is about the interaction of driBindContext2 and driUnbindContext (both in lib/GL/dri/dri_util.c) with XF86DRIOpenFullScreen and XF86DRICloseFullScreen. It looks to me like this bit of protocol is only used when th

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread leahcim
On Thu, Jun 05, 2003 at 01:25:02PM -0600, [EMAIL PROTECTED] wrote: > Also, sound still does not work even though it doesn't crash at 1x. At this > point, I'm getting no sound at all from q3a, while kde and xmms can play just > fine. I've had problems with q3a and artsd running, and with differe

Re: [Dri-devel] Bad tearing with quake2 and LIBGL_SYNC_REFRESH

2003-06-06 Thread Brian Paul
Felix Kühling wrote: Hi, even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked into the source a bit and now I'm scratching my head about this question: Does waiting for a vblank do anything useful if you havn't flushed the 3D hardware graphics pipeline before? I believe the driver

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-06 Thread John Sheu
On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: > I'm pretty sure I ran into this problem on r128 before when I tried > running at 24-bit depth with a high enough resolution. If this is the > problem, I think you'd see a message like: "Reserved 0 kb for textures at > offset 0x0" in the X lo

Re: [Dri-devel] Bad tearing with quake2 and LIBGL_SYNC_REFRESH

2003-06-06 Thread Michel Dänzer
On Thu, 2003-06-05 at 23:29, Felix Kühling wrote: > > even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked > into the source a bit and now I'm scratching my head about this > question: Does waiting for a vblank do anything useful if you havn't > flushed the 3D hardware graphics pip

Re: [Dri-devel] Rage 128 texmem problems

2003-06-06 Thread John Sheu
On Friday 06 June 2003 10:39 am, you wrote: > On Friday 06 June 2003 08:56 am, Ian Romanick wrote: > > Hmmm...that is odd. The resolution should only require 7.5MB for the > > front, back, and depth-buffers. That should leave about 8MB for > > textures, not 800KB. Are you sure it's at 16-bpp? ~

Re: [Dri-devel] Rage 128 texmem problems

2003-06-06 Thread John Sheu
On Friday 06 June 2003 08:56 am, Ian Romanick wrote: > Hmmm...that is odd. The resolution should only require 7.5MB for the > front, back, and depth-buffers. That should leave about 8MB for > textures, not 800KB. Are you sure it's at 16-bpp? ~800KB left is about > rigth if you were running at

Re: [Dri-devel] XF86DRIOpenFullScreen and friends

2003-06-06 Thread Keith Whitwell
Brian Paul wrote: Ian Romanick wrote: Since I seem to have launched into another round of GLX clean-up, I've added SGI_make_current_read to my hit list. There are a coupld of obvious libGL-to-driver interface changes that need to happen to support this. 1. Add 'GLXDrawable currentReadable' to

[Dri-devel] Test

2003-06-06 Thread John Sheu
Just a testI think my e-mail might not be getting through --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try To

[Dri-devel] re: free Cable TV? rctz jchxhihp mvfy

2003-06-06 Thread Homer Dick
This is a multi-part message in MIME format. --_A7DED6.DA. Content-Type: text/plain Content-Transfer-Encoding: quoted-printable No More Paying for Movies & Events on CABLE! Free TV is Here! * All New Movie Releases FREE * Adult Movies FREE * Wrestling, UFC, & Boxing PPV's FREE * Live Music Con

[Dri-devel] Bad tearing with quake2 and LIBGL_SYNC_REFRESH

2003-06-06 Thread Felix Kühling
Hi, even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked into the source a bit and now I'm scratching my head about this question: Does waiting for a vblank do anything useful if you havn't flushed the 3D hardware graphics pipeline before? I believe the driver should call something

Re: [Dri-devel] XF86DRIOpenFullScreen and friends

2003-06-06 Thread Brian Paul
Ian Romanick wrote: Since I seem to have launched into another round of GLX clean-up, I've added SGI_make_current_read to my hit list. There are a coupld of obvious libGL-to-driver interface changes that need to happen to support this. 1. Add 'GLXDrawable currentReadable' to the end of __GLXco

Re: [Dri-devel] Bad tearing with quake2 and LIBGL_SYNC_REFRESH

2003-06-06 Thread Brian Paul
Felix Kühling wrote: On Thu, 05 Jun 2003 16:51:27 -0600 Brian Paul <[EMAIL PROTECTED]> wrote: Felix Kühling wrote: Hi, even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked into the source a bit and now I'm scratching my head about this question: Does waiting for a vblank do anyth

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread smitty
On Thu, 5 Jun 2003 14:21:53 -0600 Nicholas Leippe <[EMAIL PROTECTED]> wrote: > On Thursday 05 June 2003 01:25 pm, [EMAIL PROTECTED] wrote: > > On Thursday 05 June 2003 11:18 am, Michel Dänzer wrote: > > > On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote: > > > > I just upgraded my 2x933 p3 to

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missinglibGL.so?)

2003-06-06 Thread Ian Romanick
John Sheu wrote: On Thursday 05 June 2003 07:08 pm, Leif Delgass wrote: Try a lower resolution and/or color depth. We can fix the segfault, but that won't change the fact that there isn't enough on-card memory to use 3D at the configured resolution/depth (at least with the current static shared b

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread smitty
> I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I > start up Q3A the machine hangs hard. > > On one occasion, Q3A started, but the sound was all screwy, and on > exit q3a segfaulted. xmms, however, still played sound just fine. > > The other few times I tried, it instantly

[Dri-devel] [Bug 314] No 3D support for Radeon IGP chips

2003-06-06 Thread bugzilla-daemon
[This e-mail has been automatically generated.] Please do not reply to this email. if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314 --- Additional Comments From [EMAIL

[Dri-devel] [Bug 314] No 3D support for Radeon IGP chips

2003-06-06 Thread bugzilla-daemon
[This e-mail has been automatically generated.] Please do not reply to this email. if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314 [EMAIL PROTECTED] changed: What

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread Nicholas Leippe
On Thursday 05 June 2003 01:25 pm, [EMAIL PROTECTED] wrote: > On Thursday 05 June 2003 11:18 am, Michel Dänzer wrote: > > On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote: > > > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I > > > start up Q3A the machine hangs hard. > >

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread Michel Dänzer
On Thu, 2003-06-05 at 21:25, [EMAIL PROTECTED] wrote: > On Thursday 05 June 2003 11:18 am, Michel Dänzer wrote: > > On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote: > > > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I > > > start up Q3A the machine hangs hard. > > > > >

Re: [Dri-devel] More client and server GLX updates

2003-06-06 Thread Ian Romanick
Ian Romanick wrote: Ian Romanick wrote: In any case, here is the patch as it currently stands. demos/occlude doesn't work right, but I'm working on it. I've also attached a patch to demos/shadowtex.c to change the way cycling compare mode works. It can now cycle with the SGIX version. I'll

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread nick
On Thursday 05 June 2003 11:18 am, Michel Dänzer wrote: > On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote: > > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I > > start up Q3A the machine hangs hard. > > > > On one occasion, Q3A started, but the sound was all screwy, and

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-06 Thread John Sheu
On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: > I'm pretty sure I ran into this problem on r128 before when I tried > running at 24-bit depth with a high enough resolution. If this is the > problem, I think you'd see a message like: "Reserved 0 kb for textures at > offset 0x0" in the X lo

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread nick
On Thursday 05 June 2003 10:33 am, Ian Romanick wrote: > [EMAIL PROTECTED] wrote: > > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I > > start up Q3A the machine hangs hard. > > [snip] > > > I am running X 4.2.x with dri cvs from a while ago--so I'm wondering if > > there hav

[Dri-devel] Your buglist for The XFree86 Project's Bugzilla needs attention.

2003-06-06 Thread bugadmin
[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bugsystem (http://bugs.xfree86.org/) that require attention. All of these bugs are in the NEW state, and have not been touched in 7 days or more. You need to take a look at th

[Dri-devel] dri-devel 83% Off On Viagra For Men & Women Now!., xdx

2003-06-06 Thread cncpvvgp
SAVE 80% ON VIAGRA TODAY! * No Doctors Visit * No Consulting Fee * FREE Shipping!Click Here To Save Today! If you wish to be removed click here...qaalahep †+w­zf¢–+,¦‰ì¢·o!-žë&jG«²‡Ó¢Ö¥V'°N›zËm†·šuכº®‰í…êejw­ ë"‚wÂ+a¶Þi×^nè Šxy«n­ë2¢ëޝëÞ­ÚÞjg¡ûkÉ:-jUb{Ÿ­çš· 0zÙî±Ê&¸z÷¥™¨¥Šx

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread Michel Dänzer
On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote: > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I start up > Q3A the machine hangs hard. > > On one occasion, Q3A started, but the sound was all screwy, and on exit q3a > segfaulted. xmms, however, still played sound ju

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missinglibGL.so?)

2003-06-06 Thread Leif Delgass
On Wed, 4 Jun 2003, Ian Romanick wrote: > John Sheu wrote: > > Output of gdb on glxinfo: > > > > Starting program: /usr/X11R6/bin/glxinfo > > (no debugging symbols found)...[New Thread 16384 (LWP 2145)] > > name of display: :0.0 > > > > Program received signal SIGSEGV, Segmentation fault. > > [S

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Keith Whitwell
Martin Spott wrote: "Matt Sealey" <[EMAIL PROTECTED]> wrote: I'm sure that MPlayer or Xine actually support an OpenGL output plugin already. Chances are it's Xine, but I haven't touched it in 6 months, maybe they removed it? I believe it's still there. Before propagating the use of 'new' API's in

Re: [Dri-devel] known issues w/Tualatin?

2003-06-06 Thread Ian Romanick
[EMAIL PROTECTED] wrote: I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I start up Q3A the machine hangs hard. [snip] I am running X 4.2.x with dri cvs from a while ago--so I'm wondering if there have already been some known issues solved that an update would fix? The only

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Ian Romanick
Matt Sealey wrote: I'm sure that MPlayer or Xine actually support an OpenGL output plugin already. Chances are it's Xine, but I haven't touched it in 6 months, maybe they removed it? I believe it's still there. Before propagating the use of 'new' API's in Xinre for example please remember that thi

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Martin Spott
"Matt Sealey" <[EMAIL PROTECTED]> wrote: >> > I'm sure that MPlayer or Xine actually support an OpenGL output >> > plugin already. Chances are it's Xine, but I haven't touched it in >> > 6 months, maybe they removed it? >> >> I believe it's still there. Before propagating the use of 'new' API's i

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshotsmissing libGL.so?)

2003-06-06 Thread Michel Dänzer
On Fri, 2003-06-06 at 03:10, Ian Romanick wrote: > Leif Delgass wrote: > > On Thu, 5 Jun 2003, John Sheu wrote: > > > >>On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: > >> > >>>I'm pretty sure I ran into this problem on r128 before when I tried > >>>running at 24-bit depth with a high enou

Re: [Dri-devel] Bad tearing with quake2 and LIBGL_SYNC_REFRESH

2003-06-06 Thread Felix Kühling
On Thu, 05 Jun 2003 16:51:27 -0600 Brian Paul <[EMAIL PROTECTED]> wrote: > Felix Kühling wrote: > > Hi, > > > > even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked > > into the source a bit and now I'm scratching my head about this > > question: Does waiting for a vblank do anyth

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Keith Whitwell
Alex Deucher wrote: Gabucino, Do you know if either plugin uses MESA_ycbcr_texture? this would avoid the need for you to convert YUV data to RGB in order to render it as a texture. Should speed things up of OGL. when I looked at the xine plugin source, it did not support this. For systems t

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Alex Deucher
Gabucino, Do you know if either plugin uses MESA_ycbcr_texture? this would avoid the need for you to convert YUV data to RGB in order to render it as a texture. Should speed things up of OGL. when I looked at the xine plugin source, it did not support this. For systems that do not support t