forked from fwupd/fwupd
-
Notifications
You must be signed in to change notification settings - Fork 0
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
yetist
wants to merge
204
commits into
la64/main
Choose a base branch
from
dev-main
base: la64/main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes fwupd#6381 Signed-off-by: Richard Hughes <[email protected]>
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.
Alternative proposal to fwupd#6433
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.
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.
Co-authored-by: ling.chen <[email protected]> Co-authored-by: Mason Lyu <[email protected]> Co-authored-by: Jane <[email protected]>
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
`__loongarch64` is no longer used for historical reasons and should be replaced by `__loongarch_lp64` in new code. https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html#_cc_preprocessor_built_in_macro_definitions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
可编译,可执行,但功能需要固件配合做测试