Bug 501 - Discuss Vulkan requiring software API compliance and how that meshes with our OPF compliance needs
Summary: Discuss Vulkan requiring software API compliance and how that meshes with our...
Status: CONFIRMED
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Specification (show other bugs)
Version: unspecified
Hardware: PC Linux
: Low normal
Assignee: Luke Kenneth Casson Leighton
URL:
Depends on:
Blocks:
 
Reported: 2020-09-24 00:23 BST by Cole Poirier
Modified: 2023-09-05 20:18 BST (History)
1 user (show)

See Also:
NLnet milestone: Future
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cole Poirier 2020-09-24 00:23:32 BST 
Based on a chat message Jacob sent in our Wed 23 September 2020 Libre-SOC-Microwatt Sync Jisti call:

"Note that vulkan is software API compliance, not ISA-level, so the compiler can adapt b/w vulkan and the ISA."

This has important implications for our HDL, but even greater implications for our to-be-proposed OpenPowerISA '3D GPU' or 'Unix without VSX' compliance category requirements. If you don't mind, Jacob, can you fill in some of the implications this has, as I think you know and I don't.