1. 18 Jan, 2021 1 commit
  2. 17 Jan, 2021 1 commit
  3. 10 Jan, 2021 1 commit
  4. 04 Jan, 2021 1 commit
  5. 30 Dec, 2020 2 commits
  6. 20 Dec, 2020 1 commit
  7. 17 Dec, 2020 2 commits
  8. 13 Dec, 2020 1 commit
  9. 08 Dec, 2020 2 commits
  10. 08 Nov, 2020 2 commits
  11. 03 Nov, 2020 2 commits
  12. 01 Nov, 2020 1 commit
  13. 28 Oct, 2020 5 commits
  14. 26 Oct, 2020 1 commit
  15. 24 Sep, 2020 1 commit
  16. 23 Jul, 2020 1 commit
  17. 22 Jul, 2020 2 commits
  18. 06 Jul, 2020 1 commit
    • Rabeeh Khoury's avatar
      u-boot features and fixes, more kernel modules · 5c7bf24b
      Rabeeh Khoury authored
      1. Manually edited patch 0018-lx... to fix atheros phy related config.
      2. Just before booting the kernel toggle back the fan full speed signal
      to enable the kernel driver to initialize the AMC6821 device
      3. Add u-boot poweroff command that set S5# (GPIO3 7) signal to low;
      thus turning off the HoneyComb / ClearFog CX boards.
      Signed-off-by: default avatarRabeeh Khoury <rabeeh@solid-run.com>
      5c7bf24b
  19. 22 Jun, 2020 2 commits
  20. 14 May, 2020 1 commit
    • Rabeeh Khoury's avatar
      Different method to install ubuntu rootfs · 914af8a1
      Rabeeh Khoury authored
      Previously multistrap was used to download and create an ubuntu rootfs;
      but multistrap failed under docker build since it required binfmt
      installed.
      
      This technique of installing ubuntu rootfs is totally different method,
      takes more time to build but works under the native runme.sh script and
      under docker build.
      
      The method idea is -
      1. Build a simple rootfs with a kernel that can be booted via
      qemu-system-aarch64.
      2. Install an initi script called S99bootstrap-ubuntu.sh under
      /etc/init.d.
      3. Run a qemu-system-aarch64 virtual machine with 1GByte of system
      memory and use cortex-a57 which is the closed to cortex-a72,
      virtualization wise and has the buildroot rootf as initrd and the
      destination ubuntu-core.ext4 partition as a drive.
      4. The VM would boot the kernel, mount the rootfs and run the
      S99bootstrap-ubuntu.sh script
      5. The script would download an ubuntu base image and then 'apt install'
      in a virtual chrooted environment the reset of the packages to make this
      rootfs to be bootable.
      6. Use 'reboot' in the VM which triggers the '-no-reboot' flag for qemu
      that makes the vm exit; and thus installation is continued.
      7. ubuntu-core.ext4 partition is now ready to be used further on for
      imaging and installations.
      Signed-off-by: default avatarRabeeh Khoury <rabeeh@solid-run.com>
      914af8a1
  21. 05 May, 2020 1 commit
  22. 04 May, 2020 1 commit
  23. 22 Apr, 2020 1 commit
  24. 13 Apr, 2020 1 commit
  25. 12 Apr, 2020 4 commits
  26. 24 Mar, 2020 1 commit
    • Rabeeh Khoury's avatar
      Unify boot images of SPI, SD and eMMC and automate RCW creation · 20848b19
      Rabeeh Khoury authored
      Using conditional load and jump in RCW and boot=auto as a parameter for
      ATF it is possible now to build a single image that can be booted from
      SPI, SD or eMMC.
      
      Still there is a small difference BL2 stage where on SPI it is located
      on address 0x0 and SD/eMMC is located with 0x1000 (8 blocks of 512
      bytes) offset.
      
      Additional feature is runtime RCW file creation; this will be further
      enhanced to create the SERDES and PLL multipliers creation in runtime
      too.
      Signed-off-by: default avatarRabeeh Khoury <rabeeh@solid-run.com>
      20848b19