#
✕ nick:jannau
#asahi-dev · 2026-11-05 16:40
jannauindenting by tabs and then less than 8 spaces should be fine
#asahi-dev · 2026-11-04 17:37
jannaucan you easily boot into an older kernel? or macos?
#asahi-dev · 2026-11-04 17:34
jannaudoes `nvme smart-log /dev/nvme0` report anything out of the ordinary?
#asahi-dev · 2026-11-04 17:32
jannauunlikely that it is asahi-7.2.15-1 compared to asahi-7.2.14-1 (which runs here w/o issues) judging by the diff
#asahi-dev · 2026-11-04 11:04
jannauand at that point we're duplicating the implementations in pwrctrl
#asahi-dev · 2026-11-04 11:03
jannauand I guess we need separate loops for create_device and power_on_device
#asahi-dev · 2026-11-04 10:57
jannauthe unwind code on error is a little unwiedly but otherwise I don't see an issue with it
#asahi-dev · 2026-11-04 10:55
jannauI would also exclude the documentation from count of changed. it's neither bad nor in pcie-apple
#asahi-dev · 2026-11-04 10:47
jannauthe ask was to my understanding to turn on power for each port individually in pcie-apple because the driver does everything else on a per-port basis
#asahi-dev · 2026-11-04 10:46
jannauwhich driver? I think that already caused confusion in the initial submission
#asahi-dev · 2026-11-04 10:41
jannausee "To be clear, I'm not suggesting delaying switching of the power. I'm merely suggesting managing it on a per port basis."
#asahi-dev · 2026-11-04 10:41
jannauI interpretet that as referring to hiding the loop over all ports in pci_pwrctrl_power_on_devices()
#asahi-dev · 2026-11-04 10:08
jannauI think the main reason why it is not picked up is that it was entangled in the previous power GPIO submission: https://lore.kernel.org/linux-pci/20220502093832.32778-3-marcan@marcan.st/
#asahi-dev · 2026-11-04 10:06
jannaucan't we just power on devices in a loop before we loop over apple_pcie_setup_port(). we have https://github.com/AsahiLinux/linux/commit/1a71d5c8ad462e8a6cd0a436c5e92b3c56bc5271 downstream which essentially does the same for the PERST# gpios.
#asahi-dev · 2026-11-04 09:48
jannauyuka: into what kind of trouble did you run with powering on devices per port?
#asahi-dev · 2026-11-04 09:47
jannauafter looking at the code pci_pwrctrl_create_device / pci_pwrctrl_power_on_device would work for M2 Pro as well
#asahi-dev · 2026-11-04 07:49
jannauYouwes09: I saw your message but haven't looked at it yet. I saw the rust changes and remember that they might cause issues but forgot all details. I have to look at code
#asahi-dev · 2026-11-03 23:09
jannauI've tagged and pushed asahi-7.2.15-1
#asahi-dev · 2026-11-03 23:06
jannauno, my PCIe dts looks different, did you see that maz did not like pci_pwrctrl_power_on_devices() when yuka send PCI pwrctrl support in July. I fear we need it for Mac Pro support with the large PCIe switch though
#asahi-dev · 2026-11-03 23:01
jannauhuh, I missed that nvme was picked up
#asahi-dev · 2026-11-03 22:51
jannauArend did not address how the DMA direction conflict should be handled, might still be advisable to send a v2 based on wireless.git with the conflict resolved (and Arand's Acked-by: imported)
#asahi-dev · 2026-11-03 22:40
jannauMichaelReeves[m]: I think t602x upstream has it already, for M3 pcie support is missing as whole. I have a prepared branch for it ready to send. I haven't send it so far as it losely depends on m3 nvme
#asahi-dev · 2026-11-03 20:46
jannauj714c
#asahi-dev · 2026-11-03 20:39
jannau"Starting CPU 17 (0:2:5)... Started."
#asahi-dev · 2026-11-03 19:23
jannauin the changelog?
#asahi-dev · 2026-11-03 17:24
jannauplease drop it and mention under chnages that it was already picked up. rebasing it before the cover letter in b4 doesn't seem to cause issues (that way make dtbs_check remains warning free). check the base commit for sending to make sure
#asahi-dev · 2026-11-03 10:19
jannaumyria: the downstream kernel requires avd-fw 0.2 with the mandatory supported codecs check I've added in asahi-wip, the upstream submissions v2 and v3 require new firmware which dows more
#asahi-dev · 2026-11-02 20:43
jannau`python3 -m urlcache $IPSW $FILES` in asahi-installer/src should work
#asahi-dev · 2026-11-02 19:32
jannauhttps://forge.fedoraproject.org/asahi/avd-fw has compattibility patches to provide the config at the place asahi-7.2.* kernels expect it
#asahi-dev · 2026-11-02 19:31
jannauflokli: no that was done before we settled on the change in the firmware, https://github.com/AsahiLinux/linux/commit/faf8d1233a82cff11182dc7e83bcdd356f5feb83 does read from 0x400
#asahi-dev · 2026-11-02 17:47
jannaualso switched to the v3 upstream avd DTS and fixed 1 compatibility issue with the current fw, there might be more, I did not test thouroughly
#asahi-dev · 2026-11-02 17:44
jannauI dropped a few patches which I believe are no longer necessary. power-domain or less likelydart issue might be caused by that
#asahi-dev · 2026-11-02 17:41
jannauI've updated asahi-wip and the bits branches to v7.3 and picked devicetree changes up. bits/000-devicetree has almost 250 commits
#asahi-dev · 2026-11-02 14:47
jannauhttps://patch.msgid.link/20260925-apple-m3-nvme-v1-0-5e832e2f4aa9@jannau.net
#asahi-dev · 2026-11-02 14:32
jannauM3* nvme support but I can send a v2
#asahi-dev · 2026-11-02 10:14
jannauAdityaGarg8[m]: thanks, that fixes things on bcm4388 as well
#asahi-dev · 2026-11-01 21:43
jannauI get an iommu read fault and nothing works
#asahi-dev · 2026-11-01 21:43
jannauthe 7.3 downstream branch has an issue with https://github.com/torvalds/linux/commit/f0ba5fd51ff23077ce66cb9be79d41a4b7c19c5e
#asahi-dev · 2026-11-01 21:42
jannauMichaelReeves[m]: I haven't tested you series without other asahi downstream patches yet. might have been one of the patches of bits/080-wifi that still applied on top. I saw Arend's reply and put testing on my TODO
#asahi-dev · 2026-11-01 09:29
jannaudownload wheel(s) from pypi and create a venv when the installer runs?
#asahi-dev · 2026-11-01 09:23
jannaudependencies in which form? python packages?
#asahi-dev · 2026-10-31 17:50
jannauindeed silly
#asahi-dev · 2026-10-31 17:47
jannautransfer done: https://github.com/AsahiLinux/asahi-va-driver thanks
#asahi-dev · 2026-10-31 17:39
jannausofus: even when you type AsahiLinux for "Specify an organization or username"? My understanding is that that should send an invite to the organisation to accept the transfer
#asahi-dev · 2026-10-31 17:38
jannauaccepted but I don't have permissions to transfer the repo
#asahi-dev · 2026-10-31 16:41
jannauif that does not work you could add me as member of that repo and I can transfer it
#asahi-dev · 2026-10-31 16:40
jannausofus: why not? because of organization permissions? There should be a combo field "Specify an organization or username"
#asahi-dev · 2026-10-31 15:57
jannaunah, codec was a typo. "*va--driver" is the terminology commonly used.
#asahi-dev · 2026-10-31 15:54
jannaumeine neither. It took 3 downloads with mismatched size before I checked the tarball content
#asahi-dev · 2026-10-31 15:53
jannauok. I'll tag v0.2 and make a release for avd-fw

plus ›