14:30 <renmg> hi, I'm an experienced (windows and linux) reverse engineer specialized in DRM-protected software getting into ARM in the next few days as my first ARM machine (M3 pro) is arriving, are there any mailing lists / groups to get up to speed as to what asahi currently needs? I would love to contribute.

14:35 <j`ey> renmg: best place is github.com/asahilinux

14:36 <j`ey> the docs/wiki has good background info about m1n1 (the bootloader/RE tool)

14:40 <j`ey> note that M3 is barely supported currently (and only M3 Max is a little supported)

14:40 <renmg> yeah i read the wiki and i saw that i likely won't be able to do anything on them, but that's fine, and it's why i intend to contribute

14:41 <renmg> spent a good chunk of time reading the code of conducts last night as well, seems that if i do end up reverse engineering a system component, i cannot do anything but write hardware docs for someone else to implement, correct?

14:42 <j`ey> most of the the people that RE stuff here, try to use m1n1 with its tracing capabilites, to avoid reading kexts

14:42 <j`ey> so that they can also contribute code

14:43 <renmg> ah, i understand

14:44 <j`ey> before you started decompiling stuff I would clarify it with mar(c)an

14:45 <renmg> yeah, I'll familiarize myself with m1n1 and minimize decompilation if I ever do end up needing it, and I'll clear it with whoever will have to end up accepting or rejecting my contributions, don't wanna put the project at risk or waste anyone's time here

14:50 <sven> the issue with decompilation is that it's very easy to end up implementing apple's logic 1:1 instead of understanding the hardware. that's why it's better to be very careful and the reason for that policy

14:51 <sven> (see e.g. all those retro game decompilation projects which create source code that compiles 1:1 to the original game for an extreme example of that)