#asahi · 2023-06-29 11:03
ydaltonhi, i've noticed that sometimes when entering recovery mode, the keyboard backlight goes on. does the presence or absense of the backlight indicate that you're in 1TR or regular recovery mode? because so far i've seen conflicting results.#asahi · 2023-06-26 19:49
ydaltonhuh, interesting#asahi · 2023-06-26 19:47
ydaltonj`ey: hold on, unicorn is a library for emulation?#asahi · 2023-06-26 19:42
ydaltonoh i didn't see this, thanks for the read#asahi · 2023-06-26 19:39
ydaltonoh right, i must have mixed up the terms#asahi · 2023-06-26 19:36
ydaltonthey're all high edge triggered i guess#asahi · 2023-06-26 19:35
ydaltonand what about devices internal to the soc?#asahi · 2023-06-26 19:33
ydaltonsorry, my only understanding of gpio and i2c comes from school classes, and they didn't do a particularly good job at that lol#asahi · 2023-06-26 19:30
ydaltonalso i saw the i2c uses the _LOW version#asahi · 2023-06-26 19:28
ydaltonso either will work, but you'll have to find the better option, am i understanding that correctly?#asahi · 2023-06-26 19:24
ydaltonalright, i'll take a look at that python script#asahi · 2023-06-26 19:20
ydaltonafaik m1n1 can hexdump memory regions right?#asahi · 2023-06-26 19:20
ydaltonalthough tbh tracing mmio writes was gonna get old soon#asahi · 2023-06-26 19:17
ydaltonwait that's R?#asahi · 2023-06-26 19:16
ydaltonif i recall correctly, the way alyssa reverse engineered part of the gpu driver was to do it through macOS first#asahi · 2023-06-26 19:13
ydaltonthe first one though, that looks like normal python code?#asahi · 2023-06-26 19:13
ydaltonwow thanks, although i have no idea how to even write any of these#asahi · 2023-06-26 19:10
ydaltonlol, looking through the MMIO tracer i saw a stray 0xdeadcafe which piqued my curiosity#asahi · 2023-06-26 19:09
ydaltoni haven't found anything, although that might be helpful#asahi · 2023-06-26 19:06
ydaltoni'm trying to figure out how the AVD works#asahi · 2023-06-26 19:05
ydaltoneh i'll see if _HIGH works since most other devices do that#asahi · 2023-06-26 19:03
ydaltonlol there it is#asahi · 2023-06-26 19:00
ydaltonbut how can you know when to use one or the other?#asahi · 2023-06-26 18:58
ydaltonnever knew about that#asahi · 2023-06-26 18:58
ydaltonah, it says all symbols#asahi · 2023-06-26 18:57
ydaltonnext to the search there's a dropdown to choose if you want to look in C source code or device trees#asahi · 2023-06-26 18:57
ydaltonoh, it's not a bug, its a feature??#asahi · 2023-06-26 18:56
ydaltonhuh, i think bootlin's linux source code explorer is bugged, i searched for _LOW and it didn't show any apple silicon device trees#asahi · 2023-06-26 18:54
ydaltonoh, in the i2c0 node, i see#asahi · 2023-06-26 18:53
ydaltonwhere's that?#asahi · 2023-06-26 18:52
ydaltonto see _LOW#asahi · 2023-06-26 18:52
ydaltoneven in other device trees (outside apple silicon) its pretty rare#asahi · 2023-06-26 18:51
ydaltoncan i just get away with using IRQ_TYPE_LEVEL_HIGH, seeing i haven't seen it in one of the linux device trees#asahi · 2023-06-26 18:51
ydaltonand comparing that with the linux device tree i see those same numbers#asahi · 2023-06-26 18:50
ydaltonno i mean, i usually see something like "interrupts = [753, 643, 642, 856]"#asahi · 2023-06-26 18:49
ydaltoni've never seen something like that#asahi · 2023-06-26 18:49
ydaltonhuh?#asahi · 2023-06-26 18:44
ydaltonyes#asahi · 2023-06-26 18:44
ydaltonyeah that's what i mean#asahi · 2023-06-26 18:44
ydaltonm1n1 has a command in the shell that retrieves the device tree passed from iboot (i think?)#asahi · 2023-06-26 18:39
ydaltonhi, question about device tree. comparing my device tree spat out my m1n1 and the device tree in the kernel source, i've noticed in the interrupts section, the Linux version always uses the IRQ_TYPE_LEVEL_HIGH macro rather than IRQ_TYPE_LEVEL_LOW. how can i know when to use one or the other when writing my own node? thanks!