From: Alistair Popple <apopple@nvidia.com>
To: dri-devel@lists.freedesktop.org
Cc: nova-gpu@lists.linux.dev, jhubbard@nvidia.com,
Alistair Popple <apopple@nvidia.com>
Subject: [PATCH 0/2] Add libdrm support for auxbus devices
Date: Fri, 31 Jul 2026 16:04:16 +1000 [thread overview]
Message-ID: <20260731060416.1400253-4-apopple@nvidia.com> (raw)
In-Reply-To: <20260731060416.1400253-1-apopple@nvidia.com>
The new Nova[1] NVIDIA GPU driver exposes GPUs as logical devices on an
auxbus. Currently libdrm doesn't support auxbus, so it ignores Nova GPUs
during enumeration. This adds support for devices on an auxbus.
Rather than follow the lead of virtio and resolve the logical auxbus device
back to the physical PCI device, we add a new bus type and associated parser.
This is because in future it's a single physical GPU may present multiple auxbus
devices, so it needs to be possible to resolve individual devices even if they
share the same parent GPU.
[1] - https://rust-for-linux.com/nova-gpu-driver
Alistair Popple (2):
xf86drm: Pass PCI path rather than maj/min when parsing sysfs files
xf86drm: Expose auxiliary bus GPUs as DRM_BUS_AUXILIARY
xf86drm.c | 135 +++++++++++++++++++++++++++++++++++++++++++++++-------
xf86drm.h | 12 +++++
2 files changed, 130 insertions(+), 17 deletions(-)
--
2.54.0
prev parent reply other threads:[~2026-07-31 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 6:04 [PATCH libdrm 0/2] Add libdrm support for auxbus devices Alistair Popple
2026-07-31 6:04 ` [PATCH libdrm 1/2] xf86drm: Pass PCI path rather than maj/min when parsing sysfs files Alistair Popple
2026-07-31 6:04 ` [PATCH libdrm 2/2] xf86drm: Expose auxiliary bus GPUs as DRM_BUS_AUXILIARY Alistair Popple
2026-07-31 6:04 ` Alistair Popple [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260731060416.1400253-4-apopple@nvidia.com \
--to=apopple@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhubbard@nvidia.com \
--cc=nova-gpu@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox