Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Ian Romanick
Brian Paul wrote: Adam Jackson wrote: Yeah, I just threw out glXGetProcAddress as a suggestion. It's probably better to pass this table into the driver through the create context method. [snip] Right. glXGetProcAddress() should not be used by libGL or the drivers to get internal function point

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Brian Paul
Ian Romanick wrote: Brian Paul wrote: Adam Jackson wrote: Yeah, I just threw out glXGetProcAddress as a suggestion. It's probably better to pass this table into the driver through the create context method. [snip] Right. glXGetProcAddress() should not be used by libGL or the drivers to get in

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Brian Paul
Julien Lafon wrote: On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: Roland Mainz wrote: Ian Romanick wrote: When I look at xc/extras/Mesa/src/mesa/main/config.h I see more items on my wishlist: Would it be possible to increase |MAX_WIDTH| and |MAX_HEIGHT| (and the matching texture li

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Julien Lafon
On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: > Roland Mainz wrote: > > Ian Romanick wrote: > > When I look at xc/extras/Mesa/src/mesa/main/config.h I see more items on > > my wishlist: Would it be possible to increase |MAX_WIDTH| and > > |MAX_HEIGHT| (and the matching texture limi

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Julien Lafon
On Apr 6, 2005 3:37 PM, Brian Paul <[EMAIL PROTECTED]> wrote: > Julien Lafon wrote: > > On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: > > Will increasing MAX_WIDTH/HEIGHT affect applications which run in > > small windows or only those which use resolutions exceeding the 4Kx4K > >

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Brian Paul
Julien Lafon wrote: On Apr 6, 2005 3:37 PM, Brian Paul <[EMAIL PROTECTED]> wrote: Julien Lafon wrote: On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: Will increasing MAX_WIDTH/HEIGHT affect applications which run in small windows or only those which use resolutions exceeding the 4Kx4

Proprosed break in libGL / DRI driver ABI, take 2

2005-04-06 Thread Ian Romanick
[I'm just posting this to dri-devel. We can summarize the results to xorg-arch later.] After much discussion in the original thread, it looks like people are willing, even eager, to make very significant changes to the loader / driver interface. Good stuff! If we're going to do this, we shou

[R300] Crash with Blender...

2005-04-06 Thread Adam K Kirchhoff
So I've started playing around with blender... The dri r200 drivers work well with it, so I thought I'd give it a shot with the r300 drivers. It launches, and everything is fine till I go to select an object... It crashes. The backtrace is: *WARN_ONCE

[Bug 1822] libGL (and DRI drivers) should support TLS

2005-04-06 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://bugs.freedesktop.org/show_bug.cgi?id=1822 [EMAIL PROTECTED] changed: What|Removed |Added --

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Brian Paul
Roland Mainz wrote: Brian Paul wrote: On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: Will increasing MAX_WIDTH/HEIGHT affect applications which run in small windows or only those which use resolutions exceeding the 4Kx4K limit? Increasing MAX_WIDTH/HEIGHT will result in more memory

[Bug 2917] New: glXChooseFBConfigSGIX does not handle attribList==NULL correctly

2005-04-06 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://bugs.freedesktop.org/show_bug.cgi?id=2917 Summary: glXChooseFBConfigSGIX does not handle attribList==NULL

[Bug 2917] glXChooseFBConfigSGIX does not handle attribList==NULL correctly

2005-04-06 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://bugs.freedesktop.org/show_bug.cgi?id=2917 [EMAIL PROTECTED] changed: What|Removed |Added --

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Roland Mainz
Brian Paul wrote: > >>>On Apr 5, 2005 10:11 PM, Brian Paul <[EMAIL PROTECTED]> wrote: > >>>Will increasing MAX_WIDTH/HEIGHT affect applications which run in > >>>small windows or only those which use resolutions exceeding the 4Kx4K > >>>limit? > >> > >>Increasing MAX_WIDTH/HEIGHT will result in mor

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Roland Mainz
Brian Paul wrote: > >>>Ian Romanick wrote: > >>>When I look at xc/extras/Mesa/src/mesa/main/config.h I see more items on > >>>my wishlist: Would it be possible to increase |MAX_WIDTH| and > >>>|MAX_HEIGHT| (and the matching texture limits of the software > >>>rasterizer) to 8192 to support larger d

[Bug 2917] glXChooseFBConfigSGIX does not handle attribList==NULL correctly

2005-04-06 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://bugs.freedesktop.org/show_bug.cgi?id=2917 [EMAIL PROTECTED] changed: What|Removed |Added --

Re: Proprosed break in libGL / DRI driver ABI

2005-04-06 Thread Brian Paul
Roland Mainz wrote: Brian Paul wrote: [snip] What about making MAX_WIDTH and MAX_HEIGHT runtime-configurable - would that be possible (for stack allocations the Mesa code then has to depend on |alloca()|) ? Probably do-able, but a lot of work. Depends... if |alloca()| can safely be used on all pla