#
✕ nick:amarioguy
#asahi-dev · 2025-10-13 12:47
amarioguyvalid
#asahi-dev · 2025-10-13 12:40
amarioguyalr ping me when that dwc3 series is sent, going to begin integrating it then
#asahi-dev · 2025-10-13 12:38
amarioguyor did you submit a v3 or smth
#asahi-dev · 2025-10-13 12:38
amarioguycurrent version is still v2 on the mailing list right?
#asahi-dev · 2025-10-13 12:38
amarioguygot it
#asahi-dev · 2025-10-13 12:38
amarioguyah we no longer rely on FDTs, mostly the hardware part is our concern
#asahi-dev · 2025-10-13 12:37
amarioguywe have USB2 working fine, it's more specifially USB3
#asahi-dev · 2025-10-13 12:37
amarioguyand figured i'd ask if it's "safe" to do so relatively speaking
#asahi-dev · 2025-10-13 12:37
amarioguyreason i'm asking is i might be bringing that code in to my UEFI implementation to bring up XHCI
#asahi-dev · 2025-10-13 12:36
amarioguyas in "there aren't like super major breaking bugs" kinda thing
#asahi-dev · 2025-10-13 12:36
amarioguysven: is the USB3 bringup series that's currently on the mailing list stable?
#asahi-dev · 2025-08-07 12:31
amarioguywell including what was said about xARTs/gigalockers earlier, we do also care about those
#asahi-dev · 2025-08-07 12:23
amarioguysnklp: saw your messages, wanted to clarify something about SEP, for the purposes of Asahi, we only really particularly care about AP<->SEP communication, because the SEP's firmware itself is basically a black box we have no control over apart from firmware version (it's signed by Apple with no means of signing our own)
#asahi-dev · 2025-06-14 18:14
amarioguyquick q - anyone remember the register that was masking SErrors/"disabling error reporting" in the January/February 2021 blog post?
#asahi-dev · 2025-06-10 17:24
amarioguyahh i see
#asahi-dev · 2025-06-10 17:19
amarioguyseems like LPIs might be more general based on what you're saying
#asahi-dev · 2025-06-10 17:18
amarioguymakes sense - i should look at how that works, because my understanding of the GIC documentation led me to believe that you use SPIs for HW not on the PCIe bus and LPIs as a stand-in for MSIs
#asahi-dev · 2025-06-10 17:16
amarioguyalright makes sense - i kinda thought that at first but wanted to sanity check it
#asahi-dev · 2025-06-10 17:11
amarioguyok so still probably safer to not do ext spi ranges in my emulated distributor - but then we have a different problem, most apple platforms have > 1024 irqs so i'm not sure if i need to compress some irqs to a single intid
#asahi-dev · 2025-06-10 17:09
amarioguycan't find which series it's a part of unfortunately
#asahi-dev · 2025-06-10 17:08
amarioguythat seems to just be a warning and define tho, seems to be part of a larger patchset for the gic driver?
#asahi-dev · 2025-06-10 17:08
amarioguymaz: "irqchip/gic-v3: Warn about inconsistent implementations of extended ranges", commit ad5a78d
#asahi-dev · 2025-06-10 16:59
amarioguyjust saw maz's cursed patchset for that...
#asahi-dev · 2025-06-10 16:58
amarioguyso it turns out that the cpu interface not supporting extended spi ranges isn't a roadblock to supporting them period....
#asahi-dev · 2025-06-07 23:50
amarioguymay as well try tho
#asahi-dev · 2025-06-07 23:49
amarioguysven: no yea for sure this is definitely not a single day work, definitely didn't mean to imply that, personally doubt i'm gonna be the one to finish it out
#asahi-dev · 2025-06-07 22:05
amarioguyok fair enough - should be able to work on this tomorrow then
#asahi-dev · 2025-06-07 21:56
amarioguyor do we just...not let anything access gl2?
#asahi-dev · 2025-06-07 21:55
amarioguy(for m1/m2/m3)
#asahi-dev · 2025-06-07 21:55
amarioguysven: i assume to "disable" SPTM/GXF - we need to set the same defeature register iboot sets on m4?
#asahi-dev · 2025-06-07 21:42
amarioguyok so will have to do a mach-o here then
#asahi-dev · 2025-06-07 21:40
amarioguyi assume the KDK kernels also need SPTM?
#asahi-dev · 2025-06-07 21:40
amarioguyyes exactly my concern, if the de-feature disables the nested case, that's bad
#asahi-dev · 2025-06-07 21:39
amarioguybtw moving to asahi-re for a sec
#asahi-dev · 2025-06-07 21:39
amarioguyright - i have an m4 system anyhow, just got it in today so i can look into it in a day or so - i believe apple does have a way to do nested virtualization of SPTM/GXF stuff so it probably can be done but to say "messy" is putting it lightly i suspect
#asahi-dev · 2025-06-07 21:35
amarioguyohhhh i see the dilemma now ugh
#asahi-dev · 2025-06-07 21:35
amarioguyik that on m4 apple makes it so that you either run under SPTM at all times if you specify a mach-o to kmutil, or you don't get GXF at all if you do raw binary instead, but wouldn't tracing be possible in the latter case anyways?
#asahi-dev · 2025-06-07 21:34
amarioguyor the opposite, where you need it jettisoned entirely?
#asahi-dev · 2025-06-07 21:33
amarioguysven: for m4 bringup, i assume the problem is mainly that you need GXF for m1n1 to be able to do HV tracing?
#asahi-dev · 2025-06-07 21:25
amarioguyfl0_id: hm - i guess you could try reading ICH_VTR_EL2? (would be a mrs(ICH_VTR_EL2) in m1n1 console) would verify if the CPU interface exists at least
#asahi-dev · 2025-06-07 19:03
amarioguyright, heard of that one, for now, i'll probably just hard limit my support to m1/m2 and pro equivalents until i get more time to properly examine the m4 case
#asahi-dev · 2025-06-07 19:01
amarioguysven: does m4 at least boot to m1n1 shell as of rn?
#asahi-dev · 2025-06-07 18:56
amarioguywhich m1n1 then recovers from
#asahi-dev · 2025-06-07 18:56
amarioguythe uart timeout is concerning tho - because an undefined MSR would throw an exception
#asahi-dev · 2025-06-07 18:55
amarioguyfl0_id: saw the results - that register should be well defined on the platform?
#asahi-dev · 2025-06-02 23:59
amarioguyjust post it whenever you're done, i read IRC backlogs often here so dw about me missing it or anything
#asahi-dev · 2025-06-02 23:58
amarioguyfl0_id: any update on the MSR?
#asahi-dev · 2025-06-02 19:51
amarioguykettenis: actually, i saw a commit recently adding some SMBIOS handling to m1n1 - i assume the FDTs are supposed to have necessary SMBIOS information in the future?
#asahi-dev · 2025-06-02 19:21
amarioguyah got it - it's not a major rush or anything, just makes it quite annoying to find what my actual changes are
#asahi-dev · 2025-06-02 19:19
amarioguyprobably part of building the rust side, which makes sense, i guess my real question is why is rust/target not in gitignore :P

plus ›