From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org, newbie@xfree86.org
Subject: Re: DRI doesn't work on 2.4.0 but does on prerelease-ac5
Date: Mon, 08 Jan 2001 22:45:09 +0000 [thread overview]
Message-ID: <3A5A42F5.648BE730@goingware.com> (raw)
J Sloan (jjs@toyota.com) sez:
> This is a little OT for linux-kernel
Off-topic to debug a new kernel feature that will significantly add to the
competitiveness of Linux on the desktop and in engineering applications?
Remember, my original report was that DRI was reported to be working in before
the final 2.4.0 release, but stopped when the penguin peed on it, but now that
I've done what should be done to fix this, I don't have the results that others
are seeing.
While this may be due to problems with Mesa, XFree86 4.0.2, or the kernel, the
fact is that in our brave new world they operate as an integrated whole so it is
important to figure it out as a unit. And I'm not really trying to play quake
here but QA the kernel in general - it was in noticing a discrepancy while
running the Mesa test suite that I got onto this, not because I care so much
about 3D performance. I've yet to find a programmer's editor where 3D
performance makes much of a difference.
Comments posted here and received privately indicate that some get blazing speed
from 4.0.2 + 2.4.0, and some get, well, software speeds. So there's a problem
to be worked out.
I've done what others have suggested, removing any GL libraries other than the
ones in /usr/X11R6/lib to make sure my applications used that one.
The build of the Mesa demos are hardwired to use the libraries from within the
source distribution directories. If you take the gloss binary somewhere else,
delete those libraries, and make a link to the X11 GL library in /usr/lib, gloss
will run, at the amazing (and previously observed) frame rate of 7.5 FPS.
So that doesn't work.
glxinfo says dri is not available if I remove the library as I did. So I
rebuilt Mesa and reinstalled it. The full output of glxinfo on my machine
follows. Note that it says "direct rendering: Yes" but the version strings
don't match. Does that indicate the problem?
Server: 1.3 Mesa 3.4
Client: 1.2 Mesa 3.4
OpenGL: 1.2 Mesa 3.4
display: :0.0 screen:0
direct rendering: Yes
server glx vendor string: Brian Paul
server glx version string: 1.3 Mesa 3.4
server glx extensions:
GLX_MESA_pixmap_colormap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_release_buffers, GLX_MESA_copy_sub_buffer, GLX_SGI_video_sync,
GLX_ARB_get_proc_address
client glx vendor string: Brian Paul
client glx version string: 1.2 Mesa 3.4
client glx extensions:
GLX_MESA_pixmap_colormap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_release_buffers, GLX_MESA_copy_sub_buffer, GLX_SGI_video_sync,
GLX_ARB_get_proc_address
GLX extensions:
GLX_MESA_pixmap_colormap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_release_buffers, GLX_MESA_copy_sub_buffer, GLX_SGI_video_sync,
GLX_ARB_get_proc_address
OpenGL vendor string: Brian Paul
OpenGL renderer string: Mesa X11
OpenGL version string: 1.2 Mesa 3.4
OpenGL extensions:
GL_ARB_multitexture, GL_ARB_texture_cube_map, GL_ARB_tranpose_matrix,
GL_EXT_abgr, GL_EXT_blend_color, GL_EXT_blend_func_separate,
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_histogram,
GL_EXT_packed_pixels, GL_EXT_paletted_texture, GL_EXT_point_parameters,
GL_EXT_polygon_offset, GL_EXT_rescale_normal,
GL_EXT_shared_texture_palette, GL_EXT_stencil_wrap, GL_EXT_texture3D,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_object,
GL_EXT_texture_lod_bias, GL_EXT_vertex_array, GL_HP_occlusion_test,
GL_INGR_blend_func_separate, GL_MESA_window_pos, GL_MESA_resize_buffers,
GL_NV_texgen_reflection, GL_PGI_misc_hints, GL_SGI_color_matrix,
GL_SGI_color_table, GL_SGIS_pixel_texture, GL_SGIS_texture_edge_clamp,
GL_SGIX_pixel_texture
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x25 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x29 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 16 0 0 None
--
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-09 2:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 22:45 Michael D. Crawford [this message]
2001-01-09 16:17 ` DRI doesn't work on 2.4.0 but does on prerelease-ac5 Ragnar Hojland Espinosa
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 13:02 Gareth Hughes
2001-01-10 4:21 Bill Crawford
2001-01-10 4:37 ` Alan Cox
2001-01-10 5:18 ` Alan Olsen
2001-01-08 18:35 Michael D. Crawford
2001-01-08 22:06 ` Bill Nottingham
2001-01-08 22:55 ` khromy
2001-01-06 23:20 Michael D. Crawford
2001-01-07 3:30 ` Alan Olsen
2001-01-07 17:55 ` Dax Kelson
2001-01-07 19:11 ` Jeff Hartmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A5A42F5.648BE730@goingware.com \
--to=crawford@goingware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=newbie@xfree86.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox