#asahi-dev · 2025-06-02 19:18
amarioguybtw does anyone know why after an m1n1 build rust is leaving behind a lot of target stuff that isn't in the gitignore?#asahi-dev · 2025-06-02 16:22
amarioguyshouldn't matter#asahi-dev · 2025-06-02 16:21
amarioguynot really smth that needs a script - i just need someone to run mrs(ICC_CTLR_EL1, call="el1") in the m1n1 proxyclient console#asahi-dev · 2025-06-02 16:20
amarioguytest for m3 max#asahi-dev · 2025-06-02 16:20
amarioguyfl0_id: i saw it#asahi-dev · 2025-06-02 01:40
amarioguynote that i think that register has to be read from EL1#asahi-dev · 2025-06-02 01:39
amarioguyneed to verify if the vGIC cpu interfaces gained support for extended SPI/PPI ranges (M1 and M2 along with Pro counterparts say no on that front, i want to verify if it's also true on the later chips, since for some of those core counts on the newer ones, seem to be pushing against the limit where those ranges would be needed)#asahi-dev · 2025-06-02 01:37
amarioguycan someone check the ICC_CTLR_EL1 on any M4 Pro models? (same for M3 and m3 pro if you have either)#asahi-dev · 2025-05-31 14:55
amarioguyah i see, thanks for the info, probably will implement one of the workarounds then#asahi-dev · 2025-05-31 14:47
amarioguyjust need to know that so i can determine whether i should hold off on fast forwarding my fork to current#asahi-dev · 2025-05-31 14:47
amarioguyin what scenarios is the HV affected?#asahi-dev · 2025-05-31 14:46
amarioguythat mmu_setup_secondary issue#asahi-dev · 2025-05-29 19:42
amarioguyah#asahi-dev · 2025-05-29 18:36
amarioguywell t2/a10x#asahi-dev · 2025-05-29 18:36
amarioguynickchan: wait why would t8015 require usb3? or is this for t2?#asahi-dev · 2025-05-29 01:28
amarioguymaz: not sure if you're still active so apologies in advance for the ping, but does kvm exactly care much about AIC2 seemingly routes interrupts to cores at random? didn't seem like there was any special code to do that in either the AIC driver or the KVM vgic code, but then again the fact that virtual CPU state is entirely maintained by the HV means that it may not matter much i suppose#asahi-dev · 2025-05-29 01:05
amarioguy(ik you can have CPUs opt out of interrupts via the SIQ cfg msr but iirc that only allows filtering between P and E core clusters#asahi-dev · 2025-05-29 01:04
amarioguyjust refreshing my memory here since i'm at the point where i have to finish the vgic implementation now: AICv2 and v3 i hear don't support setting CPU affinities?#asahi-dev · 2025-05-26 02:19
amarioguywait no ugh - this isn't a quick fix#asahi-dev · 2025-05-26 01:54
amarioguyah i figured out how - gonna submit a PR soon for this because this was causing headaches...#asahi-dev · 2025-05-25 23:59
amarioguyquick q is it possible to get m1n1 to reallocate the framebuffer to a location that's page aligned? testing on a J416s here (M2 Pro MBP, Early 2023) and while I *could* do hacks to make it work would want to know if there's a "clean" way to do it (since FB is allocated by iBoot - not sure if that's possible tbh)#asahi-dev · 2024-10-05 01:33
amarioguy(well for USB2 anyways)#asahi-dev · 2024-10-05 00:36
amarioguynever mind lol, found the original commit for it, seems like iBoot does the PHY config, and the u-boot driver just resets the DWC3, so that's fine lol#asahi-dev · 2024-10-05 00:33
amarioguyjust asking mainly because the ATC code in u-boot looks quite barren so just clarifying#asahi-dev · 2024-10-05 00:04
amarioguystate of the controllers *when u-boot starts i mean, not after bringup#asahi-dev · 2024-10-05 00:03
amarioguyquick question, when exiting m1n1 and chainloading into u-boot what's the state of the type-c controllers? do i need to bring up both the ATC PHY and the DWC3 (along with the PHY tunables) or is the PHY already taken care of in m1n1?#asahi-dev · 2024-08-26 23:25
amarioguyno it's not to run 4k only software, actually need to look at it to see what it does (there are other OSes that assume 4k pages :/)#asahi-dev · 2024-08-26 23:24
amarioguycould someone link the latest version of the "16k IOMMU pages with 4k cpu pages" patch?#asahi-dev · 2024-08-25 19:00
amarioguysaw a comment indicating bypass mode and the probe func seems to be setting bypass mode but just making sure#asahi-dev · 2024-08-25 19:00
amarioguyin u-boot are you all still running the DARTs in bypass mode or are you now using translation mode#asahi-dev · 2024-08-10 21:25
amarioguyso yea back to figuring out how to get this working properly :/#asahi-dev · 2024-08-10 21:24
amarioguynot even a 32 bit read works lol#asahi-dev · 2024-08-10 21:21
amarioguylooks like smth is wrong with PCI controller startup after all#asahi-dev · 2024-08-10 21:21
amarioguynope#asahi-dev · 2024-08-10 21:11
amarioguyi've not had problems with ECAM space so far fwiw, mainly just writing to/reading from BAR registers#asahi-dev · 2024-08-10 21:11
amarioguyjannau: doesn't seem like it? at least edk2 can enumerate devices on the bus and ECAM space can be written to, but i'm not 100% sure if this means that it isn't power/clock gated in some way#asahi-dev · 2024-08-10 21:10
amarioguyi wouldn't be surprised honestly#asahi-dev · 2024-08-10 20:50
amarioguyi adapted the u-boot asmedia xhci code for what i'm doing, 16 bit write and all but who knows if i missed smth#asahi-dev · 2024-08-10 20:48
amarioguyi'm going to try that actually#asahi-dev · 2024-08-10 20:47
amarioguyhmm odd, i've been combing u-boot traces/source to see what you're doing that isn't working on my end, not sure why the 16-bit write to the same register isn't being accepted in my case#asahi-dev · 2024-08-10 20:45
amarioguyprime example being writing ASMT_REG_ADDR during fw upload#asahi-dev · 2024-08-10 20:44
amarioguyat least to those registers#asahi-dev · 2024-08-10 20:44
amarioguyindicating i think that the bus only allows 32 bit writes per the asahi docs#asahi-dev · 2024-08-10 20:44
amarioguyhmm how is u-boot able to do 16bit/8bit writes to some PCI BAR registers on Apple chips? trying those same writes myself results in an SError with L2C_ERR_INF=0x2 #asahi-dev · 2024-08-05 21:41
amarioguygot it, honestly i forgot the tracing facility existed for m1n1 honestly so that's my bad, i'll get that up and running haha#asahi-dev · 2024-08-05 21:16
amarioguyik i'm asking a lot of pcie questions, my apologies i'm just finishing bringing up the asmedia controller for my project and need to shave the yaks to let it work#asahi-dev · 2024-08-05 21:14
amarioguyi'm hitting data aborts/serrors when doing 8 bit/16 bit writes to them, but it looks like U-boot can do non 32 bit writes just fine?#asahi-dev · 2024-08-05 21:14
amarioguyjannau: quick question, are you supposed to write to PCIe memory (like XHCI controller capability/operational regs) under the HV with 32 bit writes?#asahi-dev · 2024-07-29 16:19
amarioguy`<0x02000000 0x0 0xc0000000 0x5 0xc0000000 0x0 0x40000000>;` for anyone who's unsure of what address range i'm trying to access#asahi-dev · 2024-07-29 16:10
amarioguywhenever i'm trying to use them, seems the range is undefined (address below 0xFFFFFFFF, untranslated) in ranges