Thomas Weißschuh

Results 271 comments of Thomas Weißschuh

I would recommend to first test the current API with my patch. That should still work and give a first hint whether my code is correct. For the sysfs-API it...

FYI I fixed a few bugs in v1 of the patch. You can find the current version of the patch here: https://git.sr.ht/~t-8ch/linux/log/mhi-firmware

I have probably the same problem. Stack trace: ``` #0 0x00007f4bad424a7f in fu_plugin_mm_device_add (plugin=plugin@entry=0x55ebc8c289f0, modem=modem@entry=0x55ebc8bf9b90) at ../fwupd-1.7.4/plugins/modem-manager/fu-plugin-modem-manager.c:231 #1 0x00007f4bad424bf0 in fu_plugin_mm_setup_manager (plugin=0x55ebc8c289f0) at ../fwupd-1.7.4/plugins/modem-manager/fu-plugin-modem-manager.c:313 #2 fu_plugin_mm_name_owner_updated (plugin=0x55ebc8c289f0) at ../fwupd-1.7.4/plugins/modem-manager/fu-plugin-modem-manager.c:329 #3...

Beginning with 5.19 the kernel will ["make life miserable for split lockers"](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b041b525dab95352fbd666b14dc73ab898df465f).

Thanks for the report! I won't do anything about it right now, as beginning with 6.5 the whole allowlist and `force_load` will completely go away. So `force_load=1` will effectively will...

Unfortunately anything involving `acpi_enforce_resources=lax` is a complete no-go for upstream defaults.

If someone figures out how to change RPM values via WMI this would absolutely be a candidate for this driver. I was not able to do so far.