#asahi-dev · 2025-08-03 15:36
jannauI started preparations for those. ideally I'd also like to submit the missing devices (15" m2 air and all t602x based devices) for 6.18#asahi-dev · 2025-08-03 15:35
jannauI will look at four level dart/iopgtbl and spi-hid + touchpad#asahi-dev · 2025-08-03 15:10
jannauroughly 1/4 of the 963 commits are in bits/200-dcp which could also be squashed#asahi-dev · 2025-08-03 15:09
jannauI've pushed asahi-6.16.0-1 to github. 967 non merge commits compared to v6.16. backl to lkess than 1000 commits from upstream. main contribution are imported rust patches from v6.16, squashing of the 210-gpu branch and other patches upstreamed for v6.16#asahi-dev · 2025-08-03 14:00
jannausmall compile warning fix after today's merges: https://github.com/AsahiLinux/m1n1/pull/478#asahi-dev · 2025-08-03 13:59
jannauI don't think the linux driver can do anything about this on j314s side. afaik that's handled by cd3217 fw or possible smc#asahi-dev · 2025-08-03 09:12
jannaueven though they are mostly documentation / examples at this point#asahi-dev · 2025-08-03 09:11
jannauI think the stale trace PRs are useful to keep as open as that makes them easier to discover#asahi-dev · 2025-08-03 08:55
jannausure, was more a reminder for myself to add them#asahi-dev · 2025-08-03 08:54
jannau469 still needs fuses for t600x and t8112 or?#asahi-dev · 2025-08-03 08:48
jannauand the kernel is not ready either. My plan was to see if we can have at least for a while both variants supported#asahi-dev · 2025-08-03 08:47
jannauplease wait on GPU init one. I need go through all devices again to verify that the paramters are unchanged#asahi-dev · 2025-08-03 08:46
jannauyes, but to avoid the annoying false failures for every PR#asahi-dev · 2025-08-03 08:35
jannauposted to #fedora-asahi-devel as well, let's wait a few days before merging it#asahi-dev · 2025-08-03 08:30
jannauhttps://github.com/AsahiLinux/m1n1/pull/477#asahi-dev · 2025-08-03 08:23
jannauI agree#asahi-dev · 2025-08-03 08:08
jannauI think we should solve that differently, i.e. either not run those checks in github or use a rpm spec inside the github m1n1 repo#asahi-dev · 2025-08-03 08:07
jannaubut overall the checks are bad because they are using an out of sync rpm .spec#asahi-dev · 2025-08-03 08:06
jannauthey are just warnings in the sense that the failures do not block merging#asahi-dev · 2025-08-02 16:49
jannauhttps://github.com/AsahiLinux/m1n1/pull/476 would make my life a little easier but I can deal with it until the next release#asahi-dev · 2025-08-02 16:48
jannausven: I think so. marcan or I also took care of updating the fedora package but that's a separate task anyway#asahi-dev · 2025-07-28 22:17
jannauinconvenient#asahi-dev · 2025-07-28 22:11
jannauI find it unlikely that's just refurbished, I would have expected bug reports for that. it fails violently in m1n1#asahi-dev · 2025-07-28 22:06
jannauannoying to look a a sample size of 1#asahi-dev · 2025-07-28 22:06
jannauany guess whether that's specific to my system, mac pros in general or certain refurbished devices?#asahi-dev · 2025-07-28 21:59
jannauthe template ADT from ipsw has those properties though#asahi-dev · 2025-07-28 21:57
jannauany idea what '"wlan.msf.source" = "fdr"' (from ioreg) could mean? wlan/bt misses calibration data in the ADT on my (refurbished) mac pro. ioreg has wifi-calibration-fdr instead of wifi-calibration-msf#asahi-dev · 2025-07-26 15:47
jannauI've pushed asahi-6.15.8-1 to github with a reshuffled bits/020-dart#asahi-dev · 2025-07-24 10:41
jannauI think it's only annoying in one place. reording shouldn't be a mayor issue. I simply did not think of it#asahi-dev · 2025-07-24 09:25
jannauideally the display darts shouldn't be reset until the first device attaches#asahi-dev · 2025-07-24 09:24
jannaubut iommu groups have to share the same domain ops#asahi-dev · 2025-07-24 09:23
jannauwhich is annoying since locked darts ideally would use different iommu domain ops#asahi-dev · 2025-07-24 09:23
jannaubut it's annoying for the full display support as it would mean to support combinations of locked and unlocked darts#asahi-dev · 2025-07-24 09:21
jannaum1n1 locks currently the dart of the boot display controller. this ensures the boot framebuffer works#asahi-dev · 2025-07-24 09:20
jannaudisplay makes upstreaming dart rather annoying, I probably should reorder the t602x dart with the locked dart support#asahi-dev · 2025-07-24 09:17
jannaudart is on my list#asahi-dev · 2025-07-18 17:40
jannauI've pushed asahi-6.15.7-1 to github, ~110 asahi specific commits less than asahi-6.15.6-1, mostly by squashing in bits/210-gpu#asahi-dev · 2025-07-15 14:11
jannauI've pushed asahi-6.15.6-1 to github#asahi-dev · 2025-07-15 12:26
jannauflokli: I've pushed a fix and verified it compiles with 1.87#asahi-dev · 2025-07-15 12:02
jannauI'm compiling with 1.88#asahi-dev · 2025-07-15 10:24
jannauerr, yes. I forgot to do that#asahi-dev · 2025-07-15 10:18
jannausee asahi-wip#asahi-dev · 2025-07-15 10:18
jannauchaos_princess: I was still seeing probe order issues and have moved the snd_pcm_set_managed_buffer call to aop_pcm_open. This is what we did for DCP audio as well to avoid the same issue#asahi-dev · 2025-07-13 22:21
jannauit's even used in this way in the kernel. so it might okay in principle#asahi-dev · 2025-07-13 22:12
jannauso platform_device_register_full() still works and passes data to the childs due to probe order?#asahi-dev · 2025-07-13 10:40
jannaumight be time to convert to auxilary bus/dev. see nova-core / nova-drm as example#asahi-dev · 2025-07-13 10:32
jannaufor example "of:NdcpT(null)Capple,t8112-dcpCapple,dcp"#asahi-dev · 2025-07-13 10:32
jannauit looks that way because that's how it's build for of devices. it would have the compatible strings appended with an 'C' as prefix if the node had that#asahi-dev · 2025-07-13 10:23
jannauit changes because of_dev_modalias starts to work with fwnode set#asahi-dev · 2025-07-13 10:15
jannauchaos_princess: the module load issue is wrong modalias. with fwnode set it's "of:NaudioT(null)" instead of "platform:snd_soc_apple_aop" and the module only hast the latter