#asahi-re · 2022-01-20 11:13
marcanso I managed to pull the field diagnostics image from Apple's CDN (normally loads only in field diags mode, but the loader is in the recovery mode image of course)#asahi-re · 2022-01-20 08:07
marcanif you just want the Apple logo back while running m1n1, just do p.fb_restore_logo() or p.fb_shutdown(True)#asahi-re · 2022-01-20 08:04
marcanyou can extract the im4p with img4tool and the image with something like https://github.com/realnp/ibootim#asahi-re · 2022-01-20 08:04
marcanif you're looking for the actual Apple logo used by iBoot, it's in ipsw updates, e.g. Firmware/all_flash/applelogo@1x~mac-USBc.im4p, in a custom format#asahi-re · 2022-01-20 08:02
marcanwhere are you trying to render it and how?#asahi-re · 2022-01-20 08:02
marcannull-nop[m]: that file seems to be unused#asahi-re · 2022-01-20 05:20
null-nop[m]im trying to render `gAppleBootPict` #asahi-re · 2022-01-20 05:18
null-nop[m]https://github.com/apple/darwin-xnu/blob/main/pexpert/pexpert/AppleBoot.h#L42 - even this is related to PowerPC?#asahi-re · 2022-01-20 04:19
marcanI'm not sure exactly what you want to do#asahi-re · 2022-01-20 04:19
marcannull-nop[m]: that code has nothing to do with M1s. BootX is for PowerPC Macs.#asahi-re · 2022-01-20 03:18
null-nop[m]cc marcan #asahi-re · 2022-01-20 03:17
null-nop[m]perhaps will need gfx api? metal?#asahi-re · 2022-01-20 03:17
null-nop[m]is it possible to interpret the logo's pixel and colors as-is on the desktop?#asahi-re · 2022-01-20 03:17
null-nop[m]in display.c file i see it looks up color index from CLUT#asahi-re · 2022-01-20 03:15
TaherAli[m]i'm trying to figure out how the boot loader renders an image on boot process. here's the apple logo: https://opensource.apple.com/source/BootX/BootX-81/bootx.tproj/sl.subproj/appleboot.h.auto.html#asahi-re · 2022-01-16 12:47
svenor just padding introduced by the compiler#asahi-re · 2022-01-16 06:31
JTLreserved sort of thing?#asahi-re · 2022-01-16 03:56
marcanlove it when I'm trying to work out what some fields in a struct do, I look a the DCP code, and they are just... never initialized#asahi-re · 2022-01-14 15:56
h_your project is inspring an interest in me to do more reverse engineering. It seems like you know what you are doing. Anyways, thanks for clarifying that. I hope this weekend to set up the lab with my mac mini#asahi-re · 2022-01-14 04:59
marcanI should probably write an article or give a talk about this some day... it's something that doesn't get talked about much in RE circles#asahi-re · 2022-01-14 04:59
marcanthings get interesting when you get into the finer details of what is copyrightable and what is not; e.g. I've heard a legal opinion that register names are not copyrightable (but I'd still much rather write my own anyway, to be safe and because the official ones often suck)#asahi-re · 2022-01-14 04:57
marcaninstead I'd much rather people always stick to safe things, like looking at input/output including MMIO and other activity traces#asahi-re · 2022-01-14 04:56
marcan(and I've seen it go very wrong when someone didn't know what they're doing, and put an entire project in jeopardy, so I can't just let random people do it)#asahi-re · 2022-01-14 04:55
marcanthere are a few people I trust to peek at binaries occassionally and still be able to write non-infringing code (including myself), but there is no good way to evaluate that other than through trust and watching people work over time#asahi-re · 2022-01-14 04:54
marcanh_: that is correct, as a general rule#asahi-re · 2022-01-12 19:41
h_that, it sounds like, someone else then implements the driver/sw for#asahi-re · 2022-01-12 19:41
h_and if one is going to decompile anything, or look at the code in any way, the output of that work process has to be HW documentation#asahi-re · 2022-01-12 19:38
h_ok. so you're allowed to observe the outputs of the program, but not at the underlying implementation (binary code)#asahi-re · 2021-12-17 10:41
Jamie[m]1just making sure i'm not unnecessarily replicating what's already been done#asahi-re · 2021-12-17 10:41
Jamie[m]1cool#asahi-re · 2021-12-17 10:12
svenbut that 32bit stuff makes sense. Maybe that’s m3wrap-v1 then ;)#asahi-re · 2021-12-17 10:12
svenmaybe, but most of the iPhone RE stuff isn’t documented or even available as source code#asahi-re · 2021-12-17 10:08
Jamie[m]1is there some prior art on REing this stuff that I've missed?#asahi-re · 2021-12-17 10:08
marcanthey did indeed have something like this#asahi-re · 2021-12-17 10:07
Jamie[m]1(just that I think this has equally as much right to be called "an M3 mailbox", not least because apple's kexts call it that)#asahi-re · 2021-12-17 10:07
marcanJamie[m]1: sounds like this is the 32-bit era mailbox#asahi-re · 2021-12-17 10:07
Jamie[m]1(to be clear I'm not arguing that it should be a common codebase, that would indeed be messy)#asahi-re · 2021-12-17 10:06
Jamie[m]1the masks in the upper half of MSG1 also match up to a 32-bit register here#asahi-re · 2021-12-17 10:06
Jamie[m]1exactly as in the linux m3 mailbox driver#asahi-re · 2021-12-17 10:06
Jamie[m]1)#asahi-re · 2021-12-17 10:06
Jamie[m]1(e.g. the host writes 8 to the offset 0x48 to ack an IRQ#asahi-re · 2021-12-17 10:05
Jamie[m]1and some in exact register offsets#asahi-re · 2021-12-17 10:05
Jamie[m]1but there are a ton of similarities in register order#asahi-re · 2021-12-17 10:05
Jamie[m]1the key difference being that messages are just 32 bit#asahi-re · 2021-12-17 10:05
Jamie[m]1fwiw on further RE I am very confident that the mailbox mechanism in the AVD shares ancestry with the other M3 mailbox#asahi-re · 2021-12-16 16:15
marcanJamie[m]1: I've looked at the firmware thing; I'm going to have some kind of fwcutter for the kernel in the installer#asahi-re · 2021-12-16 12:16
svensure, was just curious#asahi-re · 2021-12-16 12:15
Jamie[m]1we can try and reconcile it once i understand it enough, i guess#asahi-re · 2021-12-16 12:13
Jamie[m]1except that it's not identical