Language Selection

English French German Italian Portuguese Spanish

Graphics: Intel Gen12, Navy Flounder, Sway and DRM-Next

Filed under
Hardware
  • Intel Gen12 Graphics Bring EU Fusion - EUs Fused In Pairs

    While we remain eager to find out more about (and benchmark) Intel Gen12 graphics in Tiger Lake and Xe discrete graphics with this generation bringing the biggest changes to the ISA since i965, Linux patches and bug reports do continue offering new tid-bits of information on Gen12.

    One bit that I don't believe has been reported publicly or at least not widely is that starting with Intel Gen12 graphics there is "EU Fusion" or the execution units now being paired for yielding a larger warp size.

  • "Navy Flounder" Is The Newest AMD Navi 2 GPU Being Added To The Linux Driver

    In addition to the "Sienna Cichlid" support recently published for the open-source AMD Radeon Linux kernel graphics driver, there is another new graphics processor being added to their driver: Navy Flounder.

    Sent out this week were patches for Navy Flounder as another Navi 2 part, Navi 22 to be exact. The patches mostly reuse the existing Sienna Cichlid code paths. The codename, like Sienna Cichlid, is the Linux naming convention currently being used by the AMD Linux team of a color followed by a fish species.

  • Sway 1.5 Wayland Compositor Released With Adaptive-Sync/VRR, New Protocols

    Sway 1.5 is out as a big feature update to this Wayland compositor inspired by the i3 window manager. A big user-facing feature with Sway 1.5 is support for Adaptive Synchronization / Variable Refresh Rate, such as AMD FreeSync.

    Up to now the FreeSync/Adaptive-Sync has been principally been in place for the Linux desktop when running on an X.Org session. However, Sway now supports Adaptive-Sync/VRR for reducing stuttering and tearing within games.

  • Early Intel DG1 Graphics Card Enablement Sent In To DRM-Next For Linux 5.9

    As we have been anticipating for weeks, initial (but still early) enablement of the Intel DG1 graphics card on their open-source driver stack will indeed be sent in for the upcoming Linux 5.9 cycle and is currently being queued in the DRM-Next repository.

    It was in late May that Intel sent out the DG1 patches to light up the graphics card on Linux and building off all the existing Gen12/Xe graphics code already mainlined within the kernel. Since then the kernel work has continued with other features getting squared away.

AMD Navi 22 is listed in a Linux patch under the fuzzy....

  • AMD Navi 22 is listed in a Linux patch under the fuzzy name “Navy Flounder”

    Some time ago there was a rumor that AMD had discovered that users were snooping around in their controllers to find clues about new products coming to market. There were rumors that AMD started using alternative code names to hide its graphics cards from prying eyes. Sienna Cichlid, who is believed to be Navi 21, was the first example that came to light. And now AMD seems to use the code name Navy Flounder to hide the silicon Navi 22.

Comment viewing options

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

More in Tux Machines

Today in Techrights

Android Leftovers

LibreOffice 6.4.5 finally for Slackware 14.2

The Document Foundation recently released version 7.0.0 of their Libre Office suite of applications. The packages for Slackware-current can be found in my repository. But the situation for Slackware 14.2 used to be different – I got stuck after LibreOffice 6.2 because the newer source releases (6.3 and onwards) require versions of system software that our stable Slackware 14.2 platform does not offer. From time to time during the last year, when there was time and the build box was not compiling packages, I messed around with the libreoffice.SlackBuild script in futile attempts to compile recent versions of LibreOffice on Slackware 14.2. I failed all the time. Until last week. After I had uploaded the new KDE Plasma5 packages to ‘ktown‘, I had an epiphany and decided to use a new approach. What I did was: question all the historic stuff in the SlackBuild script that got added whenever I needed to work around compilation failures; and accept that the compilation needs newer versions of software than Slackware 14.2 offers. The first statement meant that I disabled patches and variable declarations that messed with compiler and linker; and for the second statement I stuck to a single guideline: the end product, if I were able to compile a package successfully, has to run out of the box on Slackware 14.2 without the need to update any of the core Slackware packages. Read more

Web Browsers: New Tor RC, Firefox/Mozilla Trouble, and Web Browsers Need to Stop

  • New release candidate: 0.4.4.4-rc

    There's a new alpha release available for download. If you build Tor from source, you can download the source code for 0.4.4.4-rc from the download page. Packages should be available over the coming weeks, with a new alpha Tor Browser release likely in the coming weeks.

    Remember, this is a release candidate, not a a stable release: you should only run this if you'd like to find and report more bugs than usual.

  • Mozilla is dead

    If Mozilla wants to survive, the management will be fired with unearned compensation, the most important departments will be strengthened, products that nobody ordered will be discontinued and the organization will be limited to its core competence. Browser, email, security, adaptability and the fight for a free Internet. And they work with all their might to ensure that the products will become an integral part of everyday life and all operating systems.

    Three months. That’s all the time they have for a clear signal. After that, users have to make a decision. Unfortunately, it will probably only be something with chromium.

    Poor Internet.

  • Web browsers need to stop

    I call for an immediate and indefinite suspension of the addition of new developer-facing APIs to web browsers. Browser vendors need to start thinking about reducing scope and cutting features. WebUSB, WebBluetooth, WebXR, WebDRM WebMPAA WebBootlicking replacing User-Agent with Vendor-Agent cause let’s be honest with ourselves at this point “Encrypted Media Extensions” — this crap all needs to go. At some point you need to stop adding scope and start focusing on performance, efficiency, reliability, and security5 at the scope you already have.