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

Linux-Firmware Install Directory Problem - Variscite #86

Open
waddle77 opened this issue Jun 3, 2022 · 0 comments
Open

Linux-Firmware Install Directory Problem - Variscite #86

waddle77 opened this issue Jun 3, 2022 · 0 comments

Comments

@waddle77
Copy link
Contributor

waddle77 commented Jun 3, 2022

When building with a Variscite board I noticed that Variscite appends an install procedure that copies a lot of necessary files for the wilink8 build to a folder called ti-connectivity. The issue seems to be that the root build (poky/meta/recipes-kernel/linux-firmware/linux-firmware.bb) runs an install procedure that expects the correct directory (sans Variscite append). To mitigate this problem, we had to go into the variscite meta folder and make the following change inside the do_install() function:

install -d ${D}${nonarch_base_libdir}/firmware/bcm
install -m 0755 ${WORKDIR}/lib/firmware/brcm/* ${D}${nonarch_base_libdir}/firmware/brcm/
# install -m 0755 ${WORKDIR}/tibt/initscripts/TIInit_*.bts ${D}${nonarch_base_libdir}/firmware/ti-connectivity
# install -m 0755 ${WORKDIR}/tiwlan/*.bin ${D}${nonarch_base_libdir}/firmware/ti-connectivity
# install -m 0755 ${WORKDIR}/wl1271-nvs.bin ${D}${nonarch_base_libdir}/firmware/ti-connectivity

Not sure how best to approach this fix. Maybe we need to contact variscite and see if our build system is just skipping something important. What I did was comment out the last 3 lines to stop those copies from happening.

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

No branches or pull requests

1 participant