this sounds interesting..
As I gave my 'resume' in the previous thread, I'll just copy/paste some of that info here :
I have very strong C/C++/Tcl/Tk/Java/ASM knowledge..
I've been using Linux for 8 years now and I've always liked to use terminals for everything, so i'm used to command line stuff...
I run E17 as a WM, and I usually have around 50+ xterms running constantly.. I must have used a GUI for browsing my files twice in my entire life
I'm known in the open source world as KaKaRoTo, I'm the lead developer and project manager of the aMSN Project (http://amsn-project.net - an MSN Messenger clone) for which I've done quite a lot of stuff, mainly reverse engineering both the protocols and disassembled code.
Amongst other things, I wrote the libsiren library (SIREN audio codec).. it was an ASM to C reverse engineering of Microsoft's proprietary audio codec.
I work for Collabora (Open Source centric company), so I've been working with gstreamer, farsight and telepathy, and I'm the maintainer of libnice (first open source library implementing the ICE specifications) which is a NAT traversal library (GUADEC talk slides : http://people.collabora.co.uk/~kakaroto/libnice-talk-gcds2009.pdf ).
Pretty much all my code is open source and available if you know how to use google...
Oh, I graduated from Polytechnique Montreal as a Software Engineer... I think that's pretty much it
So yeah, I've worked on many things, lots of reverse engineering (protocols, raw data, etc..), as well as ASM to C RE. I'm used to read ASM (x86) code without problems, I've also had to do some RE for ARM processors (RE-ed and wrote the first code ever to access the microphone on the iPhone on the very first firmware, but it was closed sourced by the contractor).
I also wrote something along the lines of oSpy in a previous job (closed source too), and then contributed some stuff to oSpy itself (http://code.google.com/p/ospy
Never done MIPs, but the transition probably won't be very hard (just like when I did ARM RE for the first time, it took an hour or two to get used to the new calling conventions and instruction set).
I'm not sure how much time I can spend on this, but I'm interested in the project, I can probably help you out a little. Send me that test file, I'll try to RE it and see if I can do it and how hard I find it.. also tell me how much time you're expecting me to have available for you, so I can tell you whether or not I can take on that task.