答复: new config language.

[YhLu]

Ron,

How about the status of freebios2 support on K8?

Today I use to the code and try on Tyan s2880 found two problem
1. I use RH as host compiler system. payload make statement in make.base
with perl doesn't work, it produce strange size images near One mega byte.
2. I change that back to dd, and make one 512K romimage, But the code only
can execute to "jumping to LinuxBIOS". And then retry several times. I use
debug card and see the post code is 01--> 08--> 11 ->01...>11 -> 12. end.

Do you know the progress of Suse LinuxBIOS support on opteron?

Regards

Yinghai Lu

-----邮件原件-----
发件人: ron minnich [mailto:[e-mail]] 
发送时间: 2003年6月8日 20:41
收件人: [e-mail]
主题: new config language.

I'm opening up this discussion, which was formerly just between the folks 
actively doing freebios2. We're getting closer to having things working 
and I am happy to hear any comments.

linuxbios.a now builds for the K8 with the new config tool. Not all of 
linuxbios, just linuxbios.a, but that's quite a way to working.

Things are stricter now. We've been able to operate before with code like 
this:

#if SOME_VARIABLE_THAT_WAS_UNDEFINED == 0
    stuff
#endif

because in the GNU C preprocessor, 
#if (a == 0)
and
#ifndef a

are equivalent if a is undefined.

I think that is a very poor way to operate: it can fool people, and in a 
BIOS you want more checking.

Now that you can use an 'if' operator in the config language, setting up 
some things is a lot easier:

For example, this:
expr ROM_SECTION_SIZE
=(USE_FALLBACK_IMAGE*65536)+(USE_NORMAL_IMAGE*(ROM_SIZE 
- 65536))

expr
ROM_SECTION_OFFSET=(USE_FALLBACK_IMAGE*(ROM_SIZE-65536))+(USE_NORMAL_IMAGE
*0)

now becomes this:
default FALLBACK_SIZE=65536
if USE_FALLBACK_IMAGE 
  option ROM_SECTION_SIZE  = FALLBACK_SIZE
  option ROM_SECTION_OFFSET= (ROM_SIZE - FALLBACK_SIZE)
end
if USE_NORMAL_IMAGE
  option ROM_SECTION_SIZE  = (ROM_SIZE - FALLBACK_SIZE)
  option ROM_SECTION_OFFSET= 0
end

Much better. However, if you have not defined USE_FALLBACK_IMAGE or 
USE_NORMAL_IMAGE, then you're going to get an error, which in the past was 
not the case.

So we'll have to learn to be a bit more careful about defining things 
before they are used, and not using things that were never defined. This 
is all proving to be easy, but people will need to take more care with the 
Config files (which, in deference to Windows and MacOS, are now named 
Config.lb).

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

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

ron minnich  writes:
> 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.

Just to clarify it boots and works with the apics disabled.
> Where are we? We are all collectively close. But we're not done.

Yep that sounds like a good summary.

Eric