FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-12-16T20:21:56Z 2020-12-16T20:21:56Z Mitchell Horne mhorne@FreeBSD.org 2020-12-16T20:21:56Z urn:sha1:d8462732ce74ccaf077dac625168cfa75f4a3b7e Leave more room for bootloaders at the beginning of the image. In particular, the u-boot files for the HiFive Unleashed are ~5MB in size. 2020-12-16T18:40:49Z Glen Barber gjb@FreeBSD.org 2020-12-16T18:40:49Z urn:sha1:d3df64ad991881a50dd2b4e58c16e69958cf0f3b snapshot builds. Sponsored by: Rubicon Communications, LLC (netgate.com) 2020-12-15T15:13:06Z Emmanuel Vadot manu@FreeBSD.org 2020-12-15T15:13:06Z urn:sha1:ff9c6d3f09d14b02b30a7f1bbf0613a8a23ec0f5 We now have a u-boot port and config.txt for booting on all 64bits variant of the RPI boards (RPI2v1.1, RPI3* and RPI4*) so use the new u-boot-rpi-arm64 and the config_arm64.txt files. Discussed with: karels, kevans 2020-12-09T20:38:26Z Glen Barber gjb@FreeBSD.org 2020-12-09T20:38:26Z urn:sha1:4708d329f8932d5cd87a56a417b647a6fef2708d Sponsored by: Rubicon Communications, LLC (netgate.com) 2020-12-09T02:21:25Z Glen Barber gjb@FreeBSD.org 2020-12-09T02:21:25Z urn:sha1:5523003a4cb036c64a3e2b61221c647582c0fafc directory to allow properly building *.iso and *.img files. Sponsored by: Rubicon Communications, LLC (netgate.com) 2020-12-08T00:48:50Z Mitchell Horne mhorne@FreeBSD.org 2020-12-08T00:48:50Z urn:sha1:3083b412e9fe246d325006f0b00bd63bd4f7445f For platforms that don't have any of the memstick, cdrom, or dvdrom release images (i.e. riscv64), the release-install target will trip up when invoking md5(1) on the non-existent image files. Skipping this allows the install to complete successfully. 2020-12-08T00:42:03Z Mitchell Horne mhorne@FreeBSD.org 2020-12-08T00:42:03Z urn:sha1:a0b9e2e854027e6ff61fb075a1309dbc71c42b54 Add two release flavors for RISC-V. First, the traditional "big-iron" images, capable of generating distribution sets and VM images. Installer images won't be built yet, but can be trivially enabled in the future with the addition of riscv/make-memstick.sh. Second, a GENERICSD embedded image. I've opted for this instead of board-specific SD card images as it allows users to just dd the u-boot they want. The RISC-V hardware ecosystem is still young, so a configuration for e.g. the new PolarFire SoC Icicle Kit would likely see very few users. Reviewed by: gjb Relnotes: yes Differential Revision: https://reviews.freebsd.org/D27045 2020-12-08T00:37:11Z Mitchell Horne mhorne@FreeBSD.org 2020-12-08T00:37:11Z urn:sha1:d46a2a0013e1b0293d5c25c487f76a22b681072f RISC-V has the same booting requirements as arm64 (loader.efi, no legacy boot options), so generated images for both architectures have the same partition layout. Reviewed by: gjb Differential Revision: https://reviews.freebsd.org/D27044 2020-12-08T00:35:13Z Mitchell Horne mhorne@FreeBSD.org 2020-12-08T00:35:13Z urn:sha1:86635d499298956e08e9ac8edc4bd8cdfa5e4587 Since the few existing RISC-V hardware platforms are single board computers, we can piggyback off of arm/arm64's embedded build support for generating SD card images. I don't see a pressing need to change the naming in this file at this time. Reviewed by: gjb, manu Differential Revision: https://reviews.freebsd.org/D27043 2020-11-24T17:53:13Z Emmanuel Vadot manu@FreeBSD.org 2020-11-24T17:53:13Z urn:sha1:e6b9cee76b14d687fb7ee6e37f381349b749401b Both RPI2 and BEAGLEBONE are still popular and used arm boards. Both u-boots can coexist as they are named differently and live in the fat partition. This leave us with only one image that can be used for both of those boards and all the other ones supported by FreeBSD provided that you install the correct u-boot on it. Reviewed by: imp Relnotes: yes Differential Revision: https://reviews.freebsd.org/D27283