-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support for SoloKeys v2 #3
Comments
The last time I asked, I was told me they don't want to write a fwupd plugin and want to do their own thing instead. 🙁 |
That's not an entirely accurate summary of our conversation, Richard. We definitely want our own tooling (lib/CLI/GUI), because there's more to a Solo 2 than just updates. But we clearly see the value in updates via fwupd, and are working towards supporting this for Solo 2, with the surrounding effort it entails. |
Okay, let me know if there's something you want me to review. Perhaps it's not as disappointing as I thought. |
@hughsie There was a reason to remove support for SoloKeys v1 in the latest release? |
@mhalano it was a good chunk of code that was being shipped to millions of computers that SoloKey said they weren't going to use. |
@nickray Can we do something related to update of this chunk of code and make support for SoloKey v1 good again? |
Solo 1 support in fwupd would be a separate issue. It never actually worked, and we're not working towards this. |
I saw in the latest firmware the support for SoloKeys v1 was removed. Which is a bummer, I think. But could we have support for the new SoloKeys v2?
The text was updated successfully, but these errors were encountered: