Announcement

Collapse
No announcement yet.

Intel Sandy Bridge Linux Graphics? It's A Challenge

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • smitty3268
    replied
    Originally posted by mattst88 View Post
    I don't guess there are any workarounds other than an extra frame every 40* seconds?

    * (24 frames/sec - 23.976 frames/sec) * 40 sec = ~1 frame.
    According to that Anandtech article, Intel did come up with a workaround in their drivers that can change the framerate to 23.970. That comes out to 1 frame every 160 seconds.

    Leave a comment:


  • popper
    replied
    Originally posted by deanjo View Post
    It is not a "programming error". It is a hardware limitation.
    well i did put a there ;D
    but still... is it a case of a control 'bit' being set/unset on or off wrongly, or a 'real hardware errata' that they know about and have not fixed, did anyone bother to report this known error on [email protected] for instance ?

    Leave a comment:


  • deanjo
    replied
    Originally posted by mattst88 View Post
    Indeed.

    The difficulty of that workaround is that one has to spend more money on an otherwise unnecessary graphics card that would replace the otherwise OK integrated graphics provided on Sandy Bridge CPUs.
    A $30 dollar graphics card is a small price to pay.

    Leave a comment:


  • mattst88
    replied
    Indeed.

    The difficulty of that workaround is that one has to spend more money on an otherwise unnecessary graphics card that would replace the otherwise OK integrated graphics provided on Sandy Bridge CPUs.

    Leave a comment:


  • deanjo
    replied
    Originally posted by mattst88 View Post
    I don't guess there are any workarounds other than an extra frame every 40* seconds?

    * (24 frames/sec - 23.976 frames/sec) * 40 sec = ~1 frame.
    Sure there is, get an nvidia.

    Leave a comment:


  • mattst88
    replied
    Originally posted by deanjo View Post
    Yes, that is the case. Intel has had a loooooooooooong time to fix that issue with their hardware.
    I don't guess there are any workarounds other than an extra frame every 40* seconds?

    * (24 frames/sec - 23.976 frames/sec) * 40 sec = ~1 frame.

    Leave a comment:


  • deanjo
    replied
    Originally posted by mattst88 View Post
    To be clear, a hardware problem that has existed since Clarkdale is preventing accelerated playback of 23.97 FPS video without stuttering on Sandy Bridge's graphics?
    Yes, that is the case. Intel has had a loooooooooooong time to fix that issue with their hardware.

    Leave a comment:


  • deanjo
    replied
    Originally posted by popper View Post
    No..i think its just a lack of time before they fix that programming error
    It is not a "programming error". It is a hardware limitation.

    Leave a comment:


  • mattst88
    replied
    To be clear, a hardware problem that has existed since Clarkdale is preventing accelerated playback of 23.97 FPS video without stuttering on Sandy Bridge's graphics?

    Leave a comment:


  • saski
    replied
    Currently Gallium sufferes from vaious bottlenecks hurting performance especially on weaker IGPs utilizing shared memory. For instance the mobile Radeon HD4250 does much less FPS in OpenGL games than with the classic mesa stack. With faster GPUs is seems to be the opposite in some cases. My best guess ist that Intel avoids Gallium at this time to maximize the performance of their IGPs under Linux - just my two cents

    - saski

    Leave a comment:

Working...
X