Github messages for voidlinux
 help / color / mirror / Atom feed
From: blacklightpy <blacklightpy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] riscv64-musl port
Date: Wed, 21 Feb 2024 11:53:54 +0100	[thread overview]
Message-ID: <20240221105354.84CCB289A3@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13207@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

New comment by blacklightpy on void-packages repository

https://github.com/void-linux/void-packages/pull/13207#issuecomment-1956388744

Comment:
> Today my VisionFive 2 Rev. 1.3B arrived and would like to participate. 🎉
> 
> Does anybody has some documentation on how to setup a basic void setup on this board with microSD?

@dataCobra I found this: https://old.reddit.com/r/voidlinux/comments/zl6odc/void_on_riscv/j05fnic/

Instructions for Debian from https://wiki.debian.org/InstallingDebianOn/StarFive/VisionFiveV2:
- Most of VisionFive V2 hardware support is merged to upstream Linux kernel;
- A Linux kernel fork with the patches applied is available at [github.com/yuzibo/vf2-linux](https://github.com/yuzibo/vf2-linux).
- Current support state could be followed at [RVSpace JH7110 Upstream Status page](https://rvspace.org/en/project/JH7110_Upstream_Plan).
- If you want to boot Debian sid image on vf2, you can refer to [vf2-debian-image](https://github.com/yuzibo/vf2-debian-image), which from mmdebstrap and upstream kernel with several upstream patches. (by 2023/12/27)
- An alternative option is to boot from microSD and update u-boot and firmware using *flashcp* command as described at [RVSpace Quick Start Guide](https://doc-en.rvspace.org/VisionFive2/Quick_Start_Guide/VisionFive2_SDK_QSG/spl_new.html#updating_spl_and_u_boot-vf2__section_zpj_cqt_yvb).
- You can mostly follow the instructions given for [InstallingDebianOn/StarFive/VisionFiveV1](https://wiki.debian.org/InstallingDebianOn/StarFive/VisionFiveV1).
- However, at least some u-boot versions expect `uEnv.txt` to be named `vf2_uEnv.txt` instead. 

So you'll be cross-compiling the kernel and base system with the RV64 toolchain and there maybe a bunch of patches here and there. Check out yuzibo's kernel and debian images to see if you can find anything. The image seems to be built with Docker Compose.. I haven't checked much into it, but hope this helps.

  parent reply	other threads:[~2024-02-21 10:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 11:37 [PR PATCH] " voidlinux-github
2019-07-19 13:35 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-19 13:35 ` voidlinux-github
2019-07-26 21:56 ` voidlinux-github
2019-07-27 12:58 ` voidlinux-github
2019-07-27 14:56 ` voidlinux-github
2019-07-27 15:32 ` voidlinux-github
2020-12-30 18:20 ` leahneukirchen
2020-12-31  9:26 ` Anachron
2020-12-31  9:26 ` Anachron
2021-01-03 13:35 ` advancedwebdeveloper
2021-01-15  2:56 ` HadetTheUndying
2021-06-23  7:09 ` dkwo
2022-01-14  7:05 ` jcgruenhage
2022-01-14 16:43 ` leahneukirchen
2022-03-03  6:18 ` jailbird777
2022-03-04 19:24 ` leahneukirchen
2022-03-04 22:23 ` jailbird777
2022-03-04 22:50 ` leahneukirchen
2022-06-03  2:10 ` github-actions
2022-09-02  2:15 ` github-actions
2022-09-17  2:13 ` [PR PATCH] [Closed]: " github-actions
2023-01-08 19:38 ` JamiKettunen
2023-01-14 18:26 ` leahneukirchen
2023-01-15  0:21 ` Johnnynator
2023-01-15 13:35 ` Anachron
2023-01-15 15:06 ` Johnnynator
2023-05-27 16:38 ` blacklightpy
2023-08-25 19:27 ` Anachron
2023-08-25 19:42 ` RoozbehOssia
2023-08-26 12:46 ` leahneukirchen
2023-08-26 14:36 ` [PR PATCH] [Updated] " leahneukirchen
2023-08-29 20:30 ` Anachron
2023-08-29 20:33 ` leahneukirchen
2023-08-29 21:14 ` leahneukirchen
2023-08-30  7:44 ` sug0
2023-09-03 12:10 ` blacklightpy
2023-09-03 12:16 ` blacklightpy
2023-09-03 12:21 ` blacklightpy
2023-09-03 12:50 ` blacklightpy
2023-10-10 13:35 ` Piraty
2023-10-18 21:43 ` RoozbehOssia
2024-01-17  1:46 ` github-actions
2024-01-17  3:54 ` fvalasiad
2024-02-21 10:25 ` dataCobra
2024-02-21 10:53 ` blacklightpy
2024-02-21 10:53 ` blacklightpy [this message]
2024-02-21 11:38 ` dataCobra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240221105354.84CCB289A3@inbox.vuxu.org \
    --to=blacklightpy@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).