I´m novice, and i´m trying to follow the instructions of the Epia´s
How to file.
I can´t execute the config tool. My file is named "NLBConfig.py,v" ,
why is there the ",v" at the end of the file? is it normal?
This is the the same for my config file.
I renamed them as "NLBConfig.py" and "motherboard.config" but
impossible to execute.
I used "python .../NLBConfig.py ..../motherboard.config /.../"
It gives me a mistake at the first line, so i don´t think this is this
way it works.
--------------------------------------------------
Oreka ! Nous sommes l'internet moins cher !
Surfez 25% moins cher avec http://www.oreka.com
might be useful, did not look.
ron
---------- Forwarded message ----------
Date: Mon, 31 Mar 2003 18:13:12 -0500
From: Russ Cox <rsc(a)plan9.bell-labs.com>
Reply-To: 9fans(a)cse.psu.edu
To: 9fans(a)cse.psu.edu
Subject: [9fans] vga docs
If you're writing VGA drivers and don't have paper
docs nearby, this is almost as good.
http://web.inter.nl.net/hcc/S.Weijgers/FreeVGA/home.htm
Hello,
I have a question regarding GPL and NDA issue.
I have documents for a specific chipset which I get with NDA.
And I'm trying to port Linuxbios on that chipset.
As LinuxBIOS is GPL, I know I must make my port publicly available.
In this case, Is it a violation of NDA or not? Does it depend on NDA?
I think there are many people on this list who were in similar situation.
So please tell me some advice.
-
HeeChul Yun,
Embedded S/W Team at ETRI
phone: +82-42-860-1673
At the EPIA HOWTO have a sample declaration to the etherboot config file
like below:
Comment out the following line(s) :-
CFLAGS32+= -DPCIBIOS
Uncomment the following line(s) :-
#CFLAGS32+= -DLINUXBIOS -DCONFIG_TSC_CURTICKS -DCONSOLE_SERIAL \
-DCOMCONSOLE=0x3f8 -DCOMPRESERVE -DCONFIG_PCI_DIRECT \
-DELF_IMAGE
Look the -DCONFIG_TSC_CURTICKS , anybody have it wrotte wrong ?
the right is CONFIG_TSC_CURRTICKS .
Also for the version 5.0.9 of the etherboot, I needed to use -DPCBIOS
and added the pcbios.S object file for include the int15() object code
to make the compilation susseful.
Rgds.
--
Ivan Gustavo Munix dos Santos
-----------------------------
http://www.munix.com.br
mailto:ivan@munix.com.br
Skydental SJC.
Av. Heitor Vila lobos, 1565
Fone: 12-39232925 Ramal 215
Sao Jose Dos Campos - SP
Hello
If this problem is not solved yet, I would suggest trying
a newer mkelfImage. I have been using version 2.2 from
ftp://ftp.lnxi.com/pub/src/mkelfImage/
and that one works fine (I'm also using an Epia card.)
I tried with the version in the freebios tree and got
a similar "Unknown bootloader class" error.
With regards
Jarmo
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.
Hello,
I'm hoping to get Linuxbios running on a Fabiatech FB2510 PC/104 cpu
board.
It's quite similar too the existing advantech/pcm-5823 motherboard. It
has a GX1 Northbridge/CPU, CS5530 Southbridge, SMC FDC37B787 SuperIO,
and RTL8139C 10/100 Ethernet.
It has a 2-MBit SST39SF020A flash in a PLC-32 package, so DOC is not an
option. But it appears there are included utilities for writing this
flash in the Linuxbios cvs tree. Alternately I have a Universal
programmer.
I'm figuring I can base my work off the pcm-5823 and other GX1/CS5530
based motherboard configurations.
What are the areas I may have to customize for FB2510? I'm willing and
able to dig into the source code if necessary. Just point me to where
it is necessary. Is there any information I'm going to have to ask
Fabiatech for?
My goal is to boot with Linuxbios along with the ide_disk driver from
Etherboot. The Linux kernel and initrd/rootfs will be on an IDE flash
drive.
I'm currently using a FAT16 formatted IDE Flash with the very simple
syslinux bootloader, which loads a bzImage and gzipped initrd/rootfs.
How do I get Linux onto an IDE device so Etherboot's ide_disk driver
will load the kernel and my initrd?
Thanks,
Joey Nelson
Thanks Greg,
I think, that is very good overview about the flow.
It may be good idea to continue this flow on this thread or
somewhere else.
I think,One cannot expect Greg to do all the documentation as Peter
said 8-10 hours is a lot of time. May be out of the
many implementors in this forum, if one contributes by giving
more details about any one of these files in detail of one's own
choice ,basically significance,flow about it and Do's and Dont's,etc
and any experiences. Probably a structure needs to be proposed as well and rest should fall in place for documentation at least.
If not 8 hours by one person, atleast an hour can be contributed
may not be an issue.
As Greg has listed the files flow in the order of
execution.
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
May in the top of the mail, one can take list his favourite file
and contribute his knowledge on it.
So that in future, if one reads this thread or one integrates these
inputs into a formal document, it would be easy for him or her.
This again a suggestion to further get more documentation on
this.
Thanks and Regards
Deepak
-----Original Message-----
From: linuxbios-admin(a)clustermatic.org
[mailto:linuxbios-admin@clustermatic.org]On Behalf Of Greg Watson
Sent: Friday, March 28, 2003 10:20 PM
To: linuxbios(a)clustermatic.org
Subject: Re: Information about BIOS and the boot process
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, dkotian3(a)vsnl.net 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.
>
>
>
>ivan(a)munix.com.br 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
>Linuxbios(a)clustermatic.org
>http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>_______________________________________________
>Linuxbios mailing list
>Linuxbios(a)clustermatic.org
>http://www.clustermatic.org/mailman/listinfo/linuxbios
_______________________________________________
Linuxbios mailing list
Linuxbios(a)clustermatic.org
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.
ivan(a)munix.com.br 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
Linuxbios(a)clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
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" <rminnich(a)lanl.gov>
To: <dkotian3(a)vsnl.net>
Cc: <linuxbios(a)clustermatic.org>; <ivan(a)munix.com.br>
Sent: Friday, March 28, 2003 7:55 PM
Subject: Re: Information about BIOS and the boot process
> On Fri, 28 Mar 2003 dkotian3(a)vsnl.net 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
> Linuxbios(a)clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
