Language Selection

English French German Italian Portuguese Spanish

ATI's Radeon X800 XL 512MB

Filed under
Hardware
Reviews

The PC graphics business is famous--some would say notorious--for what are known as "kicker" products. Because of the ever-increasing complexity of bringing a new GPU architecture to market, both ATI and Nvidia develop many derivative parts from core architectures to get the most out of them. This exercise stems from two motivations: The first is to "use the whole cow" as Nvidia CEO Jen Hsun Huang is fond of saying, meaning they do more yield-bin sorting to squeeze every bit of clock out of GPUs rolling off the fab line. The other is to address microsegments of the market, especially at the mid and low ends of the market where most of the business actually gets done.

Both ATI's R4xx and Nvidia's NV4x architectures have proven their mettle in the benchmark arena, and we've seen a gaggle of derivative parts based on these two designs. We recently saw both companies make a serious play at the low end: ATI with its HyperMemory and Nvidia with its TurboCache--both attempts to swipe some market share from the PC graphics volume leader, Intel.

As both architectures move toward the autumn of their product cycles, it becomes increasingly hard to squeeze more kickers out of these core designs. But whereas HyperMemory and TurboCache, with their reduced frame buffers, seek to do more with less, ATI is taking its high midrange X800XL GPU and looking to do more with more. 256MB more, to be precise. You'll soon be seeing X800XL-based cards equipped with 512MB frame buffers. Is more memory the answer to our problems, especially since you don't get any more memory bandwidth, just a bigger data "parking lot?" Continued...

More in Tux Machines

today's howtos

Graphics: VC4 and AMDVLK Driver

  • VC4 display, VC5 kernel submitted
    For VC5, I renamed the kernel driver to “v3d” and submitted it to the kernel. Daniel Vetter came back right away with a bunch of useful feedback, and next week I’m resolving that feedback and continuing to work on the GMP support. On the vc4 front, I did the investigation of the HDL to determine that the OLED matrix applies before the gamma tables, so we can expose it in the DRM for Android’s color correction. Stefan was also interested in reworking his fencing patches to use syncobjs, so hopefully we can merge those and get DRM HWC support in mainline soon. I also pushed Gustavo’s patch for using the new core DRM infrastructure for async cursor updates. This doesn’t simplify our code much yet, but Boris has a series he’s working on that gets rid of a lot of custom vc4 display code by switching more code over to the new async support.
  • V3D DRM Driver Revised As It Works To Get Into The Mainline Kernel
    Eric Anholt of Broadcom has sent out his revised patches for the "V3D" DRM driver, which up until last week was known as the VC5 DRM driver. As explained last week, the VC5 driver components are being renamed to V3D since it ends up supporting more than just VC5 with Broadcom VC6 hardware already being supported too. Eric is making preparations to get this VideoCore driver into the mainline Linux kernel and he will then also rename the VC5 Gallium3D driver to V3D Gallium3D.
  • AMDVLK Driver Gets Fixed For Rise of the Tomb Raider Using Application Profiles
    With last week's release of Rise of the Tomb Raider on Linux ported by Feral Interactive, when it came to Radeon GPU support for this Vulkan-only Linux game port the Mesa RADV driver was supported while the official AMDVLK driver would lead to GPU hangs. That's now been fixed. With the latest AMDVLK/XGL source code as of today, the GPU hang issue for Rise of the Tomb Raider should now be resolved.

AMD Ryzen 7 2700X Linux Performance Boosted By Updated BIOS/AGESA

With last week's initial launch-day Linux benchmarks of the Ryzen 5 2600X / Ryzen 7 2700X some found the Linux performance to be lower than Windows. While the root cause is undetermined, a BIOS/AGESA update does appear to help the Linux performance significantly at least with the motherboard where I've been doing most of my tests with the Ryzen 7 2700X. Here are the latest benchmark numbers. Read more

GNU: The GNU C Library 2.28 and Guix on Android

  • Glibc 2.28 Upstream Will Build/Run Cleanly On GNU Hurd
    While Linux distributions are still migrating to Glibc 2.27, in the two months since the release changes have continued building up for what will eventually become the GNU C Library 2.28. The Glibc 2.28 work queued thus far isn't nearly as exciting as all the performance optimizations and more introduced with Glibc 2.27, but it's a start. Most notable at this point for Glibc 2.28 is that it will now build and run cleanly on GNU/Hurd without requiring any out-of-tree patches. There has been a ton of Hurd-related commits to Glibc over the past month.
  • Guix on Android!
    Last year I thought to myself: since my phone is just a computer running an operating system called Android (or Replicant!), and that Android is based on a Linux kernel, it's just another foreign distribution I could install GNU Guix on, right? It turned out it was absolutely the case. Today I was reminded on IRC of my attempt last year at installing GNU Guix on my phone. Hence this blog post. I'll try to give you all the knowledge and commands required to install it on your own Android device.
  • GNU Guix Wrangled To Run On Android
    The GNU Guix transactional package manager can be made to run on Android smartphones/tablets, but not without lots of hoops to jump through first.