- Sep 29, 2022
-
-
Define a flag and enable it to build kvmtool and kvm-unit-tests for rdv2 platform. Also define a variable describing the kvmtool supported platform to help decide output directory while packaging the binary. Add the kvmtool/kvm-unit-tests build script to the original BUILD_SCRIPTS list as well allowing it to be the part of whole stack building. Signed-off-by:Sathyam Panda <sathyam.panda@arm.com> Change-Id: I55cf58c31fa038d0fefcbf1697f839296a29ae81
-
Define and add ArmVirtKvmTool package to the existing list of RD-V2 UEFI packages to build and provide firmware that can be used for UEFI based guest OS boot in a virtualized environment created with the help of kvmtool and linux KVM. Also define EDK2_OUT_DIR flag to point to the output directory to build ArmVirtKvmTool as current build-scripts don't create any ArmVirtKvmTool-$(ARCH) output directory. Signed-off-by:
-
- Sep 28, 2022
-
-
GNU GRUB autogen.sh defaults to using the python command which defaults to python2 version. This is not available on newer Linux distributions since the EOL of python2 [1]. To resolve this, override the PYTHON environment variable to python3 when building grub. [1]: https://www.python.org/doc/sunset-python-2/ Note: this change will not be required when grub is updated with the latest version which includes following commit: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=8f35208db4154ede690a18e408375815bbf320b7 Signed-off-by:
Joel Goddard <Joel.Goddard@arm.com> Change-Id: I8b9b36e5ba97e07b50ecb5bdba1ac3ce90be043b
-
add-apt-repository command fails in Ubuntu 18.04. To resolve this, install software-properties-common before invoking the add-apt-repository command. In addition to that, add -y to add-apt-repository command to prevent the script from waiting for user input. Signed-off-by:Joel Goddard <joel.goddard@arm.com> Change-Id: I6572cb6ee3954f1d206212640c93002258e09cf4
-
This reverts commit 052e11c6. Linux kernel patches for SMMU Test Engine are now available and can be used with the related smmute tools scripts to test I/O virtualization use-case. So revert the change that disabled LINUX_TOOLS_IOMMU_BUILD build config. Change-Id: I506dee124c8bbd52c80fd33f4b6dec025d695c92 Signed-off-by:
Vivek Gautam <vivek.gautam@arm.com>
-
Vijayenthiran Subramaniam authored
Change the build configurations of RD-V2 based on the host machine architecture. Environment variable BUILD_MACHINE_ARCH is used for host specific changes in the configuration. Signed-off-by:Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I5dcd58db499c9e99ee1b3f3c4a151435a19f025c
-
Add rdv2 platform support in the build-test-tftf.sh script. Signed-off-by:
Shriram K <shriram.k@arm.com>
Change-Id: I47b93e9df841228ad0387ebbdfe1fd6c6767ffd2 -
Add tftf build flags in the rdv2 platform config file. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I51855884d5069693fd15550240cfe83e4070c75a
-
- Sep 27, 2022
-
-
Shriram authored
Print a message that the tftf build has completed successfully, at the end of script execution. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I2891f93df13c70b0bc481ce2d7e76ef32c7e84cd -
Shriram authored
Add a workaround for the invalid indirect expansion error encountered when the software stack is built with $UEFI_BUILD_ENABLED set to zero(eg: tftf) on a Ubuntu 20.04 machine. The error occurs when the if condition checks the value assigned to local variable $uefi_out. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: Ie8ec7c3332597175011048c2ba7a03722869434a -
Introduce platform build options: - CSS_SGI_FW_FIRST_SUPPORT: TFA build option to enable firmware first implementation on the RD-N2-Cfg1 platform. - CSS_SGI_ERR_INJ_SUPPORT: TFA build option to enable error injection support on RD-N2-Cfg1 platform. Default value is set to 1 as RD-N2-Cfg1 platform has either firmware-first or kernel-first error handling enabled. Signed-off-by:Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I39a1c3e4ef3d1120a22ffe8abcfa481a9858768c
-
Set this flag to enable kernel first error handing on RD-N2-Cfg1. This flag is disbaled by default. Signed-off-by: -
Enable build options to add firmware first error handling support for Base Element RAM on RD-N2-Cfg1 platform. Signed-off-by: -
Introduce MPAM config fragment file for rdn2cfg1. Add kernel configurations required for enabling MPAM to the file. Additionally, add the config fragment file to defconfig's config list if MPAM is enabled for the platform. Signed-off-by:Rohit Mathew <rohit.mathew@arm.com> Change-Id: I26158d822145a4d18b40e754773d7689bcab099c
-
Current build-system uses a base defconfig to build .config file for linux. Though there is a provision to pass additional config fragments, these are not properly appended to a base defconfig generated .config and are treated as separate config files altogther. The existing framework also uses an outdated config fragment path. Revise and re-introduce fragments framework. Instead of treating fragments as individual configs, treat them as additions or deletion of configs from the existing .config built from base defconfig. Make use of existing build framework to pass one or more config fragments. Fragments are appended to the .config file generated from defconfig one at a time. The kernel image is finally built with the appended .config. Signed-off-by: -
For software at lower exception levels than EL3 to access MPAM system registers without trapping, MPAM system register for EL3 should be configured accordingly. Define 'ENABLE_MPAM_FOR_LOWER_ELS' build option provided by Arm Trusted Firmware for RD-N2-Cfg1 and set it to '1' to enable MPAM access from lower ELs. Signed-off-by: -
Booting with buildroot currently experience delays due to missing entropy for /dev/random etc. Enabling RNG_TOOLS also doesn't help with buildroot. So disable the PACKAGE_URANDOM_SCRIPTS for now to avoid running the random-number-generator start-up scripts that cause the boot delay. Signed-off-by: -
Vijayenthiran Subramaniam authored
When building buildroot on a x86_64 host, BR2_TOOLCHAIN_EXTERNAL should be set to y to indicate that an external toolchain should be used to build for aarch64 target. Add a new x86_64 host specific config fragment for buildroot and move out the x86_64 host specific config into this file from the defconfig file. Signed-off-by: -
Vijayenthiran Subramaniam authored
Buildroot can be build on both x86_64 and aarch64 host machines. The config files required to build on either of these host machines can be different. In order to support build of buildroot on both x86_64 and aarch64 host machines, add support to pick config fragments specific to the host machines and merge them with the base configuration. Once the merge is done, delete the config file which is copied to the buildroot's configs folder. With this support, $BUILDROOT_DEFCONFIG file will hold the configs that is common across both architectures. $BUILDROOT_X86_64_HOST_CONFIG file can hold configs that are specific to x86_64 host and $BUILDROOT_AARCH64_HOST_CONFIG file can hold configs that are specific to aarch64 host. Signed-off-by: -
Vijayenthiran Subramaniam authored
Previously mkfs.ext3 was used to create an ext3 partition on a zero-filled raw image file and then mount that partition to a mount point using fuse-ext2 tool. The Linux and ramdisk images were then copied to this mount point. fusermount tool was used to sync the contents and unmount the partition. Also, tune2fs utility was needed to assign the UUID for this partition. fuse-ext2 tool is not available for AArch64 host machines by default. To avoid this dependency, a single mkfs.ext3 command is used to create an ext3 partition with UUID out of the raw image file. Signed-off-by:
-
- Sep 26, 2022
-
-
Add rdn2cfg1 platform support in the build-test-tftf.sh script. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I6b9c385464627860cf0345f89ac95c5daec307b6 -
Add tftf build flags in the rdn2cfg1 platform config file. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: Icccec8cdcb3c1908e7a5b30a564591b306e65f90 -
Add rdn2 platform support in the build-test-tftf.sh script. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I51db26230e64b5106707d06eeadb1b9cff11a390 -
Add tftf build flags in the rdn2 platform config file. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I02652cc2beaec96835a6713f8e171934e26c9ddd -
Add rdv1 platform support in the build-test-tftf.sh script. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I531eb15a73ec28f6bf184c079d3700636ef3c919 -
Add tftf build flags in the rdv1 platform config file. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: Ifd75428edec17cb8b344dab5e4b20319e88826a7 -
If a platform defines $ARM_TF_BUILD_VARIANT in the platform config file, extract the platform variant flag and pass it to the TF-A build script by appending it to the $ARM_TF_BUILD_FLAGS. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: Idf6f3dd232a36283dcf5ed5e9d883fb6e6e19a65 -
Add support for $TFTF_PLATFORM_VARIANT flag in the build-tftf.sh script. The TFTF build system uses this flag to determine the platform variant. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I6f8e12786c090912fdce778acf37abfc26a93dd2 -
Add the $TFTF_BUILD_ENABLED flag in the config file for the platforms that support TFTF. The build-test-tftf.sh script sets this flag. This flag can be manually enabled in the config file to allow clean/build/package the TFTF component separately using build-tftf.sh script. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I60d925b946da9670a00d95219bd137ded8770f0e -
The $LINUX_COMPILER variable from the platform config includes $TOP_DIR by default. Hence remove the extra $TOP_DIR included by the build-tftf.sh while assigning $LINUX_COMPILER environment variable to the $CROSS_COMPILE. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: Ib01bf9ca7a2c46a8cacd53e00fb79152d7765e5a -
Changes to restructure the build-test-linuxboot.sh script: 1. Use Go version 1.17.11 and use the tag v0.9.0 to clone u-root repo. 2. Add seperate functions to install Golang, u-root and add checks in the setup functions to remove directories in case of incomplete installations/setup-failures. This enables the script to setup/build the components separately. 3. Add explicit command in linuxboot-uroot-automation.sh script to create mount point before mounting the stage-2 linuxboot disk image to avoid mounting-related failures. Signed-off-by:Shriram K <shriram.k@arm.com>
Change-Id: I54c5d5c0a08ac0fbadcef2a78bc8e9abf8b37492
-
- Sep 23, 2022
-
-
Vijayenthiran Subramaniam authored
install_gcc_toolchain function is called only for x86_64 host machines. Since install_libfdt function call is inside install_gcc_toolchain function, it won't be called for aarch64 host machine. Hence move out install_libfdt function call outside. Also, use the parameter passed to the install_libfdt function only for x86_64 host as the aarch64 host uses preinstalled gcc. Signed-off-by: -
This patch introduces two major changes to build-test-acs.sh. The first change is to build only the platform binaries and not to build the ACS disk image from source. And hence recommend to use the prebuilt ACS image downloaded from github for the test. The prebuilt image is available at: https://github.com/ARM-software/arm-systemready/tree/main/SR The second change is to disable RAS functionality, as RAS requires the external aborts and SErrors to be handled by EL3. This is not recommended for SBSA test. Change-Id: Ie84cc1ec00d4968f4e45bc919de78386476a73b3 Signed-off-by:
Pranav Madhu <pranav.madhu@arm.com> -
Move build-test-acs.sh into sgi folder. Change-Id: I86458ab142f9d1a43b7e52cc0a54fe372a2c8f57 Signed-off-by:Pranav Madhu <pranav.madhu@arm.com> -
Neoverse Reference Design platform RD-Edmunds has been renamed to RD-V2 and all corresponding references have been changed. Signed-off-by:
-
- Sep 22, 2022
-
-
Sathyam Panda authored
Move a copy of smmute test application to the platform's output directory so that it can be available for testing. Also cleanup the respective tools path, where smmute test binary is copied, during clean up. Signed-off-by:
-
Sathyam Panda authored
Add helper function to download, build and install LIBFDT library for GCC 11.2 toolchain. This library is required for the building of kvmtool. Signed-off-by: -
Sathyam Panda authored
Define a flag and enable it to build kvmtool and kvm-unit-tests for rdn2cfg1 platform. Also define a variable describing the kvmtool supported platform to help decide output directory while packaging the binary. Add the kvmtool/kvm-unit-tests build script to the original BUILD_SCRIPTS list as well allowing it to be the part of whole stack building. Signed-off-by: -
Sathyam Panda authored
Define a flag and enable it to build kvmtool and kvm-unit-tests for rdn2 platform. Also define a variable describing the kvmtool supported platform to help decide output directory while packaging the binary. Add the kvmtool/kvm-unit-tests build script to the original BUILD_SCRIPTS list as well allowing it to be the part of whole stack building. Signed-off-by: -
Sathyam Panda authored
Add a script to build, clean and package kvmtool which is used to setup Linux KVM based virtual machines on a Linux host OS. Also add provision to build, clean and package kvm-unit-tests which is used to carry out unit testing for Linux KVM hypervisor. Signed-off-by:
-
