aboutsummaryrefslogtreecommitdiffstats
path: root/conf/machine
AgeCommit message (Collapse)Author
2024-03-07rock-5[ab]: use regular yocto kernelTrevor Woerner
Upstream kernel support for both the rock-5a and rock-5b landed in version 6.5. Nanbield contained linux-yocto recipes for both 6.1 and 6.5 so it was best to simply have these MACHINEs use linux-yocto-dev. Post-nanbield oecore master only has a recipe for 6.6 (so far), therefore these two MACHINEs can use linux-yocto by default, instead of linux-yocto-dev. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2024-02-26remove /boot partitionTrevor Woerner
In order to boot successfully, most Rockchip SoCs require a specific partitioning scheme which was defined many years (and many SoCs) ago. That partitioning scheme places the SPL and U-Boot at specific offsets at the start of the boot block device: https://opensource.rock-chips.com/wiki_Partitions The Rockchip partitioning scheme goes on to also define the locations of a number of additional partitions, including the "boot" and "root" partitions. Since both the SPL and U-Boot have already been placed on the block device, the "boot" partition only contains the extlinux config file and the kernel+dtb/fitImage; it doesn't contain any bootloader artifacts (other than the extlinux config). The location of the SPL partition is a hard dependency since the BOOTROM etched inside the Rockchip SoCs is programmed to load and run a validated binary it finds at this location. The locations of the "boot" and "root" partitions are not so rigid since it is U-Boot which interacts with them. U-Boot is very flexible with how it finds boot components, and in its support for various devices, filesystems, sizes, etc. Both oe-core's U-Boot metadata and wic's bootimg-partition script contain logic to generate the extlinux pieces required for a bootloader to boot a Linux system. If both are enabled, the wic pieces silently clobber the U-Boot pieces. However, the mechanisms contained in the U-Boot metadata are much more flexible, from a user's point of view, than the mechanisms in wic's bootimg-partition. If a user wishes to setup some sort of A/B redundant update mechanism, they must have redundant root partitions (in order to update their filesystem contents) but they also need to have redundant boot partitions if they wish to update the kernel as part of their update mechanism. Pairing redundant kernel partitions with redundant filesystem partitions becomes unnecessarily complicated. Therefore it makes sense to combine the kernel and the filesystem into the same partition so that both the kernel and filesystem are updated, or rolled back, in lock-step as one unit. Specific kernel versions and configurations often have dependencies on user-space components and versions. The /boot location is not going away. This patch simply transfers responsibility for its creation to the more flexible U-Boot mechanism and includes the kernel as part of the same partition as the root filesystem. Not only does it add flexibility, it also makes update schemes more straightforward. Although having a separate /boot partition is a "requirement" of the Rockchip partitioning scheme, it is not an actual hard requirement when using a flexible, open-source bootloader (such as U-Boot) instead of using Rockchip's proprietary miniloader, preloader, and trust.img. Build-tested for all boards. Run-tested on: nanopi-m4-2gb, nanopi-m4b, nanopi-r2s, nanopi-r4s, roc-rk3328-cc, rock-3a, rock-5a, rock-5b, rock-pi-4b, rock-pi-e, rock-pi-s, rock64 Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2024-01-29allow user-provided WKS_FILETrevor Woerner
Allow the user to provide their own WKS_FILE in situations where they want a different layout (e.g. to support A/B updates). Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2024-01-24KERNEL_DEVICETREE: 32-bit re-orgTrevor Woerner
The upstream kernel reorganized the 32-bit arch/arm device-tree directory structure to separate out the device-trees by manufacturer (similar to the organization of the arch/arm64 device-trees). Update the references to 32-bit arm device-trees to match. This patch can now be applied since all pre-6.5-rc1 kernels have been removed from oe-core. NOTE: trying to build a post-6.5-rc1 32-bit kernel with this patch applied will fail Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Stephen Chen <stephen@radxa.com>
2024-01-20rock-4c-plus: addStephen Chen
ROCK 4C Plus is a Rockchip RK3399-T based SBC from Radxa. Specs: - Rockchip RK3399-T, 2x Cortex-A72 @ 1.5GHz, 4x Cortex-A53@1GHz - Mali T860MP4 GPU - RaspberryPi 4 form factor - 64bit LPDDR4 - eMMC - Micro SD - SPI Nor Flash - Two Micro-HDMI (HDMI 4K and HDMI 2K) - 4-lane MIPI DSI - MIPI CSI - GbE LAN with Power over Ethernet (PoE) support - Wi-Fi 5 and BT5.0 wireless module - 3.5mm headphone jack - Four USB ports (two USB2.0 and two USB3.0) - RTC - LEDs - Power button - Pwm fan - 40-pin color expansion header https://wiki.radxa.com/Rock4/4cplus Signed-off-by: Stephen Chen <stephen@radxa.com>
2024-01-20rock-3a: addTrevor Woerner
The ROCK 3A has an rpi form factor and features: - 4x Cortex-A55 ARM processor - Mali G52 GPU - 0.8TOPS NPU - 32bit 3200Mb/s LPDDR4, up to 4K@60 - HDMI, MIPI DSI, MIPI CSI - 3.5mm jack with mic - USB Port - GbE LAN - PCIe 3.0, PCIe 2.0 - 40-pin color expansion header - RTC - supports USB PD and QC powering https://wiki.radxa.com/Rock3/3a Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Anthony Davies <anthony.t.davies@gmail.com>
2024-01-20orangepi-5-plus: addAbhisit Sangjan
The Orange Pi 5 Plus is an RK3588-based SBC featuring: - Rockchip RK3588 4x Cortex-A76, 4x Cortex-A55 - Mali-G610 - 6TOPS NPU - 2x 2.5G ethernet ports – onboard NIC connected to PCIe 2.0 interface - 2x USB 2.0 host ports - 2x USB 3.0 host ports (exposed over USB 3.0 hub) - Type-C port featuring USB 2.0/3.0 and Alt-DP mode - PCIe 2.0/USB 2.0/I2S/I2C/UART on E.KEY socket - RTC - ES8388 on-board sound codec – jack in/out, onboard mic, speaker amplifier - SPI NOR flash - RGB LED (R is always on) - IR receiver - PCIe 3.0 on the bottom for NVMe, etc. - 40pin GPIO header (with gpio, I2C, SPI, PWM, UART) - Power, recovery and Mask ROM buttons - 2x HDMI out, 1x HDMI in - Slots/connectors for eMMC, uSD card, fan, MIPI CSI/DSI - 4 GB, 8 GB, 16 GB and 32 GB of RAM http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-5-plus.html Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Abhisit Sangjan <abhisit.sangjan@gmail.com>
2024-01-17roc-rk3308-cc: addTrevor Woerner
The T-Firefly ROC-RK3308-CC is a miniature and compact main board which is equipped with a cost-effective RK3308 Core Processor and a high-performance CODEC. Features: - Rockchip RK3308, 64-bit, quad-core, Arm Cortex-A35 processor @ 1.3GHz - 100M ethernet - PoE - USB 2.0 and Type-C (OTG and power) - 802.11 b/g/n WiFi and Bluetooth 4.2 https://en.t-firefly.com/product/rocrk3308cc Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2024-01-17roc-rk3328-cc: addTrevor Woerner
AKA the "renegade" The ROC-RK3328-CC platform is built on the Rockchip RK3328 system-on-chip optimized for low cost, low power, and high performance IO. It features a high performance native USB 3.0 interface and Gigabit MAC. Specs: - RaspberryPi 2/3 form factor - quad-core ARM Cortex-A53 @ 1.5GHz - ARM Mali-450 MP2 - DDR4 RAM - USB 3.0 - GbE MAC https://libre.computer/products/roc-rk3328-cc/ https://wiki.t-firefly.com/ROC-RK3328-CC/intro.html Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-12-18rock-5a: addStephen Chen
The Radxa ROCK 5 Model A is an SBC in roughly a RaspberryPi-ish form factor packed with a wide range of class-leading functionality, features and expansion options. The ROCK 5A board comes in several LPDDR4x RAM memory options: 4GB, 8GB, 16GB, and 32GB. It uses the Rockchip RK3588S SoC (quad A76 @ 2.2GHz + quad A55 @ 1.8GHz, Mali G610mp4 GPU), has both 8k and 4k HDMI, Gb ethernet with PoE support, USB2/3, M.2 E Key (NVMe or SATA), a 40-pin RaspberryPi-ish 3V3 GPIO header, USB Type-C power, MIPI DSI/CSI, SDcard slot, optional eMMC, and more. https://wiki.radxa.com/Rock5/5b https://radxa.com/products/rock5/5a/ [ with the following tweaks by Trevor: - switch to information URL to one that points to information in english - improved the commit message - add rock-5a to README ] Signed-off-by: Stephen Chen <stephen@radxa.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-11-16allow KERNEL_IMAGETYPE overrideAnthony Davies
Update machine include files to allow overriding of KERNEL_IMAGETYPE. [ with the following 2 tweaks by Trevor: - remove the "v3" from the commit's subject - extended patch to rk3308 and rk3588s, which were added in between this patch being submitted, and this patch being applied ] Signed-off-by: Anthony Davies <anthony.t.davies@gmail.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-11-02rock-pi-s: addTrevor Woerner
ROCK Pi S is a Rockchip RK3308 based SBC from Radxa. It contains a 64-bit quad core processor, USB, ethernet, wireless connectivity, and voice detection engine in 1.7-inches square. The ROCK Pi S comes in two RAM sizes 256MB or 512MB DDR3, and uses an sdmmc card for OS and storage. Optionally, some versions of the ROCK Pi S provide on-board storage via 1Gb/2Gb/4Gb/8Gb of SLC NAND flash. "S" stands for "small square" since the total board size of the rock-pi-s is 1.7-inches square. This BSP assumes booting from sdmmc, and using ttyS0 for the serial console (similar to Raspberry Pi). The latest version of the binary ddr initializer code from rkbin does not provide a uart0 option, therefore all diagnostic output from rkbin and u-boot is lost on the console (and replaced with a stream of gibberish until the Linux kernel starts). Therefore, by default, the build assumes the user would prefer to see this information and have the option to interact with U-Boot, which means an older version of rkbin is used. The user can override this decision by setting: RKBIN_RK3308_LATEST = "1" Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-10-30nanopi-m4b: addTrevor Woerner
NanoPi M4B is a RK3399-based (dual-core A72, quad-core A53 with NEON) board in the same form factor as the RPi B3+ (including compatible connectors) with onboard 2.4/5.0 dual-band WiFi + Bluetooth 5.0 with USB type-C power from FriendlyElec. https://www.friendlyelec.com/index.php?route=product/product&product_id=275 Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-10-02nanopi-r2s: addTrevor Woerner
The NanoPi R2S is a mini router with edge computing and dual GbE ports by FriendlyElec. It is based on the Rockchip RK3328 - a quad A53 core, 64-bit SoC running at 1.2GHz with at least 1GB of DDR4 RAM. It has one USB 2.0 host and is powered via a USB type-C connector (5V/2A). https://www.friendlyelec.com/index.php?route=product/product&product_id=282 Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-10-02rock-pi-e.conf: remove redundant MACHINEOVERRIDESTrevor Woerner
The MACHINE name is already added to the MACHINEOVERRIDES implicitly, no need to add it explicitly. Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-09-29rock-5b: addTrevor Woerner
Add support for the Radxa Rock 5B https://wiki.radxa.com/Rock5/5b The device-tree for this board is better in the 6.5 (and later) kernels, therefore set the kernel to linux-yocto-dev for now (eventually this won't be needed as linux-yocto moves forward). Unfortunately the TF-A project does not currently have support for the rk3588. Therefore, for the time-being, the only way to supply a TPL/DDR-init for the rk3588 is to use the closed-source rkbin binaries from Rockchip. If/when TF-A adds support for the rk3588 we can investigate switching. The rk3588 comes in two variants: rk3588 and rk3588s. The "s" option is a stripped-down version of the rk3588. In the Linux kernel these two SoCs are kept separate, with the rk3588 building on the rk3588s, so we've mimicked that same behaviour here. Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-09-21nanopi-r4s: addTrevor Woerner
Add a MACHINE definition for the FriendlyElec NanoPi R4S https://www.friendlyelec.com/index.php?route=product/product&product_id=284 Include a device-tree patch to enable the 2nd PCIe ethernet. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-09-16linux-yocto: remove non-rockchip archsTrevor Woerner
Remove the non-rockchip architectures from the kernel build since these are all a waste of build time, filesystem space, and runtime memory. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2023-01-30rock-pi-4: remove MACHINETrevor Woerner
The last kernel to not split the rock-pi-4[abc] MACHINEs into separate device trees was 5.10. The linux-yocto kernels supported in this release are all after 5.10. Therefore remove the rock-pi-4 MACHINE. By now, on master, everyone should be selecting specific MACHINEs from one of the variants and not using "rock-pi-4". NOTE: this layer will continue to use "rock-pi-4" as a MACHINEOVERRIDE when the specific variant doesn't matter Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2022-11-21rockchip.wic.inc: let wic update fstab againlangdaleQuentin Schulz
The commit ed3a97f7b2e4 ("rockchip-wic.inc: don't let wic edit fstab") removing this ability was introduced to fix an issue in the wic tool in OE-Core in which wic partitions whose "mountpoint" is not a valid path are still added to fstab. This was eventually fixed in OE-Core in commit 7aa678ce804c ("wic:direct.py: ignore invalid mountpoints during fstab update") which is part of release Honister (3.4) and later. Therefore, it should be safe to now let wic update fstab again for partitions with a valid mountpoint path. The benefit being that the wic partitions with a mountpoint are now automounted at boot. Cc: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
2022-11-21rockchip-defaults: remove xf86-input-keyboardTrevor Woerner
xf86-input-keyboard was removed from openembedded-core at its commit: f1d7c33b64 (xf86-input-keyboard: remove the recipe, 2022-07-20). Therefore remove it from the XSERVER definition. Reviewed-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2022-10-20add support for PX30 SoCQuentin Schulz
Rockchip PX30 SoC is a quad-core ARM Cortex-A35 CPU fully implementing the ARMv8-A instruction set with ARM Neon Advanced SIMD and Cryptography Extensions. This adds a base configuration file which can be included by PX30-based boards and the required changes in U-Boot and TF-A for proper support. Cc: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
2022-03-08wic: add e2fsprogs dependencyTrevor Woerner
Started seeing the following error in my builds: ERROR: A native program mkfs.ext4 required to build the image was not found Please make sure wic-tools have e2fsprogs-native in its DEPENDS Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-12-13override syntax fixupTrevor Woerner
The _virtual notation is not an override. These syntax "fixes" need to be reverted. In the case of the kernel override, when it was added, the rock-pi-e needed the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel will suffice. So this mistake actually switched the rock-pi-e from linux-yocto-dev back to linux-yocto inadvertently but at a time when linux-yocto-dev was no longer required. In the case of the bootloader overrides, u-boot was always the default, so these overrides were always redundant. Therefore, in the end, simply removing these overrides is the best way forward (considering these aren't doing anything, and the builds are working fine regardless). Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-10-05nanopi-m4: add common overrideTrevor Woerner
Add a common override for both nanopi-m4 MACHINEs. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-10-05include/nanopi-m4: remove KMACHINETrevor Woerner
There is no "nanopi-m4" defined in any yocto kernel metadata (yet?), therefore remove this superfluous line. Build (core-image-base) and run tested (both systemd and sysvinit) on: - nanopi-m4 Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-09-25rockchip-wic.inc: don't let wic edit fstabMarkus Volk
For a while we've noticed that /etc/fstab ends up with "junk" appended to the end e.g.: /dev/sda1 loader1 vfat defaults 0 0 /dev/sda2 reserved1 vfat defaults 0 0 /dev/sda3 reserved2 vfat defaults 0 0 /dev/sda4 loader2 vfat defaults 0 0 /dev/sda5 atf vfat defaults 0 0 /dev/sda6 /boot vfat defaults 0 0 In most cases this doesn't appear to affect the systems negatively. However, with the recent patch to switch to UUIDs [0aa5e600: "use uuid instead of hard-coding root device"] this started becoming an issue on systems using systemd. Therefore we need to stop wic from adding these junk entries so that systems continue to boot correctly. Build tested with core-image-base, nodistro, with both sysvinit and systemd for: - marsboard-rk3066 - rock2-square - firefly-rk3288 - vyasa-rk3288 - nanopi-m4[-2gb] - tinker-board[-s] - rock-pi-e - rock-pi-4[abc] - rock64 Run tested, core-image-base, both sysvinit and systemd on: - tinker-board - rock-pi-e - rock-pi-4b - rock64 Commit message updated by Trevor Woerner <twoerner@gmail.com> Tested-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: MarkusVolk <f_l_k@t-online.de>
2021-09-20use uuid instead of hard-coding root deviceTrevor Woerner
Recent upstream kernel changes have made the mmc probing order unpredictable. Therefore, boards with both an emmc and sdmmc interface aren't guaranteed to boot with a hard-coded root device selected. For example, on the rock64, with linux-yocto 5.10.y, using the uSD card (i.e. the sdmmc interface) about 50% of the time the boot would succeed, and roughly 50% of the time it wouldn't: ... [ 0.612233] Waiting for root device /dev/mmcblk1p7... [ 0.634551] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 0.639064] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ di) [ 0.640007] mmc0: new high speed SDXC card at address 5048 [ 0.641176] mmcblk0: mmc0:5048 SD64G 58.0 GiB [ 0.647610] random: fast init done [ 0.648279] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 0.648941] GPT:376479 != 121634815 [ 0.649252] GPT:Alternate GPT header not at the end of the disk. [ 0.649796] GPT:376479 != 121634815 [ 0.650106] GPT: Use GNU Parted to correct GPT errors. [ 0.650598] mmcblk0: p1 p2 p3 p4 p5 p6 p7 NOTE the discrepancy between the kernel waiting for device /dev/mmcblk1p7, which comes from the hard-coded kernel cmdline, and the kernel probing putting the sdmmc on mmcblk0. With linux-yocto 5.13.y on the rock64 using the uSD card the board would never boot, the sdmmc always appears on mmcblk0. Instead of simply changing the hard-coded root device (i.e. from mmcblk0 to mmcblk1) switch to using partition UUIDs instead. Hard-coding the boot device would work with 5.13.y but would fail 50% of the time with 5.10.y; who knows what other kernels will do? In any case, switching to UUIDs works regardless of board, kernel, or available mmc interfaces. Boot tested on: - rock64 - nanopi-m4-2gb - tinker-board - rock-pi-e - rock-pi-4b Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-08-19machines: Adjust for new location of tune files in coreKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2021-08-04switch to the new bitbake OVERRIDE syntaxTrevor Woerner
With bitbake commit 7dcf317cc141dc980634f8c18bfa84f83e57206a ("bitbake: Switch to using new override syntax"), applied on Aug 2, 2021, the OVERRIDE separator is now a colon instead of an underscore. Therefore all builds performed with a bitbake before this change must use a meta-rockchip commit before this one, and any builds performed with a bitbake after this change must use a meta-rockchip starting from this commit onwards. Build-tested for all meta-rockchip MACHINEs. Run tested on: - tinker-board - nanopi-m4-2gb - rock64 - rock-pi-4b - rock-pi-e The tinker-board and rock-pi-e work fine. The rest of the boards seem to have a, hopefully unrelated, issue running a 5.13-yocto-standard kernel. However, all boards work with the 5.10-yocto-standard kernel. Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2021-07-26remove LINUX_VERSION_EXTENSIONTrevor Woerner
Adding "-rockchip" to the Linux kernel name implies, to me anyway, that this is a vendor kernel. The PREFERRED_PROVIDERs of all kernels specified in this BSP are upstream linux-yocto kernels, not vendor kernels. Therefore remove the version name extension to avoid confusion. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-07-26rock-pi-e: update preferred kernelTrevor Woerner
The latest updates to linux-yocto-dev now include support for the rock-pi-e so do away with our custom recipe and use the one from oe-core. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-30wic/wks cleanupTrevor Woerner
By exporting a couple more variables the wks file for every rockchip device can be built from one template instead of having separate wks files for each board and platform. The following BSP variables were checked before and after this change to make sure they remained valid/sensible: - WKS_FILE - UBOOT_SUFFIX - SPL_BINARY - IMAGE_FSTYPES Built-tested for every MACHINE in this BSP. Run-tested on the following devices to ensure they continue to boot correctly to a cmdline (core-image-base): - tinker-board - rock-pi-e - rock-pi-4b - rock64 - nanopi-m4-2gb Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-30IMAGE_FSTYPES: remove ext4Trevor Woerner
The ext4 IMAGE_FSTYPES does not need to be mentioned explicitly. It will be automatically generated in cases where it is needed. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-30conf/machine/include/nanopi-m4.inc: add full include pathTrevor Woerner
Specify the full include path to the rk3399.inc file. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-28conf/machine/include/rockchip-wic.inc: createTrevor Woerner
Create a conf/machine/include/rockchip-wic.inc file to contain all the common wic/wks things for easy inclusion by any MACHINEs that use wic for their image creation. NOTE: the wic image type of rock-pi-e changed from "wic.xz" to "wic" which matches all the other meta-rockchip MACHINEs that use wic The following variables were checked before and after to make sure they remain correct/sensible: - IMAGE_FSTYPES - WKS_FILE_DEPENDS - IMAGE_BOOT_FILES - RK_CONSOLE_BAUD - RK_CONSOLE_DEVICE - RK_BOOT_DEVICE - SERIAL_CONSOLES - WICVARS Build-tested for all currently-defined MACHINEs. Boot-tested on the following boards to make sure they continue to boot to a console correctly (core-image-base): - tinker-board - rock64 - rock-pi-4b - rock-pi-e - nanopi-m4-2gb Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-27console cleanupTrevor Woerner
Consolidate all the various console definitions to the common conf/machine/include/rockchip-defaults.inc file and create RK_CONSOLE_BAUD and RK_CONSOLE_DEVICE variables that can be reused in the wks files. The following variables were checked before and after this patch to make sure they are sensible: - SERIAL_CONSOLES - RK_CONSOLE_DEVICE - RK_CONSOLE_BAUD A boot test was performed on the following boards to make sure they all continue to boot to a cmdline: - tinker-board - rock-pi-e - nanopi-m4-2gb - rock64 - rock-pi-4b Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-23rock-pi-e: use common rk3328.incTrevor Woerner
Now that there is a second rk3328-based MACHINE (rock64) switch rock-pi-e to use the common rk3328 include. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-06-17rock64: add machineYann Dirson
This is a RK3328 board from Pine64. Board details at https://wiki.pine64.org/wiki/ROCK64. Default image is built to boot from SD-card. Building an image for eMMC requires to set RK_BOOT_DEVICE="mmcblk0". Signed-off-by: Yann Dirson <yann@blade-group.com>
2021-05-04NanoPi-M4: declare "usbhost" and "serial" in MACHINE_FEATURESYann Dirson
Signed-off-by: Yann Dirson <yann@blade-group.com>
2021-05-04NanoPi-M4: let all variants use the same KMACHINE typeYann Dirson
This will allow us to define a single set of kernel BSP for all variants of the board (which only need to differ in u-boot dts). Signed-off-by: Yann Dirson <yann@blade-group.com>
2021-03-23NanoPi-M4: add machinesYann Dirson
We have two board variants, respectively with 2GB and 4GB RAM. Signed-off-by: Yann Dirson <yann@blade-group.com>
2021-03-04tinker board: refactor machine configTrevor Woerner
Create a common conf/machine/include/tinker.inc and re-spin - conf/machine/tinker-board.conf - conf/machine-tinker-board-s.conf to just contain the differences. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-02-26rock-pi-e: addTrevor Woerner
Add support for Radxa's ROCK Pi E device https://wiki.radxa.com/RockpiE It's a great surprise to find upstream U-Boot and the Linux kernel already provide support for this board! On the kernel side this support was added in 5.11. However, that support is so new that even linux-yocto-dev (which is based on 5.11) doesn't include the commits that add support for this board yet. As a result I've added a custom Linux kernel recipe (linux-stable-bleeding) which should, in time, become unnecessary. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2021-01-29rock-pi-4: Split our variant machinesJoshua Watt
Splits out the three variants of the rock-pi-4 (A, B & C) into their own machines. Unfortunately, it is not possible to have a single machine that works for all three, as there isn't any known ways for the bootloader to distinguish them. The old rock-pi-4 machine is kept around for use with older kernels Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
2020-06-25Use TF-A recipe from meta-armJoshua Watt
Converts the build to pull the canonical TF-A recipe from meta-arm instead of duplicating it in this layer. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
2020-04-19Use linux-yocto kernel from OE-coreJoshua Watt
Updates all machines to use the linux-yocto kernel from OE-core instead of maintaining distinct kernels in this repository. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
2020-02-14veyron-speedy: remove machineTrevor Woerner
This MACHINE hasn't built successfully in a long time. Remove it, and everything associated with it that isn't used anywhere else. Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2020-02-11Allow to override WKS_FILE variableSergey 'Jin' Bostandzhyan
Currently machine configs define the partition layout for each machine by setting the WKS_FILE variable. However, there are situations where it may be needed to use a different, non default layout. To simplify such configurations we will set WKS_FILE using ?= so that it can be easily overriden in local configurations. Signed-off-by: Sergey Bostandzhyan <jin@mediatomb.cc>
2020-02-11Add tinker-board-s machine configurationSergey 'Jin' Bostandzhyan
Asus Tinker Board-S has emmc on mmcblk1, this is also the default configuration when building the image. If you need an image for booting from the sd card set RK_BOOT_DEVICE to mmcblk0 Signed-off-by: Sergey Bostandzhyan <jin@mediatomb.cc>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-26 07:57:57 +0000