Adapt the repo checking file to using the per-machine configuration
files instead of using the single config file.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Managing a single config file is difficult for distributions and is
prone to possible merge conflicts. Split the file per machine.
Suggested-by: Robie Basak <robie.basak@oss.qualcomm.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Create tarball before testing the contents, preventing extra files from
sneaking in. Also pass correct subdir for testing the instalation of the
binaries.
Reported-by: Robie Basak <robie.basak@oss.qualcomm.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Add machine mappings for:
- "Qualcomm QCS615 IQ 615 EVK"
This fixes the fastrpc library config parser warning where
DSP_LIBRARY_PATH is not found for "Qualcomm QCS615 IQ 615 EVK"
in /usr/share/qcom/conf.d/00-hexagon-dsp-binaries.yaml,
and ensures 615 EVK boards resolve the expected DSP library
directory.
Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
It doesn't make sense to check if distribution is correct if install
fails. Change the order of steps.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Latest tarball didn't include the config file. In order to prevent such
mistakes in future, perform checks on the distribution before packing
it.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Add machine mappings for:
- "Qualcomm Technologies, Inc. Lemans Ride"
- "Qualcomm Technologies, Inc. Lemans Ride Rev3"
This fixes the fastrpc library config parser warning where
DSP_LIBRARY_PATH is not found for "Qualcomm Technologies, Inc.
Lemans Ride" in /usr/share/qcom/conf.d/00-hexagon-dsp-binaries.yaml,
and ensures Lemans Ride boards resolve the expected DSP library
directory.
Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
The Qualcomm / Lantronix SDM845-HDK is an non-fused devkit using SDA845
SoC. For ADSP and CDSP we are going to reuse the existing firmware from
linux-firmware, so provide symlinks for the Hexagon DSP libraries too.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
YAML config files are required by the userspace lib in order to be able
to find DSP binaries. Add all provided config files to the generated
tarball.
Fixes#45
Reported-by: Robie Basak <robie.basak@oss.qualcomm.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
As the rest of the non-binary files, the conf file is covered by the MIT
licence. Add SPDX header to the file.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Add validation to ensure paths in config.txt exist in
00-hexagon-dsp-binaries.yaml, reporting each missing path once.
Signed-off-by: Vinayak Katoch <vkatoch@qti.qualcomm.com>
Add DSP_LIBRARY_PATH entries in a new YAML file for the
supported machines to enable consistent, machine-specific
DSP library resolution.
The machine entries are sorted alphabetically by machine name
to ensure maintainability and stability as new properties are
added in the future.
Update the Makefile to install the YAML file to the conf.d
directory alongside the DSP binaries.
Signed-off-by: Vinayak Katoch <vkatoch@qti.qualcomm.com>
Normally firmware targeting different DSPs has different DSP substrings
in versions. The SA8775P and QCS8300 platforms had the same version for
all firmware, which promted us to add cdsp- and adsp- prefixes to the
firmware subdirs.
Firmware for Hamoa follows the normal practice, which renders the cdsp-
prefix useless. Drop it in order to make Hamoa close to other platforms.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
2025-10-22 15:34:46 +03:00
623 changed files with 338 additions and 20 deletions
# Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
machines:
Qualcomm Technologies, Inc. Robotics RB3gen2:
DSP_LIBRARY_PATH:qcm6490/Thundercomm/RB3gen2/dsp
Loaded 20 of 623 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.