#asahi-gpu · 2021-01-13 13:09
davidrysk[m]No cmake or meson#asahi-gpu · 2021-01-13 13:08
davidrysk[m]Im suggesting plain make at this point#asahi-gpu · 2021-01-13 13:08
davidrysk[m]I can write some example makefiles#asahi-gpu · 2021-01-13 13:08
bloomdavidrysk[m]: Overestimating my ability to use anything but meson tbh#asahi-gpu · 2021-01-13 07:58
rupNow it's clear why marcan mentioned two machines in the Patreon video.#asahi-gpu · 2021-01-13 07:57
rupdavidrysk[m]: I got it; I didn't pay attention to the goal to dual boot. So to answer my own question: I could do with one machine; however, switching between them can soon become tedious. Now it#asahi-gpu · 2021-01-13 04:52
rupSorry to harp on the first question: what's a recommended hardware setup for the GPU work which for me would be repeating/reproducing all your work? At least that is how I think I could make some headway.#asahi-gpu · 2021-01-13 04:48
rupI have tons of questions to ask.#asahi-gpu · 2021-01-13 04:47
rupdavidrysk[m]: thank you!#asahi-gpu · 2021-01-13 04:41
davidrysk[m]bloom: have you thought about adding Makefiles? :)#asahi-gpu · 2021-01-13 04:41
davidrysk[m]Basically one would compile a simple shader, intercepting the system calls that push it to the GPU, and figure out the format, instruction set, etc#asahi-gpu · 2021-01-13 04:40
rupYes, I have, once, but I need to read it several times, which I shall.#asahi-gpu · 2021-01-13 04:39
davidrysk[m]take a look at bloom's article here: https://rosenzweig.io/blog/asahi-gpu-part-1.html#asahi-gpu · 2021-01-13 04:39
rupI see. Can you describe, in brief, what the workflow is like, for those of you hacking on the GPU/graphics aspect? (Everything is new to me, for example, I don't have a clear idea of 'blackbox RE', but I hope to disambiguate concepts through conversations).#asahi-gpu · 2021-01-13 04:36
davidrysk[m]People here are already doing blackbox RE of the GPU#asahi-gpu · 2021-01-13 04:36
davidrysk[m]Yeah. That's more on topic for #asahi though.#asahi-gpu · 2021-01-13 04:35
rupOk, so that is something one is blocking on Apple for: the tooling to boot a custom OS object?#asahi-gpu · 2021-01-13 04:33
davidrysk[m]The documentation is there, but the tooling doesn't function yet#asahi-gpu · 2021-01-13 04:33
davidrysk[m]The planned goal is to be able to dual boot, but Apple hasn't yet provided the tooling for signing a custom OS object.#asahi-gpu · 2021-01-13 04:29
rupFrom what I gleaned; in hearing marcan on the Patreon video, and IRC logs here, I need, at the least, one Apple M1 machine (say, the Mac Mini) at the outset. The introductory work bloom has talked about has been on MacOS if I understood correctly. For the GPU work, at some point of time, would one need two machines: one to look at MacOS graphics internals, and one to boot the Asahi kernel and run/test a graphics driver?#asahi-gpu · 2021-01-13 04:23
rupHello, I'm completely new to low-level graphics and reverse engineering altogether, but I wish to learn as much as I can following this project.#asahi-gpu · 2021-01-13 03:33
bloomdavidrysk[m]: "Metal"#asahi-gpu · 2021-01-13 03:04
davidrysk[m]what do you normally see when AGX_SELECTOR_SET_API is used?#asahi-gpu · 2021-01-13 02:36
bloom[via an appropriately timed system("ioreg -n AGXDeviceUserClient") ]#asahi-gpu · 2021-01-13 02:35
bloom | | | "IOUserClientCreator" = "pid 1183, a.out"#asahi-gpu · 2021-01-13 02:35
bloom | | | "AppUsage" = ()#asahi-gpu · 2021-01-13 02:35
bloom | | | "API" = "Equestria"#asahi-gpu · 2021-01-13 02:34
bloomwhile it's running will show that it's working, i.e.#asahi-gpu · 2021-01-13 02:34
bloom% ioreg -n AGXDeviceUserClient#asahi-gpu · 2021-01-13 02:34
bloomclang compile with -framework IOKit ... the header selectors.h is in wrap/#asahi-gpu · 2021-01-13 02:33
bloom^ that should reproduce the error#asahi-gpu · 2021-01-13 02:33
bloomdavidrysk[m]: https://github.com/AsahiLinux/gpu/blob/main/lib/iokit.c#asahi-gpu · 2021-01-13 02:33
davidrysk[m]I started digging at trying to figure out how it does error handling but got sidetracked :)#asahi-gpu · 2021-01-13 02:32
bloomdavidrysk[m]: Yes, why?#asahi-gpu · 2021-01-13 02:31
davidrysk[m]bloom: are you still poking at IOConnectCallMethod?#asahi-gpu · 2021-01-13 02:12
bloompushed some code to poke iokit#asahi-gpu · 2021-01-13 02:11
JTLassumed as much#asahi-gpu · 2021-01-13 02:09
bloomJust poking at the fact there's an IOKit call that returns, among other things, that date.#asahi-gpu · 2021-01-13 02:08
bloom*emoticon#asahi-gpu · 2021-01-13 02:08
bloomIt was sardonic, hence the emotion :)#asahi-gpu · 2021-01-13 02:08
JTLOtherwise, nevermind#asahi-gpu · 2021-01-13 02:08
JTLJust asking why, given said modules are proprietary#asahi-gpu · 2021-01-13 02:08
JTL> Would it be too much to ask that macOS's proprietary kernel modules were reproducible?#asahi-gpu · 2021-01-13 02:07
bloomJTL: Why what?#asahi-gpu · 2021-01-13 02:02
JTLwhy?#asahi-gpu · 2021-01-13 01:44
bloomWould it be too much to ask that macOS's proprietary kernel modules were reproducible? ;P#asahi-gpu · 2021-01-13 01:43
bloomKext build date: Oct 31 2020 00:19:38#asahi-gpu · 2021-01-13 01:09
bloomall the function names are starting to blend :p