#asahi-dev · 2023-02-20 14:20
jannauappears so, I can read from enabled pcie usb hcd but not from the disbaled wlan adapter#asahi-dev · 2023-02-20 14:18
jannauthat doesn't work at all#asahi-dev · 2023-02-20 14:15
jannauhow do I check the bar from the HV?#asahi-dev · 2023-02-20 14:00
jannauhttps://www.jannau.net/asahi/t8103_tbt_lspci_2023-02-20.txt#asahi-dev · 2023-02-20 13:53
jannauno change#asahi-dev · 2023-02-20 13:49
jannauseems to be 0. should I be able to write to it from the hv? writes don't seem to stick#asahi-dev · 2023-02-20 13:37
jannauthunderbolt nvme probing fails on "if (readl(dev->bar + NVME_REG_CSTS) == -1) {" in nvme_pci_enable()#asahi-dev · 2023-02-20 12:46
jannauseems to be only a cosmetical problem anyway#asahi-dev · 2023-02-20 12:37
jannauit does so on my thinkpad but not on the mac mini#asahi-dev · 2023-02-20 12:34
jannauI assumed it shows the host controller for since you asked for `boltctl list -a`#asahi-dev · 2023-02-20 12:17
jannaus/when/after/#asahi-dev · 2023-02-20 12:15
jannauI suspect the M3 boot failure happens when disconnecting the cable at the wrong time#asahi-dev · 2023-02-20 12:03
jannauwe also have to fix bolt on asahi linux (or there's a problem with my kernel config). it doesn't display the host controller. boltd log shows some dmidecode errors. sounds like it might need to learn that thunderbolt is not x86/acpi specific#asahi-dev · 2023-02-20 11:58
jannauyes, I think replugging the hub requires a reset and sometimes results in the M3 failed to boot#asahi-dev · 2023-02-20 11:57
jannauthere is however no nvme block device#asahi-dev · 2023-02-20 11:57
jannaunvme 0000:03:00.0: enabling device (0000 -> 0002)#asahi-dev · 2023-02-20 11:56
jannauthe device is visible in lspci and the kernel detects a nvme device but it ends with#asahi-dev · 2023-02-20 11:55
jannauI can't get the nvme to work however#asahi-dev · 2023-02-20 11:54
jannausven: tb seems to work for the most part. connected to the thunderbolt4 hub (goshen ridge) with i225 pcie ethernet and alpine ridge nvme case (directly and through a downstream port on the hub)#asahi-dev · 2023-02-19 21:25
jannauI see that occasionally#asahi-dev · 2023-02-19 21:22
jannausven: works now somewhat. it was an active cable#asahi-dev · 2023-02-19 18:30
jannauirqs work now and the thunderbolt connection is detected. it fails with "-ETIMEDOUT: M3 firmware failed to boot"#asahi-dev · 2023-02-19 18:22
jannauyou changed the default mode from usb to usb4 in tipd#asahi-dev · 2023-02-19 18:21
jannaualready trying that#asahi-dev · 2023-02-19 18:16
jannauno, dwc3 fails to probe with "DWC3 controller soft reset failed."#asahi-dev · 2023-02-19 18:04
jannauno, I didn't but there is something missing since usb-pd@3f is deferred. I assumed that was the one connected to the hv port#asahi-dev · 2023-02-19 18:00
jannauargh, did I mix up the ports?#asahi-dev · 2023-02-19 17:56
jannauyes, nothing suspicious changed there. is it normal that the second tps698x is not removed/disabled when using the first usb-c port for the HV?#asahi-dev · 2023-02-19 17:51
jannauno tps6598x interrupts explains why nothing happens on device plug#asahi-dev · 2023-02-19 17:16
jannaunothing on device plug#asahi-dev · 2023-02-19 17:15
jannauI would assume a passive cable#asahi-dev · 2023-02-19 17:15
jannauyes, tried replugging multiple devices. thunderbolt3 nvme adapter, thunderbolt3 monitor (afaik dp and usb) and usb4 hub. I expect the latter two to be broken#asahi-dev · 2023-02-19 17:10
jannausven: any config dependencies except enabling the added CONFIG_* and PCI_HOTPLUG? I see the thunderbolt pcie controller but no devices#asahi-dev · 2023-02-19 16:54
jannauchadmed: I get an out of memory error from run_guest.py with a larger kernel (with debug symbols)#asahi-dev · 2023-02-19 14:34
jannauit either reserves the iova or suppurt direct (1:1) mappings#asahi-dev · 2023-02-19 14:21
jannauthe series ended up the way it is because asahi needs translation#asahi-dev · 2023-02-19 14:21
jannautranslation from iova to physical memory#asahi-dev · 2023-02-19 14:15
jannaustill depends on patches in the asahi tree to support mappings with translation. I plan to send them out after v6.3-rc1#asahi-dev · 2023-02-19 14:14
jannauit's not, but v13 got picked up for v6.3#asahi-dev · 2023-02-19 13:25
jannauthanks for the reviews#asahi-dev · 2023-02-19 13:06
jannauthat's the way I understand it#asahi-dev · 2023-02-19 11:52
jannauthe PMU regression fix was merged yesterday for 6.2#asahi-dev · 2023-02-19 11:06
jannauProxyUtils default heap size is 1GB#asahi-dev · 2023-02-19 11:03
jannauyes, compressed_writemem should fail (from quick code inspection) if it can't allocate enough heap#asahi-dev · 2023-02-19 09:53
jannauhave you tried compressing the same initrd with xz?#asahi-dev · 2023-02-19 09:51
jannauin payload.c:decompress_gz()#asahi-dev · 2023-02-19 09:51
jannau"#asahi-dev · 2023-02-19 09:51
jannauthat's close: "unsigned int source_len = size, dest_len = 1 << 30; // 1 GiB should be enough hopefully#asahi-dev · 2023-02-19 09:50
jannauyou could try https://github.com/AsahiLinux/m1n1/pull/268 which defers uncompressing to linux#asahi-dev · 2023-02-19 09:50
jannauhow large is the initrd uncompressed?