From Fedora Project Wiki
No edit summary
Line 72: Line 72:
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->


Is necessary for users testing RustICL compability in softwares, but in the same way this will just be a standard and users can install a HIP or Intel Compute Runtime if wants


== Benefit to Fedora ==
== Benefit to Fedora ==

Revision as of 22:30, 2 March 2024

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Idea.png
Guidance
For details on how to fill out this form, see the documentation.
Idea.png
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.


Change Proposal Name

Important.png
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Preinstall mesa-libOpenCL in Fedora ISOs releases

Owner

Current status

  • Targeted release: Fedora Linux 40
  • Last updated: 2024-03-02
  • [<will be assigned by the Wrangler> devel thread]
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Build ISOs and OStree images with mesa-libOpenCL in built.

mesa-libOpenCL brings RustICL, that is a Mesa Gallium's frontend that implements OpenCL 3.0 API.

RustICL already is conformant with Intel GPUs in the same way supports all necessary capabilities for run modern softwares including Davinci Resolve(IIRC). Distributes ISOs WITH mesa-libOpenCL package as default preinstalled can help in driver adoption and can turn more easy for sofwares that depends of OpenCL drivers.

RustICL can works in various Gallium backends drivers, in the same way Zink is already supported, Zink Powered with RustICL brings a OpenCL on Vulkan implementation that can run across drivers that supports the all required extensions for use it.

Releases modifications:

Build ISOs: including mesa-libOpenCL as default package.


Feedback

Is necessary for users testing RustICL compability in softwares, but in the same way this will just be a standard and users can install a HIP or Intel Compute Runtime if wants

Benefit to Fedora

The most benefits will be the increase adoption, and including a OpenCL standard driver as default, that allows to help users to uses softwares that depends of OpenCL out of the box.


Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes