project: help-wanted: get rid of unexplained errors item

Diagnostic messages aren't errors.

Signed-off-by: James Calligeros <[email protected]>

Author: chadmed

docs/project/help-wanted.md

@@ -15,4 +15,3 @@ any questions or are in need of assistance.
 | Extend tipd driver | **Unclaimed** | Add support to reset other Apple Silicon machines, and to enable serial, to [tipd](https://github.com/AsahiLinux/linux/blob/asahi/drivers/usb/typec/tipd/core.c). On the Macs, some parts of the USB specification are implemented by (undocumented) CD321x chips, similar to [TPS65982](https://www.ti.com/lit/ds/symlink/tps65982.pdf). Apple added some [debugging features](../hw/soc/usb-pd.md) to their Type-C ports, and if we want to make use of those when running Linux on an M1/M2 host for development (connected to another M1/M2 machine being the target of experimentation), we need to extend the `tipd` driver. | suggested by sven |
 | Bluetooth suspend | **Unclaimed** | Currently, when suspending and then resuming Bluetooth breaks. This is either an issue with the way hci_bcm4377 uses the bluetooth suspend API or we are missing some special vendor-specific commands before suspend or after resume. It's probably possible to figure this out without making the hypervisor survive a full suspend/resume cycle by using Apple's PacketLogger which is part of the "Additional Tools for XCode" to look for additional commands. It's probably also a good idea to compare how hci_bcm4377 suspend works to other Bluetooth drivers since it's also possible that it's just misusing some API that gets the device stuck in a wrong state. | sven |
 | Keyboard layout cleanup (XKB/hid_apple) | Unclaimed | Apple keyboard support across the Linux desktop stack has been hit-and-miss, across layouts and hardware keyboards. Since our keyboard drivers are not upstream yet, we have the chance to do some major cleanup. In particular, the keyboards on these machines have a soft *Fn* key that is handled entirely in software. The `hid_apple` driver currently does this in the kernel, but this is the wrong approach. This key should be handled in userspace in XKB/Wayland (Xorg cannot do it, but it's deprecated), so that we can have more comprehensive Fn key mappings including letting users customize the key bindings like they would any other modifier key, or offer special symbols like macOS does. This should probably be done by introducing new XKB keyboard models, which do this mapping in userspace. To test this, use the `fnmode=0` module parameter for `hid_apple` to disable all Fn key processing. We will later want to introduce a new fnmode that *only* does Fn key combination emulation for the edit keys (insert/delete/home/end/pgup/pgdown), which is the minimum required for a usable TTY and Xorg, and leave the rest to XKB, defaulting to this mode on Apple Silicon machines. Besides the Fn story, there are also many regional Mac layouts that need to be fixed in XKB configuration, and everyone with a non-English keyboard is welcome to help out with that effort. [Relevant xkeyboard-config issue](https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/379)| marcan |
-| Various unexplained errors | Unclaimed | As of asahi-6.8.10-4, there continue to be a variety of low-severity messages logged in the dmesg.  They don't appear to prevent proper functioning, but someone with kernel debugging experience should track them down and submit fixes for them.  Here are [some examples](https://gist.github.com/zzywysm/d4f1669ff3b7454e2821a65e31c511e1) from a M1 MacBook Air, found by running `sudo dmesg`. | ? |