#
…

2022-06-18

00:56nafod has quit [Quit: Ping timeout (120 seconds)]
00:56nafod has joined #asahi-re
01:00DragoonAethis has joined #asahi-re
01:04DarkShadow44 has joined #asahi-re
01:20Emantor has joined #asahi-re
02:27PhilippvK has joined #asahi-re
05:20the_lanetly_052 has joined #asahi-re
06:49Astra[m] has joined #asahi-re
07:32MajorBiscuit has joined #asahi-re
08:52MajorBiscuit has quit [Quit: WeeChat 3.5]
11:37chadmed has quit [Ping timeout: 480 seconds]
11:42chadmed has joined #asahi-re
11:46chadmed has quit []
12:29the_lanetly_052__ has joined #asahi-re
12:35the_lanetly_052 has quit [Ping timeout: 480 seconds]
12:44the_lanetly_052__ has quit [Remote host closed the connection]
14:06MajorBiscuit has joined #asahi-re
14:06MajorBiscuit has quit []
14:13MajorBiscuit has joined #asahi-re
14:26sveni've started to look into bluetooth with R's notes a bit. looks like apple calls the transport used for communication with the actual chip "apple converged IPC" and maybe also "apple converged PCI"
14:42MajorBiscuit has quit [Ping timeout: 480 seconds]
15:20MajorBiscuit has joined #asahi-re
15:51MajorBiscuit has quit [Ping timeout: 480 seconds]
15:57MajorBiscuit has joined #asahi-re
16:03MajorBiscuit has quit [Quit: WeeChat 3.5]
16:43nicolas17 has joined #asahi-re
16:55marcan(no idea where those came from, but public decryption keys for public firmware blobs are fair game FWIW)
16:55nicolas17oh so he just tweeted them out lol
16:55marcanso I guess we can finally decrypt iBoot/SMC and answer some mysteries that way (RE policy still applies as usual, don't do that if you're writing drivers and I don't know you know what you're doing)
16:56svenhuh, cute
16:57sventhe one iboot i briefly looked at contained almost no strings and wasn't much fun to reverse engineer fwiw
16:57marcanI'm more interested in things like like SMC, I looked at an iPhone one and that helped answer some questions but there was enough that was different to leave plenty of mysteries
16:57marcanalso since SMC is always on, this is good for proving absence of backdoors and such
16:58svenyeah, i looked for the ANS shutdown sequence I think
16:58svenand even finding that was annoying
16:58svenand I missed the PMGR reset anyway
16:58marcanthe DCP client side would be nice to find too
16:59marcanand also exactly what algorithm apple used to use for mode selection before they nixed it
16:59marcanalso, IIRC iBoot talks to some EPIC endpoints besides the iBoot/disp0 one
17:00marcanand I'd love to know what it does with those
17:00marcanI already reversed some of it, it's in proxyclient stuff
17:00marcanbut I didn't find anything useful to solve the hotplug problem
17:00marcanthough I bet it could be done with i2c shenanigans poking the dp2hdmi chip, but that's *another* layer of blind undocumented registers
17:01marcan(since the HPD pin goes through it)
17:01marcanwe do have firmare for that one
17:01marcan... it's x86. 80186.
17:01marcanso yeah, nice rabbit hole for someone to go down if they're bored
17:01nicolas17as if knowing there's an x86 iPhone baseband wasn't cursed enough already
17:02marcantbh though, the current "shut down DCP" solution is quite pretty, and better than prodding magic registers and having to have linux prod them back
17:02marcanI think I'm going to stick with that for now
17:03marcanneed to fix up Linux RTKit so it uses an always-safe sequence to bring up RTKit that works regardless of what shutdown mode a copro is in
17:03marcanthen it doesn't have to care
17:05nicolas17these keys were probably extracted via JTAG on a CPFM00 (prototype) M1 chip that "fell off a truck", but if you hypothetically exploited a bootrom bug or something on a production M1, you could get the same keys
17:05nicolas17(I know marcan knows this, just stating it for everyone reading :p)
17:09marcanRight. I don't endorse all that "fell of a truck" stuff, but if the end result is data that is in everyone's M1 anyway being published, I'm not going to say no to using it.
17:10marcanUltimately those keys being public help a lot of causes, including verifiability of the boot chain.
17:10marcan(I wish Apple just stopped encrypting this stuff)
18:12roxfan2which fw ois 80186? o.o
18:12marcanjannau: ah, thanks!
18:12jannaurequires unfortunately another reg since we have offsetted the regs by 0x4000
18:13sventhat was on purpose because not all mailboxes have that reg
18:13sveniirc SEP and the thunderbolt ones don’t
18:14jannauah, then adding it conditionally where needed is the right thing to do
18:14jannauroxfan2: the dp to hdmi converter used for the hdmi ports
18:16jannauanswering your question which chip is 80186
18:24svenalright, so these myster config space writes (https://github.com/rqou/m1-bluetooth-prototype/blob/f2873340b28fed052550ca51554e85af5cd24b0e/test.py#L184) actually just configure the memory/MMIO/whatever windows that can be accessed in the BAR
18:24sventhat still seems to be common broadcom stuff, there are some vague references to this in the wlan driver as well
18:24sven*mystery
18:26svenfirmware selection also seems to be rather simple: get the chip name from the PCI dev id and then get the antenna or whatever island code name from the DT just like wifi. there's only a third component I don't understand yet (USI vs. MUR)
18:47nicolas17does anyone know if AWDL is implemented in the macOS driver or in the Wi-Fi firmware?
19:35marcanboth, I believe
20:47jakebot6 has joined #asahi-re
22:16nsklaus_ has joined #asahi-re
23:00jakebot6 has quit [Quit: The Lounge - https://thelounge.chat]
23:16jakebot6 has joined #asahi-re
…