I noticed you forked nixos-hardware. I am curious if you're trying to build the july RC of u-boot for starfive2? I would prefer to use it over the starfive fork. Figured I'd ask instead of potentially duplicating efforts.

It seems like the build process around the opensbi/dynamic_fw.img is a bit changed, I haven't quite gotten it all building yet.

Lately I've been working with the Milk-V Duo, which is a low-cost Pico-sized SBC with some solid capabilities. The current build system uses Buildroot as well as some other tools to build a custom image. The only real problem with this system is it's only effective if you clean out the repository and clone it again. Do you think that it would be feasible and more effective to port NixOS to the Duo as opposed to using the Buildroot system?

Hi!

Thanks for this resource.

Just wanted to point this out: StarFive VisionFive 2 SBC Now Supports TianoCore EDK II (UEFI) (rvspace.org)

I'm not sure how hard it would be to use nixpkgs's edk2 infra to build this, but I thought you might find it interesting, or worth packaging.

Does it make sense to have the u-boot visionfive2 package generate and output the visionfive2_fw_payload.img file?

This is what the user guide uses for upgrading u-boot in place, which is my goal.

the fcff4f7 introduced a bug witch result in:

error: anonymous function at /nix/store/5c6y44wg6vpp0r6kpxl4c2abmrwm4b1q-source/starfive/visionfive/v2/opensbi.nix:1:1 called with unexpected argument 'withPayload'

       at /nix/store/wvms094v8gmkff7wfs05p1zmzdvzc4mk-source/lib/customisation.nix:74:16:

           73|     let
           74|       result = f origArgs;
             |                ^
           75|
(use '--show-trace' to show detailed location information)

hey @NickCao -- I've been checking out your work, and I can see end0 and end1 come up, but I'm not getting any connectivity. known issue?