build other jh7100 components from source?

[colemickens]

Is it possible to build these components from source, which you pull binary releases for?

I guess there might not be a huge up-side, but it'd be sweet if they were built from source and you could just use the bare repos as the flake inputs and get "auto" updates for all the components.

But then again, this brings me back to the same issue I've hit with rpi+tow-boot, where I wound up baking every last bit of the firmware into the tow-boot repo so that it was self-contained. It always feels weird to have device-specific repos and then pull firmware bits from nixpkgs, to me anyway.

[colemickens]

referring to these, of course:

• https://github.com/starfive-tech/JH7100_ddrinit
• https://github.com/starfive-tech/JH7100_secondBoot
• https://github.com/starfive-tech/bootloader_recovery

from:

    jh7100_ddrinit = {
      url = "https://github.com/starfive-tech/JH7100_ddrinit/releases/download/ddrinit-2133-211102/ddrinit-2133-211102.bin.out";
      flake = false;
    };
    jh7100_secondBoot = {
      url = "https://github.com/starfive-tech/JH7100_secondBoot/releases/download/bootloader-211102_VisionFive_JH7100/bootloader-JH7100-211102.bin.out";
      flake = false;
    };
    jh7100_recovery_binary = {
      url = "https://github.com/starfive-tech/bootloader_recovery/releases/download/JH7100_recovery_binary/jh7100_recovery_boot.bin";
      flake = false;
    };

[MatthewCroughan]

We cannot guarantee (unless the resulting binaries really are identical) that we would be flashing the original firmware, unless we just take the binaries they are already distributing, and likely using when flashing boards in the factory. I'm not sure it would benefit us to compile it from source, for this reason, since the point of the attribute flashOriginal is to really flash the true original. However, you're right that it would be beneficial to nix flake update and have all of the new sources made available, should things change upstream. It's definitely worth looking into.