#asahi-re · 2023-01-14 01:24
amarioguymarcan: i don't want to wade into binary re in #asahi but i looked at the reduced security tickets they root to a different root ca#asahi-re · 2023-01-13 13:10
ChaosPrincessq3k: you might want to look at what sandcastle people are doing. though caveat emptor on their code, i recommend checking it before using#asahi-re · 2023-01-13 10:13
marcanmight want to compare with S3C2400 which has the RX TO enable bit in a different position#asahi-re · 2023-01-13 10:13
marcanq3k: I believe the original implementation had discrete IRQs, then Apple merged them into one, so it's possible that one still has them split#asahi-re · 2023-01-13 10:08
q3ks,UTCON,UCON,#asahi-re · 2023-01-13 10:07
q3ki guess i'll just continue poking at it and re-re-read the original firmware's implementation#asahi-re · 2023-01-13 10:07
q3kthe only thing i've found so far is that if i poke some other bits in UTCON i start getting interrupts on another IRQ, but that still doesn't seem to be the rx timeout.#asahi-re · 2023-01-13 10:06
q3kmarcan: yeah, i think i have all of this correct. i am getting the rx threshold interrupt, just not the timeout interrupt. pretty sure sequencing is also correct, i'm 'just' using the linux driver already there, and even if it's broken at startup then during the next threshold-driven drain of the fifo things should re-sequence correctly.#asahi-re · 2023-01-13 03:44
marcanyou need to make sure the IRQs are enabled (possibly masked at the IRQ controller, but enabled as far as the UART goes), clear the UTRSTAT bits (they're write 1 to clear), drain the RX FIFO, and then you should get an IRQ next time a byte comes in and times out#asahi-re · 2023-01-13 03:44
marcaninternally edge triggered that is#asahi-re · 2023-01-13 03:43
marcani.e. RXTO won't fire if you enable it with stuff already in the FIFO#asahi-re · 2023-01-13 03:43
marcanalso IIRC these chips only have edge triggered IRQs, so you need to get the sequencing right#asahi-re · 2023-01-13 03:41
marcandid you look at the bit defines from linux?#asahi-re · 2023-01-13 03:40
marcanq3k2: I looked at that (mostly blind over the same UART lol), IIRC the closest relative was S3C2400 but some things were moved around#asahi-re · 2023-01-12 11:36
q3k2anyone here who dealt with reverse engineering the S5L UART peripheral/drivers? i'm currently porting Linux to the iPod Nano 5G (S5L8730) which has a seemingly very similar version of the peripheral, but i can't get RX timeout interrupts working.#asahi-re · 2023-01-08 11:24
Baboon<r0ni> dont recall irc working like that // https://oftc.irclog.whitequark.org/asahi-re/2023-01-01#asahi-re · 2023-01-08 11:24
BaboonThks amarioguy#asahi-re · 2023-01-07 23:58
jannauon the otherhand I'm not sure if there's that much to RE. the swap surface structure has 3 timestamps. ts3 seems to be the current time and is always set, ts1/ts2 are not always set (at least during boot). ts1 and ts2 have a delta less than a frame duration, ts1 is in the future (maybe a deadline), ts2 is less clear. timestamps have a resolution of 24MHz#asahi-re · 2023-01-07 23:52
jannauI don't think anyone has looked at VRR/"pro-motion" yet. RE through tracing might be a little bit annoying since the current python based proxy tracing is slow#asahi-re · 2023-01-07 23:51
jannausawyer: that would be dcp. drivers/gpu/drm/apple in the linux tree and proxyclient/hv/trace_dcp.py and proxyclient/m1n1/fw/dcp/ in m1n1. there is little content here since we mostly RE it through HV tracing, discussions are mostly in #asahi-dev since it doesn't involve binary RE#asahi-re · 2023-01-07 23:06
sawyerHi all, wasn't able to find anything in the asahi-re logs but I have a 16 inch m1 on its way and was wondering if either someone else is working on vrr/"pro-motion" support or if that would be something where help would be welcome? I don't have a ton of prior reverse engineering experience, but hopefully have enough systems dev background to make some progress#asahi-re · 2023-01-04 23:22
roxfanah ok#asahi-re · 2023-01-04 23:20
jannauworks for me, there was simply no talk since 2023-01-01#asahi-re · 2023-01-04 23:18
roxfanoh, logs are broken?#asahi-re · 2023-01-01 20:56
amarioguyok i am convinced at this point that the "tag" part of xART manager messages are an index of sorts#asahi-re · 2023-01-01 20:05
amarioguynow time to solve the "different" CRC question#asahi-re · 2023-01-01 20:05
amarioguybtw - hi all will be less flaky hopefully this year#asahi-re · 2023-01-01 20:04
amarioguyBaboon: yes - build the kernelcache with kmutil then set it as the custom boot object#asahi-re · 2023-01-01 19:34
r0nidont recall irc working like that#asahi-re · 2023-01-01 17:33
Baboon(I ;ay quit this chan but I'll read the log so if you have any idea, do not hesitate to write it even if I'm gone :P)#asahi-re · 2023-01-01 17:28
Baboon(with a virtualized M1 mac or a "real"one)#asahi-re · 2023-01-01 17:27
BaboonKDK doc says no but maybe you are aware of a way...#asahi-re · 2023-01-01 17:27
Baboonhi, do you know if it is possible to boot kernel variant on M1 CPUs?#asahi-re · 2022-12-06 09:13
karpouzioh whoops i'm on wrong channel. going to #asahi-dev#asahi-re · 2022-12-06 09:13
karpouziah ok cool, amarioguy and marcan finished #2#asahi-re · 2022-12-06 09:11
karpouziis this page still up to date? https://github.com/AsahiLinux/docs/wiki/Yaks-in-need-of-shaving#asahi-re · 2022-12-06 09:09
karpouzigood evening#asahi-re · 2022-12-05 02:25
marcaneiln: given they're two independent blocks I think the answer is to just expose them as separate devices and let userspace figure out how to balance work#asahi-re · 2022-12-04 19:47
eilnyknow the word concurrency does remind me of a certain orange lang...#asahi-re · 2022-12-04 19:47
eilnultra's gonna be the problem child #asahi-re · 2022-12-04 19:47
eilnafaik t8103 ane vs. ane-0 just need mmio base adjustment + small tweaks for soc/pwr #asahi-re · 2022-12-04 19:46
eilnnaming hell#asahi-re · 2022-12-04 19:46
eilnthe ne i was referring to earlier was "computation engine" or the madd groups#asahi-re · 2022-12-04 19:46
eilnmarcan: yes yes #asahi-re · 2022-12-03 14:15
marcanhence my theory about silicon bug or power delivery issues#asahi-re · 2022-12-03 14:15
marcanso there is only one die, max, with two anes, and one is always disabled#asahi-re · 2022-12-03 14:15
marcanpro only has one ane#asahi-re · 2022-12-03 14:15
marcanpro does not have ane1 at all#asahi-re · 2022-12-03 14:15
marcanane1 is the broken one, which means also ane3 on ultra#asahi-re · 2022-12-03 14:14
marcanif ane0 works on max then ane2 will work on ultra since it's just two of the same thing