ixp-imx: update to 4.2.2.24.4 as used with NXP BSP LF6.6.52_2.2.0 #2082
+96
−151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On current master isp-imx (specific to i.MX 8MP) fails to build due to a boost update in oe-core.
Updating from 4.2.2.24.0 to 4.2.2.24.4 on its own did not fix the issue but was done anyway.
Further fixes were needed as outlined in the commit comment.
No tests on real HW were done.
If isp-imx without tuningext makes sense I do not know. I assume it is a server which together with a PC application allow to get a tuning xml file to then use in production.
Note: This cannot be backported as is to scarthgap. If this PR is accepted into master I will provide a PR against scarthgap: