Language Selection

English French German Italian Portuguese Spanish

Vulkan update: version 1.1 conformance for Raspberry Pi 4

Filed under
GNU
Graphics/Benchmarks
Linux
  • Vulkan update: version 1.1 conformance for Raspberry Pi 4

    It has been almost a year since we announced conformance for Vulkan 1.0 on Raspberry Pi 4 devices. Since then, we have been working on improving driver performance, expanding the feature set, and advancing towards Vulkan 1.1 support.

    Today we are excited to announce that Khronos has just granted Vulkan 1.1 conformance to Raspberry Pi 4.

    All the required driver changes for Vulkan 1.1 have already been merged in the upstream v3dv Mesa driver and will hopefully be available soon in Raspberry Pi OS.

  • Raspberry Pi 4 Granted Official Vulkan 1.1 Conformance - Phoronix

    Last week I mentioned how Mesa landed Vulkan 1.1 support for the V3DV driver most notably used by the Raspberry Pi 4 and newer. With those changes in Mesa Git, The Khronos Group has now officially granted this driver Vulkan 1.1 conformance for the Raspberry Pi 4.

    It's now official with The Khronos Group signing off on the Vulkan 1.1 conformance test results for the V3DV driver running on the Raspberry Pi 4 Model B single board computer.

  • Vulkan 1.1 conformance achieved for the Raspberry Pi 4 | GamingOnLinux

    Good news for fans of the tiny Raspberry Pi 4 Model B, as it has been announced that the v3dv Mesa driver has hit Vulkan 1.1 conformance officially now.

    Shared on the Raspberry Pi website, with a post from Igalia’s Iago Toral they mention that it's been almost a year since the driver officially hit Vulkan 1.0 so it's great to see it continue to advance. In the post they noted that all the required changes are already merged in the upstream Mesa project. This means it will be available officially with the next major Mesa release later this year (Mesa 21.3).

Raspberry Pi 4 achieves Vulkan 1.1 conformance

  • Raspberry Pi 4 achieves Vulkan 1.1 conformance, gets up to 60% GPU performance boost

    Khronos has just granted Vulkan 1.1 conformance to Raspberry Pi 4 SBC, and following the implementation of various optimizations and new features such as geometry shaders, the v3dv Mesa driver delivers up to 60% higher GPU performance in Unreal Engine 4.

    Iglia started Vulkan driver work for Raspberry Pi 4 almost two years ago, with the triangle demo showcased in February 2020, followed by Vulkan 1.0 conformance in November 2020, and now the driver is certified conformant to Vulkan 1.1. While many GPUs are conformant, the Raspberry Pi 4 is only joined by a couple of complete platforms including several NVIDIA Jetson modules (Vulkan 1.2), and possibly some Intel and Google platforms shown as “Confidential” at this time.

Comment viewing options

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

More in Tux Machines

Programming Leftovers

  • Notes on packaging Krita with G’MIC

    Krita 3 and later are compatible with G’MIC, an open-source digital image processing framework. This support is provided by G’MIC-Qt, a Qt-based frontend for G’MIC. Since its inception, G’MIC-Qt was shipped as a standalone, externally built executable that is an optional, runtime dependency of Krita. Krita 5 changes the way G’MIC-Qt is consumed. In order to support CentOS and macOS, G’MIC-Qt has been converted into a dynamically loadable library that is a dependent of Krita. This file reviews these changes, and how to package Krita accordingly.

  • Qt WebAssembly clipboard

    Clipboard use on desktop platforms is ubiquitous. Most people use it without thinking. Copy, Paste, and Cut keyboard strokes are in-grained into muscle memory. On the web, it can present security issues as someone could read or write to your clipboard without you knowing. Up until now, Qt for WebAssembly's clipboard was text-only and only within the app itself. Qt 6.3 will have better clipboard support between host and app but also adds copy/pasting of images.

  • Attempting to compile Shotcut video editor
  • The Numbers: Performance benefits of the new Qt Quick Compiler

    In my previous post, the history and general architecture of the new Qt Quick Compiler technology was explained. As promised there, the performance numbers are presented in this post.

  • Monetizing cross-platform use cases faster and easier with Qt Digital Advertising Platform

    Many of you have been raising the question: when will Qt provide a full framework to monetize my Qt-based cross-platform application, implementing an advertising campaign directly on my user interface? Now all the community and Qt users in general can start in no time implementing and managing advertising campaigns targeting cross-platform use cases. We are excited to announce that Qt Digital Advertising 1.0 has been released!

  • Ads may be coming to KDE, the popular Linux desktop [Ed: Misleading clickbait. KDE and #Qt are not the same thing]
  • Qt Launches Digital Advertising Platform To Integrate Ads Into App UIs

    The Qt Company this morning announced Qt Digital Advertising 1.0 as its new ad platform that allows for developers to easily integrate advertising campaigns into Qt-based, cross-platform applications. The Qt Company devised Qt Digital Advertising as a way for the community and Qt users to integrate and manage advertising campaigns within Qt-powered programs. This is a new plug-in for the Qt toolkit for managing and monetizing campaigns for any Qt-based application.

  • Parsing PNGs Differently | Hackaday

    There are millions of tiny bugs all around us, in everything from our desktop applications to the appliances in the kitchen. Hidden, arbitrary conditions that cause unintended outputs and behaviors. There are many ways to find these bugs, but one way we don’t hear about very often is finding a bug in your own code, only to realize someone else made the same mistake. For example, [David Buchanan] found a bug in his multi-threaded PNG decoder and realized that the Apple PNG decoder had the same bug. PNG (Portable Network Graphics) is an image format just like JPEG, WEBP, or TIFF designed to replace GIFs. After a header, the rest of the file is entirely chunks. Each chunk is prepended by a four-letter identifier, with a few chunks being critical chunks. The essential sections are IHDR (the header), IDAT (actual image data), PLTE (the palette information), and IEND (the last chunk in the file). Compression is via the DEFLATE method used in zlib, which is inherently serial. If you’re interested, there’s a convenient poster about the format from a great resource we covered a while back.

Announcing the D-Installer Project | YaST

As you may know, YaST is not only a control center for (open)SUSE Linux distributions, but it is also the installer. And, in that regard, we think it is a competent installer. However, time goes by, and YaST shows its age in a few aspects. During summer 2021, the team discussed how YaST should look in the near future. Read more

Qubes OS 4.1.0-rc4 has been released!

The fourth release candidate for Qubes 4.1.0 is here! There are no major changes to report. We’ve just focused on fixing bugs that were discovered and reported in the third release candidate. If you’re currently using any Qubes 4.1.0 release candidate, a regular update is sufficient to upgrade to the latest one. Otherwise, read on for more about how to get started with testing Qubes 4.1.0-rc4. Read more

Google v. Oracle: The End of an Era - Software Freedom Law Center

The Supreme Court?s April 3rd decision of the long-running dispute between Oracle and Google brings to a last victorious conclusion the free software movement?s legal campaign, which began more than thirty years ago. Though the Justices have only now resolved the issue of API copyright, it was among the first of the legal problems with which FSF and I dealt. The heart of the free software movement?s long-term strategy was to harness the power of independent reinvention. Writing from scratch new programs that implemented both sides of all major software APIs was the technical pillar of our master plan. Licensing those programs on terms that protected the resulting commons?giving every user rights to study, copy, modify and share, with copyleft restriction on downstream licensing?was the legal pillar. The master plan of GNU was the independent reimplementation of both sides of all Unix APIs, thus allowing anything that could be done by general purpose computers to be done by software in which users had rights and free invention could flourish. When FSF and I started working together, in 1993, the Foundation?which was made possible by Richard Stallman?s 1990 MacArthur prize?was new, and the 1991 GPLv2 license brilliantly constructed for Stallman by Jerry Cohen was even newer. Gaining broad legal acceptance for GPLv2 and assessing the risk from the patenting of purely software inventions were immediate legal problems in need of my attention. But the threat posed by broad API copyright was the most urgent. The urgency arose because the issue was already headed for the US Supreme Court. Read more