Page 1 of 8 123 ... LastLast
Results 1 to 10 of 72

Thread: Broadcom Open-Sources VideoCore IV 3D Graphics Stack

  1. #1
    Join Date
    Jan 2007
    Posts
    14,658

    Default Broadcom Open-Sources VideoCore IV 3D Graphics Stack

    Phoronix: Broadcom Open-Sources VideoCore IV 3D Graphics Stack

    In celebrating two years that Raspberry Pi has been around, Eben Upton has announced today that they are open-sourcing their OpenGL ES 1.1/2.0 graphics stack for the Broadcom VideoCore IV 3D graphics subsystem and it will help the Raspberry Pi with having a truly free graphics stack...

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

  2. #2
    Join Date
    Feb 2013
    Posts
    59

    Default

    wow, this is pretty amazing. It is a shame this is an old slow gpu though. If broadcom released a competitive videocore v with support for decoding vp9/h265, opencl etc then it would be more useful but it is good news for raspberry pi owners.

  3. #3
    Join Date
    Jul 2011
    Posts
    74

    Default Great news!

    Now, getting a Raspberry Pi is actually worth it

  4. #4
    Join Date
    Sep 2009
    Location
    Edinburgh, UK
    Posts
    53

    Default

    Quote Originally Posted by sandy8925 View Post
    Now, getting a Raspberry Pi is actually worth it
    There is some analysis here.
    http://www.freelists.org/post/raspi-...ook-QPU-docs,1

    The docs seem very useful but there are some licensing issue and some gaps as well.

    Nevertheless, it is very good news for RPi owners.

  5. #5
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    910

    Default

    This is fantastic news, indeed!

    In particular, as it comes quite unexpected.

  6. #6
    Join Date
    Jul 2013
    Posts
    204

    Default

    Its amazing how messy the code seems after being used to looking at Mesa's.

    Something interesting a stumbled across was this in the glsl compiler

    /*
    detect uses of reserved keywords (anything from the list, or anything containing '__')
    */

    if ((type >= ASM && type <= USING) || (type == IDENTIFIER && strstr(data.s, "__")))
    glsl_compile_error(ERROR_LEXER_PARSER, 3, g_LineNumber, NULL);

    This is the same issue that was affecting Metro running on Mesa that was fixed recently. Looks like there are others who are abiding by the more strict definition.

  7. #7
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    910

    Default DSI displays finally usable?

    BTW, does that mean we can eventually make use of the DSI port (for LCD displays)?
    AFAIK this was not possible so far as each DSI display needs a dedicated bit of driver code.

  8. #8
    Join Date
    Aug 2011
    Posts
    516

    Default

    Quote Originally Posted by tarceri View Post
    Its amazing how messy the code seems after being used to looking at Mesa's.

    Something interesting a stumbled across was this in the glsl compiler

    /*
    detect uses of reserved keywords (anything from the list, or anything containing '__')
    */

    if ((type >= ASM && type <= USING) || (type == IDENTIFIER && strstr(data.s, "__")))
    glsl_compile_error(ERROR_LEXER_PARSER, 3, g_LineNumber, NULL);

    This is the same issue that was affecting Metro running on Mesa that was fixed recently. Looks like there are others who are abiding by the more strict definition.
    As always, thanks for your work on Mesa Timothy! Looking forward to your next crowd funding

    On another note, is someone able to evaluate already if these docs would facilitate the creation of a Gallium3D driver for VideoCore?

  9. #9
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,072

    Default

    Broadcom saw the light. Now the question is is it the train.

  10. #10
    Join Date
    Nov 2012
    Location
    France
    Posts
    566

    Default

    Quote Originally Posted by curaga View Post
    Broadcom saw the light. Now the question is is it the train.
    Broadcom releasing the source code of something is more like "seeing the pretty lights of the community's BFG", they always get flamed around for doing it wrong...

Posting Permissions

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