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

Include fwupd support status in HCL #9659

Open
rocodes opened this issue Dec 19, 2024 · 0 comments
Open

Include fwupd support status in HCL #9659

rocodes opened this issue Dec 19, 2024 · 0 comments
Labels
C: doc C: other C: website P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@rocodes
Copy link

rocodes commented Dec 19, 2024

How to file a helpful issue

The problem you're addressing (if any)

With built-in firmware update support, it could be nice to include either a written mention of this as another recommended criteria in the "system requirements" page https://www.qubes-os.org/doc/system-requirements/, and/or potentially as a column in the hcl itself (for example, matching against https://fwupd.org/).

Unfortunately, not all vendors in LVFS provide solid or timely support. For example, users with HP laptops report that HP lags behind in terms of what is made available to non-Windows users, and the manual update process is ...painful. But it would be great to make it easier for users to figure out which laptops are likely to have support via qubes-fwupdmgr.

The solution you'd like

Users can learn from one place (the HCL) if they are likely to have a smooth support story when purchasing a laptop, including for firmware updates.

The value to a user, and who that user might be

User trying to make a confident decision about Qubes compatibility for a new laptop purchase

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@rocodes rocodes added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: doc C: other C: website P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

2 participants