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.

Sign up for GitHub

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

Jump to bottom

Phase out support for bitaxeMax in future firmware updates #310

Open
skot opened this issue Aug 28, 2024 · 4 comments · May be fixed by #331
Open

Phase out support for bitaxeMax in future firmware updates #310

skot opened this issue Aug 28, 2024 · 4 comments · May be fixed by #331
Assignees
@skot @WantClue
Labels
enhancement New feature or request

Comments

@skot
Copy link
Owner

skot commented Aug 28, 2024

we can do this with a json file in the releases that specifies the minimum HW revision required to run the update. Then AxeOS needs a change to implement this.

This is paired with the esp-miner firmware migration the bitaxeorg GitHub org
@skot skot added the enhancement New feature or request label Aug 28, 2024
@jddebug
Copy link

jddebug commented Aug 29, 2024

Why phase out support? I have a lot of these. They have only recently become stable.

@benjamin-wilson
Copy link
Collaborator

Why phase out support? I have a lot of these. They have only recently become stable.

The Max was one of the earliest working bitaxes and did not have a large number of sales when compared to the Ultra and Supra. We believe it has reached a state of stability and now is a good time to sunset any more development. Support for older ASICs adds complexity, bloat and maintenance costs that burdens development of new Bitaxe versions.

@skot
Copy link
Owner Author

skot commented Aug 30, 2024

We may want to phase out new update support for some of the earlier Ultras too.. So this JSON should allow for hardware revision number based filtering

@WantClue WantClue linked a pull request Sep 8, 2024 that will close this issue
Test update asic model identifier #331
Open
@Kubaaaaaaaaaa
Copy link

Why phase out support? I have a lot of these. They have only recently become stable.

The Max was one of the earliest working bitaxes and did not have a large number of sales when compared to the Ultra and Supra. We believe it has reached a state of stability and now is a good time to sunset any more development. Support for older ASICs adds complexity, bloat and maintenance costs that burdens development of new Bitaxe versions.

But there could be some UI enhancements in the future that even owners of old MAXs could benefits from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skot skot

@WantClue WantClue

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Test update asic model identifier WantClue/ESP-Miner-WantClue
5 participants
@skot @benjamin-wilson @jddebug @WantClue @Kubaaaaaaaaaa