Provide firmware & Hexagon DSP packages for several devkits#29
Open
lumag wants to merge 12 commits into
Open
Conversation
Collaborator
|
Mind a rebase? #30 fixes a cache issue. |
Contributor
Author
done |
Provide a way to generate firmware packages for IFC6410, Inforce's APQ8064-based kit. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a way to generate firmware packages for IFC6560, Inforce's SDA660-based kit. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Contributor
Author
|
@ricardosalveti gentle ping. |
Provide a way to generate firmware packages for Open-Q 835 HDK aka HDK835, Lantronix's APQ8098-based kit. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a way to generate Hexagon DSP binary packages for IFC6560, Inforce's SDA660-based kit. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a way to generate Hexagon DSP binary packages for Open-Q 835 HDK (aka HDK835), Lantronix's APQ8098 -based kit. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a packagegroup for Inforce IFC6410. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a packagegroup for Inforce IFC6560. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Provide a packagegroup for Lantronix Open-Q 835 HDK. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Add recipe to generate separate initramfs for Inforce IFC6410 containing firmware files. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Add recipe to generate separate initramfs for Inforce IFC6550 containing firmware files. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
… initramfs Add recipe to generate separate initramfs for Lantronix Open-Q 835 HDK containing firmware files. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
In order to ensure the lack of the conflicts, pull new packagegroups into the initramfs-firmware-mega-image. Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
|
|
||
| DESCRIPTION = "QCOM Firmware for Inforce IFC6410 board" | ||
|
|
||
| LICENSE = "CLOSED" |
Collaborator
There was a problem hiding this comment.
CLOSED doesn't really mean much here, it is just to not break the build, can't we expect a valid license for these files?
Contributor
Author
There was a problem hiding this comment.
I was able to find licence files in the PDF format. Would you have any recommendations how to use them?
Contributor
Author
There was a problem hiding this comment.
|
This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow the implementation in meta-qcom and provide recipes to package firmware and Hexagon DSP binaries for several 3rd party development kits:
Historically these recipes lived in meta-qcom, but later they were remvoed, leaving on actual Qualcomm-designed hardware in that layer.