#asahi-dev · 2026-04-11 18:14
lacamar[m]xarkes: nice#asahi-dev · 2026-04-11 17:26
freetolgabut i got some other arm devices to play with ig#asahi-dev · 2026-04-11 17:26
freetolgai may be motivated but i know literally 0 about this#asahi-dev · 2026-04-11 17:25
xarkeswell I guess it's helping the overall progress on m4, what I'm doing at the moment is pretty basic tbh, compared to what's coming ahead#asahi-dev · 2026-04-11 17:23
freetolgaWhat is the goal right now for you#asahi-dev · 2026-04-11 17:21
xarkesnah, you need at least one patch in the aic driver otherwise it wont boot#asahi-dev · 2026-04-11 17:21
freetolgaDo i just take your dts, compile it with latest asahi kernel and concatenate it with m1n1?#asahi-dev · 2026-04-11 17:19
freetolgaI had some other success i shared in offtopic and im getting really bored of macos and strongly believe its holding back the m4 cpu so im motivated to try dts things with you#asahi-dev · 2026-04-11 17:18
xarkesah yeah aerm it was more like a chair <-> keyboard interface problem, but it works fine now#asahi-dev · 2026-04-11 17:17
freetolgayou were talking about your dts being unstable when you first wrote it#asahi-dev · 2026-04-11 17:17
xarkeswhat stability issue?#asahi-dev · 2026-04-11 17:16
freetolgaxarkes: only keyboard or did you fix the stability issue?#asahi-dev · 2026-04-11 16:38
fl0_idxarkes whoop whoop#asahi-dev · 2026-04-11 16:30
xarkesfinally spent some more time on m4, I now have a working keyboard#asahi-dev · 2026-04-11 13:34
chaos_princessit is already sent to ml#asahi-dev · 2026-04-11 13:32
flokliVery nice! Do you expect this to be upstreamable?#asahi-dev · 2026-04-11 11:09
jannauit was fine yesterday when testing on fedora under the hypervisor. on gentoo I experienced stutter with 2 different bt audio devices initially. It's fine now for minutes though.#asahi-dev · 2026-04-11 11:01
chaos_princessno, i've had both kde connect and the scanning ui open while playing audio and had no noticeable issues#asahi-dev · 2026-04-11 10:59
jannauchaos_princess: did you still got occasional bt audio artifacts during scanning? I initially got some but after reconnecting it's fine for minutes#asahi-dev · 2026-04-10 22:50
jannauI've tagged and pushed asahi-6.19.11-3 to github. Only change is bt audio stream priority which fixes audio stuttering, new config CONFIG_BT_BRCMEXT=y#asahi-dev · 2026-04-10 22:06
jannau+0x2000 looks to be wdt's raw counter, it appears to be read-only#asahi-dev · 2026-04-10 21:06
yukaAnd I can't write anything to +0x2004, it just stays as 0x000000#asahi-dev · 2026-04-10 21:03
yukaso yeah I can keep resetting the cur_time to 0 for all the three watchdogs (+0x0, +0x10, +0x20), but then it still reboots after ~120sec#asahi-dev · 2026-04-10 20:59
yukajannau: what is +0x2000 in your opinion? the kernel driver doesn't use or mention it#asahi-dev · 2026-04-10 20:34
jannauI've seen it at 0xb1f..... just before reboot. reset either through a reset signal or power-gating#asahi-dev · 2026-04-10 20:22
yukabecause for me it's at 0xaf[something] before it reboots#asahi-dev · 2026-04-10 20:22
yukaResets = wraps around?#asahi-dev · 2026-04-10 20:21
jannaupmu.info-fault_log is all zero even after an wdt timeout. possible that iboot resets that#asahi-dev · 2026-04-10 20:15
jannaureboot is ~125 seconds after reset (assuming wdt.reg[0] + 0x2000 resets to 0)#asahi-dev · 2026-04-10 19:50
yukaOh I commented out the part in wdt_disable to see what was the original value#asahi-dev · 2026-04-10 19:39
jannauto prove that it isn't the watchdog you could do wdt_reboot() but keep WDT_CTL as zero#asahi-dev · 2026-04-10 19:37
jannauif 0x1c is not 0 then the wdt_disable() either isn't done or does not work#asahi-dev · 2026-04-10 19:26
yuka0x1c contains '4' but setting it to 0 (like done by wdt_disable) doesn't stop it from rebooting#asahi-dev · 2026-04-10 19:26
yukaon m4, +0x0, +0x1, +0x2 are all counting up. 0x04, 0x14, 0x24 contain some non-zero numbers#asahi-dev · 2026-04-10 19:25
yukabut I guess I have to run it on the m1 pro to get some idea what to expect when the watchdog is disabled#asahi-dev · 2026-04-10 19:24
yukaThe monitor is useful#asahi-dev · 2026-04-10 16:20
jannausee https://paste.debian.net/hidden/7c8d4a7e for monitoring, use `mon.poll()` from the shell for updates#asahi-dev · 2026-04-10 16:18
jannauwdt-version = 2 is constant since m1, compatible is [wdt,t8101, wdt,s5l8960x] on m1, m2, a18 pro#asahi-dev · 2026-04-10 16:11
yukado you have this as well?#asahi-dev · 2026-04-10 16:11
yuka compatible = [wdt,t8132, wdt,s5l8960x]#asahi-dev · 2026-04-10 16:11
yukawdt-version = 2#asahi-dev · 2026-04-10 16:11
jannauon a18 pro#asahi-dev · 2026-04-10 16:09
yukaOn M4?#asahi-dev · 2026-04-10 16:06
jannauwdt.c doesn't use the compatible but the path "/arm-io/wdt" and the compatible hasn't changed. used regmonitor to watch its mmio and as far as I can see all watchdogs are disabled#asahi-dev · 2026-04-10 16:02
yukaI will look at this next#asahi-dev · 2026-04-10 16:01
yukaso the old wdt_disable no longer works#asahi-dev · 2026-04-10 16:01
jannauyes, m1n1 disables the watchdog and reenables it in kboot#asahi-dev · 2026-04-10 16:01
yukayeah the watchdog compatible in the adt also changed#asahi-dev · 2026-04-10 16:00
yukabut I guess wdt_disable#asahi-dev · 2026-04-10 16:00
yukaI did not know m1n1 did take care of the watchdog unless it went into the hv mode