Language Selection

English French German Italian Portuguese Spanish

Vulkan 1.1

Filed under
Graphics/Benchmarks
  • Intel Publishes 56 Patches For Conformant Vulkan 1.1 Support With ANV Driver

    Intel has joined the party with NVIDIA and AMD in offering launch-day Linux driver support for the big new Vulkan 1.1 update available today from The Khronos Group.

  • AMDVLK Open-Source Radeon Driver Arrives With Vulkan 1.1 Support

    When writing about the big Vulkan 1.1 release a few days ago I was wondering myself whether the official AMDVLK Vulkan driver or RADV Mesa-based Vulkan driver would be first to the table with Vulkan 1.1 patches... It turns out AMDVLK won this round, at least by a small measure of time.

    The AMD developers working on this official Vulkan Linux driver that's also part of the AMDGPU-PRO driver have just uploaded their revised code for supporting Vulkan 1.1. With around 13,000 lines of new code, they have enabled Vulkan 1.1 support within their AMDVLK/XGL code-base.

  • Vulkan 1.1 Released As The First Major Update To This Graphics/Compute API

    The Khronos Group has today announced Vulkan 1.1 as the first major update to this high-performance graphics/compute API since the initial Vulkan 1.0 release two years ago. And it's thankfully a hard launch with multiple vendors putting out Vulkan 1.1 conformant drivers today.

  • NVIDIA Releases First Linux Drivers For Vulkan 1.1

    Just as we have been accustomed to seeing over the years with OpenGL and now Vulkan, NVIDIA is first out the door with Windows and Linux drivers for this new graphics API update.

    Vulkan 1.1 is now available today, check out our launch article for all of the details. As mentioned there, multiple vendors have conformant drivers in place but NVIDIA is the first making them available.

  • Khronos Group has released Vulkan API version 1.1 today, new NVIDIA beta driver & AMD driver available

    For those interested, Khronos Group has today announced the release of the Vulkan [Official Site] API version 1.1 and NVIDIA already have a beta driver ready.

Khronos Group Releases Vulkan 1.1

  • Khronos Group Releases Vulkan 1.1

    Vulkan ecosystem momentum continues to grow with improved developer tools, wide industry adoption, and new specification for evolved functionality and performance

  • Khronos Group Releases Vulkan 1.1

    The Khronos Group has announced the release of the Vulkan GPU API version 1.1 and SPIR-V 1.3 specifications.

Comment viewing options

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

More in Tux Machines

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)

Total War: WARHAMMER

Red Hat changes its open-source licensing rules

From outside programming circles, software licensing may not seem important. In open-source, though, licensing is all important. So, when leading Linux company Red Hat announces that -- from here on out -- all new Red Hat-initiated open-source projects that use the GNU General Public License(GPLv2) or GNU Lesser General Public License (LGPL)v2.1 licenses will be expected to supplement the license with GPL version 3 (GPLv3)'s cure commitment language, it's a big deal. Read more

Android Leftovers