codedude/wiki
1
0
Fork 0
forked from sig_altarch/wiki
Code Pull Requests Activity

Compare commits

base: codedude:6990758bd0af66eb453b9ba22f0ba693a1c8dc07
Branches Tags
codedude:main
codedude:gh-pages
sig_altarch:main
sig_altarch:gh-pages
..
compare: codedude:43725f3488034db00d6772ab338703f38d00a777
Branches Tags
codedude:main
codedude:gh-pages
sig_altarch:main
sig_altarch:gh-pages

No commits in common. "6990758bd0af66eb453b9ba22f0ba693a1c8dc07" and "43725f3488034db00d6772ab338703f38d00a777" have entirely different histories.
6990758bd0 ... 43725f3488

10 changed files with 11 additions and 559 deletions
Show Stats Expand all files Collapse all files

15
Dockerfile
View File

@ -1,15 +0,0 @@
FROM rockylinux:9
RUN dnf update -y &&\
dnf install -y git python3-pip &&\
dnf clean all
# bind volume $CWD > /wiki exists in docker-compose.yml
RUN mkdir /wiki
COPY requirements.txt /wiki
WORKDIR /wiki
RUN pip3 install -r requirements.txt
EXPOSE 8000
CMD mkdocs serve -a 0.0.0.0:8000

23
README.md
View File

@ -1,27 +1,6 @@
# SIG/AltArch Wiki
This is a Wiki for the Rocky Linux Alternative Architectures SIG. It's an information repository that records the group efforts and findings.
The AltArch special interest group looks at porting Rocky Linux to diverse or non-traditional platforms. Think small boards (Raspberry Pi and relatives), or other processor architectures like RISC-V and armhfp (32-bit ARM).
This Wiki is browseable at **https://sig-altarch.rocky.page** .
## Contributing
Feel free to contribute to this Wiki via pull request.
You can test any changes locally by running it with Docker/Podman compose on your PC. Clone this wiki, `cd` into the folder, and run:
```
docker-compose up
```
It should build and run the wiki container. You can browse it and see your live edits by visiting `localhost:8000` .
@TODO - fill in :)
## Continuous Integration / Continuous Deployment

11
docker-compose.yml
View File

@ -1,11 +0,0 @@
version: '3.2'
services:
wiki:
volumes:
- type: bind
source: .
target: /wiki
build:
context: .
ports:
- 8000:8000

97
docs/RPi/solutions/solutions.md
View File

@ -1,97 +0,0 @@
---
title: Solutions
author: Funzi
---
# Solutions and Troubleshooting
## `dnf` always claims to require a restart
### Symptom
Even though the system has been restarted recently, e.g., after a Kernel update, `dnf needs-restarting -r` always
returns with exit code `1`.
```
# dnf needs-restarting -r
Core libraries or services have been updated since boot-up:
* dbus
* dbus-daemon
* glibc
* linux-firmware
* systemd
Reboot is required to fully utilize these updates.
More information: https://access.redhat.com/solutions/27943
```
**This affects both Rocky Linux 8 and 9.** However,
a [patch for 9.3 is to be released soon](https://github.com/rpm-software-management/dnf-plugins-core/pull/468).
### Cause
The `dnf` plugin uses the `mtime` of `/proc/1` which is set to start of epoch due to lack of RTC on Raspberry Pi. The
correct system time is set later at boot once network connectivity is established and an NTP server is reachable.
Compared to 1970, every package update is after the last reboot which causes the wrong result.
### Solution
Until 9.3 is released, or if the system is still on
8.x, [the patch](https://github.com/rpm-software-management/dnf-plugins-core/pull/468/commits/b8132e1e04fb44c9ef8ab7dbcea2d2b3b920be2c)
can be manually applied to all versions.
```
# patch /usr/lib/python3.6/site-packages/dnf-plugins/needs_restarting.py <<EOF
--- a/plugins/needs_restarting.py
+++ b/plugins/needs_restarting.py
@@ -34,6 +34,7 @@ import functools
import os
import re
import stat
+import time
# For which package updates we should recommend a reboot
@@ -199,7 +200,28 @@ class ProcessStart(object):
@staticmethod
def get_boot_time():
- return int(os.stat('/proc/1').st_mtime)
+ """
+ We have two sources from which to derive the boot time. These values vary
+ depending on containerization, existence of a Real Time Clock, etc.
+ For our purposes we want the latest derived value.
+ - st_mtime of /proc/1
+ Reflects the time the first process was run after booting
+ This works for all known cases except machines without
+ a RTC - they awake at the start of the epoch.
+ - /proc/uptime
+ Seconds field of /proc/uptime subtracted from the current time
+ Works for machines without RTC iff the current time is reasonably correct.
+ Does not work on containers which share their kernel with the
+ host - there the host kernel uptime is returned
+ """
+
+ proc_1_boot_time = int(os.stat('/proc/1').st_mtime)
+ if os.path.isfile('/proc/uptime'):
+ with open('/proc/uptime', 'rb') as f:
+ uptime = f.readline().strip().split()[0].strip()
+ proc_uptime_boot_time = int(time.time() - float(uptime))
+ return max(proc_1_boot_time, proc_uptime_boot_time)
+ return proc_1_boot_time
@staticmethod
def get_sc_clk_tck():
--
2.41.0
EOF
```
It is advisable to `version-lock` the plugin version until it's fixed upstream. On 8.x, that might be the only solutions
if the patch is not backported to 8.x upstream.
**Use at your own risk!**
```
# dnf versionlock add python3-dnf-plugins-core
```

150
docs/events/meeting-notes/2023-10-20.md
View File

@ -1,150 +0,0 @@
# SIG/AltArch meeting 2023-10-20
## Attendees:
* Sherif
* Bryan
* Pratham Patel
* Pablo Greco
* Alan Marshall
* Brian Clemens
* Neil Hanlon
## Discussions:
### Current Status
Originally, Skip and Pablo built rpi image and kernel. Afterwards, Sherif began working with Pablo to build a generic arm kernel for more than just RPis. GenericArm image is being built with Empanadas, but not widely used. It should support Rpi as well as others.
As a rule, we cannot rely on EPEL dependencies, and will need to pull them into our build roots. We should work on/request tooling to aid in these operations--i.e., something to identify dependencies, and perform imports of them for us.
#### Kernels
Building 5.15 and 6.1 kernels in SIG/AltArch, but will be moving them to SIG/Kernel
Will also include kernel-mainline (6.5/6.6).
#### SBCs
Recently, Bryan and Pratham began working with other SBCs like 3 Libre Computing boards, Orange Pi 5, Rock5b, Odroid purchased by RESF provided to several testers.
##### Libre boards
* are largely generic
* Rocky uboot is problematic (USB issues), but upstream uboot works w/ our kernel
* (Neil has tested this and it works great -- it's running a bunch of IOT stuff for him)
* Pratham - have we tested building from their source? or just using their uboot?
* Bryan - it's been 6-8 months since we've tried it, but it should be re-investigated
* We all recall it being a USB-related issue, but this should be confirmed.
##### Orange Pi 5
* requires 6.5-ish kernel
* nothing upstreamed in uboot yet
##### Rock5b
* requries a 6.6-rc kernel
* uboot 3.10 + some pci patches
##### Odroid
* hasn't been looked into yet
### Discussions
Pablo:
* Need to separate kernel vs uboot. We are near to the end of the year, so we are very close to a new kernel LTS being cut which will probably be based on
* re: uboot -- would like to stay as close to vanilla (Fedora) uboot as possible, but that is obviously difficult for every single board, practically. Ideally, we can build these as RPMs, just like "normal" uboot (this would also make composing images a lot easier, logistically speaking). Another option, if we have to, is to build specific binaries and provide them in a "one-off" repo to users as needed.
Sherif:
* tool like `arm-image-installer` script to download the right uboot, image, etc, and put it into the disk at the right place. basically: make it pretty fool proof
* like spi-tool (?) from Pine64
* Fedora and Debian are doing something like this
* In general, we want to have the least amount of uboots required, whatever the case
* try to port changes into a single generic uboot where possible
* tl;dr - there are *a lot* of boards. can't please everyone
Pratham - questions on Kernels
* was using elrepo kernels to test (mainline, mostly)
* realized RHEL kernels are missing configs for booting these boards
* built kernel.org kernel, and it boots all three libre boards and the rock5b
* How to proceed from here? There are a lot of configs which need setting, e.g..
* Storytime!
* we all use the same kernel.org tarballs -- without changes
* Sherif and Pablo worked on changes to contribute to elrepo, they are very welcoming, in general.
* The configs and specs are going to be--mostly, where the Kernel contributions can be
* we should always be contributing back to elrepo, so that the entire community can benefit from the changes/features we add
* We also begin to limit the amount of backports/changes we need to do over time
* the current rocky LTS kernel is the same now as elrepo, due to the PR we've introduced
* another example - HPC sig kernel
* stripped down kernel for compute nodes, based on the Rocky base kernel with patches
* openpatch :D
* https://elrepo.org/bugs/view.php?id=1345
* We should document this and our policy on upstreaming work to ELRepo for Kernel changes.
* tl;dr - base work on elrepo and make PRs there, then bring them into SIG/Kernel
#### Generic Image
* Pablo - some boards look for grub binaries in a _highly_ specific location, and we need to make sure that we make a copy of those (links) into those locations
* i.e., their uboots aren't looking for grubx64.efi in the right place
* Neil - We can announce the availability of this more generally in our 9.3 / 8.9 releases coming in November.
### alternative alternative architctures
#### 32 bit arm (armhfp/arm7vl)
* We are looking for hardware which we can use to do these builds. We have some VMs currently, but they are not quite powerful enough.
* OSU OSL should have some Lenovo eMags for us, at some point.
* Neil to reach out to Ramareth
* Neil to reach out to Aaron from Ampere
* If we can't get anything from OSU, let's ping SolidRun or Ampere to see if they can do anything for us and figure it ourselves.
#### riscv
* right now, it takes 2+ days to build gcc in qemu
* there have been a lot of good changes in qemu to add more support but we should try and do native builds if possible.
* Neil - Investigate what and how much riscv hardware we need.. and where we'll host it
* https://www.crowdsupply.com/milk-v/milk-v-pioneer
## Decisions
* Images should be generic so as to be able to be installed on any board, where possible.
* uboot can live on SPI or external flash
* We need to help document this for our users and have guides on how to get the SBCs working. This is a big pain point for many SBC users as there is so much variation.
* To this end, we should investigate some tooling to aid in writing images for boards which will boot on the first try.
* Uboot should similarly be generic and work for all boards, insofar as it is practical to do so.
* Some boards this doesn't make sense for, e.g., ones that have uboot from 2014 + hundreds of patches, however, these are few and far between. For these, we can package them as RPMs and provide them (see note below re: licensing)
* We will wait for the next Kernel.org LTS to be cut, as that should have all the changes for the boards we're talking about.
* We will engage with our upstreams (Fedora, ELRepo, etc) for changes we make with the Kernel SIG for AltArch/SBC support.
* This necessitates participating in SIG/Kernel to represent our needs in these kernels.
* We should strive to perform native builds when possible, but recognize that emulation is a necessary evil.
!!! note "uboot and other licensing"
We need to ensure that we are careful about the licensing of softwares we wish to include in the SIG distribution.
## Action items:
* Libre Compute - Try/Investigate using vendor tree to build uboot - Pratham
* Investigate `arm-image-installer` script/tool for helping write disk images for specific boards - Sherif (?)
* Odroid N2 - Track installability
* Investigate backport of uboot configuration to work with our uboot and/or track upstreaming process
* Orange Pi 5 - Track installability
* Investigate backport of uboot configuration to work with our uboot and/or track upstreaming process
* Rock5b - Track installability
* Investigate backport of uboot configuration to work with our uboot and/or track upstreaming process
* Libre Computing Boards (3)
* Investigate backport of uboot configuration to work with our uboot and/or track upstreaming process
* Maintenance - Importing dependencies from Fedora/EPEL
* Investigate tooling for this
* Document process on backporting uboot and kernels - Pablo
* To include information on how we work and interact with upstreams, with examples! - Sherif
* Check and investigate which boards have hardcoded grubx64 paths in their uboot; address them
* Acquire armhfp (arm7vl) hardware - Neil to reach out to OSU OSL
* Neil - Investigate what and how much riscv hardware we need.. and where we'll host it
### Next Meeting
* Discuss meeting time - biweekly?
## Old business:
* N/A

103
docs/events/meeting-notes/2023-12-15.md
View File

@ -1,103 +0,0 @@
# SIG/AltArch meeting 2023-12-15
## Attendees:
* Sherif
* Bryan
* Pablo Greco
* Neil Hanlon
* Skip Grube
## Follow Ups
* Libre Compute - Try/Investigate using vendor tree to build uboot - Pratham
* Investigate `arm-image-installer` script/tool for helping write disk images for specific boards - Sherif (?)
* Odroid N2 - Track installability
* Orange Pi 5 - Track installability
* Rock5b - Track installability
* Libre Computing Boards (3)
* Maintenance - Importing dependencies from Fedora/EPEL
* Neil is working on this as part of SIG/HPC, too
* Document process on backporting uboot and kernels - Pablo
* To include information on how we work and interact with upstreams, with examples! - Sherif
* Check and investigate which boards have hardcoded grubx64 paths in their uboot; address them
## Discussions
* Neil provided Sherif with 2 RPi CM4s (+ IO boards), an RPi5, and a SiFive VF2 (RiscV) at SC23 in November
* Need to work on integrating SBC and related changes into SIG/Kernel mainline in order to have unified kernel
* Bryan has tried mainline kernel, but it isn't booting -- ends up in dracut shell.
* Will figure out how to capture logs via serial
* Libre Tritium H5
* It's all Skip's fault
* 32-bit arm (armhfp/arm7vl) Rocky Port
* Sherif has some odroid boards from work he can donate
* Odroid XU4 x2
* Odroid XU4Q x1 - XU4 w/ massive heatsink
* Current status (per Pablo)
* have the full bootstrap up to 9.1; we need to start building atop it
* need to add Peridot support for armhfp (i can't remember if we included the arch as an option)
* where will we host the odroid boards from Sherif
* Most of the SBCs for arm7vl/armhfp are not powerful enough to be good build hosts. Maybe we should try Honeycombs? (Solid-run)
* Pablo used his honeycomb and a fedora image to do the initial bootstrap builds
* Neil will reach out to OSU about availability of Lenovo eMAGs for us
* has neil spoken to Fabian? - No ; Neil will do this
* RISCv Rocky Port Status
* Neil - Investigate what and how much riscv hardware we need.. and where we'll host it
* This probably is going to be a whole bunch of VF2s
* P670 (16-core - MilkV oasis) would be great, but, upstream support is not yet there. VF2 is a better target for Rocky 9
* Various conversations happened here but Neil was dealing with keeping all the mice in his house dead. The following is second-hand :)
* Rpi Kernel - Should it live?
* We want to get rid of it, but we can't yet. Skip says yes
* Plan:
* Build the rpi kernel as a variant of the mainline
* rpi kernel will be subsumed into kernel-mainline-sbc, not further upstream
* This will allow more obvious contribution to ELrepo for SBCs
* RPI image will be replaced with a new GenericArm-SBC image produced by Empanadas which includes kernel-mainline-sbc
* Next meetings
* Dec 29 - Cancel.
* Jan 12 - Keep
## Action Items
* Neil to actually make tickets for the follow ups / decisions. But, like, for real this time.
* Neil to reach out to people re: ARMHFP hardwares
* Ampere
* OSUOSL
* Fabian (arrfab)
* Neil to figure out what RISCv hardware we need
* Announce Dec 29th meeting cancelation
## Old business
### 2023-10-20
#### Action Items
* Libre Compute - Try/Investigate using vendor tree to build uboot - Pratham
* Investigate `arm-image-installer` script/tool for helping write disk images for specific boards - Sherif (?)
* Odroid N2 - Track installability
* Orange Pi 5 - Track installability
* Rock5b - Track installability
* Libre Computing Boards (3)
* Maintenance - Importing dependencies from Fedora/EPEL
* Document process on backporting uboot and kernels - Pablo
* To include information on how we work and interact with upstreams, with examples! - Sherif
* Check and investigate which boards have hardcoded grubx64 paths in their uboot; address them
* Acquire armhfp (arm7vl) hardware - Neil to reach out to OSU OSL
* Neil - Investigate what and how much riscv hardware we need.. and where we'll host it
#### Decisions
* Images should be generic so as to be able to be installed on any board, where possible.
* uboot can live on SPI or external flash
* We need to help document this for our users and have guides on how to get the SBCs working. This is a big pain point for many SBC users as there is so much variation.
* To this end, we should investigate some tooling to aid in writing images for boards which will boot on the first try.
* Uboot should similarly be generic and work for all boards, insofar as it is practical to do so.
* Some boards this doesn't make sense for, e.g., ones that have uboot from 2014 + hundreds of patches, however, these are few and far between. For these, we can package them as RPMs and provide them (see note below re: licensing)
* We will wait for the next Kernel.org LTS to be cut, as that should have all the changes for the boards we're talking about.
* We will engage with our upstreams (Fedora, ELRepo, etc) for changes we make with the Kernel SIG for AltArch/SBC support.
* This necessitates participating in SIG/Kernel to represent our needs in these kernels.
* We should strive to perform native builds when possible, but recognize that emulation is a necessary evil.
!!! note "uboot and other licensing"
We need to ensure that we are careful about the licensing of softwares we wish to include in the SIG distribution.

89
docs/events/meeting-notes/2024-01-12.md
View File

@ -1,89 +0,0 @@
# SIG/AltArch meeting 2024-01-12
## Attendees:
* Sherif
* Bryan
* Neil Hanlon
* Skip Grube
* Jason Rodriguez
* Jonathan Maple
## Follow Ups
* SBC Testing with *vendor* uboot - https://git.resf.org/codedude/SBC-Testing
* Basically everything is working except one of the Libre boards (Frite)
* https://git.resf.org/codedude/SBC-Testing/src/branch/main/testing/details.md
* Whack-a-mole with kernel options and support for different kernels
* Might be possible to patch for RK3389, as enabling this board breaks Libre borads
* Also is possible to disable USB2 for RK3389, but this is not preferable
* Kernel Config - RHEL vs Kernel KConfigs
* SIG/Kernel kernel is based on the Fedora Rawhide branch of kernel, but uses the KConfig named ['.redhat'](https://gitlab.com/cki-project/kernel-ark/-/blob/os-build/Kconfig.redhat)
* We want to use this as a base, and change config options as needed to enable SBCs
* January 2024 UBoot is out with fixes, should help with some of the reliance on Vendor UBoots
* Bryan will work on testing new uboot with these boards for next meeting
* OSU OSL has arm hardware available for us, this will help enable armhfp/arm7vl/32-bit arm
* Hoping to have this ready to build things in the beginning of February
* RISCV hardware
* Should look at getting a few more SiFive VF2
## Open Floor
* Raspberry Pi 5 Support
* check upstream for firmware, throw into our repo, rebuild image and test
## Action Items
* Build Jan 2024 UBoot - Sherif
* Raspberry Pi 5 Support - Skip
* Order RPI 5 hardware for testers/altarch - Neil
* ~~Maybe buy this locally in London instead for Pablo~~ -- nevermind they're not in London...
* Pimironi or pihut - ship to Sherif
* Neil to actually make tickets for the follow ups / decisions. But, like, for real this time
* I'm really going to do it this week, I promise.
* Setup ARM hardware for armhfp - neil
* Neil to figure out what RISCv hardware we need
## Old business
### 2023-12-15
* Neil to actually make tickets for the follow ups / decisions. But, like, for real this time.
* Neil to reach out to people re: ARMHFP hardwares
* Ampere
* OSUOSL
* Fabian (arrfab)
* Neil to figure out what RISCv hardware we need
* Announce Dec 29th meeting cancelation
### 2023-10-20
#### Action Items
* Libre Compute - Try/Investigate using vendor tree to build uboot - Pratham
* Investigate `arm-image-installer` script/tool for helping write disk images for specific boards - Sherif (?)
* Odroid N2 - Track installability
* Orange Pi 5 - Track installability
* Rock5b - Track installability
* Libre Computing Boards (3)
* Maintenance - Importing dependencies from Fedora/EPEL
* Document process on backporting uboot and kernels - Pablo
* To include information on how we work and interact with upstreams, with examples! - Sherif
* Check and investigate which boards have hardcoded grubx64 paths in their uboot; address them
* Acquire armhfp (arm7vl) hardware - Neil to reach out to OSU OSL
* Neil - Investigate what and how much riscv hardware we need.. and where we'll host it
#### Decisions
* Images should be generic so as to be able to be installed on any board, where possible.
* uboot can live on SPI or external flash
* We need to help document this for our users and have guides on how to get the SBCs working. This is a big pain point for many SBC users as there is so much variation.
* To this end, we should investigate some tooling to aid in writing images for boards which will boot on the first try.
* Uboot should similarly be generic and work for all boards, insofar as it is practical to do so.
* Some boards this doesn't make sense for, e.g., ones that have uboot from 2014 + hundreds of patches, however, these are few and far between. For these, we can package them as RPMs and provide them (see note below re: licensing)
* We will wait for the next Kernel.org LTS to be cut, as that should have all the changes for the boards we're talking about.
* We will engage with our upstreams (Fedora, ELRepo, etc) for changes we make with the Kernel SIG for AltArch/SBC support.
* This necessitates participating in SIG/Kernel to represent our needs in these kernels.
* We should strive to perform native builds when possible, but recognize that emulation is a necessary evil.
!!! note "uboot and other licensing"
We need to ensure that we are careful about the licensing of softwares we wish to include in the SIG distribution.

46
docs/events/meeting-notes/2024-01-26.md
View File

@ -1,46 +0,0 @@
# SIG/AltArch meeting 2024-01-26
## Attendees
* Neil Hanlon
* Bryan (codedude)
* Sherif Nagy
## Follow Ups
* Jan 2024 Uboot - Sherif completed, published 18 Jan
* RPI5 - Not going great
* Fedora can't boot it either, and it's not upstream yet
* Kernel is still missing Pi5 DTB
* Armbian is working, but they're probably patching the DTB
* Skip was working on firmware, not sure of status
* Bryan has a working Kernel, but it's hacky and broken... but it works (nominally)
* SBC Testing
* Testing of new Uboot underway
* Libre Tritium H5 - works fine
* Libre Le Potato - _appears_ that Libre hasn't upstreamed their entire uboot
* 2024 uboot, lots of NIC resets; vendor firmware doesn't do this
* Fedora “recommends” using vendor uboot for Potato
* **Q**: Do we want to recommend Le Potato but with Vendor Uboot for now?
* Rock5B/OrangePi uboot patches - not actually working right
* thefossguy built a one-off uboot for the OrangePi using an upstream tool (which is possibly proprietary/non-free)
## Tickets
https://git.resf.org/sig_altarch/meta/issues/4 - Jan 2024 uboot - Closed
## Open Floor
* mainline-sbc kernel
* [ ] Neil to get documentation for Kernel Packer and start the sbc kernel config repo
* SIG/Kernel tickets for variant creation
* https://git.rockylinux.org/codedude/kernel-mainline-sbc
* [SIG/Kernel#1](https://git.resf.org/sig_kernel/meta/issues/1)
* [SIG/Kernel#7](https://git.resf.org/sig_kernel/meta/issues/7)
* [SIG/Kernel#8](https://git.resf.org/sig_kernel/meta/issues/8)
* KernelPacker needs two things:
* Spec template + KConfig
## Action Items
* [ ] Neil to get documentation for Kernel Packer and start the sbc kernel config repo

20
docs/RISCV64/visionfive_2.md → docs/riscv64/visionfive2/visionfive2.md
View File

@ -1,5 +1,5 @@
---
title: StarFive VisionFive 2
title: VisionFive 2
author: Pratham Patel
tested with: TBD
tags:
@ -20,7 +20,7 @@ This Wiki contains the necessary information a user needs to know before using R
| Item | Description |
|---------------|--------------------------------------------------------------------------------------------------------|
| Processor/SoC | StarFive JH7110 (`rv64imafdcbx` with up-to 1.5GHz max freq) |
| Processor/SoC | StarFive JH6110 (`rv64gc` with up-to 1.5GHz max freq) |
| Memory | LPDDR4: 2GB/4GB/8GB |
| Storage | SD card slot |
| | SPI flash for u-boot |
@ -68,8 +68,6 @@ To install Rocky Linux on the VisionFive 2 SBC, there is one pre-requisite that
### Pre-requisite: Update board firmware
**NOTE: PLEASE READ THESE STEPS AND CAREFULLY FOLLOW THEM. IF DONE INCORRECTLY, YOUR BOARD MAY GET BRICKED!**
1. Download the following files:
- [sdcard.img](https://github.com/starfive-tech/VisionFive2/releases/download/VF2_v2.8.0/sdcard.img) (this image is from release v2.8.0)
- [u-boot-spl.bin.normal.out](https://github.com/starfive-tech/VisionFive2/releases/download/VF2_v2.11.5/u-boot-spl.bin.normal.out)
@ -112,17 +110,3 @@ The board firmware has now been updated!
## Current things that are WIP
A Rocky Linux image :stuck_out_tongue_closed_eyes:
## Maintainers
There are several developers who are working on the RISC-V port of Rocky Linux in general, but following are all the maintainers who are supporting the VisionFive 2 SBC. These usernames are what they use on the [Rocky Linux Mattermost chat](https://chat.rockylinux.org/).
- [@codedude](https://git.resf.org/codedude)
- [@skip77](https://git.resf.org/skip)
- [@neil](https://git.resf.org/neil)
- [@pgreco](https://git.resf.org/pgreco)
- [@tgo](https://git.resf.org/tgo)
- [@mustafa](https://git.resf.org/mustafa)
- [@alangm](https://git.resf.org/alangm)
- [@sherif](https://git.resf.org/sherif)
- [@thefossguy](https://git.resf.org/thefossguy)

16
docs/support/hardware/supported.md
View File

@ -8,31 +8,31 @@ author: Bryan Z.
## Raspberry Pi SBCs
| Model | Image | Status |
|---------------|-----------------------------------|---------------|
|-------------------------------------------------------------------|
| Pi 4B | RockyLinux_Rpi_9-latest.img.xz | Complete |
| Pi 3B/B+ | RockyLinux_Rpi_9-latest.img.xz | Complete |
## Banana Pi
| Model | Status |
|---------------|---------------------------------------------------|
|-------------------------------------------------------------------|
| Unknown | Stage 1(hardware being procured) |
## Orange Pi
| Model | Status |
|---------------|---------------------------------------------------|
|-------------------------------------------------------------------|
| Unknown | Stage 1(hardware being procured) |
## Pine
| Model | Image | Status |
|---------------|----------------------------------------------------------|----------------------------------------|
|-------------------------------------------------------------------------------------------------------------------|
| Pine64 | | Stage 1(hardware being obtained) |
| RockPro64 | Rocky-9.1-aarch64-generic-Minimal-rk3399-sda.raw.tar.gz | Complete |
| A64_LTS | | Stage 1(hardware being obtained) |
## Libre Computer
| Model | Status |
|---------------|----------------------------------------------------------------|
|--------------------------------------------------------------------------------|
| Renegade | Stage 2(hw obtained, initial testing to discover whats needed) |
| La Frite | Stage 2(hw obtained, initial testing to discover whats needed) |
| Tritium | Stage 2(hw obtained, initial testing to discover whats needed) |
@ -40,10 +40,10 @@ author: Bryan Z.
## Ordoid
| Model | Status |
|---------------|-----------------------------------------------------------------|
|---------------------------------------------------------------------------------|
| N2+ | Stage 2(hw obtained, initial testing to discover what's needed) |
## Khadas
| Model | Image | Status |
|---------------|---------------------------------------------------|
| In early phases of discovery. | | |
|-------------------------------------------------------------------|
| In early phases of discovery. |