Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 43

Thread: R600 Gallium3D Can Now Do OpenGL 3.0, GLSL 1.30

  1. #11
    Join Date
    Jul 2011
    Posts
    44

    Thumbs up

    Wow! Congratulations and THANK YOU to everyone who made it possible!

    Better powersaving management and my 4200+6650 will be shine with opensource drivers.

  2. #12
    Join Date
    Sep 2008
    Posts
    989

    Default

    Can we please document all these various environment variables somewhere? As a driver tester I hate having to dig through the source to find these, and it's not every time that Michael documents which env vars he uses when he posts articles (sometimes he just says "a flag" and doesn't mention which one), and of course they aren't in any of the documentation.

    A better way would be to ship a /etc/mesa-debug.conf config file in /etc with a simple var=value format, but only ship and read from that file if mesa is compiled in debug mode (i.e. with debug symbols etc). Might need an option like --enable-debug-conf in configure. Then, ship a default mesa-debug.conf that briefly documents all possible settings but leave them commented out, so the user can easily uncomment and change them as desired.

    This method would also remove the need for the user to hack environment variables into the pipeline before starting X, because it seems that you might get strange behavior if some of your mesa-using programs are running with the flags, and some without. Especially e.g. tiling...

  3. #13
    Join Date
    Oct 2008
    Location
    Sweden
    Posts
    983

    Default

    It's pretty easy to find these: grep debug_get_bool_option *

    Anyway, going to all that trouble for something that's a, likely to disappear once these features are finished and b, only of interest to a very small number of people seems like a waste of time.

  4. #14
    Join Date
    Sep 2008
    Posts
    989

    Default

    Quote Originally Posted by whizse View Post
    It's pretty easy to find these: grep debug_get_bool_option *

    Anyway, going to all that trouble for something that's a, likely to disappear once these features are finished and b, only of interest to a very small number of people seems like a waste of time.
    Setting up the debug configuration infrastructure would be a one-time investment. Anyone who wants to write a debug option into their code afterwards would still be calling ONE function; it's just that the name of the function would be different from "debug_get_bool_option". Or maybe, heck, we could change the implementation of that function to DO exactly what I've proposed.

    Then of course they'd have to write something like this:

    #Enable GLSL 1.30 support on Radeon 2xxx or later
    #R600_GLSL130=1

    in the mesa-debug.conf.example file, but that would take about 3 seconds of a developer's valuable time Can't have that.

  5. #15
    Join Date
    Oct 2008
    Location
    Sweden
    Posts
    983

    Default

    There's already drirc for that.

  6. #16
    Join Date
    Jan 2009
    Posts
    1,591

    Default

    bridgman or anyone at AMD give this kid some money (lots of them preferably)


  7. #17
    Join Date
    Jun 2009
    Posts
    2,926

    Default

    It's working, w00t w00t!

    Thanks Marek and other devs!

  8. #18
    Join Date
    Dec 2011
    Posts
    38

    Question

    why use environment variable and not enable those features by default?

    it is patent issue again?

  9. #19
    Join Date
    Oct 2008
    Posts
    3,027

    Default

    Quote Originally Posted by unknown2 View Post
    why use environment variable and not enable those features by default?

    it is patent issue again?
    A dev commented here earlier:

    Quote Originally Posted by arlied
    The big items left are:

    EXT_transform_feedback needs upstream kernel patch, and it currently locks up on all R700 class hardware.

    cayman needs some more work to finish off a few integer opcodes (divide/mod).

    Its got 7620/7846 on piglit on my rv635 right now, a few of the remaining issues should be solved by Jerome's tiling work.
    Even after the drivers enable GL3 by default, it will still be disabled unless you enable the patented fp texture option - that's true of all the drivers, and it should be the only patented bit required.

  10. #20
    Join Date
    Mar 2008
    Location
    Istanbul
    Posts
    134

    Default

    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD RS780
    OpenGL version string: 2.1 Mesa 8.0-devel (git-f9f8ce3)
    Yes, Still 2.1 on RS780

    I also wonder that, if we could enable GPU acceleration at Firefox via layers.acceleration.force-enabled flag with full OpenGL3 support and have proper graphics??

Posting Permissions

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