#asahi-dev · 2025-10-19 17:36
amarioguy2alright checked mailing list, not there, got my answer, now i'll shut up#asahi-dev · 2025-10-19 17:28
amarioguy2definitely do not intend for you to speed that up, that's just gonna be bad for both of us#asahi-dev · 2025-10-19 17:27
amarioguy2ugh feel dumb now asking that#asahi-dev · 2025-10-19 17:27
amarioguy2whoops sorry!#asahi-dev · 2025-10-19 16:35
amarioguy2sven: any luck getting the PHY patches posted?#asahi-dev · 2025-06-29 16:48
amarioguy2(in case it helps - i'm envisioning the flow here as: timer FIQ fires, traps to EL2, masks the FIQ for a bit to handle it, then HV kicks it to the guest as a virtual IRQ where it proceeds from there)#asahi-dev · 2025-06-29 16:44
amarioguy2my first guess would be the start exception lower proxy call?#asahi-dev · 2025-06-29 16:43
amarioguy2quick question - if we want to redirect the timer IRQ to the guest (as an vIRQ, not enabling the FIQ in EL1 or injecting a virtual FIQ) where would it be best to inject a virtual IRQ in the HV exception handler?#asahi-dev · 2025-06-21 16:53
amarioguy2fl0_id: yes that's sorta been the reason i sometimes ask questions here#asahi-dev · 2025-06-21 16:31
amarioguy2also had a quirk a couple times where sometimes a few instructions before an exception is hit it will "speculate" to the exception directly - which was *so* annoying when trying to debug why exceptions happened#asahi-dev · 2025-06-21 16:30
amarioguy2i don't think it's a foundational m1n1 debugger problem? but at the same time wanted to point the weird behavior out in case anyone else had that behavior (it usually tends to happen when the Windows first-stage bootloader hits an exception and enters the branch loop)#asahi-dev · 2025-06-21 16:28
amarioguy2btw one note on the backtrace thing in m1n1 - more of an aside i wanted to note than anything else - i've had certain situations during my debugging where the hv debugger backtrace is just infinitely spamming the same two addresses when it tries to print the backtrace#asahi-dev · 2025-06-20 21:05
amarioguy2might have a timer interrupt and MADT soon#asahi-dev · 2025-06-20 21:03
amarioguy2fl0_id: i see, thanks! looks like the spec of the vGIC remains unchanged on M3 - which makes implementation at least consistent across M1-M3 platforms#asahi-dev · 2022-11-30 22:03
amarioguy2let's not forget a new challenger, ANE :)#asahi-dev · 2022-11-30 21:57
amarioguy2thanks irc for being supportive :)#asahi-dev · 2022-11-30 21:56
amarioguy2i'm sorry i'm taking a while on figuring stuff out btw life has been particularly unforgiving lately that hobby time is hard to come by#asahi-dev · 2022-11-30 21:56
amarioguy2alright will do#asahi-dev · 2022-11-30 21:55
amarioguy2or well before you commit it, it was your tracer to start with#asahi-dev · 2022-11-30 21:55
amarioguy2fair - tho i do think i want to fix up the tracer still before i commit it to m1n1#asahi-dev · 2022-11-30 21:52
amarioguy2ventura is likely gonna have even more#asahi-dev · 2022-11-30 21:52
amarioguy2sven: on a more serious note, the sep tracer i think should probably not go into tree until i decipher how AP side negotiates which "ipc"/communication protocol more in depth, as tracing 12.3 already had unknown SKS messages very early#asahi-dev · 2022-11-30 21:49
amarioguy2sven: have fun dealing with the untracked stuff :D#asahi-dev · 2022-11-30 20:54
amarioguy2anyways my bad for bringing that up#asahi-dev · 2022-11-30 20:53
amarioguy2...side note i really need to stop bringing up ideas that are 99% certain to not ever happen moving forward...#asahi-dev · 2022-11-30 20:33
amarioguy2puts that idea on ice#asahi-dev · 2022-11-30 20:33
amarioguy2again tho definitely no motivation to move away from DT atm so...#asahi-dev · 2022-11-30 20:33
amarioguy2believe that table has an enum for irqchips#asahi-dev · 2022-11-30 20:32
amarioguy2chaosprincess: there *is* the CSRT table#asahi-dev · 2022-11-30 20:31
amarioguy2obviously i'm not saying that it should happen or even that it will lol#asahi-dev · 2022-11-30 20:31
amarioguy2re acpi - meant it more in a hypothetical sense like if it were to ever happen for whatever reason#asahi-dev · 2022-11-30 18:01
amarioguy2i just thought that for now the "DT vs ACPI" talk would probably be best saved until after the asahi DTs approach anything resembling the term stable, don't want the project to suddenly run into issues with booting because of this kind of change or anything#asahi-dev · 2022-11-30 18:01
amarioguy2i need acpi or at least some semblance of it for trying to boot [proprietary os] anyways lol#asahi-dev · 2022-11-30 18:00
amarioguy2(in seriousness - if ACPI support ever becomes/became a seriously considered thing, i'd be more than willing to work on it)#asahi-dev · 2022-11-30 17:56
amarioguy2when SBSA compliance/ACPI transition /s#asahi-dev · 2022-11-30 17:56
amarioguy2saw the cpufreq news \o/#asahi-dev · 2022-11-23 00:56
amarioguy2re: the "go into OS selector every time" question there's probably some hacky workaround but officially sanctioned i don't think so#asahi-dev · 2022-11-22 13:46
amarioguy2thanksgiving break coming up, should be able to get those sep docs much more up to speed#asahi-dev · 2022-11-02 14:49
amarioguy2ah rip#asahi-dev · 2022-11-02 14:49
amarioguy2no official TBT certification#asahi-dev · 2022-11-02 14:49
amarioguy2sven: i think newest amd mobile processors (6000 series) are usb4 only#asahi-dev · 2022-11-02 14:27
amarioguy2just asking what's the state on PSCI or some derivative thereof?#asahi-dev · 2022-11-02 13:37
amarioguy2shelves that idea#asahi-dev · 2022-11-02 13:37
amarioguy2gotcha that's fair it's not like i'm adamant on this or anything lol it was just something i had thought about the viability of#asahi-dev · 2022-11-02 13:35
amarioguy2i was thinking more from a general "C is obsolete" kinda perspective#asahi-dev · 2022-11-02 13:35
amarioguy2ah you're right, i forgot ADT was verified by iboot anyways#asahi-dev · 2022-11-02 13:33
amarioguy2(ADT code is the thing I'm mainly looking at right now)#asahi-dev · 2022-11-02 13:33
amarioguy2there's already some subsystems I see that can probably be converted to rust with minimal issue#asahi-dev · 2022-11-02 13:33
amarioguy2i realize this is probably going to sound like a crazy idea but long term i think we could start bringing more and more parts of m1n1 over to rust#asahi-dev · 2022-10-25 22:39
amarioguy2(i'm already working on sep this weekend so i don't mind tacking this on the todo list for the weekend)