----- Original Message ----- From: Ronald G Minnich <[EMAIL PROTECTED]> To: Eric W. Biederman <[EMAIL PROTECTED]>; Jan Kok <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 12:54 PM Subject: Re: New NLBConfig
> 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. I don't mind. All the "NLBConfig"s in the file would need to be changed back to "NLBConfig.py", and the Makefile action to remake Makefile etc. needs to have "python " added back in so the executable bit doesn't need to be set. Do you want to do it, or have me do it? And if the latter, do you want me to send the code to one of you, or to the linuxbios list, or do you want to give me write access to the CVS so I can check stuff in (I'm jankok on SourceForge)? > 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: I don't feel qualified to propose how to solve this problem. But if you can come up with a specification that I can understand, and it involves modifying the config tool, I'm willing to do that. By the way, where is there some documentation for how to write loader scripts? Cheers, - Jan
