Re: [Mesa3d-dev] Updated i915tex
On Wed, 2008-03-12 at 15:34 +0100, Johannes Engel wrote: Thomas Hellström wrote: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Hi, Thomas! I just tested the new code. It is *very* fast compared to the code from master branch on my 945GM. But as well as using master there is one thing I do not quite understand: glxinfo's output shows for example GLX_EXT_texture_from_pixmap for both server and client but not in the GLX extensions section. That's not specific to this driver: Without DRI2, GLX_EXT_texture_from_pixmap requires setting the LIBGL_ALWAYS_INDIRECT=1 environment variable. By now, every half-decent distro should use compiz wrapper scripts to handle this automagically. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Updated i915tex
On Wed, 2008-03-12 at 12:51 +0100, Thomas Hellström wrote: Thomas Hellström wrote: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Should be i915tex_branch. Hi, that's a good new ! In this i915tex_branch just change the i915 dri code ? isn't it ? if yes, IHMO, this i915tex_branch just should have the i915tex directory and should be compiled with the rest mesa_7_0 branch. Simply don't sound good idea have a copy of all Mesa source , things should been tested with latest mesa_7_0 branch. For example last 3 commits in mesa_7_0 branch, was not reflected on i915tex_branch. or simply put the code on i915tex dir, unless we care with xf86-video-intel-2.1-branch, which have 6 months old and which is the only one that may use this code. On makefile ( as it now) -LIBNAME = i915tex_dri.so +LIBNAME = i915_dri.so and on configs/linux-dri we have to choose between i915tex and old i915. -DRI_DIRS = i810 i915tex i915 i965 mach64 mga r128 r200 r300 radeon s3v +DRI_DIRS = i810 i915tex i965 mach64 mga r128 r200 r300 radeon s3v /Thomas -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Updated i915tex
Thomas Hellström wrote: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Should be i915tex_branch. /Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Updated i915tex
Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. The reasons for doing this are the following. 1) We plan on reusing the TTM interaction for upcoming Gallium drivers. 2) It's important for us that the TTM functionality we use for this driver (user-space buffer pools) remains intact, hence it can be used for testing DRM TTM regressions. 3) The driver provides an easily accessible performance reference for TTM performance experiments with newer drivers: * For measuring buffer-handling efficiency, good benchmarks are the CPU-bound ones: gears, minimized until it becomes completely CPU-bound, and ipers. (After of course disabling damage reporting which tends to be a CPU hog). * For measuring CPU caching effects, texdown is a good benchmark, with and without subteximage. The driver still has some rough edges. The vblank code has been disabled, and due to the simplicity of the user-space buffer allocator, the memory usage for batch-buffers is higher than optimal. /Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] Updated i915tex
Thomas Hellström schrieb: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Hi, Thomas! I just tested the new code. It is *very* fast compared to the code from master branch on my 945GM. But as well as using master there is one thing I do not quite understand: glxinfo's output shows for example GLX_EXT_texture_from_pixmap for both server and client but not in the GLX extensions section. If I disable drm it appears at all of the three sections: server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) 945GM 20061102 x86/MMX/SSE2 OpenGL version string: 1.3 Mesa 7.0.3-rc2 What's that about? Greetings, Johannes - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] Updated i915tex
Thomas Hellström wrote: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Hi, Thomas! I just tested the new code. It is *very* fast compared to the code from master branch on my 945GM. But as well as using master there is one thing I do not quite understand: glxinfo's output shows for example GLX_EXT_texture_from_pixmap for both server and client but not in the GLX extensions section. If I disable drm it appears at all of the three sections: server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) 945GM 20061102 x86/MMX/SSE2 OpenGL version string: 1.3 Mesa 7.0.3-rc2 What's that about? Greetings, Johannes - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
