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

Feature request: sd:/bootorder.txt #38

Open
PlugNPush opened this issue Jan 14, 2024 · 2 comments
Open

Feature request: sd:/bootorder.txt #38

PlugNPush opened this issue Jan 14, 2024 · 2 comments

Comments

@PlugNPush
Copy link

PlugNPush commented Jan 14, 2024

Instead of hardcoding boot.firm in the main.c file, I think it would be a good idea to add a possibility to bypass it using a text file (ex: bootorder.txt) which would be able to provide a list of 1 firm file per line and detect the first one available to boot it.

This would be especially useful for using BAX firms without messing around with ordinary boot.firm locations to allow smoother updates.

Right now, I made a fork of B9S to support BAX in a hardcoded way.
I think it would be great to officially adopt this, but using a text file to specify which firm to load first and provide some flexibility.

Of course, it would always default to the hardcoded boot.firm file if no other firm is found, wether a bootorder.txt file is present or not.

@PlugNPush
Copy link
Author

I would happily provide a PR for this if I get some sort of approval for the feature itself.

@PlugNPush
Copy link
Author

I actually did not wait for the approval, I am going to use it anyways for my own use :)

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 a pull request may close this issue.

1 participant