Announcement

Collapse
No announcement yet.

Vega 12 Support Is Now Available For RadeonSI Gallium3D

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

  • Vega 12 Support Is Now Available For RadeonSI Gallium3D

    Phoronix: Vega 12 Support Is Now Available For RadeonSI Gallium3D

    One day after AMD posted the big patch set providing Vega 12 GPU support for the Linux kernel's AMDGPU driver, a patch has emerged now adding Vega 12 support to the RadeonSI Gallium3D OpenGL driver...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Is the new APU on the Atari console!! No I'm kidding.

    Comment


    • #3
      Has any of this work made Raven Ridge any more stable/usable or is it still a waiting game for 4.17?

      Comment


      • #4
        Whatever it is, it's probably not going to be all too exciting. Given up being excited about new GPU launches from AMD after the Vega fiasco
        (yes I know Vega56 is decent now, but no ITX version and V64 is still over-volted garbage, oh and stock/price unobtainable!)

        Comment


        • #5
          Sapphire Pulse Vega 56 is a decent card, but the price is crazy.

          Comment


          • #6
            Vega 56 has JUST dropped to $769AUD in some stores here in Australia, previously like a week ago it was $1098, and some stores are still trying to get that for the card.

            Comment


            • #7
              I hope they're not going to mix nomenclature. We had Polaris 10, 11, and 12, for the 36, 16, and 8 CU chips.

              Then, we get Vega 56 and 64, for 56 CUs and 64 CUs.

              So, are they going by CU counts, or from big to little?

              Comment


              • #8
                They are going in the order we started working on them.

                That's the whole idea of having code names, so we can reference products before launch without exposing all of the details
                Test signature

                Comment


                • #9
                  Originally posted by bridgman View Post
                  They are going in the order we started working on them.
                  Thanks. That helps.

                  Originally posted by bridgman View Post
                  That's the whole idea of having code names, so we can reference products before launch without exposing all of the details
                  So, are the code names like Ellesmere, Baffin, Bonaire, etc. completely gone? Or is AMD just better at keeping them secret?

                  Comment


                  • #10
                    We have pretty much changed over to <architecture><sequence> rather than a unique code name within some kind of conceptual grouping (eg Evergreen or Southern Islands). It could change again though - my impression is that we change code name approaches whenever people feel they are running out of good names.

                    Before Evergreen and the HD4xxx family we had interesting groupings of code names like "Boom", "Shaka" and "Laka" for rv610, rv630 and rv670 respectively, where the code names within a family were obviously associated but without an actual family name.
                    Test signature

                    Comment

                    Working...
                    X