Language Selection

English French German Italian Portuguese Spanish

Vega Code, Blobs and 'Leaks'

Filed under
Graphics/Benchmarks
  • Updated Vega 20 Firmware Binaries & Other AMDGPU Files Land In Linux-Firmware.Git

    For those habitually riding the bleeding-edge open-source Radeon graphics driver stack, there are some updated firmware files now available for newer AMD graphics processors.

    Hitting Linux-Firmware.Git this morning are updated Vega 20 files for the likes of the Radeon VII, Polaris 12 updates, and updated firmware for the yet-to-debut Picasso APUs. Other generations of AMD Radeon GPUs are unchanged in the linux-firmware tree.

  • Mysterious AMD GPU Benchmark Submission Appears to Be Vega, Not Navi

    While it is hard to tell what exactly this GPU is, if Linux's driver IDs can be trusted, it doesn't appear to be Navi. Even if the GPU is from the Navi lineup, it's hard to glean useful performance data and GPU specifications due to the nature of the CompuBench benchmark. For now, it appears more likely this is just another Vega 20 GPU, perhaps even a new WX Pro series model.

Radeon ROCm 2.2 Released With Vega 20 Optimization

  • Radeon ROCm 2.2 Released With Vega 20 Optimization, Caffe2 Multi-GPU Training

    One month since the release of ROCm 2.1, the Radeon Open Compute stack has now been succeeded by ROCm 2.2.

    The ROCm 2.2 release shipping today comes as a bit of a surprise. It's not the most feature-packed update but does have some nice additions while building on the already exciting ROCm 2.0 that shipped at the end of 2018.

    ROCm 2.2 brings rocSPARSE optimizations for Vega 20 with cache usage improvements, improved DGEMM performance for reduced matrix sizes, and with Caffe2 there is now support for multi-GPU training.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Android Leftovers

today's howtos

OpenJDK 8 and 11: Still in safe hands

In 2018, Oracle announced that it would only provide free public updates and auto-updates of Java SE 8 for commercial users until the end of January 2019. Java 8 is a very important platform, used by millions of programmers, so this was a big deal. The Java community needed to fill the gap. In February of this year, I was appointed as the new Lead of the OpenJDK 8 Update Releases Project. A couple of weeks later, I was appointed the new Lead of the OpenJDK 11 Updates Project. This is an important milestone in the history of OpenJDK and of Java SE because it’s the first time that a non-Oracle employee has led the current long-term OpenJDK release project. JDK 8 is still a much-used Java release in industry, and JDK 11 is the current long-term maintenance release. It’s now a couple of weeks after the first releases of JDK8u and JDK11u on my watch. I think the process went pretty well, although it was not entirely smooth sailing for the developers. Having said that, we got our releases out on the day, as planned, and so far we’ve seen no major problems. Read more

How to advance your career by contributing to open source projects

In 2017, I wrote my (so-far) most popular article of all time, "The Impact GitHub is Having on Your Software Career, Right Now…," on Medium. In that article, I cast the vision for how you can develop your career through open source contributions. It clearly struck a nerve—it got 382 points and 237 comments on Hacker News. Many of the comments hated on it so hard—they disagreed with my main premise—but I felt they had missed the point. At the time I was a recruiter with 10 years of engineering experience, working at Red Hat. There is nothing I love more than a challenge, so I went "deep cover." I quit my job as a recruiter and got a job as a software engineer in a pure closed-source company that uses BitBucket and has PCI-compliant security. Fourteen months later, I got hired by Camunda to work as the developer advocate for Zeebe, a workflow engine for orchestrating microservices, purely based on my open source contributions while working at that job. I just did everything I advised readers to do in the comments of my original Medium article. Read more