You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: topic/k2c-qli-build-ga/addn_host_setup_build_firmware.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Install and configure the software tools on the Ubuntu host computer.
16
16
pipx ensurepath
17
17
pipx install kas
18
18
19
-
#. Optionally download the kas-container script. kas is the tool used by Qualcomm Linux to sync and build the Yocto meta layers. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated evironment, consider using kas-container instead.
19
+
#. Optionally download the kas-container script. kas is the tool used by Qualcomm Linux to sync and build the Yocto meta layers. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated environment, consider using kas-container instead.
Copy file name to clipboardExpand all lines: topic/k2c-qli-build-ga/build_from_source_github.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Install and configure the required software tools on the Ubuntu host computer.
19
19
pipx ensurepath
20
20
pipx install kas
21
21
22
-
#. Optionally download the kas-container script. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated evironment, consider using kas-container instead.
22
+
#. Optionally download the kas-container script. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated environment, consider using kas-container instead.
Copy file name to clipboardExpand all lines: topic/k2c-qli-build-ga/build_with_firmware.rst
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -450,19 +450,19 @@ Build firmware
450
450
451
451
.. rubric:: CPUCP firmware
452
452
453
-
The CPUCP firmware is released as a binary and build compilation isn't required.
453
+
Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
454
454
455
455
.. rubric:: CPUSYS.VM firmware
456
456
457
-
The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
457
+
Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
458
458
459
459
.. rubric:: BTFM firmware
460
460
461
-
The BTFM firmware is released as a binary and build compilation isn't required.
461
+
Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
462
462
463
463
.. rubric:: WLAN firmware
464
464
465
-
The WLAN firmware is released as a binary and build compilation isn't required.
465
+
Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
466
466
467
467
.. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)
468
468
@@ -740,19 +740,19 @@ Build firmware
740
740
741
741
.. rubric:: CPUCP firmware
742
742
743
-
The CPUCP firmware is released as a binary and build compilation isn't required.
743
+
Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
744
744
745
745
.. rubric:: CPUSYS.VM firmware
746
746
747
-
The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
747
+
Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
748
748
749
749
.. rubric:: BTFM firmware
750
750
751
-
The BTFM firmware is released as a binary and build compilation isn't required.
751
+
Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
752
752
753
753
.. rubric:: WLAN firmware
754
754
755
-
The WLAN firmware is released as a binary and build compilation isn't required.
755
+
Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
756
756
757
757
.. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)
758
758
@@ -767,7 +767,7 @@ Build firmware
767
767
cd <FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCS9100.LE.1.0/common/build
768
768
python build.py --imf
769
769
770
-
- Firmware prebuild is successful if the following zip files are generated in the ``<FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCM6490.LE.1.0/common/build/ufs/bin`` directory:
770
+
- Firmware prebuild is successful if the following zip files are generated in the ``<FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCS9100.LE.1.0/common/build/ufs/bin`` directory:
771
771
772
772
- ``QCS9100_bootbinaries.zip``
773
773
- ``QCS9100_dspso.zip``
@@ -1030,19 +1030,19 @@ Build firmware
1030
1030
1031
1031
.. rubric:: CPUCP firmware
1032
1032
1033
-
The CPUCP firmware is released as a binary and build compilation isn't required.
1033
+
Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
1034
1034
1035
1035
.. rubric:: CPUSYS.VM firmware
1036
1036
1037
-
The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
1037
+
Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
1038
1038
1039
1039
.. rubric:: BTFM firmware
1040
1040
1041
-
The BTFM firmware is released as a binary and build compilation isn't required.
1041
+
Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
1042
1042
1043
1043
.. rubric:: WLAN firmware
1044
1044
1045
-
The WLAN firmware is released as a binary and build compilation isn't required.
1045
+
Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
1046
1046
1047
1047
.. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)
0 commit comments