#asahi-dev · 2025-06-01 12:52
nickchanafaik it's more #asahi-dev · 2025-05-31 15:22
nickchanthere's the a7 cache workaround but i really don't think that has any relation to the current issue#asahi-dev · 2025-05-31 15:19
nickchanit could be some cache or memory ordering issues#asahi-dev · 2025-05-31 15:16
nickchandummy_stack should never be used in the first place#asahi-dev · 2025-05-31 15:11
nickchanwould it be possible that some chicken bits are subtly wrong#asahi-dev · 2025-05-30 11:51
nickchanand ausb probably means apple usb#asahi-dev · 2025-05-30 11:51
nickchani think the only name for the usb phy on iphone is ausb I will call it that in the drivers#asahi-dev · 2025-05-30 04:51
nickchanand it turned out hacking data abort handler is less misreable so i didn't really use it#asahi-dev · 2025-05-30 04:47
nickchanbootleg cables with pi pico#asahi-dev · 2025-05-30 04:47
nickchanjust not a very pleasent experience using bootleg cables from pi pico with openocd#asahi-dev · 2025-05-30 04:46
nickchanI *can* use a swd debugger on a11 which has pan if that would help#asahi-dev · 2025-05-30 04:44
nickchana way to workaround is probably to patch the pan codes on startup instead of checking at runtime which is already done for the exception vectors but I suppose there's a deeper issue here#asahi-dev · 2025-05-29 19:29
nickchanin particular cfg0-device cfg1-device cfg0-host cfg1-host properties from the adt#asahi-dev · 2025-05-29 19:28
nickchanthey aren't device specific but i think they could be specific down to a SoC revision#asahi-dev · 2025-05-29 19:28
nickchanamarioguy: am just meaning i could use the tunables logic for somw usb2 phy tunables#asahi-dev · 2025-05-29 15:20
nickchanand by tunables I mean device specific tunables#asahi-dev · 2025-05-29 15:19
nickchani think usb3 is not sensitive enough to absolutely require tunables do they#asahi-dev · 2025-05-29 15:18
nickchanyay! I need similar logic too#asahi-dev · 2025-05-27 16:02
nickchannothing compared to the amount of patches in asahi linux though#asahi-dev · 2025-05-27 16:02
nickchandownstream patch load is now 96 (111 for 6.14)#asahi-dev · 2025-05-27 16:01
nickchanI think I will send i2c, spmi noeds and continue to resend cpu pmu support for the older socs in during the next cycle https://github.com/HoolockLinux/linux b4/apple-cpmu b4/i2c-no-t2 b4/t8015-spmi#asahi-dev · 2025-05-22 15:27
nickchanif gigalocker is corrupt then the init_data_protection boot-task in macOS should fail#asahi-dev · 2025-05-22 15:25
nickchanand normal macOS will obviously not boot as well since data volume is always encrypted#asahi-dev · 2025-05-22 15:24
nickchansven: i think breaking xarts would outright make the boot picker (recoveryOS) not boot - not actually tested though#asahi-dev · 2025-05-22 15:11
nickchani don't think there's rw apfs fuse drivers#asahi-dev · 2025-05-22 08:44
nickchanprobably safe to assume that corellium interanlly uses that module for something too so there's commerical interest#asahi-dev · 2025-05-22 08:44
nickchanlinux-apfs-rw maintainer does has an incentive to maintain it since it's corellium code and that guy works at corellium#asahi-dev · 2025-05-22 08:40
nickchani don't think kernel space access is really needed unless one wants to access SEP encrypted apfs from the kernel which no linux driver can do right now even for normal encryption#asahi-dev · 2025-05-22 08:38
nickchanand then an OS may need multiple volumes for different purposes and that's what the volume role is for#asahi-dev · 2025-05-22 08:37
nickchansven: volumes in a container share space (though optional fixed allocations could be made) . To tell which volume is for which OS there are "volume groups"#asahi-dev · 2025-05-22 08:32
nickchanthe gigalocker file probably isn't much of an io burden#asahi-dev · 2025-05-22 08:32
nickchanBut maybe that entirely falls in what should be handled by fuse not sure#asahi-dev · 2025-05-22 08:31
nickchanin reference to this https://lore.kernel.org/asahi/n7kkoptktdvldadvymcfmnaw3yqbk6bfmzpxvgdkpsvvpc3p7i@ilqcgz7wur7i/ and stats.asahilinux.org does have some sizable numbers#asahi-dev · 2025-05-22 08:30
nickchannow granted that is an usecase that only uses a small part of the filesystem code#asahi-dev · 2025-05-22 08:29
nickchanfor the interest of having apfs in the kernel would it be safe to assume every asahi linux user would be using it eventually as part of using the SEP's xART gigalocker file? that usecase be sufficiently common#asahi-dev · 2025-05-18 11:11
nickchanand i have seen some compile issues that only happens on like a hexagon randconfig that i would have never noticed without a ci bot#asahi-dev · 2025-05-18 11:09
nickchana forge doesn't have to be limited to a web ui#asahi-dev · 2025-05-17 17:09
nickchanand about the mux i kind of can't know about it that without having iphones of questionable origin or staring at disassembled iboots both of which i am not inclined to do#asahi-dev · 2025-05-17 17:06
nickchanA9X = S8001, A10X = t8011#asahi-dev · 2025-05-17 17:06
nickchanchaos_princess: the bigger 12.9 inch a9x iPad Pro 1st generation can do usb xhci and that's a pcie usb controller and usb3 is only supported in host mode, and the A10X 2017 iPad Pro ostensibly can do both USB3 host/device but in practice only host mode because the usb3 lightning cables are nowhere to be found#asahi-dev · 2025-05-17 17:05
nickchanjannau: A16 too cause iPhone 15 Plus and iPhone 15#asahi-dev · 2025-05-17 17:03
nickchanA16 = t8120, A17 = t8130#asahi-dev · 2025-05-17 17:03
nickchanokay I looked into the adts a bit seems like dwc2 existed on A16 and on A17 it's finally gone#asahi-dev · 2025-05-17 17:01
nickchanand it's not a dwc3 either trying to read the SNPSID#asahi-dev · 2025-05-17 16:59
nickchanthe first SoC to have something other than dwc2 is t8011 but I don't know about the specific of the non-dwc2 on that at all#asahi-dev · 2025-05-17 16:57
nickchanand then t8103 is the first soc to not have any traces of dwc2 but I think the A-series SoCs have them for a while longer#asahi-dev · 2025-05-17 16:55
nickchansven: in t8027 and t8030 they added dwc3 but it is not a clean switch as in the dwc2 still existed#asahi-dev · 2025-05-17 16:53
nickchani looked at the usb2 phy codes, a subset of bits in two of the registers are the same as older socs but even the register offsets are different suggesting common lineage but definitely seperate drivers#asahi-dev · 2025-05-17 16:43
nickchanthose features aren't in downstream yet and sending features straight to upstream aren't really asahi's pattern#asahi-dev · 2025-05-17 16:41
nickchani was thinking it was supposed for review but after seeing dp and tbt codes it's definitely not the case