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

update

Browse source
This commit is contained in:
Ronald G. Minnich 2000-12-23 03:49:45 +00:00
commit 3177ea9c43
1 changed files with 20 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

30
HOWTO/SiS630
View file

@ -44,6 +44,7 @@ Linux distribution: RedHat 6.2 or later. We haven't tried anything else.
They may all work fine.
Other software notes: You MUST have 'as' version 2.9.5 or later.
You MUST have ssh to connect to sourceforge
Recommended: you really ought to get a 32-DIP Zero Insertion Force (ZIF)
socket for the flash part. This makes taking out flash and putting in Disk
@ -60,14 +61,16 @@ name 'linuxbios' where it makes sense, and 'freebios' otherwise. But they
are the same source base.
----
NOTE: these steps are tested up to step 3, and work.
The steps for loading linuxbios are simple:
0) get linux installed on your target machine
1) Get Linuxbios source from the sourceforge
2) get a 2.4.0-test12 kernel, patch it, then build it
3) config and build linuxbios
4) put a Disk On Chip into the flash socket
5) Burn the chip
6) hit reset. You're up.
4) Get the MTD utilities from http://www.linux-mtd.infradead.org/
5) put a Disk On Chip into the flash socket
6) Burn the chip
7) hit reset. You're up.
---
Step 0)
@ -79,7 +82,9 @@ Step 1)
o You need to get linuxbios source.
cd to the directory you want the source tree to be.
Then:
export CVS_RSH=ssh (or in tcsh setenv CVS_RSH ssh)
cvs -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios login
(at the password prompt, just hit <return>)
cvs -z3 -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios
@ -97,10 +102,11 @@ o Now copy config-2.4.0-test12.sis to .config, then
make clean
make dep
make vmlinux
make modules
make modules_install
make bzdisk (You should test boot this floppy disk just to be safe)
You now have a kernel for linuxbios.
We recommend as a test that you also
make bzdisk
And then try booting this kernel on the target 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
@ -171,7 +177,7 @@ o You now need to figure out where you want to put your build images.
Here's what it looks like when you run it.
python NLBConfig.py winfast.config ~/src/bios/freebios
python ~/src/freebois/util/config/NLBConfig.py winfast.config ~/src/freebios
winfast is not a directory.
I know I should make this, but I'm too paranoid
To fix this, type
@ -202,7 +208,8 @@ o You now need to figure out where you want to put your build images.
OK, all those messages are normal. Now we do a make:
(for a full transcript, see later in the file)
cd winfast
make
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,
@ -217,7 +224,10 @@ 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 4)
Step 4) Get the MTD utilities from http://www.linux-mtd.infradead.org/
Install the erase utility where it is in your path.
Step 5)
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
@ -239,12 +249,12 @@ Step 4)
done this, or are not trained, or have a history of getting
hurt by hardware, DON'T DO IT.
Step 5) Run the following script:
Step 6) Run the following script:
Run the burn_mtd script from util/mtd
Here's how it looks when you run it:
Step 6) Hit reset. Linuxbios should come up in a few seconds.
Step 7) Hit reset. Linuxbios should come up in a few seconds.
If it doesn't work: