Announcement

Collapse
No announcement yet.

R600g Geometry Shaders Come For R600/R700

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

  • #21
    Originally posted by MWisBest View Post
    Came here to read about improved support for older ATi GPUs, instead there was Sandy Bridge...
    Discussion about improved support for ATI/AMD GPUs is in the NVidia threads. This is an ATI/AMD thread, so discussion is about Intel.

    This should be obvious by now
    Test signature

    Comment


    • #22
      Originally posted by bridgman View Post
      Discussion about improved support for ATI/AMD GPUs is in the NVidia threads. This is an ATI/AMD thread, so discussion is about Intel.

      This should be obvious by now
      Hmm, this actually makes a reasonable degree of sense. Study on the derailment of threads on forums might be an interesting subject for a thesis in sociology; assuming one hasn't been written yet.

      Comment


      • #23
        My HD 4670 is still sufficient for lightweight games. No, it won't run Crysis.

        Maybe next big release I can skip Catalyst so xscreensaver can stop crashing?

        Comment


        • #24
          Originally posted by A Laggy Grunt View Post
          My HD 4670 is still sufficient for lightweight games. No, it won't run Crysis.

          Maybe next big release I can skip Catalyst so xscreensaver can stop crashing?
          My Radeon HD 4670 is already serving me very well with R600g, gaming included.

          Comment


          • #25
            Originally posted by A Laggy Grunt View Post
            My HD 4670 is still sufficient for lightweight games. No, it won't run Crysis.

            Maybe next big release I can skip Catalyst so xscreensaver can stop crashing?
            When I used my 4670, it ran Crysis just fine in Windows. My 6750 died last week, and I stuck that back in temporarily until I got my replacement 6850. I really didn't notice much of a difference. Unless you're one of those 1080P max settings gaming kinda guy, the 4670 would be an OK graphics card.

            How does it fair in Linux?

            Comment


            • #26
              I've tried to apply this patch to the latest mesa code from git, but it fails. :/

              Code:
              patching file src/gallium/drivers/r600/r600_asm.c
              Hunk #1 FAILED at 1535.
              1 out of 1 hunk FAILED -- saving rejects to file src/gallium/drivers/r600/r600_asm.c.rej
              patching file src/gallium/drivers/r600/r600_pipe.c
              Hunk #1 FAILED at 372.
              Hunk #2 FAILED at 458.
              2 out of 2 hunks FAILED -- saving rejects to file src/gallium/drivers/r600/r600_pipe.c.rej
              patching file src/gallium/drivers/r600/r600_pipe.h
              Hunk #1 succeeded at 159 (offset -1 lines).
              Hunk #2 succeeded at 546 (offset -20 lines).
              patching file src/gallium/drivers/r600/r600_shader.c
              Hunk #1 FAILED at 210.
              Hunk #2 succeeded at 181 with fuzz 2 (offset -39 lines).
              Hunk #3 FAILED at 909.
              Hunk #4 FAILED at 1232.
              Hunk #5 FAILED at 1552.
              Hunk #6 succeeded at 6122 (offset -178 lines).
              4 out of 6 hunks FAILED -- saving rejects to file src/gallium/drivers/r600/r600_shader.c.rej
              patching file src/gallium/drivers/r600/r600_state.c
              Hunk #1 succeeded at 2067 (offset 3 lines).
              Hunk #2 succeeded at 2119 (offset 3 lines).
              Hunk #3 succeeded at 2140 (offset 3 lines).
              Hunk #4 succeeded at 2326 (offset 3 lines).
              Hunk #5 succeeded at 2455 (offset 3 lines).
              Hunk #6 succeeded at 2467 (offset 3 lines).
              Hunk #7 succeeded at 2590 (offset 3 lines).
              Hunk #8 succeeded at 2611 (offset 3 lines).
              Hunk #9 succeeded at 2626 (offset 3 lines).
              Hunk #10 succeeded at 2805 (offset 3 lines).
              Hunk #11 succeeded at 2819 (offset 3 lines).
              Hunk #12 succeeded at 2829 (offset 3 lines).
              Hunk #13 succeeded at 3002 (offset 3 lines).
              Hunk #14 succeeded at 3452 (offset 3 lines).
              patching file src/gallium/drivers/r600/r600_state_common.c
              Hunk #1 FAILED at 1162.
              1 out of 1 hunk FAILED -- saving rejects to file src/gallium/drivers/r600/r600_state_common.c.rej
              patching file src/gallium/drivers/r600/r600d.h
              Hunk #1 succeeded at 200 (offset -1 lines).
              Hunk #2 succeeded at 1837 (offset -1 lines).
              Hunk #3 succeeded at 2353 (offset -1 lines).
              Hunk #4 succeeded at 2462 (offset -1 lines).
              Hunk #5 succeeded at 2908 (offset -1 lines).
              patch unexpectedly ends in middle of line
              Hunk #6 succeeded at 3333 with fuzz 1 (offset -1 lines).
              Anyone could help?

              Comment


              • #27
                Originally posted by pejakm View Post
                I've tried to apply this patch to the latest mesa code from git, but it fails. :/

                Code:
                patching file src/gallium/drivers/r600/r600_asm.c
                Hunk #1 FAILED at 1535.
                1 out of 1 hunk FAILED -- saving rejects to file src/gallium/drivers/r600/r600_asm.c.rej
                patching file src/gallium/drivers/r600/r600_pipe.c
                Hunk #1 FAILED at 372.
                Hunk #2 FAILED at 458.
                2 out of 2 hunks FAILED -- saving rejects to file src/gallium/drivers/r600/r600_pipe.c.rej
                patching file src/gallium/drivers/r600/r600_pipe.h
                Hunk #1 succeeded at 159 (offset -1 lines).
                Hunk #2 succeeded at 546 (offset -20 lines).
                patching file src/gallium/drivers/r600/r600_shader.c
                Hunk #1 FAILED at 210.
                Hunk #2 succeeded at 181 with fuzz 2 (offset -39 lines).
                Hunk #3 FAILED at 909.
                Hunk #4 FAILED at 1232.
                Hunk #5 FAILED at 1552.
                Hunk #6 succeeded at 6122 (offset -178 lines).
                4 out of 6 hunks FAILED -- saving rejects to file src/gallium/drivers/r600/r600_shader.c.rej
                patching file src/gallium/drivers/r600/r600_state.c
                Hunk #1 succeeded at 2067 (offset 3 lines).
                Hunk #2 succeeded at 2119 (offset 3 lines).
                Hunk #3 succeeded at 2140 (offset 3 lines).
                Hunk #4 succeeded at 2326 (offset 3 lines).
                Hunk #5 succeeded at 2455 (offset 3 lines).
                Hunk #6 succeeded at 2467 (offset 3 lines).
                Hunk #7 succeeded at 2590 (offset 3 lines).
                Hunk #8 succeeded at 2611 (offset 3 lines).
                Hunk #9 succeeded at 2626 (offset 3 lines).
                Hunk #10 succeeded at 2805 (offset 3 lines).
                Hunk #11 succeeded at 2819 (offset 3 lines).
                Hunk #12 succeeded at 2829 (offset 3 lines).
                Hunk #13 succeeded at 3002 (offset 3 lines).
                Hunk #14 succeeded at 3452 (offset 3 lines).
                patching file src/gallium/drivers/r600/r600_state_common.c
                Hunk #1 FAILED at 1162.
                1 out of 1 hunk FAILED -- saving rejects to file src/gallium/drivers/r600/r600_state_common.c.rej
                patching file src/gallium/drivers/r600/r600d.h
                Hunk #1 succeeded at 200 (offset -1 lines).
                Hunk #2 succeeded at 1837 (offset -1 lines).
                Hunk #3 succeeded at 2353 (offset -1 lines).
                Hunk #4 succeeded at 2462 (offset -1 lines).
                Hunk #5 succeeded at 2908 (offset -1 lines).
                patch unexpectedly ends in middle of line
                Hunk #6 succeeded at 3333 with fuzz 1 (offset -1 lines).
                Anyone could help?
                You can fetch Dave's git branch directly rather than using patches.

                Comment


                • #28
                  Originally posted by Dukenukemx View Post
                  When I used my 4670, it ran Crysis just fine in Windows. My 6750 died last week, and I stuck that back in temporarily until I got my replacement 6850. I really didn't notice much of a difference. Unless you're one of those 1080P max settings gaming kinda guy, the 4670 would be an OK graphics card.

                  How does it fair in Linux?
                  Performance-wise, well enough.

                  My biggest problem has been with xscreensaver+Catalyst. The small gripe is it won't show the password box to unlock your screen. The big one is it occasionally crashes X when you try to unlock your screen.

                  Wine has been... well, Wine. Lots of stuff works, lots of stuff doesn't. I write decently detailed reviews of app behavior on WineHQ, with the stable build.

                  Comment


                  • #29
                    Originally posted by A Laggy Grunt View Post
                    My biggest problem has been with xscreensaver+Catalyst. The small gripe is it won't show the password box to unlock your screen. The big one is it occasionally crashes X when you try to unlock your screen.
                    How is it with open source drivers?
                    Wine has been... well, Wine. Lots of stuff works, lots of stuff doesn't. I write decently detailed reviews of app behavior on WineHQ, with the stable build.
                    Wine is a hit or a miss. World of Warcraft runs fine, but are certain settings. Dark Souls doesn't work at all.

                    Comment


                    • #30
                      Originally posted by agd5f View Post
                      You can fetch Dave's git branch directly rather than using patches.
                      http://cgit.freedesktop.org/~airlied...0-geom-shaders
                      Great, thanks for the link!

                      Comment

                      Working...
                      X