Ah, this makes more sense now (following the wiki).
I wasn't sure of the purpose of init_file_modules_task(), but if it's function is to ensure the delay so that other modules get time to initialise, that explains why I was able to get to the splash screen after a few seconds when I commented it out assigning taskHook values.
I also figured why it wouldn't run, or more precisely, not boot the firmware. The camera doesn't boot if the taskHook has capt_seq_task, movie_record_task and exp_drv_task values to addresses assigned. With just mykbd_task and init_file_modules_task assigned it boots to the splash screen almost instantly.
Guess I'll focus on the keyboard first (commenting out the mykbd_task, I can power on and off the camera with the power button, but can't power it off if left assigned, so I take that as a sign that that works, just need to find the right values). I've noticed that with the newer revision I get some suggestions in the stubs_entry.S already, that's awesome.
Then hunt down if I need different taskHook definitions for each IRQ value or if I still need to do something somewhere.
