#asahi-dev · 2022-07-05 09:05
joskechadmed_: internal speakers are fine for me?#asahi-dev · 2022-07-05 09:05
joskesven: ok, rebuilt#asahi-dev · 2022-07-05 09:03
joskeno debug logging seen in dmesg though#asahi-dev · 2022-07-05 09:03
joskeI do see this: https://paste.debian.net/1246228/#asahi-dev · 2022-07-05 09:03
joskealright, let me remove that now#asahi-dev · 2022-07-05 09:02
joskeaudio very choppy though#asahi-dev · 2022-07-05 09:02
joskewas able to pair with my bluetooth headset, and it plays audio#asahi-dev · 2022-07-05 09:00
joskeaha: Controller 50:ED:3C:1B:63:08 air [default]#asahi-dev · 2022-07-05 08:59
joskelet's reboot again#asahi-dev · 2022-07-05 08:58
joskeah my loglevel is on 5#asahi-dev · 2022-07-05 08:56
joskebluetooth0 name serial0 serial2 wifi0#asahi-dev · 2022-07-05 08:56
joske[jos@air linux]$ ls /sys/firmware/devicetree/base/aliases/#asahi-dev · 2022-07-05 08:55
joskeyes, it seems to load the fw#asahi-dev · 2022-07-05 08:54
joskeI just installed the fw into lib/firmware?#asahi-dev · 2022-07-05 08:54
joskeah yes, it should, I added it#asahi-dev · 2022-07-05 08:53
joskein /dev?#asahi-dev · 2022-07-05 08:52
joskeI can rebuild#asahi-dev · 2022-07-05 08:52
joskeshould#asahi-dev · 2022-07-05 08:52
joskeis this related: bcm43xx 0000:01:00.1: no calibration data available.#asahi-dev · 2022-07-05 08:51
joskesven: I did that, but I don't see any extra logging?#asahi-dev · 2022-07-05 08:45
joskeok#asahi-dev · 2022-07-05 08:45
joskebluetoothcl doesn't show anything#asahi-dev · 2022-07-05 08:45
joskesven: in your driver?#asahi-dev · 2022-07-05 08:34
joskehowever: blueman-manager 10.34.04 ERROR Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting#asahi-dev · 2022-07-05 08:32
joskepromising: bcm43xx 0000:01:00.1: enabling device (0000 -> 0002)#asahi-dev · 2022-07-05 08:21
joskethanks!#asahi-dev · 2022-07-05 08:19
joskehow can you easily run the firmware extractor only? (I've built the installer with sven's commit)#asahi-dev · 2022-07-05 08:06
josketo get the firmware#asahi-dev · 2022-07-05 08:06
joskelet's reboot#asahi-dev · 2022-07-05 08:06
joske:-)#asahi-dev · 2022-07-05 08:02
joskedoes this look right: https://paste.debian.net/1246219/#asahi-dev · 2022-07-05 07:55
joskeis it even the same chip on the air? (so I'm not losing my time...)#asahi-dev · 2022-07-05 07:54
joskelet me see if I understand how to do that for j313#asahi-dev · 2022-07-05 07:53
joskeindeed this is on the air#asahi-dev · 2022-07-05 07:53
joskeoh#asahi-dev · 2022-07-05 07:52
joskethe dts changes are in the commits of sven? I fixed the conflicts there (I hope)#asahi-dev · 2022-07-05 07:52
joskewhere can I find it? ;-)#asahi-dev · 2022-07-05 07:52
joskethen no#asahi-dev · 2022-07-05 07:51
joskej`ey: is it the same as the wifi firmware?#asahi-dev · 2022-07-05 07:46
joskeplease ignore if not supposed to work ;-)#asahi-dev · 2022-07-05 07:45
joskehttps://paste.debian.net/1246215/#asahi-dev · 2022-07-05 07:42
joskesven: I cherry-picked your bluetooth commits on top of asahi, is that supposed to work?#asahi-dev · 2022-06-30 20:59
joskeso no 16k pages for me#asahi-dev · 2022-06-30 20:58
joskeyes, right now still using chromium 98#asahi-dev · 2022-06-30 20:57
joskej`ey: I need vscode to work, so have no choice ;-)#asahi-dev · 2022-06-30 20:54
joskewell then I confirm it's working on MBA (with 4k pages iommu patch)#asahi-dev · 2022-06-30 20:53
joskej`ey: oh ok, indeed, seems based on Linus' v5.18#asahi-dev · 2022-06-30 20:51
joskefrom the tag, but the Makefile says 5.18.0#asahi-dev · 2022-06-30 20:50
joskeI built the new asahi branch (and u-boot and m1n1), and all seems fine, although I'm not sure the build was correct, uname says 5.18.0-asahi-dirty, shouldn't this say 5.18.7?