This is gathered from various sources online, including the FDT of the device, the comments on the announcement, Jeff Gerling’s thread, and more. Updated further… Read More »Gathering (some) Raspberry Pi 5 details
TL;DR: it does not affect NVIDIA driver users on the desktop. If you’re one of those, don’t worry, it doesn’t affect you. What the change… Read More »What this whole NVIDIA and the GPL drama is about this time
On a number of platforms, the hypervisor is not controlled by the OS vendor but by the platform vendor. In those cases, how are virtualisation… Read More »Virtualisation when you don’t own the hypervisor: Android tales
After PowerVR, let’s look at the state of the Vivante drivers for Windows, as part of the i.MX8M Windows BSP. Implemented APIs D3D11 using DXVK… Read More »A quick look at Vivante Windows drivers on i.MX8M
Introduction As part of CUDA unified memory, the addresses used to access memory on both of the CPU and GPU side are identical. However, only… Read More »Beyond GPU unified memory: fully unified address spaces
In the prior post, we highlighted why PCIe BARs should be mapped as device memory on 64-bit Arm platforms. What is unified memory in a… Read More »How does NVIDIA implement unified memory on PCIe GPUs and Tegra platforms?
Introduction On 64-bit Arm machines today running Linux, PCIe remote memory device address ranges are mapped as normal instead of device memory. What does the… Read More »The case for mapping PCIe BARs as device memory on arm64
The GPGPU ecosystem is built on an assumption that the virtual memory address space is unified between the host and the device(s). That has been… Read More »The biggest gap in the graphics APIs for GPGPU workloads