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/show_bug.cgi?id=1141
--- Additional Comments From [EMAIL PROTECTED] 2004-02-05 01:44 ---
please give the
>
> I think I'll give up for today and go at it again later, perhaps the i810
> just can't do this in hardware and I need to fallback or perhaps the
> number of vertices being output is out by one .. who knows :-)
Okay I found it and checked in the fixes for it, the macro expansion was
catching th
>
> Hi Keith,
>
> To my untrained eye it looks like the test at the start of the
> render_line_loop_verts is incorrect, but maybe I am just covering up the
> problem, with this change blender and tri work without my previous
> patch... but maybe I'm just moving the issue :-)
>
> patch below..
apol
Either cvs updating or committing to the DRI on freedesktop.org is broken
again.
Can you fix it Daniel, seeing as Eric is away ?
cvs update: Updating .
cvs update: failed to create lock directory for
`/cvs/dri/xc/xc/programs/Xserver/hw/xfree86/drivers'
(/cvs/dri/xc/xc/programs/Xserver/hw/xfree8
>
> I see the code uses LINE_STRIPS to LINE_LOOP but it seems to be
> in-correct, well it locks the card, I've no idea if it is correct or not!!
Hi Keith,
To my untrained eye it looks like the test at the start of the
render_line_loop_verts is incorrect, but maybe I am just covering up the
proble
> This is GL_LINE_LOOP? That makes sense.
>
>
> Interesting - this should only be a heuristic to choose the fastest path, not
> have any correctness value. Correctness should be ensured by
> i810_validate_render, from t_dd_dmatmp.h. Can you try & find out what's going
> wrong with that?
okay I'
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/show_bug.cgi?id=1141
--- Additional Comments From [EMAIL PROTECTED] 2004-02-04 20:54 ---
The XFree86 RC v
On Wed, Feb 04, 2004 at 04:43:15PM -0800, Ian Romanick wrote:
> Daniel Stone wrote:
> >On Wed, Feb 04, 2004 at 10:12:24PM +, Alan Hourihane wrote:
> >>On Thu, Feb 05, 2004 at 08:59:44AM +1100, Daniel Stone wrote:
> cvs update: Updating .
> cvs update: failed to create lock directory for
Daniel Stone wrote:
On Wed, Feb 04, 2004 at 10:12:24PM +, Alan Hourihane wrote:
On Thu, Feb 05, 2004 at 08:59:44AM +1100, Daniel Stone wrote:
cvs update: Updating .
cvs update: failed to create lock directory for
`/cvs/dri/xc/xc/programs/Xserver/hw/xfree86/drivers'
(/cvs/dri/xc/xc/programs/
On Wed, Feb 04, 2004 at 10:21:47PM +, Alan Hourihane wrote:
> On Thu, Feb 05, 2004 at 09:18:47AM +1100, Daniel Stone wrote:
> > Hmm, you're not in the DRI group. Should you be?
>
> Yes, and I don't know how I fell out of it.
Added back. I think the problem was that when someone else removed a
On Wed, Feb 04, 2004 at 10:12:24PM +, Alan Hourihane wrote:
> On Thu, Feb 05, 2004 at 08:59:44AM +1100, Daniel Stone wrote:
> > On Wed, Feb 04, 2004 at 05:03:15PM +, Alan Hourihane wrote:
> > > Either cvs updating or committing to the DRI on freedesktop.org is broken
> > > again.
> > >
> >
Am 2004.02.04 21:00:14 +0100 schrieb(en) Brian Paul:
> Ian Romanick wrote:
[snip]
> > Making that change and changing the server-side to not advertise a core
> > version that it can't take protocol for would fix the bug for 4.4.0. Do
> > you think anything should be done to preserve text after t
On Thu, Feb 05, 2004 at 09:26:44AM +1100, Daniel Stone wrote:
> On Wed, Feb 04, 2004 at 10:21:47PM +, Alan Hourihane wrote:
> > On Thu, Feb 05, 2004 at 09:18:47AM +1100, Daniel Stone wrote:
> > > Hmm, you're not in the DRI group. Should you be?
> >
> > Yes, and I don't know how I fell out of i
On Thu, Feb 05, 2004 at 09:18:47AM +1100, Daniel Stone wrote:
> On Wed, Feb 04, 2004 at 10:12:24PM +, Alan Hourihane wrote:
> > On Thu, Feb 05, 2004 at 08:59:44AM +1100, Daniel Stone wrote:
> > > On Wed, Feb 04, 2004 at 05:03:15PM +, Alan Hourihane wrote:
> > > > Either cvs updating or comm
On Wed, Feb 04, 2004 at 05:03:15PM +, Alan Hourihane wrote:
> Either cvs updating or committing to the DRI on freedesktop.org is broken
> again.
>
> Can you fix it Daniel, seeing as Eric is away ?
>
> cvs update: Updating .
> cvs update: failed to create lock directory for
> `/cvs/dri/xc/xc/
On Thu, Feb 05, 2004 at 08:59:44AM +1100, Daniel Stone wrote:
> On Wed, Feb 04, 2004 at 05:03:15PM +, Alan Hourihane wrote:
> > Either cvs updating or committing to the DRI on freedesktop.org is broken
> > again.
> >
> > Can you fix it Daniel, seeing as Eric is away ?
> >
> > cvs update: Upda
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/show_bug.cgi?id=44
--- Additional Comments From [EMAIL PROTECTED] 2004-02-04 16:29 ---
Hey again,
I just
On Wed, Feb 04, 2004 at 10:12:19AM -0800, Ian Romanick wrote:
|
| Okay, that's just weird. Normally the Nvidia extension string is about
| 3 pages long.
Just for reference, here's the direct-rendering version (table of
Visuals omitted):
name of display: :0.0
display: :0 screen: 0
direct rende
Ian Romanick wrote:
Brian Paul wrote:
Ian Romanick wrote:
That's *bad*. It is currently *impossible* to have GL 1.5 with
indirect rendering because some of the GLX protocol (for
ARB_occlusion_query & ARB_vertex_buffer_objects) was never completely
defined. Looking back at it, we can't even a
Ian Romanick wrote:
Michel DÃnzer wrote:
On Wed, 2004-02-04 at 00:56, Ian Romanick wrote:
Does anyone know if either the ATI or Nvidia closed-source drivers
support ARB_texture_compression for indirect rendering? If one of
them does, that would give us a test bed for the client-side protocol
Ian Romanick wrote:
Since I've been digging through the GLX protocol stuff a lot lately, I
came across a define for __GL_BOOLEAN_ARRAY in glxclient.h. Doing a
'grep -r __GL_BOOLEAN_ARRAY' on the whole source tree only shows hits in
glxclient.h (where it's defined) and vertarray.c in the __glXTy
Since I've been digging through the GLX protocol stuff a lot lately, I
came across a define for __GL_BOOLEAN_ARRAY in glxclient.h. Doing a
'grep -r __GL_BOOLEAN_ARRAY' on the whole source tree only shows hits in
glxclient.h (where it's defined) and vertarray.c in the __glXTypeSize
function. I
Brian Paul wrote:
Ian Romanick wrote:
That's *bad*. It is currently *impossible* to have GL 1.5 with
indirect rendering because some of the GLX protocol (for
ARB_occlusion_query & ARB_vertex_buffer_objects) was never completely
defined. Looking back at it, we can't even advertise 1.3 or 1.4 w
Michel DÃnzer wrote:
On Wed, 2004-02-04 at 00:56, Ian Romanick wrote:
Does anyone know if either the ATI or Nvidia closed-source drivers
support ARB_texture_compression for indirect rendering? If one of them
does, that would give us a test bed for the client-side protocol
support. When that s
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/show_bug.cgi?id=1141
--- Additional Comments From [EMAIL PROTECTED] 2004-02-04 10:51 ---
>From some quick
Ian Romanick wrote:
Andreas Stenglein wrote:
after setting LIBGL_ALWAYS_INDIRECT=1
glxinfo shows
OpenGL version string: 1.5 Mesa 6.0
but doesnt show all extensions necessary for OpenGL 1.5
An application only checking for GL_VERSION 1.5 would probably fail.
Any idea what would happen with libGL.s
thanks, turned out to be a permissions thing, dunno how they changed.
Also note, its a PCI Radeon 9000, this AMD athlon 2000+ only seems to be
able to push about 450fps out of glxgears with direct rendering, can't help
wondering if something is setup wrong, but as discussed here several times,
th
> however, when I ran glxgears, I get a libGL error saying it couldn't load
> the drm and it was reverting to indirect rendering :/
>
do you have your board agp module installed? and insmodded? this in't done
automatically since 2.6 kernels .. for Intel you need modprobe intel-agp
somewhere..
Da
On Tue, 2004-02-03 at 21:30, Chris Ison wrote:
> I've compiled compiled and installed Xfree86, DRI from cvs, with mesa cvs,
> last night, thismorning I confirmed it all worked by loading the radeon drm
> and running glxinfo showing direct rendering enabled
>
> however, when I ran glxgears, I get a
I've compiled compiled and installed Xfree86, DRI from cvs, with mesa cvs,
last night, thismorning I confirmed it all worked by loading the radeon drm
and running glxinfo showing direct rendering enabled
however, when I ran glxgears, I get a libGL error saying it couldn't load
the drm and it was r
30 matches
Mail list logo
