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

Add support for loongarch64 #1

Open
wants to merge 204 commits into
base: la64/main
Choose a base branch
from
Open

Add support for loongarch64 #1

wants to merge 204 commits into from

Conversation

yetist
Copy link

@yetist yetist commented May 12, 2022

可编译,可执行,但功能需要固件配合做测试

sam412081go and others added 25 commits November 24, 2023 06:42
If the frontend quits or crashes then there is nothing that is able to handle
the interactive request. This means that fwupd would wait for potentially a few
minutes blocking all other requests until timing out.
While trying to fix a casting error, I accidentally broke 64 bit return
addresses entirely.

Fixes: 5bb7ab8 ("trivial: amd-gpu: fix a casting error on 32 bit x86")
Logically it's a bit weird for the engine to create the per-system context,
and it makes the self tests so much slower.
The logic here is that we want to be able to add some HWIDs to a blocklist,
e.g. in the dbx case there is at least one machine that gets bricked by
attempting the dbx upgrade.
We've been doing this mostly correct on the LVFS for the last 3 years, but I
think it's a good idea to check client side too.
The plugin currently applies to all devices that support fastboot
protocol, but it has been reported that this can conflict with
some other applications that use fastboot via other software.

As fwupd only is used for updating modems with fastboot, require
explicit quirks to each modem that can support it instead of anything
that supports the fastboot protocol.
superm1 and others added 29 commits December 26, 2023 11:34
The debugger attachment needs the correct path in `dist`.
In order to populate security attributes it will be required to still
exist.

Fixes: fwupd#6576
The `esp-list` command normally fetches data using udisks2, but if
the user has set up `EspLocation` in `/etc/fwupd/fwupd.conf` it isn't
used. Start the engine so that the conffile is parsed and used as well.

Fixes: fwupd#6565
This fixes using vscode wrappers on Fedora.
Get the device family from firmware file, using the hardware if possible.
Some multi-GB firmware is impractical to load in memory and should instead be
streamed from disk or the device node.
…open flags

Old versions of fwupd used to start with OPEN_READ|OPEN_WRITE and then plugins
would set the new flags to be correct. This doesn't work very well when there
are subclassed devices that want to *inherit* flags, rather than having to set
all the same flags as the baseclass.
The factory firmware for the goodixmoc fingerprint readers appears to
have a bug that it doesn't come back after an update even when succesful.

As this is "expected" behavior set the will-disappear and needs-reboot
flags so this isn't flagged as a failure.

Link: https://community.frame.work/t/beta-lvfs-fingerprint-reader-firmware-for-framework-laptop-13-13th-gen-intel-core-amd-7040-series-fingerprint-reader-on-fedora-39-and-ubuntu-22-04/41898
In most cases mmap is blocked by the CONFIG_IO_STRICT_DEVMEM config option.

This means we now need a system reboot for updates to take effect.

Fixes fwupd#6243
This allows subclassed plugins to get the name from `fu_device_get_name()`
These have the same DPCD as the upstream port, but they might not
really have a downstream MST hub connected.

Fixes: fwupd#6578
The flag was duplicated, and we were setting the _internal_ flag in the jabra
plugin, and checking the _private_ flag in the dfu plugin.

Fixes fwupd#5381
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 this pull request may close these issues.