Merge branch 'next'

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Peter Korsgaard
2018-12-02 08:15:26 +01:00
440 changed files with 4151 additions and 4881 deletions

View File

@@ -0,0 +1,30 @@
image efi-part.vfat {
vfat {
file startup.nsh {
image = "efi-part/startup.nsh"
}
file EFI {
image = "efi-part/EFI"
}
file Image {
image = "Image"
}
}
size = 32M
}
image disk.img {
hdimage {
}
partition boot {
partition-type = 0xEF
image = "efi-part.vfat"
}
partition root {
partition-type = 0x83
image = "rootfs.ext2"
}
}

View File

@@ -0,0 +1,6 @@
set default="0"
set timeout="5"
menuentry "Buildroot" {
linux /Image root=/dev/vda2 rootwait console=ttyAMA0
}

View File

@@ -0,0 +1,5 @@
#!/bin/sh
BOARD_DIR="$(dirname $0)"
cp -f ${BOARD_DIR}/grub.cfg ${BINARIES_DIR}/efi-part/EFI/BOOT/grub.cfg

View File

@@ -0,0 +1,34 @@
The aarch64_efi_defconfig allows to build a minimal Linux system that
can boot on all AArch64 servers providing an EFI firmware and ACPI.
Building and booting
====================
$ make aarch64_efi_defconfig
$ make
The file output/images/disk.img is a complete disk image that can be
booted, it includes the grub2 bootloader, Linux kernel and root
filesystem.
Testing under Qemu
==================
This image can also be tested using Qemu:
qemu-system-aarch64 \
-M virt \
-cpu cortex-a57 \
-m 512 \
-nographic \
-bios </path/to/QEMU_EFI.fd> \
-drive file=output/images/disk.img,if=none,format=raw,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-netdev user,id=eth0 \
-device virtio-net-device,netdev=eth0
Note that </path/to/QEMU_EFI.fd> needs to point to a valid aarch64 UEFI
firmware image for qemu.
It may be provided by your distribution as a edk2-aarch64 or AAVMF
package, in path such as /usr/share/edk2/aarch64/QEMU_EFI.fd .

View File

@@ -1,3 +1,5 @@
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
CONFIG_REGULATOR_SY8106A=y
CONFIG_DRM_SUN8I_DW_HDMI=y
CONFIG_SUN8I_DE2_CCU=y
CONFIG_SND_SUN8I_CODEC_ANALOG=y

View File

@@ -15,3 +15,6 @@ CONFIG_CFG80211_WEXT=y
# wireless drivers
CONFIG_WLAN=y
# ondemand cpufreq governor
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y

View File

@@ -0,0 +1,4 @@
label Macchiatobin Linux
kernel /boot/Image
devicetree /boot/armada-8040-mcbin.dtb
append console=ttyS0,115200n8 root=/dev/mmcblk1p1 rootwait

View File

@@ -1,3 +1,3 @@
CONFIG_MARVELL_PHY=y
CONFIG_MARVELL_10G_PHY=y
CONFIG_PHY_MVEBU_CP110_COMPHY=y
CONFIG_SFP=y

View File

@@ -0,0 +1,5 @@
#!/bin/sh
BOARD_DIR="$(dirname $0)"
install -m 0644 -D $BOARD_DIR/extlinux.conf $TARGET_DIR/boot/extlinux/extlinux.conf

View File

@@ -15,19 +15,20 @@ How to build
There are two build options: mainline support and vendor support.
For the mainline BSP, we use:
- Linux v4.15
- U-Boot v2018.01
- Linux v4.19.2
- U-Boot v2018.11
For the vendor BSP, we use the sources available from Marvell Github
page at https://github.com/MarvellEmbeddedProcessors, which uses:
- Linux v4.4.52
- U-Boot v2017.03
- Linux v4.4.120
- U-Boot v2018.03
At the moment mainline support for the board is a work in progress.
Mainline kernel 4.15 enables eth2 in 1Gb (RJ45 connector J5) and
eth0 in 10Gb (SFP connector CON15 and RJ45 connector CON16).
The vendor BSP enables more hardware features out of the box,
e.g. all the network interfaces.
At the moment mainline support for the board is a work in
progress. Mainline kernel 4.19 enables eth2 in 1Gb (RJ45 connector J5),
copper 10Gb interfaces, and automatic configuration of select SFP
modules on the SFP cages. The vendor BSP enables more hardware features
out of the box, but lacks support for SFP detection and automatic
configuration.
To use the mainline BSP run the following commands:
@@ -73,10 +74,13 @@ Insert the micro SDcard in the MacchiatoBin board and power it up.
The serial console is accessible at the micro-USB Type-B connector
marked CON9. The serial line settings are 115200 8N1.
By default U-Boot will load its environment from the SPI flash. On the
first boot SPI flash may be empty or it may contain a legacy
environment incompatible with up-to-date mainline U-Boot and
kernel. Then the following commands can be used to boot the board:
Note: the following text only applies to the vendor BSP from
solidrun_macchiatobin_marvell_defconfig.
By default Marvell provided U-Boot will load its environment from the
SPI flash. On the first boot SPI flash may be empty or it may contain a
legacy environment that prevents proper boot. Then the following
commands can be used to boot the board:
=> ext4load mmc 1:1 0x01700000 /boot/uEnv-example.txt
=> env import -t 0x01700000 $filesize

View File

@@ -0,0 +1,2 @@
CONFIG_ENV_IS_IN_MMC=y
# CONFIG_ENV_IS_IN_SPI_FLASH is not set