Skip to content
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

Fix Wl18xx related recipes #19

Open
wants to merge 2 commits into
base: kirkstone
Choose a base branch
from
Open

Conversation

kraj
Copy link

@kraj kraj commented Mar 6, 2023

No description provided.

kraj added 2 commits March 6, 2023 11:04
wl18xx firmware is provided by linux-firmware-wl18xx not wl18xx-fw which
is from meta-ti layer which we do not use.

Secondly, keep the recipe scope to just var-som-mx6

Signed-off-by: Khem Raj <[email protected]>
@eranmati eranmati requested a review from varigigi March 7, 2023 09:41
@varigigi
Copy link
Contributor

@kraj, why introducing this limitation ?
This is an optional recipe which can be added whenever a customer uses wl18xx.
If a customer, for any reason would like to use wl18xx with any other SoM on a custom board, the COMPATIBLE_MACHINE would prevent the usage.
Kindly remove this addition.

@kraj
Copy link
Author

kraj commented Jun 12, 2023

@kraj, why introducing this limitation ? This is an optional recipe which can be added whenever a customer uses wl18xx. If a customer, for any reason would like to use wl18xx with any other SoM on a custom board, the COMPATIBLE_MACHINE would prevent the usage. Kindly remove this addition.

@varigigi this is to support multi-BSP setups where end customers build OE for multiple BSPs and they could have a TI based BSP and variscite based recipe, this recipe is also provided by meta-ti

I think this can be solved nicely if there was a global var-som SOC override like this but sadly, this pull has been sitting there for ages without any action.

@nsdrude
Copy link
Contributor

nsdrude commented Jun 12, 2023

I think this can be solved nicely if there was a global var-som SOC override like this but sadly, this pull has been sitting there for ages without any action.

@kraj we appreciate the feedback and pull request, we plan to introduce something like this in the next major release.

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