Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: OpenCL Gallium3D State Tracker Merged Into Mesa

  1. #11
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    764

    Default

    Quote Originally Posted by log0 View Post
    What about Intel? Are they going to implement their own OpenCL stack as they seem to not be interested in Gallium3D?
    I i understand it correct CLover doesn't depend on Gallium3D. E.g. for the new AMD cards you get direct the LLVM Code.

    BTW: On the mailing list are now the OpenCL patches for r600g.

  2. #12
    Join Date
    Jul 2010
    Posts
    541

    Default

    Quote Originally Posted by Nille View Post
    I i understand it correct CLover doesn't depend on Gallium3D. E.g. for the new AMD cards you get direct the LLVM Code.

    BTW: On the mailing list are now the OpenCL patches for r600g.
    But the title of the article is "OpenCL Gallium3D State Tracker Merged Into Mesa"

    And then there is "mesa/clover - OpenCL implementation on top of Gallium."

    How is OpenCL implemented in Mesa?

  3. #13
    Join Date
    May 2011
    Posts
    37

    Default

    Quote Originally Posted by Nille View Post
    I i understand it correct CLover doesn't depend on Gallium3D. E.g. for the new AMD cards you get direct the LLVM Code.

    BTW: On the mailing list are now the OpenCL patches for r600g.
    Clover still uses the Gallium API to communicate with the drivers even when it is passing LLVM code to r600g.

  4. #14
    Join Date
    Dec 2007
    Posts
    2,404

    Default

    Quote Originally Posted by 89c51 View Post
    Just a question.

    Is there still fragmentation in the state trackers. I mean do we still need differenst state trackers for nouveau and different for radeon???
    There aren't different state trackers for different chips. There are existing state trackers for video, OpenGL, OpenVG, etc. as welll as OpenCL now. However, each hw target (GPU or CPU) needs asic specific code to translate into asic specific commands.

  5. #15
    Join Date
    Jan 2009
    Posts
    1,762

    Default

    Quote Originally Posted by agd5f View Post
    There aren't different state trackers for different chips. There are existing state trackers for video, OpenGL, OpenVG, etc. as welll as OpenCL now. However, each hw target (GPU or CPU) needs asic specific code to translate into asic specific commands.
    thanks for the answer and sorry for the misunderstanding from my part. i was under the impression that the HW specific code had quite a lot to do with the state trackers.

  6. #16
    Join Date
    Mar 2012
    Posts
    9

    Default

    Congratulations to all people involved in this big milestone!

Posting Permissions

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