Merge branch 'r114-dev' of ssh://gitlab.fydeos.xyz/openFyde/overlays/chromium_os-raspberry_pi into r114-dev

Author: yunshansimon

README.md

@@ -98,9 +98,9 @@ The next question gives detailed differences between these confusing terms.
 
 # Introduction
 
-This document describes how to build and run Google [Chromium OS](https://www.chromium.org/chromium-os) on Raspberry Pi 3B, 3B+, 4B and the Pi 400 personal computer kit(Pi400 hereafter), from its source code and the board overlay hosted in this repository.
+This document describes how to build and run Google [Chromium OS](https://www.chromium.org/chromium-os) on Raspberry Pi 4B, Pi 400 personal computer kit (Pi400 hereafter) and the latest Raspberry Pi 5, from its source code and the board overlay hosted in this repository. Earlier models such as Raspberry Pi 3B and 3B+ were supported in earlier releases, but we have decided to drop support because of hardware performance limitations. 
 
-These overlays and the document has been tested against Raspberry Pi 3B, 3B+, 4B and Pi400 by the FydeOS team. It **will not work** on an earlier version of the Raspberry Pi line-up.
+These overlays and the document have been tested against Raspberry Pi 3B, 3B+, 4B and Pi400 by the FydeOS team. It **will not work** on an earlier version of the Raspberry Pi line-up.
 
 ### Goal of this project
 
@@ -151,7 +151,7 @@ Shell Commands are shown with different labels to indicate whether they apply to
 * An x86_64 system to perform the build. 64-bit hardware and OS are a must. The Chromium OS is a very large project, building from the source from scratch usually takes hours to over 10 hours, depending on the system configuration.
   * CPU: we recommend using a 4-core or higher processor. The Chromium OS build process runs in parallel so more cores can help shorten build time dramatically.
 
-  * Memory: we recommend at least 16GB, plus enough swap space because for this project you will need to build Chromium from source code. Linking Chromium required between 8GB and 28GB of RAM as of March 2017, so you will run into massive swapping or OOM if you have less memory. However, if you are not building your copy of Chromium, the RAM requirements will be substantially lower at a cost of losing some of the key features provided by this project.
+  * Memory: we recommend at least 16GB, plus enough swap space because for this project you will need to build Chromium from source code. Linking Chromium required between 8GB and 28GB of RAM as of March 2017, so you will run into massive swapping or OOM if you have less memory. However, if you are not building your copy of Chromium, the RAM requirements will be substantially lower at the cost of losing some of the key features provided by this project.
 
   * Disk: at least 100GB of free space, 200GB or more is recommended. SSD could noticeably shorten the build time as there are many gigabytes of files that need to be written to and read from the disk.
 

overlay-rpi4/prebuilt.conf

@@ -1 +1 @@
-FULL_BINHOST="gs://chromeos-prebuilt/board/arm64-generic/full-R108-15134.0.0-rc1/packages/"
+# FULL_BINHOST="gs://chromeos-prebuilt/board/arm64-generic/full-R108-15134.0.0-rc1/packages/"

overlay-rpi4/scripts/board_specific_setup.sh

@@ -47,25 +47,25 @@ install_raspberrypi_bootloader() {
     kernel_img=$(ls "${ROOT}/boot/Image"*)
     target_img="${efi_dir}/kernel8_a.img"
   fi
-  mount -o "${mount_opts}"  "$1" "${efi_dir}"
+  sudo mount -o "${mount_opts}"  "$1" "${efi_dir}"
 
   info "Installing firmware, kernel and overlays"
-  cp -r "${ROOT}/firmware/rpi/"* "${efi_dir}/"
+  sudo cp -r "${ROOT}/firmware/rpi/"* "${efi_dir}/"
   modify_root $1 ${efi_dir}/cmdline.txt
   if [ -d ${ROOT}/usr/src/linux/arch/arm/boot/dts ]; then
-    cp ${ROOT}/usr/src/linux/arch/arm/boot/dts/*.dtb "${efi_dir}/"
-    cp -r ${ROOT}/usr/src/linux/arch/arm/boot/dts/overlays "${efi_dir}/"
+    sudo cp ${ROOT}/usr/src/linux/arch/arm/boot/dts/*.dtb "${efi_dir}/"
+    sudo cp -r ${ROOT}/usr/src/linux/arch/arm/boot/dts/overlays "${efi_dir}/"
   else
-    cp ${ROOT}/usr/src/linux/arch/arm64/boot/dts/broadcom/*.dtb "${efi_dir}/"
-    cp -r ${ROOT}/usr/src/linux/arch/arm64/boot/dts/overlays "${efi_dir}/"
+    sudo cp ${ROOT}/usr/src/linux/arch/arm64/boot/dts/broadcom/*.dtb "${efi_dir}/"
+    sudo cp -r ${ROOT}/usr/src/linux/arch/arm64/boot/dts/overlays "${efi_dir}/"
   fi
-  gzip -9 -c ${kernel_img} > ${target_img}
-  umount "${efi_dir}"
+  gzip -9 -c ${kernel_img} | sudo tee ${target_img} > /dev/null
+  sudo umount "${efi_dir}"
   rmdir "${efi_dir}"
 }
 
 board_setup() {
-  sudo install_raspberrypi_bootloader "$1"
+  install_raspberrypi_bootloader "$1"
   install_hybrid_mbr "$1"
 }
 

overlay-rpi5-vanilla/make.conf

@@ -1,3 +1,3 @@
 USE="${USE} vulkan"
-CHROMEOS_KERNEL_CONFIG="/mnt/host/source/src/overlays/overlay-rpi5-mini/kconfig/kernel-6_1-r114-4k-smallkernel"
+CHROMEOS_KERNEL_CONFIG="/mnt/host/source/src/overlays/overlay-rpi5-vanilla/kconfig/kernel-6_1-r114-4k-smallkernel"
 TTY_CONSOLE="ttyAMA10"

project-cros-pi/chromeos-base/fyde-chromedev-flags/fyde-chromedev-flags-0.0.1-r2.ebuild renamed to project-cros-pi/chromeos-base/fyde-chromedev-flags/fyde-chromedev-flags-0.0.1-r3.ebuild

@@ -19,4 +19,5 @@ src_prepare() {
     if use kiosk_demo; then
       CHROME_DEV_FLAGS="${CHROME_DEV_FLAGS} --force-kiosk-mode"
     fi
+    default
 }