-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate XTOS on imx8/imx8x platforms #8856
Conversation
5aa71e9
to
f24dcf5
Compare
e9622e1
to
4e7b384
Compare
Thanks @LaurentiuM1234 I'm discussing now with our Yocto team in order to define the strategy of removing XTOS support. Will merge this once we have an agreement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there some public, very short document comparing "QM" versus "QXP" and a small table showing which "imx8?" belongs to what? It's pretty cryptic otherwise.
Can this wait until Zephyr updates are unblocked? I mean:
Sorry for the confusion. Not sure we have that. Maybe @dbaluta can help here. For reference:
The "imx8" and "imx8x" naming stems from the name of the family.
The transition is blocked by the same issue anyways so this can wait as well |
https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/i-mx-applications-processors/i-mx-8-applications-processors:IMX8-SERIES |
|
Thanks for the table, it is useful. I initially wondered whether it would be useful to add such a table as a comment somewhere here or in sof-docs but I suspect there's a much simpler solution... Would it be possible to very simply avoid "QM" and "QX" in commit messages and sources completely and just stick to "imx8" and "imx8m" as it has been done until now? As far as SOF is concerned it looks like a 1:1 mapping so far so it does not look like information would be lost if dropping "QM" and "QX" completely? CI compiles multiple configurations in many different ways so the time wasted to find this sort of mapping can add up quickly; it's not negligible. Also, fixing issues in other vendors' configurations is always quite stressful so every little helps. |
4e7b384
to
ad90344
Compare
ad90344
to
454e9e2
Compare
XTOS will be deprecated on imx8/imx8x and these platforms will be moved to native Zephyr so remove them from the QEMU boot test which uses SOF with XTOS. Signed-off-by: Laurentiu Mihalcea <[email protected]>
XTOS is going to be deprecated on imx8/imx8x so replace imx8 with imx8m. Signed-off-by: Laurentiu Mihalcea <[email protected]>
XTOS is going to be deprecated on all NXP's platforms so replace imx8 with AMD's rmb so that the CI test can be kept. Signed-off-by: Laurentiu Mihalcea <[email protected]>
To prepare for XTOS deprecation and switch to Zephyr native drivers on imx8/imx8x, remove the ability to build SOF with XTOS on them. Signed-off-by: Laurentiu Mihalcea <[email protected]>
V2 updates
|
To prepare for XTOS deprecation and switch to Zephyr native drivers on i.MX8QM/i.MX8QXP, remove the ability to build SOF with XTOS on said platforms. Also, remove all XTOS builds/tests for these platforms from CI.