Ron,
Is there any MB can boot to execute into LinuxBIOS after copying it to RAM?
The _RAMBASE WE use for E7501 is 0x8000, and the FreeBIOS2 default for K8 is 0x4000. How should I set the value to make the LinuxBIOS can boot into hardwaremain.c. It seems MB only execute the auto.c and crt0.base and can not jump to the right address.
Regards
Yinghai Lu
-----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年6月9日 22:01 收件人: YhLu 抄送: linuxbios@clustermatic.org 主题: Re: 答复: new config language.
On Mon, 9 Jun 2003, YhLu wrote:
How about the status of freebios2 support on K8?
we're working on it.
There are 3 big efforts going on. First, Eric is working on romcc for K8 so that it works well. Suse is trying to get it to boot. I am working on a new config language which I hope is rich enough to capture the needs of freebios2.
Where are we? We are all collectively close. But we're not done.
ron
On Mon, 9 Jun 2003, YhLu wrote:
Is there any MB can boot to execute into LinuxBIOS after copying it to RAM?
yes, many.
The _RAMBASE WE use for E7501 is 0x8000, and the FreeBIOS2 default for K8 is 0x4000. How should I set the value to make the LinuxBIOS can boot into hardwaremain.c. It seems MB only execute the auto.c and crt0.base and can not jump to the right address.
I'm not sure what's wrong here. You may have to start checking the object code to see if it is correct.
For what it is worth the new config tool is almost working ... just trying to get the sizing of the romimage correct.
Hopefully I can start paying attention to linuxbios itself soon, now that I can bulid it.
ron
YhLu YhLu@tyan.com writes:
Ron,
Is there any MB can boot to execute into LinuxBIOS after copying it to RAM?
The _RAMBASE WE use for E7501 is 0x8000, and the FreeBIOS2 default for K8 is 0x4000. How should I set the value to make the LinuxBIOS can boot into hardwaremain.c. It seems MB only execute the auto.c and crt0.base and can not jump to the right address.
???????????????
I think there is a fundamental disconnect here. Except when I miscompile auto.c the AMD reference board boots fine. And in this aspect the code is fundamentally the same as earlier revision of LinuxBIOS. auto.c just gets compiles into auto.inc
And I can't think of a board where I have had problems with jumping to hardwaremain. _RAMBASE should not strongly affect anything, it just need to be in a location where the ram initialization code always puts ram. Only with respect to stack size, and the LinuxBIOS tables should it have any issues with various locations in ram.
Eric