Re: Information about BIOS and the boot process

Agreed, I am also looking for a good documention. 
Atleast the flow in terms of implemented functions
or assembly code and some kind of Do's and Dont's
if any.
One good advantage would be more and more people
would be easily aware about the code architecture and
would get invovled in LinuxBIOS if one is interested.



[e-mail] wrote
        I am writing some code to fixup the video chipset trident 
cyberblade and V1621 RGB->CS encoder ,
and also trying to fix the IDE_BOOT for my mainboard (B860T or EPIA), so 
I am looking for information
about the real bios process, and about the layout of the common bios 
files, and of course, any information
about bios as possible.

My main problem is to find good documentation about the post, the boot 
process.

       I read on some places which the CS is set F000 and EIP FFF0, so 
in other websites I had seen CS is FFF0,
 in other 000F , causing some confusion with me.

I need some documentation about 20bits addressing lines, and the GATE 
A20 function also.

Tanks in advance.


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

Information about BIOS and the boot process

[ron minnich]

On Fri, 28 Mar 2003 [e-mail] wrote:
> Agreed, I am also looking for a good documention. 
> Atleast the flow in terms of implemented functions
> or assembly code and some kind of Do's and Dont's
> if any.

Until the architecture of the system started to stabilize this was hard. 
It is still hard due to some changes coming up. I'll try to write 
something in the next while ....

oh if only Frame would run under Crossover Office this would be so much 
easier ...

ron

Information about BIOS and the boot process

[Deepak Kotian]

Thanks Ron. The documentation would do a lot of good to 
many in the forum for the new comers (including
me)
Lot of queries should get resolved automatically.

The cvs seems to have support of lot of motherboards now, but I guess,
the knowledge/experience seems to be with the one who have supported 
those boards only.
If the implementator of LinuxBIOS for the respective motherboard 
spends even 8/10 hours to produce a document of his flow or Design, 
it would benefit a lot. To start with, If not very formal,atleast informal 
documentations can  be shared in the cvs from everyone or somewhere 
else on the site. Based on the various documentation , may be a good 
document could be produced and shared easily.

These are just suggestions, there may be better way or means to do it
though.

Regards
Deepak


----- Original Message -----
From: "ron minnich" <[e-mail]>
To: <[e-mail]>
Cc: <[e-mail]>; <[e-mail]>
Sent: Friday, March 28, 2003 7:55 PM
Subject: Re: Information about BIOS and the boot process
> On Fri, 28 Mar 2003 [e-mail] wrote:
> > Agreed, I am also looking for a good documention.
> > Atleast the flow in terms of implemented functions
> > or assembly code and some kind of Do's and Dont's
> > if any.
>
> Until the architecture of the system started to stabilize this was hard.
> It is still hard due to some changes coming up. I'll try to write
> something in the next while ....
>
> oh if only Frame would run under Crossover Office this would be so much
> easier ...
>
> ron
>
> _______________________________________________
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

Information about BIOS and the boot process

[Ivan Gustavo]

I will be happy to help in anything if need.

I think the same, with the documentation work distributed, a group can 
analyse and check if is nothing wrong,
doing a CVS area for the revised documentation.

Regds.

Deepak Kotian wrote:
> Thanks Ron. The documentation would do a lot of good to 
> many in the forum for the new comers (including
> me)
> Lot of queries should get resolved automatically.
>
> The cvs seems to have support of lot of motherboards now, but I guess,
> the knowledge/experience seems to be with the one who have supported 
> those boards only.
> If the implementator of LinuxBIOS for the respective motherboard 
> spends even 8/10 hours to produce a document of his flow or Design, 
> it would benefit a lot. To start with, If not very formal,atleast informal 
> documentations can  be shared in the cvs from everyone or somewhere 
> else on the site. Based on the various documentation , may be a good 
> document could be produced and shared easily.
>
> These are just suggestions, there may be better way or means to do it
> though.
>
> Regards
> Deepak

Information about BIOS and the boot process

[ron minnich]

btw, don't forget

make documentation
when you have built a target. If you want to fix the comments on the 
functions, we'll take the patches.

ron

Information about BIOS and the boot process

[Peter Stuge]

On Fri, Mar 28, 2003 at 11:50:03PM +0530, Deepak Kotian wrote:
> Thanks Ron. The documentation would do a lot of good to 
> many in the forum for the new comers (including
> me)
> Lot of queries should get resolved automatically.
>
> The cvs seems to have support of lot of motherboards now, but I guess,
> the knowledge/experience seems to be with the one who have supported 
> those boards only.
> If the implementator of LinuxBIOS for the respective motherboard 
> spends even 8/10 hours to produce a document of his flow or Design, 
> it would benefit a lot.

8-10 hours is a lot of time, unfortunately.


[..snip..]
> These are just suggestions, there may be better way or means to do it
> though.

I've suggested setting up a wiki in another similar situation where
relatively few and busy people had specific knowledge about the system
design.  I'm pretty sure it will work out well.

PhpWiki looks nice, at http://phpwiki.sf.net/ but I didn't get it to run
immediately when I tried setting it up.  I have a slightly unusual
configuration running however so it might just be my bad.

My $0.02.


//Peter

Information about BIOS and the boot process

[Greg Watson]

Other people probably know much more about this than me, but here's 
my experience.

There seem to be two main parts to linuxbios. The first is 
arch/{arch}/config/ctr0.base which does the very low level 
initialization, like turning on memory, etc. The second is 
arch/{arch}/lib/c_start.S which does whatever else is necessary to 
call the C function hardwaremain(). hardwaremain() then does whatever 
else is necessary to load linux.

c_start.S is linked with linuxbios.a, a library containing generic 
support routines (those found in the lib directory) and anything 
specified using the 'object'  directive in a Config file (and other 
stuff). The resultant 'executable' is called linuxbios_c. The loader 
script used to link linuxbios_c is config/linuxbios_c.ld, and is 
configured to be loaded relative to _RAMBASE.

crt0.base is not linked against anything. Any additional assembly 
routines you need must be specified using the 'mainboardinit' 
directive in a Config file. This causes the specified assembly file 
to be added to "crt0_includes.h" which is in turn included at the 
start of crt0.base (or at the end in the case of the ppc version). 
The loader script used to link crt0.base is in 
arch/{arch}/config/ldscript.base. The resultant 'executable' is 
called linuxbios and will be loaded at _ROMBASE. The tricky thing is 
that this loader script will also load the linuxbios_c 'executable' 
at a location called _payload in this file. The main task of 
crt0.base is then to initialize enough hardware so that this payload 
can be copied from rom into ram (which may also involve uncompressing 
code). Then control is transferred to _start, which is the first 
location in linuxbios_c.

To get an idea of how crt0.base works, look at the following files. 
This is the order of execution specified by the configuration file 
for sis735.

cpu/i386/entry16.inc
cpu/i386/entry32.inc
superio/sis/950/setup_serial.inc
pc80/serial.inc
arch/i386/lib/console.inc
cpu/k7/earlymtrr.inc
northsouthbridge/sis/735/raminit.inc
arch/i386/config/crt0.base

Next look at c_start.S which will show you what happens once control 
is transferred to _start. Finally, look at 
arch/{arch}/lib/hardwaremain.c to see what other stuff is done to get 
linux loaded.

Most other files are specific to particular hardware, so it can be 
pretty confusing to just browse the tree.

Hope this helps,

Greg


At 7:00 PM +0500 3/28/03, [e-mail] wrote:
> Agreed, I am also looking for a good documention.
> Atleast the flow in terms of implemented functions
> or assembly code and some kind of Do's and Dont's
> if any.
> One good advantage would be more and more people
> would be easily aware about the code architecture and
> would get invovled in LinuxBIOS if one is interested.
>
> [e-mail] wrote
>         I am writing some code to fixup the video chipset trident
> cyberblade and V1621 RGB->CS encoder ,
> and also trying to fix the IDE_BOOT for my mainboard (B860T or EPIA), so
> I am looking for information
> about the real bios process, and about the layout of the common bios
> files, and of course, any information
> about bios as possible.
>
> My main problem is to find good documentation about the post, the boot
> process.
>
> I read on some places which the CS is set F000 and EIP FFF0, so
> in other websites I had seen CS is FFF0,
>  in other 000F , causing some confusion with me.
>
> I need some documentation about 20bits addressing lines, and the GATE
> A20 function also.
>
> Tanks in advance.
>
> _______________________________________________
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
> _______________________________________________
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios