Carl-Daniel Hailfinger wrote:
On 08.09.2008 17:34, Stefan Reinauer wrote:
- Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net [080908 17:17]:
- Declare the CAR area as reserved.
What is it again that keeps us from putting CAR area somewhere where there's no real RAM?
The current v3 stage1 design may fail. I don't know of a way to tell gcc that the stack moved in the middle of a function. Maybe there is one.
roughly: asm volatile ("movl newstack, %eax\n movl %eax, %esp\n")
Why don't we just put it into the reserved area to begin with, instead of doing those luxations? Creating a generic relocator does not make much sense, because stuff like the SeaBIOS area will not have to be preserved.
Unless you want a linker running on boot, you have to know the location of the code and data in advance.
We could set up a relocation mapping. That's what FILO does to cope with this issue.