#
✕ nick:jannau
#asahi-dev · 2026-06-09 08:58
jannauflokli: this is possibly an a18 pro only issue (apparently affecting only a subset of devices)
#asahi-dev · 2026-06-07 10:15
jannauerr, no. it doesn't. I was looking at the wrong tag
#asahi-dev · 2026-06-07 10:13
jannauand the non-upstream driver in 6.17 makes the same calls anyway with the lock held
#asahi-dev · 2026-06-07 10:05
jannauthe register calls all look sane. I don't see how they could indirectly call back into atc
#asahi-dev · 2026-06-07 09:51
jannaulockdep and kasan are clean for me (excluding lockdep issues in asahi and apple drm)
#asahi-dev · 2026-06-07 09:48
jannauI have no idea how the i2c timeout could fit into this
#asahi-dev · 2026-06-07 09:46
jannauatc probe doesn't appear to fail from yesterday's post
#asahi-dev · 2026-06-07 09:44
jannauprobing tipd, dwc3 and atc at the same time is probably racy but I don't understand why that would easily reproducible on some devices and and at all on others
#asahi-dev · 2026-06-07 09:42
jannauif something changed I would expect it to be reproducible and not racy
#asahi-dev · 2026-06-07 09:38
jannauye, atc->lock is locked while registering the devices. so the only issue could be that one of register calls tries to access the locked phy. it would be unexpected and I think it's unlikely to be racy either
#asahi-dev · 2026-06-07 09:29
jannausven: due you known if any of atc sub-device register functions might call back into atc and thus deadlock? I think a deadlock during probe could be catastrophic when other devices are probe as well. asking for https://github.com/AsahiLinux/linux/issues/465
#asahi-dev · 2026-06-07 09:04
jannauI guess a little less so due to the damage handling but unless the notebook is constantly used the powered backlight while the display is "off" will burn those savings
#asahi-dev · 2026-06-07 08:43
jannaualso not how the driver works at the moment. only way I can image how it could work is that either the driver or dcp has a separate static framebuffer and dcp blits the damage into it
#asahi-dev · 2026-06-07 08:40
jannauI'm not even sure if that would fit into how compositors use kms with a hw driver
#asahi-dev · 2026-06-07 08:11
jannauthat said I think the usability advantages of dcp are more important than performance
#asahi-dev · 2026-06-07 08:09
jannaui.e. simpledrm has an advantage when only a small part is updated. without overlay cursor movement would be the prime example
#asahi-dev · 2026-06-07 08:07
jannauthe main advantage simpldedrm has over dcp is that it supports damage while dcp always swaps complete framebuffers
#asahi-dev · 2026-06-07 08:05
jannauit won't be a slideshow and I don't remember display without gpu as unsable. under kwin it ishould have improved due to using an overlay plane for the cursor
#asahi-dev · 2026-06-05 21:54
jannaucan you create a separate PR for "Factor out i2c bus device". I'd like to merge that for REASONS
#asahi-dev · 2026-06-05 21:53
jannauok, I was wondering about the weird interface
#asahi-dev · 2026-06-05 21:49
jannauthe spmi debugfs interface isn't upstream?
#asahi-dev · 2026-06-05 21:47
jannauyuka: is there a reason that https://github.com/AsahiLinux/tuxvdmtool/pull/9 is a draft?
#asahi-dev · 2026-06-05 18:26
jannauwithout hotplug
#asahi-dev · 2026-06-05 16:03
jannaudid someone make sweeps over the nvme mmio space and compared < 15 with >= 15?
#asahi-dev · 2026-06-05 16:01
jannauprinted just before it initialises namespaces
#asahi-dev · 2026-06-05 16:00
jannaumacos boot logs contain the FW version but it seems to be queried over nvme itself
#asahi-dev · 2026-06-05 15:54
jannauSErrors on M4 with 15.1 and 26.0 with the changes from the gist so hopefully a m4 and later device change and not another firmware change affecting all devices
#asahi-dev · 2026-06-05 15:28
jannauiirc 15.0 (could be 15.1)
#asahi-dev · 2026-06-05 15:25
jannauwe could switch to new compatible and add unknown_ctrl and linear_sq_ctrl as reg entries or properties but I think that's even worse
#asahi-dev · 2026-06-05 15:21
jannauadd the firmware version to the compatible string
#asahi-dev · 2026-06-05 15:20
jannauthe second option works until apple changes the firmware again
#asahi-dev · 2026-06-05 08:31
jannauI suspect there is a single gpio pin which bypasses the usb hub and allows usb device mode. unfortunately I have no good idea how to find it. likely on the smc pin controller
#asahi-dev · 2026-06-05 08:27
jannausee https://github.com/AsahiLinux/kisd/issues/11 for macos usage
#asahi-dev · 2026-06-05 08:27
jannaufor the debugusb troubles you could test https://github.com/AsahiLinux/kisd which should give you at least 10mbps
#asahi-dev · 2026-06-05 08:25
jannauStanfordAppliedCyber[m]: you could create a fat partition and load the kernelcache from there using m1n1's nvme support (not sure if it will work out of the box on a18 pro / macOS 26). that's a less cursed setup than bundling the kernelcache
#asahi-dev · 2026-06-04 15:01
jannau"debug" on the kernel command line is needed for dev_dbg, which is annoying because systemd components interpret that as well
#asahi-dev · 2026-06-04 11:51
jannaufaster e-cores at a lower freq and slower p-cores compared to m3: https://paste.debian.net/hidden/1791542a
#asahi-dev · 2026-06-04 11:47
jannaumy script does that: https://github.com/AsahiLinux/linux/commit/74dcb65d70320967842fc774591724a7fe53756b
#asahi-dev · 2026-06-04 11:45
jannaudid you normalize them to the (max) frequency
#asahi-dev · 2026-06-04 11:34
jannaubad performance on the boot core is not related to core switching
#asahi-dev · 2026-06-04 11:10
jannausurprisingly quite a difference between t8122 and t6030
#asahi-dev · 2026-06-04 11:09
jannauchaos_princess, yuka: see commit messages how I determined capacity-dmips-mhz
#asahi-dev · 2026-06-04 11:03
jannauit's only core 4 (active at m1n1 startup) which is inexplicable slow on M3. 17688 vs. 42851 Iterations/Sec for core 4 vs. core 5, 6, 7
#asahi-dev · 2026-06-04 09:58
jannauso the 83% I get from coremark could be correct
#asahi-dev · 2026-06-04 09:57
jannauthat would put the e-cores at 80% of the p-cores based on our m1 capacity-dmips-mhz
#asahi-dev · 2026-06-04 09:54
jannau"The CPU performance cores and efficiency cores are 30 percent and 50 percent faster than those in M1"
#asahi-dev · 2026-06-04 09:51
jannauwhy had I 300-400 in mind for the e-cores?
#asahi-dev · 2026-06-04 09:50
jannauoh, I should have looked at the m1/m2 capacity-dmips-mhz values. m2 with 756 / 1024
#asahi-dev · 2026-06-04 09:44
jannauand 56% of the absolute values with both at their max freqency
#asahi-dev · 2026-06-04 09:42
jannauno, p-cores are faster both absolute and relative to their max freq but I'm not trusting the results. e-core at 83% of p-core at iso frequency seems to high

plus ›