I have an ADVANTECH board based on the SIS 552 chipset. Is there any support for this board and chip set. I looked at the status: http://www.linuxbios.org/status/index.html There is an entry for SIS but no notes. I am on a very tight schedule and any help will be greatly appreciated...
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
Frank wrote:
I have an ADVANTECH board based on the SIS 552 chipset. Is there any support for this board and chip set. I looked at the status: http://www.linuxbios.org/status/index.html There is an entry for SIS but no notes. I am on a very tight schedule and any help will be greatly appreciated...
SiS used to post the LinuxBIOS on their website, it's also in the V1 source.
-Bari
The "Vl" webiste???
--- Bari Ari bari@onelabs.com wrote:
Frank wrote:
I have an ADVANTECH board based on the SIS 552 chipset. Is
there
any support for this board and chip set. I looked at the
status:
http://www.linuxbios.org/status/index.html There is an entry for SIS but no notes. I am on a very tight schedule and any help will be greatly appreciated...
SiS used to post the LinuxBIOS on their website, it's also in the V1 source.
-Bari
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
I think he means the "freebios" directory in the CVS tree ( http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/ ) as opposed to "freebios2."
On Wed, 17 Mar 2004, Frank wrote:
The "Vl" webiste???
--- Bari Ari bari@onelabs.com wrote:
Frank wrote:
I have an ADVANTECH board based on the SIS 552 chipset. Is
there
any support for this board and chip set. I looked at the
status:
http://www.linuxbios.org/status/index.html There is an entry for SIS but no notes. I am on a very tight schedule and any help will be greatly appreciated...
SiS used to post the LinuxBIOS on their website, it's also in the V1 source.
-Bari
Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Forgive me for my ignorance but now I am really confused. What is the difference between Freebios, Freebios2 and LinuxBios. I thought they were one in the same.:-(
--- "Hendricks David W." dwh@lanl.gov wrote:
I think he means the "freebios" directory in the CVS tree ( http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/ ) as opposed to "freebios2."
On Wed, 17 Mar 2004, Frank wrote:
The "Vl" webiste???
--- Bari Ari bari@onelabs.com wrote:
Frank wrote:
I have an ADVANTECH board based on the SIS 552 chipset.
Is
there
any support for this board and chip set. I looked at the
status:
http://www.linuxbios.org/status/index.html There is an entry for SIS but no notes. I am on a very
tight
schedule and any help will be greatly appreciated...
SiS used to post the LinuxBIOS on their website, it's also
in
the V1 source.
-Bari
Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused. What is the difference between Freebios, Freebios2 and LinuxBios. I thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over" freebios, but didn't change the cvs name. V1 of freebios/linuxbios is the CVS module freebios. Freebios2 is LinuxBIOS version 2.
that's as I understand it... no guarantees.
OK, thanks... --- Nathanael Noblet nathanael@gnat.ca wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused.
What
is the difference between Freebios, Freebios2 and LinuxBios.
I
thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over" freebios, but didn't change the cvs name. V1 of freebios/linuxbios is the CVS module freebios. Freebios2 is LinuxBIOS version 2.
that's as I understand it... no guarantees.
-- Nathanael D. Noblet Gnat Solutions 412 - 135 Gorge Road E Victoria, BC V9A 1L1
T/F 250.385.4613
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
On Wed, 17 Mar 2004, Nathanael Noblet wrote:
freebios was started before linuxbios. LinuxBIOS "took over" freebios, but didn't change the cvs name. V1 of freebios/linuxbios is the CVS module freebios. Freebios2 is LinuxBIOS version 2.
it's weirder than that. We built the first linuxbios using openbios as the starting point. Jeff Garzik found freebios, set up the sourceforge account with that name, and I made the mods to turn it into linuxbios. But the name stuck.
ron
Nathanael Noblet wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused. What is the difference between Freebios, Freebios2 and LinuxBios. I thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over" freebios, but didn't change the cvs name. V1 of freebios/linuxbios is the CVS module freebios. Freebios2 is LinuxBIOS version 2.
FreeBios = LinuxBIOS.
LinuxBIOS was forked when Eric wrote RomCC last year. V2 (Version2) is the new LinuxBIOS source tree that is the 100% C version of LinuxBIOS. V1 (Version 1) is the old LinuxBIOS source that used assembly and C.
"romcc is a C compiler that does not use a stack. Instead it keeps all variables in registers.
Currently LinuxBIOS has a lot of assembly code simply because memory initialization is difficult in the general case. This code cannot be written with a standard compiler because there is no memory to put a stack in. Nor on x86 are there cache blocks that can be locked into place. As code generated with romcc does not use a stack it can be used during memory initialization."
-Bari
This is very good information everyone and everyone is lot nicer then that "other" (ppc) boot loader group. Where can I get more information on RomCC and how do I incorporate that into my LinuxBios build. Does RomCC replace GCC...
--- Bari Ari bari@onelabs.com wrote:
Nathanael Noblet wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused.
What
is the difference between Freebios, Freebios2 and
LinuxBios. I
thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over"
freebios,
but didn't change the cvs name. V1 of freebios/linuxbios is
the CVS
module freebios. Freebios2 is LinuxBIOS version 2.
FreeBios = LinuxBIOS.
LinuxBIOS was forked when Eric wrote RomCC last year. V2 (Version2) is the new LinuxBIOS source tree that is the 100% C version of LinuxBIOS. V1 (Version 1) is the old LinuxBIOS source that used assembly and C.
"romcc is a C compiler that does not use a stack. Instead it keeps all variables in registers.
Currently LinuxBIOS has a lot of assembly code simply because memory initialization is difficult in the general case. This code cannot be written with a standard compiler because there is no memory to put a stack in. Nor on x86 are there cache blocks that can be locked into place. As code generated with romcc does not use a stack it can be used during memory initialization."
-Bari
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
Frank wrote:
This is very good information everyone and everyone is lot nicer then that "other" (ppc) boot loader group.
"LinuxBIOS...the bootloader for grown-ups"... I'm only kidding.
Where can I get more
information on RomCC and how do I incorporate that into my LinuxBios build. Does RomCC replace GCC...
"Consider the source" Frank :) and look through the archives http://www.missl.cs.umd.edu/archives/linuxbios/ -Bari
Might also want to check out this thread: http://www.clustermatic.org/pipermail/linuxbios/2004-March/006892.html
It answers many questions one might have about romcc.
On Wed, 17 Mar 2004, Bari Ari wrote:
Frank wrote:
This is very good information everyone and everyone is lot nicer then that "other" (ppc) boot loader group.
"LinuxBIOS...the bootloader for grown-ups"... I'm only kidding.
Where can I get more
information on RomCC and how do I incorporate that into my LinuxBios build. Does RomCC replace GCC...
"Consider the source" Frank :) and look through the archives http://www.missl.cs.umd.edu/archives/linuxbios/ -Bari
You guys are great... --- "Hendricks David W." dwh@lanl.gov wrote:
Might also want to check out this thread:
http://www.clustermatic.org/pipermail/linuxbios/2004-March/006892.html
It answers many questions one might have about romcc.
On Wed, 17 Mar 2004, Bari Ari wrote:
Frank wrote:
This is very good information everyone and everyone is lot
nicer
then that "other" (ppc) boot loader group.
"LinuxBIOS...the bootloader for grown-ups"... I'm only
kidding.
Where can I get more
information on RomCC and how do I incorporate that into my LinuxBios build. Does RomCC replace GCC...
"Consider the source" Frank :) and look through the archives
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
I should also add that on v2 romcc is of course integrated into the build.
ron
Cool... --- ron minnich rminnich@lanl.gov wrote:
I should also add that on v2 romcc is of course integrated into the build.
ron
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
I must be missing something here but in freebios v1 there is plenty of supprt for the SIS chip sets. I downloaded freebios2 (thanks you everyone for the information) but I don't see any support for the SIS chips. I thought freebios2 was a superset of freebios1 and would therefore have all of the freebios support plus some. it doesn't appear to be that way. Am I missing something...
--- ron minnich rminnich@lanl.gov wrote:
I should also add that on v2 romcc is of course integrated into the build.
ron
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
On Wednesday, March 17, 2004, at 02:26 PM, Frank wrote:
I must be missing something here but in freebios v1 there is plenty of supprt for the SIS chip sets. I downloaded freebios2 (thanks you everyone for the information) but I don't see any support for the SIS chips. I thought freebios2 was a superset of freebios1 and would therefore have all of the freebios support plus some. it doesn't appear to be that way. Am I missing something...
Not superset, improved, rewritten port of freebios1. Freebios1 had some limitations / weaknesses in that it was difficult to add a new board. Memory initialization was difficult and lots of the code was assembly, which speaking for myself isn't a skill many people excel at I would imagine.
Freebios2 addresses some of the problems developers were having with freebios1. Although I am completely unfamiliar with the amd64 stuff alot of what freebios2 does is facilitate that arch so the features and such could be added. New boards should be started on freebios2, any existing code from freebios1 can be brought into freebios2 I would imagine as it is needed. (You have to realize I am not a freebios developer) just trying to answer some of the questions I think I know the answers to so the developers can develop.
Thanks for the response. So to the experts out there: I want to add the SIS 630 based board support from freebios to freebios2. Is there a HOWTO I can reference to do this... --- Nathanael Noblet nathanael@gnat.ca wrote:
On Wednesday, March 17, 2004, at 02:26 PM, Frank wrote:
I must be missing something here but in freebios v1 there is plenty of supprt for the SIS chip sets. I downloaded
freebios2
(thanks you everyone for the information) but I don't see
any
support for the SIS chips. I thought freebios2 was a
superset of
freebios1 and would therefore have all of the freebios
support
plus some. it doesn't appear to be that way. Am I missing something...
Not superset, improved, rewritten port of freebios1. Freebios1 had some limitations / weaknesses in that it was difficult to add a new board. Memory initialization was difficult and lots of the code was assembly, which speaking for myself isn't a skill many people excel at I would imagine.
Freebios2 addresses some of the problems developers were having with freebios1. Although I am completely unfamiliar with the amd64 stuff alot of what freebios2 does is facilitate that arch so the features and such could be added. New boards should be started on freebios2, any existing code from freebios1 can be brought into freebios2 I would imagine as it is needed. (You have to realize I am not a freebios developer) just trying to answer some of the questions I think I know the answers to so the developers can develop.
-- Nathanael D. Noblet Gnat Solutions 412 - 135 Gorge Road E Victoria, BC V9A 1L1
T/F 250.385.4613
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
Frank wrote:
I must be missing something here but in freebios v1 there is plenty of supprt for the SIS chip sets. I downloaded freebios2 (thanks you everyone for the information) but I don't see any support for the SIS chips. I thought freebios2 was a superset of freebios1 and would therefore have all of the freebios support plus some. it doesn't appear to be that way. Am I missing something...
Version2 doesn't have all the earlier sources because nobody has volunteered to port all the V1 sources over yet.
-Bari
Then what is the structure. I have to know this before I port a board over. Is there a target I can use as a model. U-BOOT was quite easy to extend and add additional boards. I would just pick an exsisting board that was similar to mine and have a working port in about 3 days. I have a very bad feeling I won't be able to do this as quickly with freebios2 from freebios...
--- Bari Ari bari@onelabs.com wrote:
Frank wrote:
I must be missing something here but in freebios v1 there is plenty of supprt for the SIS chip sets. I downloaded
freebios2
(thanks you everyone for the information) but I don't see
any
support for the SIS chips. I thought freebios2 was a
superset of
freebios1 and would therefore have all of the freebios
support
plus some. it doesn't appear to be that way. Am I missing something...
Version2 doesn't have all the earlier sources because nobody has volunteered to port all the V1 sources over yet.
-Bari
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
On Wed, 17 Mar 2004, Frank wrote:
Then what is the structure. I have to know this before I port a board over. Is there a target I can use as a model. U-BOOT was quite easy to extend and add additional boards. I would just pick an exsisting board that was similar to mine and have a working port in about 3 days. I have a very bad feeling I won't be able to do this as quickly with freebios2 from freebios...
it's a little harder, as there is learning curve.
But I just added the ibm e325 in a few minutes. The epia took me longer as i rewrote the startup.
In summary, if there is chipset support in linuxbios, you can do a new platform in a few minutes. With no chipset support it takes longer.
ron
freebios2 is a clean sheet from scratch redo.
ron
On Wed, 17 Mar 2004, Frank wrote:
This is very good information everyone and everyone is lot nicer then that "other" (ppc) boot loader group. Where can I get more information on RomCC and how do I incorporate that into my LinuxBios build. Does RomCC replace GCC...
romcc is only needed for a few .c files until memory is turned on. The rest is normal gcc.
You should just cvs checkout freebios2 not freebios and it is all in there.
ron
Where can I get RomCC... --- Bari Ari bari@onelabs.com wrote:
Nathanael Noblet wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused.
What
is the difference between Freebios, Freebios2 and
LinuxBios. I
thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over"
freebios,
but didn't change the cvs name. V1 of freebios/linuxbios is
the CVS
module freebios. Freebios2 is LinuxBIOS version 2.
FreeBios = LinuxBIOS.
LinuxBIOS was forked when Eric wrote RomCC last year. V2 (Version2) is the new LinuxBIOS source tree that is the 100% C version of LinuxBIOS. V1 (Version 1) is the old LinuxBIOS source that used assembly and C.
"romcc is a C compiler that does not use a stack. Instead it keeps all variables in registers.
Currently LinuxBIOS has a lot of assembly code simply because memory initialization is difficult in the general case. This code cannot be written with a standard compiler because there is no memory to put a stack in. Nor on x86 are there cache blocks that can be locked into place. As code generated with romcc does not use a stack it can be used during memory initialization."
-Bari
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
It's in the freebios2 tree: http://cvs.sourceforge.net/viewcvs.py/freebios/freebios2/util/romcc/
On Wed, 17 Mar 2004, Frank wrote:
Where can I get RomCC... --- Bari Ari bari@onelabs.com wrote:
Nathanael Noblet wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really confused.
What
is the difference between Freebios, Freebios2 and
LinuxBios. I
thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took over"
freebios,
but didn't change the cvs name. V1 of freebios/linuxbios is
the CVS
module freebios. Freebios2 is LinuxBIOS version 2.
FreeBios = LinuxBIOS.
LinuxBIOS was forked when Eric wrote RomCC last year. V2 (Version2) is the new LinuxBIOS source tree that is the 100% C version of LinuxBIOS. V1 (Version 1) is the old LinuxBIOS source that used assembly and C.
"romcc is a C compiler that does not use a stack. Instead it keeps all variables in registers.
Currently LinuxBIOS has a lot of assembly code simply because memory initialization is difficult in the general case. This code cannot be written with a standard compiler because there is no memory to put a stack in. Nor on x86 are there cache blocks that can be locked into place. As code generated with romcc does not use a stack it can be used during memory initialization."
-Bari
Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Got it! Thank you very much... --- "Hendricks David W." dwh@lanl.gov wrote:
It's in the freebios2 tree:
http://cvs.sourceforge.net/viewcvs.py/freebios/freebios2/util/romcc/
On Wed, 17 Mar 2004, Frank wrote:
Where can I get RomCC... --- Bari Ari bari@onelabs.com wrote:
Nathanael Noblet wrote:
On Wednesday, March 17, 2004, at 12:00 PM, Frank wrote:
Forgive me for my ignorance but now I am really
confused.
What
is the difference between Freebios, Freebios2 and
LinuxBios. I
thought they were one in the same.:-(
freebios was started before linuxbios. LinuxBIOS "took
over"
freebios,
but didn't change the cvs name. V1 of freebios/linuxbios
is
the CVS
module freebios. Freebios2 is LinuxBIOS version 2.
FreeBios = LinuxBIOS.
LinuxBIOS was forked when Eric wrote RomCC last year. V2 (Version2) is the new LinuxBIOS source tree that is the 100% C version
of
LinuxBIOS. V1 (Version 1) is the old LinuxBIOS source that used
assembly
and C.
"romcc is a C compiler that does not use a stack. Instead
it
keeps all variables in registers.
Currently LinuxBIOS has a lot of assembly code simply
because
memory initialization is difficult in the general case. This
code
cannot be written with a standard compiler because there is no
memory to
put a stack in. Nor on x86 are there cache blocks that can be locked into place. As code generated with romcc does not use a stack
it
can be used during memory initialization."
-Bari
Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
__________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
Frank wrote:
Where can I get RomCC...
http://cvs.sourceforge.net/cvstarballs/freebios-cvsroot.tar.bz2
-Bari
-
Bari Ari -
Frank -
Hendricks David W. -
Nathanael Noblet -
ron minnich