aboutsummaryrefslogtreecommitdiff
path: root/release/riscv
Commit message (Collapse)AuthorAgeFilesLines
* release: Consistently use variables for invoking certain toolsBojan Novković2025-07-162-14/+4
| | | | | | | | | | | | This change cleans up the inconsistent ways of invoking makefs and mkimg by making sure that these tools are invoked through their corresponding variables. This was previously only used in a few amd64 and arm64 release scripts. Sponsored by: Klara, Inc. Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D51039 Reviewed by: emaste, markj
* riscv: add firmware partitions to GENERICSD.confMitchell Horne2024-02-141-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | Create two partitions in the existing space at the beginning of the image (8MB). These are intended to hold u-boot SPL and u-boot proper. The partition types selected are compatible with SiFive boards, e.g. the HiFive Unmatched. They can easily be overridden for a platform that uses the same scheme but different partition types, e.g. the StarFive VisionFive v2. Firmware is not actually installed, this too is left for the user. It is not as simple to create the firmware partitions after the fact, e.g. with partition indices 3 and 4. It is a shortcoming of current day u-boot that the SPL loader looks for a specific partition index, rather than the partition type, meaning that we will fail to boot if partition 2 doesn't contain u-boot. Thus, our GENERICSD images become more generically usable with current RISC-V hardware/firmware platforms. Reviewed by: manu, karels, imp MFC after: 1 month Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43849
* Increase the size of riscv GENERICSD images to 6 GBMike Karels2024-01-151-1/+1
| | | | | | | | | | The stable/13 snapshot this week failed to build the riscv GENERICSD image because it ran out of space. Checking main and stable/14 snapshots, they are also low on space, around 100% or more of capacity. Increase them all from 5 GB to 6 GB. Note, this is the only riscv image configuration. Discussed with: cperciva
* Remove $FreeBSD$: one-line sh patternWarner Losh2023-08-164-4/+0
| | | | Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
* release: Support GNU stat in mkisoimages.shJessica Clarke2022-07-151-1/+5
| | | | | | | | | | | BSD stat and GNU stat differ significantly when it comes to using a custom format string, both in the option name and in the format string itself. Handle both here (assuming Linux means GNU stat rather than BSD stat). Reviewed by: brooks, gjb Obtained from: CheriBSD Differential Revision: https://reviews.freebsd.org/D35814
* release: increase IMAGE_SIZE for arm, arm64, riscvGlen Barber2022-07-131-1/+1
| | | | | | Related to: PR 264032 MFC after: 5 minutes Sponsored by: Rubicon Communications, LLC ("Netgate")
* release: Add support for building on non-FreeBSDJessica Clarke2022-02-282-4/+6
| | | | | | | | | | | | | | | | This requires two sets of changes. Firstly, for non-FreeBSD, we do not know where tools are in PATH (and it is likely that some are not in system directories and have been built as bootstrap tools during the build), so we should leave PATH alone and trust the user. Secondly, makefs needs a master.passwd for building images from a METALOG file, so pass the directory in the image tree to makefs's -N option in order to pick up a valid FreeBSD master.passwd; this is unnecessary on FreeBSD (except in the edge case of building an image that refers to users or groups not present in the host's database, which is unlikely but technically possible) but harmless so can be done unconditionally. Reviewed by: brooks, emaste, gjb Differential Revision: https://reviews.freebsd.org/D34001
* release: Support -DNO_ROOT image buildingJessica Clarke2022-02-282-13/+56
| | | | | | | | | | | | | | | | | | | | | | | | This requires a bunch of METALOG mangling to include the files we inject into the tree. The mkisoimages.sh and make-memstick.sh scripts are now called with the current directory inside the tree so that the relative paths in the METALOG match up with the current directory. The scripts do not require this when not using a METALOG, but for simplicity we always do so. The Makefile mangles the real METALOG created from the install, as those files are shared across all uses of the tree, but the shell scripts create a temporary copy of the METALOG that they mangle as their tree modifications are specific to that image. We also need to pass -D to makefs to turn any duplicate METALOG entry errors into warnings, as we have many (harmless) instances of those. Whilst dvd1.iso should work, the !NOPKG code will need more work to support this. All media will also lack mergemaster and etcupdate trees, since more work is needed to add -DNO_ROOT modes to them. Users of install media built this way will have to manually bootstrap them. Reviewed by: brooks, gjb Differential Revision: https://reviews.freebsd.org/D33999
* mkisoimages.sh: Avoid creating temporary files in the current directoryJessica Clarke2022-02-281-3/+4
| | | | | | | | | | | | Currently the current directory is the parent of the rootfs directory, but this will change in order to support NO_ROOT builds that use a metalog manifest, since those need to have the current directory be the rootfs itself in order for the relative paths to be correct, and we do not want the non-METALOG case (which passes the directory to makefs) to pick up leftover temporary .img files from a previous failed build. Reviewed by: brooks, emaste, gjb Differential Revision: https://reviews.freebsd.org/D33998
* release: riscv64 - increase GENERICSD image sizeGlen Barber2021-12-151-1/+1
| | | | Sponsored by: Rubicon Communications, LLC ("Netgate")
* release: permanently remove the 'reldoc' target and associatesGlen Barber2021-02-181-1/+0
| | | | | | | | | | | | | | | Following 7b1d1a1658ffb69eff93afc713f9e88ed8b20eac, the structure for the reldoc target has significantly changed as result of the ASCIIDoctor/Hugo migration. As the release notes related files on the installation medium are inherently out of date, purge them entirely. Discussed within: re, doceng No objection: re (silence), doceng (silence) Timeout: 2 weeks MFC after: 1 week MFC to: stable/13, stable/12, and stable/11 only Sponsored by: Rubicon Communications, LLC ("Netgate")
* riscv: increase GENERICSD gapMitchell Horne2020-12-161-1/+1
| | | | | | | | 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. Notes: svn path=/head/; revision=368705
* Copy arm64 make-memstick.sh and mkisoimages.sh to the riscvGlen Barber2020-12-092-0/+145
| | | | | | | | | directory to allow properly building *.iso and *.img files. Sponsored by: Rubicon Communications, LLC (netgate.com) Notes: svn path=/head/; revision=368476
* RISC-V release confsMitchell Horne2020-12-082-0/+24
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 Notes: svn path=/head/; revision=368423
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-02 04:16:55 +0000