erebion/coreboot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

more details.

Browse source
This commit is contained in:
Ronald G. Minnich 2000-12-20 16:42:44 +00:00
commit b13093ba3c
1 changed files with 59 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

76
HOWTO/SiS630
View file

@ -20,23 +20,40 @@ Vendors we have experience with that work:
www.aaronix.com
Clueless vendors, who ship the wrong board:
www.dknypc.com
www.dknypc.com (we ordered MS7308E, they shipped MS7308D, but invoiced MS7308E)
Vendors who might work:
www.eurocomla.com
www.eurocomla.com (we don't know yet -- have not tried them)
You need to have a target machine (the machine that runs LinuxBIOS) and a build
machine (which will let you build LinuxBIOS). These can be one and the same
machine. In this HOWTO we assume they're different. If they are the same
machine, all the really changes is that you have to do Step 3 first.
Also, freebios and linuxbios still share the same source tree. We use the
name 'linuxbios' where it makes sense, and 'freebios' otherwise. But they
are the same source base.
----
The steps for loading linuxbios are simple:
0) Get Linuxbios source from the sourceforge
1) get a kernel, patch it, then build it
2) config and build linuxbios
3) get linux installed on your machine
3) get linux installed on your target machine
4) put a Disk On Chip into the flash socket
5) Burn the chip
6) hit reset. You're up.
---
Step 0)
o You need to get linuxbios source.
cd to the directory you want the source tree to be.
Then:
cvs -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios login
cvs -z3 -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios
Step 1:
o to www.kernel.org and get linux-2.4.0-test11
o go to www.kernel.org and get linux-2.4.0-test11
o Once you have pulled this file down and untar'ed it,
apply the proper patch from the freebios/src/kernel_patches
@ -49,24 +66,29 @@ o Now copy config-2.4.0-test11.sis to .config, then
make dep
make vmlinux
You now have a kernel for linuxbios.
You now have a kernel for linuxbios.
We recommend as a test that you also
make bzdisk
And then try booting this kernel to make sure it works.
If you want, you can also install this kernel on the target machine,
and install the modules as well, since you will need the Disk On Chip
modules to burn the Disk On Chip part.
Step 2:
o You need to get linuxbios source.
cvs -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios login
cvs -z3 -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios
o You now need to figure out where you want to put your build images.
DO NOT PUT THESE IN THE LINUXBIOS SOURCE TREE.
You want to put them OUTSIDE THE TREE, so you can always
cvs update
and not lose any of your build directory.
Linuxbios does all the builds in a single directory, outside the
source tree, much as BSD does. To build the initial Makefile,
assembly stub, and ld script, we have a config tool.
Linuxbios does all the builds in a single directory, much as BSD does.
To do the build it requires a Makefile, a crt0.S file, and a ld script
file. These are generated by a config tool located in
freebios/utils/config
The config tool is a Python program originally written by
Dean Risinger of the ACL.
To build the initial Makefile,
assembly stub, and ld script,
You need to build a config file (simple), run the config tool,
cd to the build directory, and type 'make'.
Here is a config file for the winfast 6300
@ -106,7 +128,12 @@ o You now need to figure out where you want to put your build images.
you build (the 'linux' command); and finally you need a commandline
for now.
That's the file. Here's what it looks like when you run it.
That's the file.
To run the config tool, you need two args: the first is the
name of a config file, and the second is the (absolute) pathname
of the freebios source tree.
Here's what it looks like when you run it.
python LBConfig.py winfast.config ~/src/bios/freebios
winfast is not a directory.
I know I should make this, but I'm too paranoid
@ -116,9 +143,13 @@ o You now need to figure out where you want to put your build images.
Note this first time, we got an error, since I forgot to make
the 'target' directory.
So, for the second run, I do the mkdir, then run the tool:
mkdir -p winfast
python LBConfig.py winfast.config ~/src/bios/freebios
The output of the tool is:
Will place Makefile, crt0.S, ldscript.ld in winfast
Process config file: /users/rminnich/src/bios/freebios/src/mainboard/leadtek/winfast6300/Config
Process config file: /users/rminnich/src/bios/freebios/src/northsouthbridge/sis/630/Config
@ -139,7 +170,7 @@ o You now need to figure out where you want to put your build images.
We now have three files to be loaded into the Disk On Chip. The first
is called docipl. It is 512 bytes. The second is called linuxbios.strip,
and is the binary image of the linuxbios that gets loaded into Doc.
The third file is you kernel, and is stripped and compressed,
The third file is your kernel, and is stripped and compressed,
vmlinux.bin.gz
-rw------- 1 rminnich CIC-ACL 512 Dec 20 08:41 docipl
@ -150,11 +181,20 @@ o You now need to figure out where you want to put your build images.
You're now ready to burn the Disk On Chip, but first ....
Step 3)
Get Linux installed on your machine. You still have to do this first.
Get Linux installed on your target machine.
If your build and target are the same, you have already done this.
We can't yet boot alternate media such as cdroms.
Be sure and get a kernel running which has MTD on as MODULES.
Step 4) open the machine (LEAVE THE POWER ON), yank the flash, and
Step 4)
NOTE: BE ADVISED THAT THIS STEP CAN HURT OR KILL YOU!
YOU ARE WORKING WITH A POWERED-ON COMPUTER AT THIS POINT.
THE COMPUTER NEEDS TO BE OPENED UP, AND YOU NEED TO REMOVE A CHIP
WHILE THE COMPUTER IS ON.
IF YOU HAVE NOT DONE THIS TYPE OF WORK, DO NOT DO IT!
WE TAKE NO RESPONSIBILITY FOR ANYTHING THAT HAPPENS AT THIS STEP.
Open the machine (LEAVE THE POWER ON), yank the flash, and
plug in the DoC. We recommend you practice this first with the
power off. Make sure that whatever you do, you are not shorting
things out.