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

[META] LVFS/fwupd adoption among board vendors #76

Open
xen0n opened this issue Jan 9, 2025 · 2 comments
Open

[META] LVFS/fwupd adoption among board vendors #76

xen0n opened this issue Jan 9, 2025 · 2 comments
Labels
AREA: Firmware Related to firmware -- UEFI, U-Boot, Type-I hypervisor, etc. 💥 RISK: Communication Issue has a risky non-technical perspective: communication needed for a friendly resolution

Comments

@xen0n
Copy link
Member

xen0n commented Jan 9, 2025

It could be more streamlined for the users to be able to obtain firmware updates from LVFS, but this would require cooperation from the board vendors, which is a non-technical issue. But Loongson may be able to upload for the several models they maintain themselves, such as the venerable XA61200, to start with.

This issue is mainly for gathering interested people and keeping everyone updated about the situation.
@xen0n xen0n added the AREA: Firmware Related to firmware -- UEFI, U-Boot, Type-I hypervisor, etc. label Jan 9, 2025
@jiegec
Copy link

jiegec commented Jan 9, 2025 •
edited
Loading

Question: can we use fwupd to upgrade firmware manually (i.e. download the .fd file and execute some commands) within Linux currently?

@xen0n xen0n added the 💥 RISK: Communication Issue has a risky non-technical perspective: communication needed for a friendly resolution label Jan 16, 2025
@xen0n
Copy link
Member Author

xen0n commented Jan 16, 2025

cc @kilaterlee @tsuibin (Loongson folks) -- this issue is unlikely to progress without 1st-party collaboration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
AREA: Firmware Related to firmware -- UEFI, U-Boot, Type-I hypervisor, etc. 💥 RISK: Communication Issue has a risky non-technical perspective: communication needed for a friendly resolution
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xen0n @jiegec