> http://bcm-specs.sipsolutions.net/ReverseEngineeringProcess
"creative Mac-On-Linux hack" ... where is the URL? Obviously this is used to create traces of memory accesses. Where are the traces, so that other people can have a look at them and run them throught their own tools? That page just says "we carefully analysing disassembled code", with what? IDA Pro, objdump? What tools to you have to add annotations, names to functions or jump targets? Where are the perl/python/ruby scripts that you use in correlating memory access traces with your disassembly? Later it says "Translate assembly to C". Which de-compiler are you using? I saw this pages some months ago, but it made me no wiser on how to do this reverse-engeneering :-) Hmm, some weeks ago I saw something about a PCI proxy, that was either for QEMU or for Linux itself. With it, one could, at kernel/emulator level, log any access to a PCI memory address range. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
