Search results

43 0x0ac GrandCentralAddr GrandCentralExists, 44 0x0b0 Unused44Addr PBX1Exists, 45 0x0b4 Unused45Addr PBX2Exists, 46 0x0b8 Unused46Addr PBX3Exists, 47 0x0bc Unused47Addr ATAExists, 48 0x0c0 Unused48Addr HammerHeadExists, 49 0x0c4 Unused49Addr PlatinumExists, 50 0x0c8 Unused50Addr...

If you grep for (\$|0x)0*2400\b you find it in Boot3.a, UniversalEqu.h, InternalOnlyEqu.a, InternalOnlyEqu.r, StartInit.a, ShutDownMgr.a elliotnunn/boot3 elliotnunn/CubeE elliotnunn/mac-rom elliotnunn/supermario 0xDD0 is AddrMapFlags - a set of 32 boolean flags (one per bit). 0x2400 is...

These appear to be from the gpch resources. A couple bits of misc are documented in Inside Macintosh. What bit does it check? kdia is undocumented. $ddc is BootGlobPtr which I think points to a StartGlobals record. $dd8 is UnivInfoPtr which is type ProductInfo. $68 is beyond the offsets...

Not a significant difference. That's how you know it's not a passive HDMI to DVI adapter like the one you bought. Atlona AT-DP400 is an alternative. Don't know if it's for sale anywhere. ebay? It's DisplayPort. Shouldn't matter. I don't have Apple DisplayPort displays. It works with all my...

Well, the connector is Dual Link. But probably none of the Dual Link pins are connected to anything. Also, there doesn't look like there's enough room or power for the chips required to convert Dual Link to Single Link. I don't think I've ever seen a Dual Link to Single Link adapter that...

Right. 0x1256 which is part of the 32 bit value at 0x1254. 0x1254 is Link1 and it is not 32 different bits - it is a 32 bit value which is a return address to code in ROM (specifically in the HWInit part of the ROM). There's no RAM or stack during this time in the boot process, so offsets...

What adapter did you get? It was probably not Dual Link. What Dual Link DVI supporting GPU are you using? I use this one with my Quad G5's Nvidia GeForce 7800 GT: https://gefen.com/product/dual-link-dvi-to-mini-dp-converter/ It can do 4K30, 1440p60, and 2560x1600 60Hz. etc. I suppose anything...

Right. That discussion is where the 0x78e842a8 checksum ROM came from. https://68kmla.org/bb/index.php?threads/the-820-0961-a-mystery-g3-3-3v-flashrom.48746/post-548625 And it mentions the 0x78eb4234 checksum ROM...

0x1258 is zero in both. I see 0x1254 = Link1 change from fff201f8 in FastConfigDump to fff20270 in SlowConfigDump. fff20000 (3MB + 128K, size 64K) is the address of HWInit in the ROM, according to the results created by the tbxi command. https://github.com/elliotnunn/tbxi fff201f8 is the...

0x1258 is Link2 which is probably going to be a Power PC ROM address (looks like 0xfff##### - last 1 MB of 4 MB ROM). It appears to only be used for calling SerialTestManager tests? Can you post one of your NVRAM dumps so I can compare? Is your ROM 077d.28f1 checksum 96cd923d or 077d.28f2...

I don't see where I said 0x1258 was being written to. Here's the list of events I see (DingusPPC pm7500, forcing 0x1043 to be = 9): - it reads nvram byte 0x1308 (speaker volume?) - inits all 26 ram banks. - scans all 26 ram banks. - writes to 0x1048..0x1117 (8 bytes for each hammerhead bank 0...

I didn't see anything get written to 0x1258. I wonder if 8500 is different than 7500 somewhere. I could retry using pm8500 in DingusPPC. Sure. Attached. I consider Discord like just another forum. Pick a username/password and you're done, just like any other forum. I guess so. Could run System...

DingusPPC Discord channel has the startup source code .Diagnostics.s that does the memory test. 0x1040 is called MemoryTestFlag. The "EMMO" pin of the BoardReg determines if .SerialTestManager should be executed.

Before System 7 has started. 0x1043 is definitely outside XPRAM in the grater NVRAM. The value is read after chime and reset to zero before the memory test so you never see the non-zero value during the OS. The memory test is called after calling .SerialTestManager. The Serial Test Manager...

There's mention of a rev 4 (version D) with checksum 0x78eb4234 but I only have 0x78e842a8 so I don't know if 0x78eb4234 is real.

I modified DingusPPC to log every nvram access. During startup of an emulated Power Mac 7500: - it reads nvram byte 0x1308 (speaker volume?) - inits all 26 ram banks. - scans all 26 ram banks. - it writes to 0x1048..0x1117 (8 bytes for each hammerhead bank 0 to 25 0x1048+8*26 = 0x1118). 4 bytes...

The zip files were created on Mac OS X so they preserve the resource forks (I'm currently using Monterey but other versions should also work). Decompress the zip files on Mac OS X before transferring the app to classic Mac OS. It has the built binary and the source code files (.z is a resource...

You can use my DumpNameRegistry app to capture all of NVRAM. XPRAM should be 256 bytes at offset 0x1300. PRAM is bytes inside XPRAM. https://68kmla.org/bb/index.php?threads/silicon-image-sil3112-flashing-easier-way-using-flashrom.7013/post-472471...

Another option: Turn the onboard chip into a PCI slot?

Can't you just remove the onboard ATI hardware from Open Firmware? Remove PCI device number 12 from the list of device numbers to be probed. https://68kmla.org/bb/index.php?threads/the-great-gazelle-pci-hack-thread-part-2.38360/post-467825