From Fedora Project Wiki
< Changes
mNo edit summary |
No edit summary |
||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}} | {{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}} | ||
| Line 39: | Line 37: | ||
<!-- [[Category:SystemWideChange]] --> | <!-- [[Category:SystemWideChange]] --> | ||
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/ | * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41 ] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 55: | Line 53: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Build ISOs and OStree images with mesa-libOpenCL in | Build ISOs and OStree images with mesa-libOpenCL built in. | ||
Remove Gallium's Clover Backend. | |||
mesa-libOpenCL brings RustICL, that is a Mesa Gallium's frontend that implements OpenCL 3.0 API. | mesa-libOpenCL brings RustICL, that is a Mesa Gallium's frontend that implements OpenCL 3.0 API. | ||
| Line 67: | Line 66: | ||
Build ISOs: including mesa-libOpenCL as default package. | Build ISOs: including mesa-libOpenCL as default package. | ||
== Feedback == | == Feedback == | ||
<!-- 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 testing | 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 == | ||
| Line 105: | Line 103: | ||
The most benefits will be the increase adoption, and including a OpenCL standard driver as default, that | 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. | allows to help users to uses softwares that depends of OpenCL out of the box. | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: i think is not have to be a specifical owner | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
It's necessary just for Build ISOs images with mesa-libOpenCL preinstalled | |||
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
Not looks this, it's just necessary: https://pagure.io/fedora-comps/pull-request/94 https://src.fedoraproject.org/rpms/mesa/pull-request/42 | |||
* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 126: | Line 127: | ||
* Alignment with Community Initiatives: | * Alignment with Community Initiatives: | ||
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider --> | <!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider --> | ||
Looks is OK | |||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
Can Help with OpenCL compability, but if users wants, the user can install by yourself HIP amd opencl or | |||
intel compute runtime | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== How To Test == | == How To Test == | ||
| Line 147: | Line 150: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
This is the PR: | |||
https://pagure.io/fedora-comps/pull-request/942 | |||
Is just necessary to install mesa-libOpenCL and tests if all works, this can't provide a block thing | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== User Experience == | == User Experience == | ||
| Line 162: | Line 167: | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> | --> | ||
mesa-libOpenCL brings RustICL and Clover that can help for a out of the box OpenCL experience in softwares that uses OpenCL API. | |||
== Dependencies == | == Dependencies == | ||
Latest revision as of 23:21, 2 March 2024
Guidance
For details on how to fill out this form, see the documentation.
For details on how to fill out this form, see the documentation.
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.
To report an issue with this template, file an issue in the pgm_docs repo.
Change Proposal Name
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.
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
- Name: Elias Souza
- Email: eliascontato@protonmail.com
Current status
- Targeted release: Fedora Linux 41
- 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 built in. Remove Gallium's Clover Backend.
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: i think is not have to be a specifical owner
- Other developers:
It's necessary just for Build ISOs images with mesa-libOpenCL preinstalled
- Release engineering: #Releng issue number
Not looks this, it's just necessary: https://pagure.io/fedora-comps/pull-request/94 https://src.fedoraproject.org/rpms/mesa/pull-request/42
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Community Initiatives:
Looks is OK
Upgrade/compatibility impact
Can Help with OpenCL compability, but if users wants, the user can install by yourself HIP amd opencl or intel compute runtime
How To Test
This is the PR: https://pagure.io/fedora-comps/pull-request/942 Is just necessary to install mesa-libOpenCL and tests if all works, this can't provide a block thing
User Experience
mesa-libOpenCL brings RustICL and Clover that can help for a out of the box OpenCL experience in softwares that uses OpenCL API.
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)