On Monday 07 January 2002 12:41, Eric W. Biederman wrote:
>
> I'd prefer if we don't go down the exectuable bit route. diff(1) and
> patch(1) don't support it. Plus it is one more thing to modify. The
> one decent way I have seen to do this is to have a script that sets
> the permisions on everything, that you can just run, and that might be
> worth doing.
OK, Jan, can we leave it as this:
NLBConfig.py is the tool name.
You can set the 'x' bit on that after cvs checkout or whatever and it will
run just fine. Other than that NLBConfig.py will be your version of the tool.
As for ROM setup. At some point, at the start of this project, it all looked
simple. WIth each new mainboard we find new hardware designs that break our
ideas. As a result we have a big problem with setting up the rom. Here are
the current combinations we have:
LinuxBIOS (1 or more) on FLASH, DOC
Payload (1 or more) on FLASH, DOC
ipl on FLASH, DOC (since in some cases it is easiest to use IPL for both)
e.g.
ipl LinuxBIOS1 LinuxBIOS2 Payload 1 Payload 2
L440gx NA FLASH FLASH FLASH FLASH
SBC710 FLASH FLASH FLASH DoC DoC
K7SEM DOC DOC DOC DOC DOC
K7SEM FLASH FLASH NA FLASH NA
you can see that for some motherboards we have multiple configurations. Then
there are base address issues. SBC710 DoC is at 0xd0000, for example, unlike
everything else.
I think we're going to need a way to specify all this stuff in the config
file for a given build of a mainboard. To add to the fun, there are some
things that are illegal, and finally we need to specify in the mainboard
Config max sizes for part types (e.g. SBC710 only supports 256KB flash).
So there's a great deal missing in the final step of the build that we need
to get in there.
ron
