Announcement

Collapse
No announcement yet.

AMD Posts A Horde Of New 3D GPU Documentation

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

  • #16
    Originally posted by Veerappan View Post
    I've got a MiniITX Llano at home (A6-3500, 45-65w?) that's been running for ~2 years, and it's been very reliable. It's currently running MythBuntu with an HDMI output carrying video/audio to the receiver and has been running the open-source radeon drivers since it was built. With DPM and UVD working, this machine is silent and keeps up with everything I ask of it (although I've been thinking of upgrading from a single to a dual tuner)... I can only imagine how well Trinity/Richland would perform.

    Although if you were already looking at Atom, I'm assuming you're looking for something even lower power yet (Jaguar?). I've been thinking of something similar for my next NAS upgrade (the current Phenom II 720 is definitely overkill).
    Well I'm currently deciding between Intel ATOM N2800 (16W, but a little bit less powerful than the other two, also no BIOS RAID) vs. AMD E-350 (30W and no BIOS RAID) vs AMD T56N (also 30W, but seems like a really nice mobo that could run for years without any maintenance + plenty of features). Power consumption is a big part of my plan since the whole server will be powered by batteries and solar panels (mobo + 3x HDD). BTW it will be used for OwnCloud, email server and JAVA accounting app.

    AMD makes superior HW, it's just the SW that lacks behind...

    Originally posted by Kivada View Post
    An A6-1450 is probably ideal for a fanless ITX SteamOS streamer box in the living room.
    Keep your beefy gaming box somewhere where you don't have to hear it.
    I'm thinking about AMD A6-1450 for my next laptop (11" maybe?), since 13" i7 ultrabook seems like an overkill (also the weight & height are pointless when it's that big...). For video/audio streaming I'm going to order RPi.

    Comment


    • #17
      Originally posted by sarmad View Post
      The streaming is used mainly for backward compatibility, as a better-than-nothing way of playing older games in the living room. But if you are to play newer games that run natively on SteamOS then I'm sure putting a real box under your TV will provide you a noticeably superior experience in terms of both latency and image quality.
      I would think running it over a Gbit network would be just fine, at least up till 1920x1080. The rendering would entirely be done of the gaming box, which you could use as you HTPC backend server and now game streaming rig.

      Now you might have issues trying to stream a game over wifi, but a hardline Gbit setup should have more then enough bandwidth and a low enough latency that it doesn't make any significant difference.

      Comment


      • #18
        Hey, Alex, is any of this released documentation particularly 'new' or revolutionary? I know the SI driver is in rough (but improving quickly) shape so this should help there, but I thought everything covered by r600g was in relatively good shape.

        Comment


        • #19
          Originally posted by curaga View Post
          Start encrypting your NAS drives with several chained algorithms, like AES->Blowfish->GOST->3DES and it's no longer overkill
          Fair point. AES can be hardware accelerated, but I'm not aware of instructions for the rest. I'm not using encryption yet, but I am doing RAID-Z on freenas across 3 drives, so there's at least software parity and checksum calculations.

          Comment


          • #20
            Originally posted by sarmad View Post
            "The Radeon HD 5000 "Evergreen" and Radeon HD 6000 "Northern Islands" open-source driver support is in good shape"

            That wasn't the case with my Radeon HD 6750M, which did not work at all with the open source driver (on Ubuntu 13.04).
            My 6750M has been working with the open source driver for years, your issue is probably something else. If you're booting via UEFI that could be related to that (with Ubuntu 13.04 anyway), but I'm not aware of any systems that shipped with UEFI and a 6750M... except maybe some Apple laptop of some sort? I believe I remember a 6750M BIOS being posted that was taken from some sort of Apple laptop... those have their own slew of Linux issues to begin with.



            Back on topic... this is exactly what I was hoping for when Nvidia said they would try to release some open-source docs. It tends to go like this... when one company announces something, the other company will then announce something better within a week or so. I'm hoping for even better yet open-source support on my multiple AMD APU based systems!

            Comment


            • #21
              Is it just me or are Nvidia and ATI falling all over each other to support Linux since Valve's announcements this week?

              Shame on ATI for not having released this documentation previously.

              Comment


              • #22
                Originally posted by TurbulentToothpick View Post
                Is it just me or are Nvidia and ATI falling all over each other to support Linux since Valve's announcements this week?

                Shame on ATI for not having released this documentation previously.
                AMD's Linux support (that the public knows of) is much older than Valve's, and on a different level. It always takes them some time to release newer specs and docs, has always been that way. But those are openly available and NDA-free. Legal clearing takes some time.

                Comment


                • #23
                  Originally posted by Laser View Post
                  AMD's Linux support (that the public knows of) is much older than Valve's, and on a different level. It always takes them some time to release newer specs and docs, has always been that way. But those are openly available and NDA-free. Legal clearing takes some time.
                  Well I wonder how much of that is from the hardware backlog, remember that AMD has released docs for all Radeon hardware going back to the first Radeon 7000 R100/RV200 series.

                  Once they are finally caught up to current over in legal I wonder what the delay will be like for new generations.

                  I.E. if over the next year AMD's legal team finally approved and released all pending docs for AMD's entire Radeon catalog all the way through the current gen Volcanic Islands series would the next series of card get their docs before, day of or after release?

                  That tipping point has to happen eventually, and when it does everything from then on will be only held back only by how fast the community can program.

                  Comment


                  • #24
                    Originally posted by Ericg View Post
                    Hey, Alex, is any of this released documentation particularly 'new' or revolutionary? I know the SI driver is in rough (but improving quickly) shape so this should help there, but I thought everything covered by r600g was in relatively good shape.
                    All of the information in the register documents has been available via header files in the driver code since it was first released.

                    Comment


                    • #25
                      Originally posted by Kivada View Post
                      I would think running it over a Gbit network would be just fine, at least up till 1920x1080. The rendering would entirely be done of the gaming box, which you could use as you HTPC backend server and now game streaming rig.

                      Now you might have issues trying to stream a game over wifi, but a hardline Gbit setup should have more then enough bandwidth and a low enough latency that it doesn't make any significant difference.
                      While a Gbit ethernet is fast enough, encoding a 1920x1080 video stream takes its own time and processing power. Yes, the time is not that big, but add that to the communication latency and you'll get a noticeable delay. Also, a game will have to sacrifice some graphics details in order to accommodate for a 1920x1080 video being encoded in real time.
                      A couple of weeks ago a Microsoft representative asked people not to plug gaming machines into the Xbox One's HDMI input slot because of the latency that will affect the experience, and you're talking here about a direct connection, no router in the middle, no long distance, and no encoding at the source.

                      Comment


                      • #26
                        Originally posted by agd5f View Post
                        All of the information in the register documents has been available via header files in the driver code since it was first released.
                        Okay, so this is mostly just formality and organizational thing (moving references out of the header files and now saying "look at the documentational pdfs"). Just checking

                        Comment


                        • #27
                          Originally posted by Ericg View Post
                          Okay, so this is mostly just formality and organizational thing (moving references out of the header files and now saying "look at the documentational pdfs"). Just checking
                          There's more detail in the documents than in the header files (eg more explanation of what things do), so it's not just header file in a different format, but these are more like "documentation to back up the code" rather than "documentation for areas which don't have code today". The 3D acceleration docs also might help new devs get started more than just looking at code would.

                          Comment

                          Working...
                          X