#
#asahi-re · 2025-10-28 21:26
nicolas17also the source dump is for the kernel alone
#asahi-re · 2025-10-28 21:23
svenit won’t even have all function names probably
#asahi-re · 2025-10-28 21:23
svenit won’t have full debug symbols, etc
#asahi-re · 2025-10-28 21:22
sventhose development builds are also meant for people who write kexts and are probably not what Apple uses internally
#asahi-re · 2025-10-28 21:22
nnymI suspected that something was missing. So it's true after all.
#asahi-re · 2025-10-28 21:20
svenkeep in mind the the source dump is incomplete because Apple redacts all the interesting parts
#asahi-re · 2025-10-28 21:19
nicolas17I'm actually not sure if ghidra can use complete debugging symbols (with line numbers and local variable names) even if they were present...
#asahi-re · 2025-10-28 21:18
nnymYeah.
#asahi-re · 2025-10-28 21:18
nicolas17you can cross-reference it to the source code then
#asahi-re · 2025-10-28 21:17
nnymYeah but this is a development build and XNU's source code is public.
#asahi-re · 2025-10-28 20:51
nicolas17if you're lucky, there's symbols and functions get names :D
#asahi-re · 2025-10-28 20:51
nicolas17usually local variables and parameters never get names when decompiling native code
#asahi-re · 2025-10-28 20:49
nnymWell, they do have names but they're like "param_1" and "uVar1".
#asahi-re · 2025-10-28 20:47
nnymI have `kernel.development.t6041` from the 25A353 KDK loaded in Ghidra and functions and global variables have names but parameters and local variables don't. Is this how it should be?
#asahi-re · 2025-10-24 08:18
chadmedhttps://asahilinux.org/2025/10/progress-report-6-17/
#asahi-re · 2025-10-22 20:37
k70yes please
#asahi-re · 2025-10-22 14:24
auscyber_k70: you wanted one right?
#asahi-re · 2025-10-22 14:23
auscyber_im in australia, so if anyone wants me to send them one (ofc paying like a quarter of what i paid with shipping, lemme know)
#asahi-re · 2025-10-22 14:23
auscyber_i got my 4 central scrutinizer boards!
#asahi-re · 2025-10-17 11:44
jannauit's atc-phy2 on the m5 macbook pro so it's not necessarily constant
#asahi-re · 2025-10-17 11:43
jannaufor one most of the ADT nodes ashould be missing except for atc-phy3 on j314 for example
#asahi-re · 2025-10-17 11:42
jannaulook for atc-phyX, dart-usbX, usb-drdX, acioX, ...
#asahi-re · 2025-10-17 11:39
jannaufrom interpolation from other macbook pros
#asahi-re · 2025-10-17 11:30
nnymYou can tell? It's all the same to me.
#asahi-re · 2025-10-17 11:21
chaos_princessyea, thats hdmi
#asahi-re · 2025-10-17 11:16
nnymInteresting. In case you're still interested, the names are "ATC{0,1}-USB-V", "ATC{0..3}_CIO_USB", "ATC{0..3}_USB_AON", "ATC{0..3}_USB", "ATC{0..3}-USB-DART", "AUSB{0..3}-AONPCIE-V", and "ATC{0..3}_USB_AON_V".
#asahi-re · 2025-10-17 11:11
jannauI would be more surprised if it didn't but I haven't tested
#asahi-re · 2025-10-17 11:10
chaos_princessdoes that port accept vdms too?
#asahi-re · 2025-10-17 11:09
jannausomeone should design a power supply which reboots magsafe macs every 10 minutes or so
#asahi-re · 2025-10-17 11:08
jannaumagsafe has only a standalone usb PD controller (hpm) and uses no USB functionality on the SoC
#asahi-re · 2025-10-17 11:07
jannauthe 4th is used to drive the HDMI port via DP to HDMI bridge in constant DP-altmode, no usb functionality
#asahi-re · 2025-10-17 11:06
chaos_princesscould be magsafe, could be hdmi, what are the names?
#asahi-re · 2025-10-17 11:04
nnymJ616c has 6 groups of 4 similarly named USB pmgr devices but there are only 3 USB ports. The exceptions are "ATC{0,1}-USB-V" which are only 2. What does that mean? Is the MagSafe port the 4th?
#asahi-re · 2025-10-16 21:24
chaos_princessmachine-specific as in different machines of the same type. My j314 vs your j314 and so on. Ofc they change between socs
#asahi-re · 2025-10-16 21:22
nnymI'm seeing some differences between J516c and J616c.
#asahi-re · 2025-10-16 21:13
chaos_princessi think reg are never machine-specific
#asahi-re · 2025-10-16 21:11
nnymOh. Well, as it turns out, I don't need it for now. I was looking at `/arm-io/pmgr`'s `reg` and it's the same in the IPSW.
#asahi-re · 2025-10-16 20:48
jannaulike wlan secrets
#asahi-re · 2025-10-16 20:47
svenalso the usual warning: the full ADT blob contains a bunch of sensitive data
#asahi-re · 2025-10-16 20:19
jannaunnym: this is probably one of the best places to ask. I could only offer j314c but I'm not really sure what you expect to find there. Maybe ask specific questions what you're looking for
#asahi-re · 2025-10-16 20:12
nicolas17I only have a J493
#asahi-re · 2025-10-16 20:11
nicolas17and you need it filled in by the boot process rather than extracted from the ipsw?
#asahi-re · 2025-10-16 19:58
nnymJ616cAP
#asahi-re · 2025-10-16 19:56
nnymWell, I need an ADT that's similar to my J616 but from a previous generation; J516 would be best.
#asahi-re · 2025-10-16 19:39
chaos_princessin general or specific question
#asahi-re · 2025-10-16 19:36
nnymIs there some place wherefrom I can get a full ADT ripped directly from the boot environment of a different Mac (to compare to mine)?
#asahi-re · 2025-10-16 17:43
nicolas17IIRC there's A19 and A19 Pro benchmarks showing different latency for certain things that would suggest they are not using "the same" cores
#asahi-re · 2025-10-16 17:43
nicolas17chadmed: I think they stopped naming their CPU cores and it's now "the p-core of SoC X"
#asahi-re · 2025-10-16 15:15
auscyber_<jannau> "they also broke adt parsing with..." <- is this broken anyway on m4?
#asahi-re · 2025-10-16 14:50
jannaunew display related co-processcor: "scdc", role = SCODEC, DP switch-able

plus ›