Man the waters just get deeper. I though auto.c was first. I just looked at failover.c and the fallback does a 'retun bist' so who called failover.c?
Can you list out the boot sequence for me step by step? Who calls what?
It is the order they are listed in Config.lb. Or more simply the order the included files are included into crt0.S just like in freebios v1. There is just an extra step to build the assembly code now.
Thanks, I guess I'll just have to go through the code. What I was trying to get was a call tree detailed enough that I could document it in my write up on porting to my chipset.
Why does that require them to be after the big block of includes? You can't just stick them all up at the beginning of the .c file?
<snip>
So the file that uses them is included after the functions are defined.
I don't seem to be getting my question across properly....
Whats the difference for romcc between what I see in the code which looks like:
#include "header1.h" #include "cfile1.c"
void func1(void) {
}
#include "header2.h" #include "cfile2.c"
void func2(void) {
}
#include "header3.h" #include "cfile3.c"
void func3(void) {
}
And what I perceive as a "normal" setup of :
#include "header1.h" #include "header2.h" #include "header3.h"
#include "cfile1.c" #include "cfile2.c" #include "cfile3.c"
void func1(void) {
}
void func2(void) {
}
void func3(void) {
}