Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(firmware_recipes): Add firmware recipes according to platform #9

Merged
merged 3 commits into from
Apr 11, 2024

Conversation

miguelafsilva5
Copy link
Member

PR Description

This PR introduces 2 new recipes for the firmware of currently supported platforms (qemu-aarch64-virt and qemu-riscv64-virt).

The goal of this PR is to ease process of developing and understanding/reading the main recipes (up until this points, these were the default.nix). Instead of requiring the user to specify which firmware packages are required in the top level, the idea is to have the firmware recipe selected according to the platform (variable passed to nix via command line, either in the python or make commands). Following is the ideal application of these recipes in a default.nix.

    firmware = callPackage ./bao-nix/pkgs/firmware/${platform}.nix
    {
        inherit toolchain;
        inherit platform;
    };

Furthermore, it removes an unused variable from the openSBI inputs. This was causing errors for the new recipes as these do not have access to the bao package.

This recipe assigns atf and u-boot as its dependencies forcing their builds
through their own recipes.
During the installPhase, this recipe copies the binaries generated to proper
directory.

Signed-off-by: Miguel Silva <[email protected]>
This recipe assigns openSBI as its dependency forcing its build through
its own recipe.
During the installPhase, this recipe copies the binaries generated to proper
directory.

Signed-off-by: Miguel Silva <[email protected]>
@miguelafsilva5 miguelafsilva5 merged commit 8599c6b into main Apr 11, 2024
2 checks passed
@miguelafsilva5 miguelafsilva5 deleted the feat/firmware_recipe branch April 11, 2024 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants