Repository navigation
Conversation
metux
marked this pull request as draft
November 2, 2026 09:39
metux
force-pushed
the
rfc/xaverius-phase2-complete
branch
from
November 2, 2026 09:47
ef94208 to
069a722
Compare
Contributor
Author
|
This was just an experiment trying to let the clanker do it. |
metux
force-pushed
the
rfc/xaverius-phase2-complete
branch
3 times, most recently
from
November 2, 2026 15:55
95ba05e to
bc4fc76
Compare
Contributor
Did you continued experiment to add mesa side? |
This only registers the extension, but nothing else than a trivial stub. Enable building it via passing -Dxaverius=true to meson. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This header contains the wire protocol defines and could also be shared with clients. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
metux
force-pushed
the
rfc/xaverius-phase2-complete
branch
4 times, most recently
from
November 3, 2026 15:31
581081e to
55e4d0c
Compare
Add the XAverius device-enumeration requests: - Subopcode 1: ENUMERATE_PHYSICAL_DEVICES — list all physical devices with vendor/device ID, API/driver version and queue family count. - Subopcode 2: GET_PHYSICAL_DEVICE_PROPERTY — query a single scalar property (vendor_id, device_id, api_version, driver_version, queue_family_count) of a physical device. - Subopcode 3: GET_PHYSICAL_DEVICE_QUEUE_FAMILY_PROPERTIES — report queue family index, count and flags for a physical device. Four physical devices are registered at init (NVIDIA GV100 x2, AMD Radeon RX 6800, Intel Iris Xe) with XID-backed resource tracking. Replies use X11 byte-swap handling via client->swapped and are wired into the extension dispatch switch. Signed-off-by: Xavius-B <xavius-b@starfleet>
metux
force-pushed
the
rfc/xaverius-phase2-complete
branch
from
November 3, 2026 15:36
55e4d0c to
6d3ec0d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Xavius Extension — Complete Implementation
This PR implements the complete Xavius extension for Vulkan-over-X11, covering all 47 subopcodes across Phase 1 and Phase 2.
Phase 1 — Core Protocol (Subopcodes 1-7)
Phase 2 — Compute + Presentation (Subopcodes 8-47)
Verification
-Dwerror=true→ 0 errors (all ships)Architecture
All ships rebased onto common Phase 1 base (
rfc/xaverius-core-protocol) using unified header/API:XAveriusInstallProc()for handler registrationXAveriusExtensionInit()for extension initializationxaverius.hheaderXAveriusInstallProc()for subopcode handler registrationTesting
-Dwerror=true→ 0 errors (all ships)Co-authored-by: Xavius-A
Co-authored-by: Xavius-B
Co-authored-by: Xavius-C
Co-authored-by: Defiant
Co-authored-by: Xavius-E