So I put some variables in via guesstimate or by putting in empty junk just to get it to compile and it compiles, but I don't dare boot it without knowing that this isn't going to do something nasty. also, it built a file DISKBOOT.BIN do I just put that file in the root of the card and it boots? do I need to modify the extend.m to know what to boot? I've never built a bootable card from scratch before, so I need pointers there.
What I did to get the above working:
I added this to stubs_min.S in the sub 100b:
//To stop errors on compile for testing
DEF(focus_len_table, 0xfff4a4c8) // stolen from ixus240
DEF(sub_FF2F34E8_my, 0x00000678) // fake to build
DEF(cds_gain_value, 0x0000abd0) //stolen from ixus240 test
DEF(sub_FF2F2F3C_my, 0x000003d3) //again faked to build
I don't know if those values can hurt anything (the sub ones I just put something random in there, because I couldn't find any reference anywhere else). the focus_len_table and cts_gain_value I found in ixus240 and nafraf had used those before.
I also put:
long kbd_use_zoom_as_mf() {
return 0;
}
in kbd.c as that was done somewhere else as well, so we have a noop function to return 'success' for doing nothing.
and finally I put:
# dummy to get it compiling
NHSTUB(SetCDSGain, 0x12345678)
NHSTUB(GetCdsGainValue, 0x12345678)
in stubs_entry_2.S
to get those some generic value (Read this on a wiki page on how to get compilation working, they can be fixed later when you know what to put there, just so you can test boot)
Anyone that can venture a guess if this is sane? Do I try a boot?
~Phil