Announcement

Collapse
No announcement yet.

A Fresh Look At The AMD Radeon Gallium3D Performance

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

  • #16
    Originally posted by EvilTwin View Post
    i just searched for documentation of profiles or at least some profiles to understand them
    but i just found "~./phoronix-test-suite/pts-core/definitions/test-profile.xml"

    is there some kind of tutorial?
    Within PTS 1.x/2.x or PTS 3.0 (it's temporarily gone in Git) within documentations/ there should be a "writing your first test profile" HTML guide. But it literally is quite simple, the most effective guide is just looking at an existing test profile such as that for padman or doom3. From there you can simply copy and paste and then alter a bash script or XML file. I'm also always in IRC and more than happy to guide any motivated individuals... About 5 minutes of teaching and you can easily write your own test profile for almost any app.
    Michael Larabel
    http://www.michaellarabel.com/

    Comment


    • #17
      xorg.conf

      Dear Phoronix, can you share your xorg.conf for Ati R600 drivers and other tweaks in config files if need it, pleas? I'd like to try it myselft on non-production PC with Xorg edgers PPA and linux 3 kernel debs from Ubuntu PPA.

      Thank you

      Comment


      • #18
        Originally posted by TomBoyTom View Post
        Dear Phoronix, can you share your xorg.conf for Ati R600 drivers and other tweaks in config files if need it, pleas? I'd like to try it myselft on non-production PC with Xorg edgers PPA and linux 3 kernel debs from Ubuntu PPA.

        Thank you
        don't use Xorg edgers PPA or ubuntu PPA if possible, compile your own kernel to get rt functions online (it helps a bit) and compile mesa/drm/ddx from sources with -O3 (it helps a bit more in some scenarios). Beside compiling mesa from sources you can get st3c and float textures + other goodies missing in xorg edgers

        Comment


        • #19
          Originally posted by jrch2k8 View Post
          don't use Xorg edgers PPA or ubuntu PPA if possible, compile your own kernel to get rt functions online (it helps a bit) and compile mesa/drm/ddx from sources with -O3 (it helps a bit more in some scenarios). Beside compiling mesa from sources you can get st3c and float textures + other goodies missing in xorg edgers

          The options used are just "SwapbuffersWait" "false" and "ColorTiling" "true" in xorg.conf. And you can add S3TC support with any release/repositry of Mesa. (Float textures does need a recompile. Dunno if any of the Ubuntu repos enable it.)

          As for adding optimisations or using anything other than the default kernel your distro provides, I think a [citation needed] should be used...

          Comment


          • #20
            https://bugs.freedesktop.org/show_bug.cgi?id=37168 is fixed, so now I can use r600g full-time Awesome!

            Comment


            • #21
              although the gallium drivers are doing amazingly well, why is this project still being continued? isn't amd going to make their video drivers open source anyway?

              Comment


              • #22
                Originally posted by schmidtbag View Post
                although the gallium drivers are doing amazingly well, why is this project still being continued? isn't amd going to make their video drivers open source anyway?
                You mean fglrx, the proprietary drivers? No, absolutely not. They have no plans to do that. I'm 99.999999999% sure. If you think they have plans to open source Catalyst / fglrx, I need an authoritative citation.

                The gallium3d drivers are AMD's open source video driver effort.

                Comment


                • #23
                  Originally posted by allquixotic View Post
                  You mean fglrx, the proprietary drivers? No, absolutely not. They have no plans to do that. I'm 99.999999999% sure. If you think they have plans to open source Catalyst / fglrx, I need an authoritative citation.

                  The gallium3d drivers are AMD's open source video driver effort.
                  oooo ok that makes more sense now. lol so now i flip around my question - if amd is helping contribute to the open source drivers, why make proprietary ones? its not like they have much to hide.

                  Comment


                  • #24
                    Originally posted by schmidtbag View Post
                    oooo ok that makes more sense now. lol so now i flip around my question - if amd is helping contribute to the open source drivers, why make proprietary ones? its not like they have much to hide.
                    Several reasons:

                    *For the proprietary Catalyst drivers, they share 90% of the code between their Windows drivers and the Linux drivers.

                    *They compete the most with Nvidia on the performance of the Windows drivers (for gaming and stuff).

                    *There are secret algorithms and patented optimization technologies in fglrx (this is publicly unsubstantiated, but I'm pretty confident of the truth of this) that they aren't willing to expose to the general public. They call this their "Intellectual Property".

                    *They are willing to disclose most of the hardware details about their cards to enable us to write good open source graphics drivers, but there are still a few things that they won't disclose. Those things get used to their full potential in Catalyst / fglrx. Example: UVD2

                    Comment


                    • #25
                      Originally posted by schmidtbag View Post
                      oooo ok that makes more sense now. lol so now i flip around my question - if amd is helping contribute to the open source drivers, why make proprietary ones? its not like they have much to hide.
                      I think this is the 26th time I've answered this question

                      Proprietary Linux drivers allow code to be shared across OSes, including OSes which require robust DRM and the associated secrecy. Proprietary code-shared drivers allow PC hardware vendors to bring more features and performance to OSes with smaller market shares than they could if all the code had to be developed for (and supported by the sales onto) a single OS.

                      If a hardware vendor was writing a driver exclusively for Linux/BSD/Solaris etc.. there's a good chance it would be open source. If the driver shares code with other OSes with hard DRM requirements, then more of the code has to be kept secret and distributing most of the code in binary form ends up as the only practical solution.
                      Last edited by bridgman; 06-10-2011, 07:25 PM.

                      Comment


                      • #26
                        Originally posted by allquixotic View Post
                        If you think they have plans to open source Catalyst / fglrx, I need an authoritative citation.
                        Me too

                        Comment


                        • #27
                          the oss driver support is very basic when you compare opengl features. xvba nobody really needs without full h264 l5.1 support. if you want to play a game (or at least look at the heaven demo) with tesselation then you are lost without binary driver. it is fun to test oss drivers, with my intel atom netbook with gma 945 even gl2benchmark runs correctly. fbo (test 4) does not work with snb and other oss drivers do not even show the reference pictures correctly. i really would like to see it running with every oss driver.

                          http://kanotix.com/files/hellfire/contrib/gl2benchmark/

                          runs with debian squeeze, use pbuilder or debuild -b for ubuntu or debian with newer openscenegraph. the build dep is just openscenegraph, should be available everywhere. the version does not matter. if you just do "./configure && make -j4" then you can start it from the dir using:

                          OSG_FILE_PATH=data src/gl2benchmark

                          Use cursor keys to try all 4 tests - if you want fun enable interactive mode If you want to package it for a non debian system just add a simple startup script like i added in debian/gl2benchmark.sh. really nice for some rendering tests - speed is not that important, but of course you can compare that too. i found a fglrx rendering issue (which was in the opengl code on win too) with that tool, fglrx needed 10 or 11 month to get a fix. btw. it is of course crossplattform, you can build it with any os where you install osg.
                          Last edited by Kano; 06-10-2011, 07:17 PM.

                          Comment


                          • #28
                            Originally posted by allquixotic View Post
                            https://bugs.freedesktop.org/show_bug.cgi?id=37168 is fixed, so now I can use r600g full-time Awesome!
                            me to ;-) hon runs well now on the radeon driver. by using oibaf's PPA

                            Comment


                            • #29
                              Originally posted by schmidtbag View Post
                              although the gallium drivers are doing amazingly well, why is this project still being continued? isn't amd going to make their video drivers open source anyway?
                              Catalyst isn't going anywhere. AMD is however supporting the development of the oss drivers by releasing (most of) the specs for their hardware.

                              Comment


                              • #30
                                Originally posted by bridgman View Post
                                including OSes which require robust DRM and the associated secrecy.
                                *snicker* and yet it is so easily defeated.

                                Comment

                                Working...
                                X