Page 18 of 19 FirstFirst ... 816171819 LastLast
Results 171 to 180 of 184

Thread: Future of ATI Linux drivers

  1. #171
    Join Date
    Jun 2010
    Posts
    38

    Default

    Quote Originally Posted by Hans View Post
    Okay what changes do you want to see, if I may ask? Better 2d performance will arrive with fglrx 10.6 apparently.
    I've been waiting for fix for this: http://www.youtube.com/watch?v=N9Aw68eN69o - for the last 3 years, so i finally decided to make a topic about it...

  2. #172
    Join Date
    Apr 2010
    Posts
    141

    Default

    Quote Originally Posted by Vii7 View Post
    I've been waiting for fix for this: http://www.youtube.com/watch?v=N9Aw68eN69o - for the last 3 years, so i finally decided to make a topic about it...
    Lets continue this discussion in private messages :-)

  3. #173
    Join Date
    Jun 2010
    Posts
    61

    Default

    I'm suffering from the same exact issue. Tearing when moving windows, browsing pages, watching videos, even when Compiz is turned off.

    I really don't know what to do. I am so frustrated. Extremely frustrated. I'm going to tons of forums posting my problems with my ATI HD5850 card in Linux. It's been past my return window and I'm stuck with the card, I wish I bought an NVidia.

  4. #174
    Join Date
    Jun 2010
    Posts
    38

    Default

    Not compiz related, but VSync. That's why I disabled effects when doing that video, to show that it's not compiz related. Had this problem with any FGLRX i tried for the last 3 years. Just recently, since Open Drivers with support for my card I can finally use my ATi card with Linux, at least at basic functionality. Whit Open Source drivers works fine with all compiz effects applied and that cause it's capable of using VSync just right (it's synked with my monitor refresh rate all the time). And all this by default - I didn't had to do a single thing, yet with FGLRX I knocked on many doors...

  5. #175
    Join Date
    May 2010
    Posts
    684

    Default

    Quote Originally Posted by Vii7 View Post
    Not compiz related, but VSync. That's why I disabled effects when doing that video, to show that it's not compiz related. Had this problem with any FGLRX i tried for the last 3 years. Just recently, since Open Drivers with support for my card I can finally use my ATi card with Linux, at least at basic functionality. Whit Open Source drivers works fine with all compiz effects applied and that cause it's capable of using VSync just right (it's synked with my monitor refresh rate all the time). And all this by default - I didn't had to do a single thing, yet with FGLRX I knocked on many doors...
    Yeah I agree this is one of my biggest issues with fglrx.

  6. #176
    Join Date
    Jan 2009
    Posts
    615

    Default

    Quote Originally Posted by barbarbaron View Post
    2. OpenGL extensions supported by the latest intel drivers is much more than other opensource stacks:

    GL_ARB_copy_buffer, GL_ARB_depth_texture, GL_ARB_depth_clamp,
    GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex,
    GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program,
    GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader,
    GL_ARB_framebuffer_object, GL_ARB_half_float_pixel,
    GL_ARB_half_float_vertex, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object,
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex,
    GL_ARB_seamless_cube_map, GL_ARB_shader_objects,
    GL_ARB_shading_language_100, GL_ARB_shading_language_120, GL_ARB_shadow,
    GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
    GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle,
    GL_ARB_transpose_matrix, GL_ARB_vertex_array_bgra,
    GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object,
    GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos,
    GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
    GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
    GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
    GL_EXT_cull_vertex, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture,
    GL_EXT_draw_buffers2, GL_EXT_draw_range_elements, GL_EXT_framebuffer_blit,
    GL_EXT_framebuffer_object, GL_EXT_fog_coord,
    GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays,
    GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels,
    GL_EXT_pixel_buffer_object, GL_EXT_point_parameters,
    GL_EXT_polygon_offset, GL_EXT_provoking_vertex, GL_EXT_rescale_normal,
    GL_EXT_secondary_color, GL_EXT_separate_specular_color,
    GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap,
    GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D,
    GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map,
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add,
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias,
    GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB,
    GL_EXT_texture_swizzle, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra,
    GL_3DFX_texture_compression_FXT1, GL_APPLE_client_storage,
    GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object,
    GL_APPLE_object_purgeable, GL_ATI_blend_equation_separate,
    GL_ATI_envmap_bumpmap, GL_ATI_texture_env_combine3,
    GL_ATI_separate_stencil, GL_IBM_multimode_draw_arrays,
    GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat,
    GL_INGR_blend_func_separate, GL_MESA_pack_invert,
    GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, GL_MESA_window_pos,
    GL_NV_blend_square, GL_NV_depth_clamp, GL_NV_light_max_exponent,
    GL_NV_packed_depth_stencil, GL_NV_texture_env_combine4,
    GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program,
    GL_NV_vertex_program1_1, GL_OES_read_format, GL_SGIS_generate_mipmap,
    GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
    GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays, GL_OES_EGL_image

    Just compare it...
    I wouldn't say much more, but if you wanna compare, let's compare.

    The extensions Intel has that we decided not to support in Gallium:
    * GL_EXT_cull_vertex
    * GL_3DFX_texture_compression_FXT1
    * GL_NV_vertex_program
    * GL_NV_vertex_program1_1

    The extensions Intel has that r300 hw doesn't and cannot support:
    * GL_ARB_depth_clamp
    * GL_ARB_seamless_cube_map
    * GL_EXT_draw_buffers2
    * GL_NV_depth_clamp

    The extensions Intel has that we are missing in r300g:
    * GL_ARB_draw_elements_base_vertex (I have patches)
    * GL_ARB_fragment_program_shadow (it's on my todo, should be easy)
    * GL_ARB_half_float_pixel (useless without float textures anyway)
    * GL_ARB_sync (needs some work in st/mesa)
    * GL_APPLE_client_storage (huh?)
    * GL_ATI_envmap_bumpmap (I'll see what I can do)
    * GL_MESA_texture_signed_rgba (useless, app devs use GL_EXT_texture_snorm instead, which is not in Mesa)

    The first 4 on the list above are the only ones I consider important.

    The extensions r300g has that Intel has not:
    * GL_EXT_framebuffer_multisample
    * GL_EXT_texture_mirror_clamp
    * GL_ATI_texture_mirror_once
    * GL_NV_conditional_render
    * GL_SGI_color_matrix
    * GL_S3_s3tc

  7. #177
    Join Date
    Jan 2009
    Posts
    291

    Default

    Wierd... I have *never* seen that issue and I have video cards that I use personally ranging from a mach64 card, Nvidia geforce2 400 MX, and a radeon 4200... and I have uses quite a few cards in other PCs even a few framebuffers in sun hardware :-) ... and never seen it.

    Given that I have used open and closed drivers and practically every combination of window manager imaginable on my radeon and nvidia hardware .. I suspect that it is a hardware specific problem.


    I have seen lack cuased by faulty drivers or missing drivers that would cause lag and sluggishness but never tearing of that level.

  8. #178
    Join Date
    May 2010
    Posts
    684

    Default

    Quote Originally Posted by cb88 View Post
    Wierd... I have *never* seen that issue and I have video cards that I use personally ranging from a mach64 card, Nvidia geforce2 400 MX, and a radeon 4200... and I have uses quite a few cards in other PCs even a few framebuffers in sun hardware :-) ... and never seen it.

    Given that I have used open and closed drivers and practically every combination of window manager imaginable on my radeon and nvidia hardware .. I suspect that it is a hardware specific problem.


    I have seen lack cuased by faulty drivers or missing drivers that would cause lag and sluggishness but never tearing of that level.
    Every single ati card I have ever used gets tearing in compiz using fglrx. It is impossible right now for vsync and to work with compiz with fglrx on ANY ati card. You must just not notice it.

  9. #179
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by marek View Post
    I wouldn't say much more, but if you wanna compare, let's compare.

    The extensions Intel has that we decided not to support in Gallium:
    * GL_EXT_cull_vertex
    * GL_3DFX_texture_compression_FXT1
    * GL_NV_vertex_program
    * GL_NV_vertex_program1_1

    The extensions Intel has that r300 hw doesn't and cannot support:
    * GL_ARB_depth_clamp
    * GL_ARB_seamless_cube_map
    * GL_EXT_draw_buffers2
    * GL_NV_depth_clamp

    The extensions Intel has that we are missing in r300g:
    * GL_ARB_draw_elements_base_vertex (I have patches)
    * GL_ARB_fragment_program_shadow (it's on my todo, should be easy)
    * GL_ARB_half_float_pixel (useless without float textures anyway)
    * GL_ARB_sync (needs some work in st/mesa)
    * GL_APPLE_client_storage (huh?)
    * GL_ATI_envmap_bumpmap (I'll see what I can do)
    * GL_MESA_texture_signed_rgba (useless, app devs use GL_EXT_texture_snorm instead, which is not in Mesa)

    The first 4 on the list above are the only ones I consider important.

    The extensions r300g has that Intel has not:
    * GL_EXT_framebuffer_multisample
    * GL_EXT_texture_mirror_clamp
    * GL_ATI_texture_mirror_once
    * GL_NV_conditional_render
    * GL_SGI_color_matrix
    * GL_S3_s3tc
    yes r300 is really nice... Trumps UP for that

    but...

    only "* GL_ARB_" care!

    The extensions Intel has that we decided not to support in Gallium:
    ...... "No * GL_ARB_ found here"

    The extensions Intel has that r300 hw doesn't and cannot support:
    * GL_ARB_depth_clamp
    * GL_ARB_seamless_cube_map


    The extensions Intel has that we are missing in r300g:
    * GL_ARB_draw_elements_base_vertex (I have patches)
    * GL_ARB_fragment_program_shadow (it's on my todo, should be easy)
    * GL_ARB_half_float_pixel (useless without float textures anyway)
    * GL_ARB_sync (needs some work in st/mesa)


    The extensions r300g has that Intel has not:
    ...... "No * GL_ARB_ found here"



    6:0 for intel for supporting official kronos OpenGL GL_ARB_ extensions!

    but I'm sure R600g will beat intel in the future ;-)

  10. #180
    Join Date
    Jan 2009
    Posts
    615

    Default

    All extensions that have become part of the official OpenGL specification are important, including some EXT, ATI, and NV extensions (e.g. GL_EXT_draw_buffers2 and GL_NV_conditional_render, which are incorporated in OpenGL 3.0).

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •