On Tue, 3 Jul 2001, Ronald G Minnich wrote:
> On Tue, 3 Jul 2001, Armin Schindler wrote:
>
> > On Mon, 2 Jul 2001, Armin Schindler wrote:
> > I checked the CVS tree by browsing on sourceforge.net, but this file
> > isn't even there.
>
> maybe it's a cvs thing. I'll try again. but my local tree shows:
> /LinuxBIOSDoc.config/1.1/Sat Jun 23 20:58:05 2001//
LinuxBIOSDoc.config ? That file is present, but the config script
is looking for a doxyscript.base in that directory.
> > Using linuxbios standard config procedure turns out to be not that
> > easy, or I just miss something here.
>
> There's a learning curve. I can't do much about that save make the
> documentation better, sorry.
You don't have to be sorry for that, I know what it is like. And I
do think you all did a great job. The problem I have is a time
schedule for the project, so I have to find a way to create something
good in a short time and when I have to study other work and test how
I may can do it, the better way is to do it the way I know. On the
other side I want to honour the already work done, but both ways
don't match everytime.
> > I added the stpc directory to src/mainboard and placed the specific
> > crt0.S and raminit.inc there, but how can I configure the script
> > to use these ?
> You need a Config file in there showing what bits are used. Can you tell
> me what files you need to add, and I'll tell you how? If we do this right
> we'll get a HOWTO out of it.
I have the Config file, but maybe I just don't know all possibilities
of the Config contents. I used the other mainboard directories as
templates, but when I use another mainboard (an existing
template config), the problem occurs. The crt0.S in the mainboard
directory is never used, only the base version is copied in the
target.
> > I don't know much about python and actually I don't like the idea to
> > add it to my project tools just because of linuxbios.
>
> You don't really need to know python. You need to know the config
> language, but that is actually pretty easy. I was hoping you could
> look at the other mainboard/*/* directories as examples.
I didn't mean to know python itself. It is just that an additional
tool is necessary for my build system.
> You're kind of new to this but believe me given all the options the config
> tool is the best thing we could come up with. This is a
> multiple-architecture, multi-platform bios and config is kind of
> complicated.
I do believe, I just don't know that how to use it and how to
implement my needs.
> There's a config manual in the Documentation directory.
Yes I read this and it was very good when I began, but right now
I need a "deeper" look into the structure.
> We need to document this "add a mainboard" procedure. There has not been
> time, but I will try to get you a HOWTO.
That would be very great.
Maybe there already is, but what I didn't find yet are some
"hooks" in the code at specific locations, where the user/customer
can include their own additional init code without changing the main
files. So at some points specific functions are called which are
normally do nothing, but the user can specify an own file outside
the linuxbios tree, which provides these functions with his code.
(e.g. to init a special hardware, show boot logo, ...)
Thanx,
Armin
