Skip to content

Aligning SDMA firmware version and load logic with NXP BSP#1057

Merged
ricardosalveti merged 4 commits intofoundriesio:mainfrom
ricardosalveti:sdma
Mar 1, 2023
Merged

Aligning SDMA firmware version and load logic with NXP BSP#1057
ricardosalveti merged 4 commits intofoundriesio:mainfrom
ricardosalveti:sdma

Conversation

@ricardosalveti
Copy link
Copy Markdown
Member

Have SDMA provided by firmware-imx (latest revision) and add firmwared as it is required for early loading of the firmware when booting the system.

Relevant changes:
- d55fd7d3 bsp: imx: enable FW_LOADER_USER_HELPER

Signed-off-by: Ricardo Salveti <[email protected]>
Make the sdma-imx6q/7d packages available for runtime.

Signed-off-by: Ricardo Salveti <[email protected]>
Follow the NXP BSP and drop the upstream linux sdma packages from the
package list.

Signed-off-by: Ricardo Salveti <[email protected]>
Follow the NXP BSP and prefer the SDMA provided by the firmware-imx
recipe.

Also add firmwared as it is the legacy way of loading firmware with help
from userspace, which is still required for SDMA.

Signed-off-by: Ricardo Salveti <[email protected]>
@ricardosalveti ricardosalveti requested review from a team March 1, 2023 15:46
Copy link
Copy Markdown
Contributor

@angolini angolini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -0,0 +1,4 @@
do_install:append() {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is needed here, I wonder if this is needed upstream.
I'm up to reworking the firmware-imx_8 recipe mainline. I'm adding a note here, so that when I'm working on this, I remember where it's coming from

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is already there, but commented out.

Yeah, for upstream I would probably do this differently via providers or similar, as we have 2 recipes providing conflicting packages, and the ideal approach would this to be selected at runtime (not done here as we only use the NXP BSP, so we're good to assume that the one to use is firmware-imx).

@ricardosalveti ricardosalveti merged commit d1ef01c into foundriesio:main Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants