Recent content by mcginley

What a read!

I found that macos has a hexdump commandline tool which produces the output as required with the correct command lind args. One question before testing this out: do i have to crop my rom file to 0x10000 bytes? Or can I embed the complete rom because it will only load the first 65535 bytes anyway?

So i have downloaded the hex editor but it pasts hex code like 55AA53E9AD0200000000000000 How do I get my rom file into a string representation required by maciasl, like 0x55,0xAA, .... without coding a small program preferably...

Is this limited to 64kB? Have to look up the size, but it might be bigger. Also do you know if windows driver catches up this rom?

I may give it a try. However it's sad that there does not seem to be a path for Big Sure and future OS to load the ROM via SSDT. Is that something that can be set via a property in the driver kext? Thanks for sharing anyway. Can you propose a tool to generate the hex codes?

hey there! can you elaborate on how you managed to load the rom via SSDT? this is exactly what I'm trying to achieve on an iMac 12,2 with a eeprom-less wx 4170. Thanks!