Richard Smith <[EMAIL PROTECTED]> writes: > > Second thing I have got the BIOS writer guide for STPC > > So If I think I changes the replaces the code of STPC_ELITE > > for that of STPC_ATLAS then I can make it for STPC_ATLAS > > If you are going to have to do a lot of re-write work I encourage you > to start over with V2. V1 is a dead end product and will be very > difficult for the linuxbios developers to support you as we are all > focusing on V2. V2 is so much nicer to work with compared to V1. In > V2 almost everything is in C rather than assembly, even all your RAM > init code is C due to Eric's marvelous romcc which is a C compiler > designed to use registers rather than RAM.
Right. V1 is essentially frozen so nothing that used to work breaks. The very nice thing about V2 that the structure of the code makes it much easier to write reusable code. > The STPC Atlas is basically a fast cryix 486 so I don't know what > impact that has on romcc due to its smaller register set and if its > been tested on that arch much but its shouldn't be too much effort to > make it work. Right Eric? All you have to do is not tell romcc it has mmx or sse registers. For a modern memory controller that gets awfully tight but for a simpler memory controller it should be doable, to make everything fit. I almost had the Opteron memory controller working in just 8 registers. Eric _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
