Page 1 of 4 123 ... LastLast
Results 1 to 10 of 36

Thread: Intel Aims For Open-Source OpenGL 3.0 Driver By Year's End

  1. #1
    Join Date
    Jan 2007
    Posts
    15,126

    Default Intel Aims For Open-Source OpenGL 3.0 Driver By Year's End

    Phoronix: Intel Aims For Open-Source OpenGL 3.0 Driver By Year's End

    There's more good news out of the 2011 X.Org Developers' Conference in Chicago. Besides the big news that the S3TC patent might be invalid, PathScale has a working OpenCL compute stack, and other events, here's something very exciting: Intel really expects to have working OpenGL 3.0 support in Mesa for hardware drivers by the end of this calendar year!..

    http://www.phoronix.com/vr.php?view=OTkxMg

  2. #2
    Join Date
    Jan 2009
    Posts
    1,709

    Default

    i would be happier if they were aiming for a G3D driver by year's end

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

    Default

    openGL3 means the floating point HDR graphic patents are invalid to ?

  4. #4
    Join Date
    Jun 2011
    Posts
    32

    Default

    Will this cover the G45 (4500MHD) chips? I still don't have OpenGL2 I think... btw: what's the code name of the G45? It's not Sandy Bridge is it?

  5. #5
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    970

    Default

    Quote Originally Posted by elmariachi View Post
    Will this cover the G45 (4500MHD) chips?
    Probably like the H264 VAAPI G45 support
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

  6. #6
    Join Date
    Nov 2010
    Location
    Stockholm, Sweden
    Posts
    413

    Default

    I just want to spread love all over right now! Michael, you make me so happy! I work in a med-tech-company with visualization using OpenGL (which I prefer since I'm a Linux nerd), and we can't use anything more modern than OpenGL2.1 since our code is often run on virtualized machines (Xen). The virtualization means that there is only a software driver, so we depend heavily on Mesa (I think at least!).
    When these changes are released, we can finally start looking at porting everything to OpenGL 3, at least bit by bit.

  7. #7
    Join Date
    Jun 2011
    Posts
    32

    Default

    Quote Originally Posted by darkbasic View Post
    Probably like the H264 VAAPI G45 support
    It works for me!

  8. #8
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    970

    Default

    Quote Originally Posted by elmariachi View Post
    It works for me!
    Faster than a slideshow? Can you please post your experience there: http://phoronix.com/forums/showthrea...vailable/page4
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

  9. #9
    Join Date
    Nov 2007
    Posts
    1,024

    Default

    Quote Originally Posted by Azpegath View Post
    I just want to spread love all over right now! Michael, you make me so happy! I work in a med-tech-company with visualization using OpenGL (which I prefer since I'm a Linux nerd), and we can't use anything more modern than OpenGL2.1 since our code is often run on virtualized machines (Xen). The virtualization means that there is only a software driver, so we depend heavily on Mesa (I think at least!).
    When these changes are released, we can finally start looking at porting everything to OpenGL 3, at least bit by bit.
    For what it's worth, it's not until OpenGL 3.1 through 3.3 that you start seeing any real utility out of "porting" to GL3. The idea of the core/compatibility profiles doesn't even exist until 3.1 iirc, and all 3.0 did was make a few extensions core. It was pretty worthless, hence all the immense outrage from GL developers when Khronos released it in 2008. The really cool features of the GL 3.x series didn't show up until GL 3.2, and the performance of the API isn't even capable of achieving parity with D3D 10 until GL 3.3. Same goes with GL 4.x, where D3D 11 still has features that GL doesn't (despite all the nonsense of various articles and announcements claiming that 4.0 had feature parity with D3D 11).

    We need GL 3.0 to get to GL 3.3, but don't expect the world to become a magical place when Mesa supports GL 3.0. It'll basically just mean that floating point textures are supported and integers in shaders are working properly. The first already works but is disabled due to legal issues, and the latter should be done soon, which may be all that Ian meant when he said that the Intel driver would support GL 3. That is, he might have meant the driver supports GLSL 1.30 rather than the whole GL 3.0 API itself.

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

    Default

    Quote Originally Posted by elanthis View Post
    For what it's worth, it's not until OpenGL 3.1 through 3.3 that you start seeing any real utility out of "porting" to GL3. The idea of the core/compatibility profiles doesn't even exist until 3.1 iirc, and all 3.0 did was make a few extensions core. It was pretty worthless, hence all the immense outrage from GL developers when Khronos released it in 2008. The really cool features of the GL 3.x series didn't show up until GL 3.2, and the performance of the API isn't even capable of achieving parity with D3D 10 until GL 3.3. Same goes with GL 4.x, where D3D 11 still has features that GL doesn't (despite all the nonsense of various articles and announcements claiming that 4.0 had feature parity with D3D 11).

    We need GL 3.0 to get to GL 3.3, but don't expect the world to become a magical place when Mesa supports GL 3.0. It'll basically just mean that floating point textures are supported and integers in shaders are working properly. The first already works but is disabled due to legal issues, and the latter should be done soon, which may be all that Ian meant when he said that the Intel driver would support GL 3. That is, he might have meant the driver supports GLSL 1.30 rather than the whole GL 3.0 API itself.
    yes right.... wine for example supports openGL2.1 or OpenGL3.2+ because the wine openGL extansions are in 3.2+ and not in openGL3.0...

    on a openGL3.0 driver wine fallback to 2.1 renderer..

Posting Permissions

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