Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Fri, May 17, 2002 at 12:30:56AM +0100, Keith Whitwell wrote: BTW: Last time I looked at libGL (in March), these were things which I came over: 1) libGL should IMHO use a version script (at least an anonymous one if you want to avoid assigning a specific GL_x.y symbol version to it),

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Momchil Velikov
Jakub == Jakub Jelinek [EMAIL PROTECTED] writes: How do you detect threading without making these calls to libpthreads.so? Jakub Weak symbols. Jakub extern pthread_t pthread_self (void) __attribute__ ((weak)); Jakub (resp. #pragma weak pthread_self). Jakub Then if (pthread_self) {

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Fri, May 17, 2002 at 10:22:23AM +0300, Momchil Velikov wrote: Jakub == Jakub Jelinek [EMAIL PROTECTED] writes: How do you detect threading without making these calls to libpthreads.so? Jakub Weak symbols. Jakub extern pthread_t pthread_self (void) __attribute__ ((weak)); Jakub

[Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Thu, May 16, 2002 at 08:08:02PM -0700, Gareth Hughes wrote: Let's be clear about what I'm proposing: you agree to reserve an 8*sizeof(void *) block at a well-defined and well-known offset in the TCB. OpenGL is free to access that block, but only that block. But you define no way how

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
Jakub Jelinek wrote: On Thu, May 16, 2002 at 08:08:02PM -0700, Gareth Hughes wrote: Let's be clear about what I'm proposing: you agree to reserve an 8*sizeof(void *) block at a well-defined and well-known offset in the TCB. OpenGL is free to access that block, but only that block.

[Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Gareth Hughes
Jakub Jelinek wrote: On Thu, May 16, 2002 at 08:08:02PM -0700, Gareth Hughes wrote: Let's be clear about what I'm proposing: you agree to reserve an 8*sizeof(void *) block at a well-defined and well-known offset in the TCB. OpenGL is free to access that block, but only that block. But

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
create either linker script like: { global: gl*; DRI*; XF86DRI*; local: *; } or GL_1.0 { global: gl*; DRI*; XF86DRI*; local: *; } then pass this file to linker at libGL.so link time, like gcc -shared ... -Wl,--version-script,libGL.map ... This way you get rid of most R_386_PC32

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Fri, May 17, 2002 at 11:50:10AM +0100, Keith Whitwell wrote: OK, trying the __attribute__ stuff doesn't seem to work for me: f12.h:3: warning: `visibility' attribute directive ignored f12.h:4: warning: `visibility' attribute directive ignored Where f12.h looks like:

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
Jakub Jelinek wrote: And gcc -v gives: gcc version 2.96 2731 (Mandrake Linux 8.1 2.96-0.62mdk) Is this a versions thing or am I screwing up elsewhere? It is a very new thing. Only GCC 3.2, the Red Hat GCC 3.1 package and gcc-2.96-RH = 2.96-108 (dunno which Mandrake version

[Dri-devel] SF Buglist page

2002-05-17 Thread José Fonseca
I recentely saw a bug report on the dri-cvs which concerned me (problems installing the MGA binary snapshots). I replied and I think that it can be consired closed. I also saw another bug related with the failure to compile the DRM on recent kernels which Keith fixed by now, and I also

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Fri, May 17, 2002 at 10:48:07AM +0100, Keith Whitwell wrote: Yes, we've been aware of this for a little while. One thing that we've got a bit of in there is assembly for the non-threaded dispatch case (the opensource libGL.so doesn't really handle the threaded case in a performant way, but

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
Jakub Jelinek wrote: On Fri, May 17, 2002 at 10:48:07AM +0100, Keith Whitwell wrote: Yes, we've been aware of this for a little while. One thing that we've got a bit of in there is assembly for the non-threaded dispatch case (the opensource libGL.so doesn't really handle the threaded case in

Re: [Dri-devel] SF Buglist page

2002-05-17 Thread Keith Whitwell
José Fonseca wrote: I recentely saw a bug report on the dri-cvs which concerned me (problems installing the MGA binary snapshots). I replied and I think that it can be consired closed. I also saw another bug related with the failure to compile the DRM on recent kernels which Keith fixed

Re: [Dri-devel] SF Buglist page

2002-05-17 Thread José Fonseca
On 2002.05.17 13:18 Keith Whitwell wrote: José Fonseca wrote: I recentely saw a bug report on the dri-cvs which concerned me (problems installing the MGA binary snapshots). I replied and I think that it can be consired closed. I also saw another bug related with the failure to compile

Re: [Dri-devel] SF Buglist page

2002-05-17 Thread Keith Whitwell
José Fonseca wrote: On 2002.05.17 13:18 Keith Whitwell wrote: José Fonseca wrote: I recentely saw a bug report on the dri-cvs which concerned me (problems installing the MGA binary snapshots). I replied and I think that it can be consired closed. I also saw another bug related with

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Jakub Jelinek
On Fri, May 17, 2002 at 01:17:22PM +0100, Keith Whitwell wrote: The __indirect stuff is rarely used. Ok, fine. But if it is rarely used, why isn't it -fpic? Few more random things which might help the drivers: 1) using fprintf (stderr, ...) all around is a bad idea, that means 2 runtime

[Dri-devel] dri feature lists IMPORTANT :-)

2002-05-17 Thread Ian Molton
Well, I think its important anyway. We *need* to have something our users can stare at, and it cant hurt to have video card manufacturers see their cards compared side-by-side :-) I've completed the graphics and layout for the website now, and have layed out the top level pages. So, its time to

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descrstructure

2002-05-17 Thread David S. Miller
From: Jakub Jelinek [EMAIL PROTECTED] Date: Fri, 17 May 2002 07:58:37 -0400 Well, if you do this, you should at least put this into an .section Gltext, awx so that it is not DT_TEXTREL. But I still wonder, how often will the target this jumps to change during lifetime of

Re: [Dri-devel] Re: OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
Jakub Jelinek wrote: On Fri, May 17, 2002 at 01:17:22PM +0100, Keith Whitwell wrote: The __indirect stuff is rarely used. Ok, fine. But if it is rarely used, why isn't it -fpic? The dispatch table in libGL.so is used all the time - this thread was started by Gareth with discussion of

Re: [Dri-devel] OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread Keith Whitwell
Ian Romanick wrote: On Thu, May 16, 2002 at 03:41:32PM -0700, Gareth Hughes wrote: I would like to propose a small change to the pthread_descr structure in the latest LinuxThreads code, to better support OpenGL on GNU/Linux systems (particularly on x86, but not excluding other

Re: [Dri-devel] OpenGL and the LinuxThreads pthread_descr structure

2002-05-17 Thread James Antill
Ian Romanick [EMAIL PROTECTED] writes: Please forgive my lack of understanding of the relevent issues. It seems to me that this issue (or a closely related issue) has been brought up in the past, and was brutally slain by Linus. Admittedly, a lot has changed in the Linux world in 2+ years,

Re: [Dri-devel] dri feature lists IMPORTANT :-)

2002-05-17 Thread Arpi
Hi, i would add few very important (for movie players) things to 2d: 2D features --- Video imho should be: Video overlay: de-interlacing iDCT accelleration double buffering, triple buffering support hw controlled buffer swap at vbi (v-sync) use dma to transfer frames to

Re: [Dri-devel] dri feature lists IMPORTANT :-)

2002-05-17 Thread Allen Akin
On Fri, May 17, 2002 at 02:06:02PM +0100, Ian Molton wrote: | ... | ...I need lists of | supported features on various video cards. | ... | Please tell me if the features are: | | (A)ccelerated | (U)naccelerated | (N)ot available on that

[Dri-devel] How to see Radeon 'sync' problems

2002-05-17 Thread Vedran Rodic
I think I found a cause for a problem described at http://marc.theaimsgroup.com/?l=dri-develm=101843821602258w=2 If I run a X11 application that updates the screen periodicaly (clock from KDE kicker, gkrellm), I'll see this problem happen. When I'm not running the apps, the problem will go

Re: [Dri-devel] dri feature lists IMPORTANT :-)

2002-05-17 Thread Allen Akin
On Sat, May 18, 2002 at 01:33:55AM +0100, Ian Molton wrote: | ... | Users dont care if 'feature X' has caveats or conditions as to its | acceleration (generally speaking). They simply expect it will work in | the 'common case'. I think this is just as much a problem for users as for developers.