#asahi-dev · 2024-07-22 20:13
jannegin the driver's probe() reading from the BAR results in SError when the device was runtime suspended#asahi-dev · 2024-07-22 20:12
jannegany idea why the generic PCI runtime suspend breaks the gl9755 sd card reader?#asahi-dev · 2024-04-04 09:23
jannegalso relevant for BOOTSTD conversion: https://lore.kernel.org/u-boot/20240403190715.144725-1-heinrich.schuchardt@canonical.com/T/#t#asahi-dev · 2024-04-04 09:22
jannegI assumed efi_boot_mgr would already prefer the designated EFI partition#asahi-dev · 2024-04-04 09:21
jannegkettenis: https://paste.centos.org/view/78395209#asahi-dev · 2024-04-04 06:06
jannegnice simplification on the ESP selection though#asahi-dev · 2024-04-04 06:06
jannegkettenis: I've seen you've rebased asahi/u-boot onto v2024.04 and folded ESP slection into asahi_esp_devpart() but the env loading / usb xhci fw loading is still using '%d' for disk/partition#asahi-dev · 2024-03-29 14:55
jannegyes, but it is m3 only. the cursed 13.5 FW which shipped with the devices released last year uses ascwrap-v4 but with 14.x "ascwrap-v6" is in the compatible string#asahi-dev · 2024-03-29 14:41
jannegnot the most pressing issue. first fixing the HV and then finding out how ascwrap-v6 differs from ascwrap-v4 (that's a macOS 14 thing)#asahi-dev · 2024-03-29 14:15
jannegi.e. a splitted performance cluster. not saying it breaks anything but it is unintuitive#asahi-dev · 2024-03-29 14:13
jannegI need linux user-space but it looks like we might end up with p-core, 4 * e-core, 3 * p-core#asahi-dev · 2024-03-29 14:06
jannegit boots without HV (cpu numbers don't match with DT though). it looks like a timer issue in m1n1's hypervisor#asahi-dev · 2024-03-29 12:46
jannegno, seems to be a timer issue with the HV#asahi-dev · 2024-03-29 11:34
jannegunsure if this is the problem#asahi-dev · 2024-03-29 11:09
jannegDocumentation/arch/arm64/booting.rst only speaks about the primary CPU and at least based kernel messages it seems to assume that this is cpu0#asahi-dev · 2024-03-29 11:07
jannegoh, the joys of not booting with cpu0. m1n1 and hypervisor seems to work now but linux doesn't seem to be happy#asahi-dev · 2024-03-28 21:21
jannegcounter resolution is 24 MHz though#asahi-dev · 2024-03-28 20:28
jannegsetting BIT(1) specifically#asahi-dev · 2024-03-28 20:22
jannegmsr(s3_1_c15_c1_5, 0x3uL) switches CNTFRQ_EL0 to 24 MHz#asahi-dev · 2024-03-28 20:10
jannegM3 performance cores come out of reset with 1GHz as CNTFRQ_EL0. I guess I should check the counter resolution and then see which reg write changes that #asahi-dev · 2024-03-27 21:05
jannegno, just commits changing something in net/bluetooth/ maybe 20 commits#asahi-dev · 2024-03-27 19:02
jannegseems to be false alarm. I can't reproduce#asahi-dev · 2024-03-27 18:50
jannegbcm4378 (mac mini m1) works here#asahi-dev · 2024-03-27 18:29
jannegyes, seems to be easy enough to bisect. reverted half of the v6.7..v6.8 changes and it's working#asahi-dev · 2024-03-27 18:04
jannegleio: https://github.com/jannau/linux/tree/beta-6.8/asahi-wip bt le pairing seems to be broken, wifi works#asahi-dev · 2024-03-26 21:20
jannegI've really tried with 300ms. and it might be the delay and not the ignorant debounce implementation#asahi-dev · 2024-03-26 21:13
jannegleio: this seems to improve M2 desktop HDMI reliability: https://github.com/jannau/linux/commit/5ef7d920caa52ee0331ec1c71f3a67857a6a3427 (either use the branch with rust 1.76+ or that commit on-top of asahi-6.6-16)#asahi-dev · 2024-03-25 11:47
jannegthanks#asahi-dev · 2024-03-24 21:17
jannegok, issue should be fixed then#asahi-dev · 2024-03-24 18:40
jannegcurrently not, I would expect a sync on resuming and using my 6.8 bits branches as base#asahi-dev · 2024-03-24 18:27
jannegmy expectatation is that we will continue with the bits branches from https://github.com/jannau/linux/tree/beta-6.8/bits/000-devicetree, ... which already contain the fixups#asahi-dev · 2024-03-24 18:08
jannegsven: when you have time please refresh asahi-wip-6.8 with https://github.com/jannau/linux/tree/beta-6.8/asahi-wip#asahi-dev · 2024-03-24 17:02
jannegaxboe: did the broken asahi-wip-6.8 kernel have CONFIG_DRM_APPLE=y?#asahi-dev · 2024-03-24 09:54
jannegthanks#asahi-dev · 2024-03-24 09:15
jannegsven, marcan: please, update asahi-wip with https://github.com/jannau/linux/tree/asahi-wip . just a linear update since I don't think the hassle with full merge of the bits branches for 6.6 is justified at this point. I also pushed a signed asahi-6.6-16 tag. not sure if we want to use that or one signed with marcan's key#asahi-dev · 2024-03-24 08:03
jannegHW cursors#asahi-dev · 2024-03-24 08:03
jannegissue with supporting overlays is that compositors then try to use the overlay for SW #asahi-dev · 2024-03-24 08:02
jannegI think dcp only supports planar yuv and no nv12. macos fourccs are probbably 420v, 422v and 444v. not quite clear based on dcp fw strings#asahi-dev · 2024-03-24 07:58
jannegI can't remember having seen black panels but I'm not using plasma 6 yet#asahi-dev · 2024-03-24 07:53
jannegchadmed_: I spoke about the profile activate error in #kwin:kde.org, they don't see that anywhere else, it isn't triggered by SW cursors. appears to be an issue wit damage tracking. brokeness vanishes after repaint, for example by moving a window over it#asahi-dev · 2024-03-24 07:47
jannegleio: who knows which issues that fixes. I'm certain it explains the suspend issue. other than that I'm surprised it was working at all (except the initialization at boot)#asahi-dev · 2024-03-23 23:27
jannegleio: ^^^#asahi-dev · 2024-03-23 23:25
janneginteresting that the power-domain doesn't need to be active continuously while the display is on only for mmio access#asahi-dev · 2024-03-23 23:21
jannegI suppose it only works on start because simple-framebuffer keeps the power-domain active long enough for the initial setup#asahi-dev · 2024-03-23 23:12
jannegI wonder how that ever worked. doesn't fix sleep completely but doesn't break completely. monitor power-cycle restores the display#asahi-dev · 2024-03-23 22:49
jannegsigh, this could explain some of the m2* hdmi issue: https://paste.debian.net/1311792/#asahi-dev · 2024-03-21 17:33
jannegcursor support and HiDPI handling coming next#asahi-dev · 2024-03-21 17:32
jannegthird attempt I'm aware off#asahi-dev · 2024-03-21 17:31
jannegsweet, the u-boot utf-8 video console changes are merged in next, no more broken chars in the efi text console used by grub, sd-boot, ...#asahi-dev · 2024-03-17 21:07
jannegit doesn't conflict as long as efi_bootmgr is used as bootmeth. https://source.denx.de/u-boot/u-boot/-/commit/550862bc1279278a029c8c17871a0c6241c522d8 broke it with CMD_BOOTEFI_BOOTMGR but that's unrelated to standard boot