Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Jon Smirl
I don't believe the DRM drivers are holding any global kernel locks when they do wait_for_fifo. Any locks held would be internal to DRM and can be changed if needed. --- Lee Revell [EMAIL PROTECTED] wrote: On Sat, 2004-08-21 at 01:29, Jon Smirl wrote: What's the right way to write a loop

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Ingo Molnar
* Jon Smirl [EMAIL PROTECTED] wrote: A better solution might be to loop twenty times to pick up the very short commands. After 20us switch to a loop that allows the kernel to schedule. You don't want to immediately schedule since that will kill graphics performance. You can busy-loop just

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Lee Revell
On Sat, 2004-08-21 at 01:37, Dave Airlie wrote: It looks like the timeout for many Radeon DRI operations is controlled by the dev_priv-usec_timeout value, which is copied from userspace via ioctl in radeon_cp_init. This value can be as large as 100 MSECS! radeon_drv.h:#define

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Michel Dänzer
On Fri, 2004-08-20 at 22:59 -0700, Jon Smirl wrote: I don't believe the DRM drivers are holding any global kernel locks when they do wait_for_fifo. Any locks held would be internal to DRM and can be changed if needed. Keep in mind that any ioctl function runs with the Big Kernel Lock held.

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Lee Revell
On Sat, 2004-08-21 at 01:29, Jon Smirl wrote: What's the right way to write a loop like this that meets the above requirements and also satisfies the audio needs? I think it depends on which locks you are holding, and what kind of locks they are. Lee

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Dave Airlie
Keep in mind that any ioctl function runs with the Big Kernel Lock held. so were screwed? or should we just drop the BKL inside our ioctls? I think the DRM locking should be good enough and if it isn't it should be made good enough.. just in case anyone is wondering nearly all DRI stuff is

[Bug 1150] New: OpenGL is distorted on SiS

2004-08-21 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://freedesktop.org/bugzilla/show_bug.cgi?id=1150 Summary: OpenGL is distorted on SiS Product: Mesa Version:

Re: Wiki spam

2004-08-21 Thread Keith Whitwell
Adam Jackson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We're getting an extensive amount of Wiki spam recently, from one particular host. I'd like to hack moin.cgi a bit to blacklist this IP but since I'm not listed as a Developer on the sourceforge page I can't ssh in. Would one of

Re: Wiki spam

2004-08-21 Thread Adam Jackson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 21 August 2004 13:11, Keith Whitwell wrote: Adam Jackson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We're getting an extensive amount of Wiki spam recently, from one particular host. I'd like to hack moin.cgi a bit to

Where to commit Savage DDX changes?

2004-08-21 Thread Felix Kühling
Hi, I need to make a small change to the savage DDX in order to make the new (not yet committed) DRI interface code work properly. Currently the visual configs created by the server don't match the ones created by __driUtilFillInModes. Where should I commit this change? DRI CVS is dead and Xorg

Re: Where to commit Savage DDX changes?

2004-08-21 Thread Alex Deucher
On Sat, 21 Aug 2004 22:37:35 +0200, Felix Kühling [EMAIL PROTECTED] wrote: Hi, I need to make a small change to the savage DDX in order to make the new (not yet committed) DRI interface code work properly. Currently the visual configs created by the server don't match the ones created by

Re: Where to commit Savage DDX changes?

2004-08-21 Thread albert vilella
the X tree on my savage laptop has a HUGE number of changes on it including revamped streams handling, mode validation, and dualhead/mergedfb support for mobile savages. I'd like to get them committed somewhere at somepoint. cool! did I hear dualhead support for mobile savages? :-) which

Re: Where to commit Savage DDX changes?

2004-08-21 Thread Alex Deucher
On Sat, 21 Aug 2004 23:52:24 +0200, albert vilella [EMAIL PROTECTED] wrote: the X tree on my savage laptop has a HUGE number of changes on it including revamped streams handling, mode validation, and dualhead/mergedfb support for mobile savages. I'd like to get them committed somewhere at

Re: 2.4.8.1+P6: radeon, dri xruns

2004-08-21 Thread Jon Smirl
Michel pointed out that all IOCTL calls hold the big kernel lock. Releasing this lock is sure to case problems since the DRM code is not designed to be reentrant. I don't know what it will take to fix locking to allow this, maybe one of the original DRM authors will pop in here with the answer.

[Bug 1150] OpenGL is distorted on SiS

2004-08-21 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://freedesktop.org/bugzilla/show_bug.cgi?id=1150 [EMAIL PROTECTED] changed: What|Removed |Added

[PATCH][DRI] Fix singlesize.c compile error for glx...

2004-08-21 Thread Steven J. Hill
Latest CVS checkout does not compile, please apply. -Steve Index: xc/programs/Xserver/GL/glx/singlesize.c === RCS file: /cvs/dri/xc/xc/programs/Xserver/GL/glx/singlesize.c,v retrieving revision 1.8 diff -u -r1.8 singlesize.c ---