It was little old me that added that list of items a while ago, and I will be updating it this weekend with videos etc.It seems that Coutts seems to be jumping all over the place doing different things, that dont seem to be connected. (I dont mean this in a negative way, its just an observation, people really appreciate your efforts here). I think we just need some logical way to first work out what we need to do, what doesnt work, then some way to try to look into the stuff that doesnt work.I know there is massive differences in experience and level and comfort with the code.Do we need to find any stubbs stuff still Coutts for example?Im sure theres quite a few "easy" tasks that still need to be done, it seems that Coutts is the main man here, so perhaps he can spend a little time defining what needs to be done etc?
Ok and after we have found that Coutts?Are there any other stubbs etc that need finding?
Quote from: Jamez on 20 / April / 2011, 01:14:14Ok and after we have found that Coutts?Are there any other stubbs etc that need finding?not really that I know of, but that would definitely help the menu a lot.
5dhack.c- copy_and_restart() // copy ML code into ram, soft reboot camera.- my_dispatch_hook() // called by copy_and_restart. replace canon init tasks with ML ones so the camera calls ML tasks instead, before the soft reboot.- call_init_funcs() //ML init functions- my_init_task() //call canon's init task and display ML boot text- menu_init() // menu.c - menu initialization- debug_init() // debug.c - debug initialization- call_init_funcs() // call all of the init functions---end--of--5d-hack.c---
Started by Athiril « 1 2 » DSLR Hack development
Started by TheNewDeal « 1 2 » DSLR Hack development
Started by anwe79 « 1 2 » Firmware Dumping
Started by Diphallia DSLR Hack development
Started by vio1 General Discussion and Assistance
