From ssuciu at sitelite.com  Wed Jan  1 09:30:00 2003
From: ssuciu at sitelite.com (Sorin Suciu)
Date: Wed Jan  1 09:30:00 2003
Subject: VIA EPIA
Message-ID: <9FA210D7CF79564D8CCE1528F303933409308A@mail.SiteLite-Dublin.local>

Hi,
Can anyone help me with the procedures needed to setup LinuxBios for a VIA EPIA?
Got the rom image and the kernel. I need to flash it but I haven't got the software. Is this process documented somewhere (as www.linuxbios.org ) does not seem to work and www.cwlinux.com 
documentation is not very explicit in this direction. Any help, suggestion would be greatly appreciated..
Thanks
SS


From pyro at linuxlabs.com  Wed Jan  1 12:13:01 2003
From: pyro at linuxlabs.com (Steven James)
Date: Wed Jan  1 12:13:01 2003
Subject: Help NS Geode experts
In-Reply-To: <NNEHJEGKOBOALJLKPJLDIEDMCCAA.bezanson@netaudiotech.com>
References: <NNEHJEGKOBOALJLKPJLDIEDMCCAA.bezanson@netaudiotech.com>
Message-ID: <1041441796.3e132404c9b9c@zax.linuxlabs.com>

Greetings,

I'm no Geodeexpert, but perhaps I can help.

Typically at powerup, the adress space at ffff0000 - ffffffff is mapped to
f0000:0000 (top of real mode memory at 1M). The CPU will start up at f0000:fff0.

The practical upshot is that the end of your romimage should be line up at
ffffffff to get the power on jmp vector in the right place.

G'day,
sjames

Happy New Year LinuxBIOS



Quoting Adam Bezanson <bezanson at netaudiotech.com>:

> Hi guys,
> 
> I've finally built linuxbios for my SC1200 based board.
> I've written my own flash programming utility so I can program
> the "romimage" file produced into my flash part from Linux command
> line.
> This all seems to work fine. On my board, I have the ability (with a
> jumper)
> to direct the ROMCS# signal to one of 3 chips on the board. One is a
> Disk on Chip which currently has a DOS filesystem on it, one is a 2Mbit
> flash chip which has the original Insyde BIOS, and the 3rd is a 16Mbit
> flash part soldered on the board where I'm trying to put linuxbios.
> 
> This 3rd chip is at 0xffe00000 - 0xffffffff, in order to enable this
> addressing I must hit bit 2 in F0 offset 0x52 to enable the Upper ROM
> size
> based on the ROM Mask at F0 offset 0x6e. This isn't enabled by default
> so
> I think as the chip comes up only 0xfffc0000 - 0xffffffff is visible.
> I'm not 100% sure, but I assume as the chip comes up it starts trying
> to fetch instructions from 0xfffc0000, is this true?
> 
> My question is, where should I program the "romimage" file that comes
> out of the build process? It would seem to me that the linuxbios.rom
> part
> would have to
> start at 0xfffc0000.
> 
> Other notes: I've set up my PMR and MCR registers correctly for my
> target. I
> figured them
> out by hand and then verified their values when I run with the Insyde
> BIOS.
> So I'm 100% sure
> the values I'm using are correct for my target.
> 
> I've set the SCx200_DOCCS_BASE to 0xffe00000 for the moment
> and the CTRL to 0x070007ff
> I'm not sure if the BASE value is correct due to the questions I pose
> above.
> 
> All of my efforts have resulted in nothing happening at startup. Nothing
> out
> of the
> serial port nor are the Port 80 codes moving after the board is reset.
> 
> Any ideas/help would be appreciated.
> 
> Thanks and have a happy new year.
> 
> Adam
> 
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------












From nick-linuxbios at bostonimportcenter.com  Wed Jan  1 16:26:00 2003
From: nick-linuxbios at bostonimportcenter.com (Nicholas Mistry)
Date: Wed Jan  1 16:26:00 2003
Subject: booting from usb?
Message-ID: <1140.66.30.63.6.1041456950.squirrel@65.85.27.130>

As being a novice when it comes to linuxbios, i was wondering what would
need to be done to have linuxbios be able to boot from a usb device?

IE:  usb cdrom, usb HD, usb CF reader, usb pen drive, etc....

Is this something that would have to be done (or would be better
accomplished) after linux loads its usb drivers, etc.. ?






From bezanson at netaudiotech.com  Wed Jan  1 17:11:00 2003
From: bezanson at netaudiotech.com (Adam Bezanson)
Date: Wed Jan  1 17:11:00 2003
Subject: Help NS Geode experts
In-Reply-To: <1041441796.3e132404c9b9c@zax.linuxlabs.com>
Message-ID: <NNEHJEGKOBOALJLKPJLDGEDOCCAA.bezanson@netaudiotech.com>

Ahhh thanks, It's working now!!!
Although my kernel isn't starting up.
I'm getting the same thing that was reported to the
list last month about gunzip errors

Welcome to start32, the open sourced starter.
This space will eventually hold more diagnostic information.

January 2000, James Hendricks, Dale Webster, and Ron Minnich.
Version 0.1

   200:init_bytes() - zkernel_start:0xfff10000  zkernel_mask:0x0000ffff
Searching for 16 byte tags
    63:rom_read_bytes() - overflowed source buffer. max_block = 14
init_bytes found 0 tags
Gunzip setup
gunzip_setup
output data is 0x00100000
Gunzipping boot code
bad gzip magic numbers

Was the solution ever mentioned? What have I configured wrong?
My kernel? or the zkernel_start address?

Thanks,
Adam



-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org]On Behalf Of Steven James
Sent: Wednesday, January 01, 2003 12:23 PM
To: Adam Bezanson
Cc: linuxbios at clustermatic.org
Subject: Re: Help NS Geode experts


Greetings,

I'm no Geodeexpert, but perhaps I can help.

Typically at powerup, the adress space at ffff0000 - ffffffff is mapped to
f0000:0000 (top of real mode memory at 1M). The CPU will start up at
f0000:fff0.

The practical upshot is that the end of your romimage should be line up at
ffffffff to get the power on jmp vector in the right place.

G'day,
sjames

Happy New Year LinuxBIOS



Quoting Adam Bezanson <bezanson at netaudiotech.com>:

> Hi guys,
>
> I've finally built linuxbios for my SC1200 based board.
> I've written my own flash programming utility so I can program
> the "romimage" file produced into my flash part from Linux command
> line.
> This all seems to work fine. On my board, I have the ability (with a
> jumper)
> to direct the ROMCS# signal to one of 3 chips on the board. One is a
> Disk on Chip which currently has a DOS filesystem on it, one is a 2Mbit
> flash chip which has the original Insyde BIOS, and the 3rd is a 16Mbit
> flash part soldered on the board where I'm trying to put linuxbios.
>
> This 3rd chip is at 0xffe00000 - 0xffffffff, in order to enable this
> addressing I must hit bit 2 in F0 offset 0x52 to enable the Upper ROM
> size
> based on the ROM Mask at F0 offset 0x6e. This isn't enabled by default
> so
> I think as the chip comes up only 0xfffc0000 - 0xffffffff is visible.
> I'm not 100% sure, but I assume as the chip comes up it starts trying
> to fetch instructions from 0xfffc0000, is this true?
>
> My question is, where should I program the "romimage" file that comes
> out of the build process? It would seem to me that the linuxbios.rom
> part
> would have to
> start at 0xfffc0000.
>
> Other notes: I've set up my PMR and MCR registers correctly for my
> target. I
> figured them
> out by hand and then verified their values when I run with the Insyde
> BIOS.
> So I'm 100% sure
> the values I'm using are correct for my target.
>
> I've set the SCx200_DOCCS_BASE to 0xffe00000 for the moment
> and the CTRL to 0x070007ff
> I'm not sure if the BASE value is correct due to the questions I pose
> above.
>
> All of my efforts have resulted in nothing happening at startup. Nothing
> out
> of the
> serial port nor are the Port 80 codes moving after the board is reset.
>
> Any ideas/help would be appreciated.
>
> Thanks and have a happy new year.
>
> Adam
>
>
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------










_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios





From LeeCausier at GameBox.net  Wed Jan  1 17:20:01 2003
From: LeeCausier at GameBox.net (Lee Causier)
Date: Wed Jan  1 17:20:01 2003
Subject: booting from usb?
In-Reply-To: <1140.66.30.63.6.1041456950.squirrel@65.85.27.130>
References: <1140.66.30.63.6.1041456950.squirrel@65.85.27.130>
Message-ID: <3E136A12.4090800@GameBox.net>

I would say that you would need to use a linux kernel with usb support 
in to either (depending on what you're aiming at) load another kernel 
and initrd from a USB device, the bootstrap that (more flexible) or just 
boot, mounting the appropriate USB device as / - safer I would guess 
(not sure) as you can always put in a CD with a working software set,

Bear in mind I may be wrong on this, I'm no expert, so as always, YMMV.
Nicholas Mistry wrote:

>As being a novice when it comes to linuxbios, i was wondering what would
>need to be done to have linuxbios be able to boot from a usb device?
>
>IE:  usb cdrom, usb HD, usb CF reader, usb pen drive, etc....
>
>Is this something that would have to be done (or would be better
>accomplished) after linux loads its usb drivers, etc.. ?
>
>
>
>
>_______________________________________________
>Linuxbios mailing list
>Linuxbios at clustermatic.org
>http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>  
>





From rminnich at lanl.gov  Wed Jan  1 18:53:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  1 18:53:00 2003
Subject: Help NS Geode experts
In-Reply-To: <NNEHJEGKOBOALJLKPJLDGEDOCCAA.bezanson@netaudiotech.com>
Message-ID: <Pine.LNX.4.44.0301011702360.29170-100000@carotid.ccs.lanl.gov>

On Wed, 1 Jan 2003, Adam Bezanson wrote:

> Welcome to start32, the open sourced starter.
> This space will eventually hold more diagnostic information.
> 
> January 2000, James Hendricks, Dale Webster, and Ron Minnich.
> Version 0.1

no, hyou definitely need to be setting ELF_BOOT or whatever. the old 
start32 is obsolete.

gosh we need a newer HOWTO.

ron



From pyro at linuxlabs.com  Wed Jan  1 19:01:00 2003
From: pyro at linuxlabs.com (Steven James)
Date: Wed Jan  1 19:01:00 2003
Subject: Help NS Geode experts
In-Reply-To: <NNEHJEGKOBOALJLKPJLDGEDOCCAA.bezanson@netaudiotech.com>
References: <NNEHJEGKOBOALJLKPJLDGEDOCCAA.bezanson@netaudiotech.com>
Message-ID: <1041466165.3e138335d2de4@zax.linuxlabs.com>

Greetings,

Most likely, you want option USE_ELF_BOOT=1 in your config file. 
ZKERNEL_START does look off as well. 

You probably want to enable the flash at ffe00000 and make
ZKERNEL_START=0xffe00000 to take maximum advantage of the nice flash size you
have available.

G'day,
sjames


Quoting Adam Bezanson <bezanson at netaudiotech.com>:

> Ahhh thanks, It's working now!!!
> Although my kernel isn't starting up.
> I'm getting the same thing that was reported to the
> list last month about gunzip errors
> 
> Welcome to start32, the open sourced starter.
> This space will eventually hold more diagnostic information.
> 
> January 2000, James Hendricks, Dale Webster, and Ron Minnich.
> Version 0.1
> 
>    200:init_bytes() - zkernel_start:0xfff10000  zkernel_mask:0x0000ffff
> Searching for 16 byte tags
>     63:rom_read_bytes() - overflowed source buffer. max_block = 14
> init_bytes found 0 tags
> Gunzip setup
> gunzip_setup
> output data is 0x00100000
> Gunzipping boot code
> bad gzip magic numbers
> 
> Was the solution ever mentioned? What have I configured wrong?
> My kernel? or the zkernel_start address?
> 
> Thanks,
> Adam
> 
> 
> 
> -----Original Message-----
> From: linuxbios-admin at clustermatic.org
> [mailto:linuxbios-admin at clustermatic.org]On Behalf Of Steven James
> Sent: Wednesday, January 01, 2003 12:23 PM
> To: Adam Bezanson
> Cc: linuxbios at clustermatic.org
> Subject: Re: Help NS Geode experts
> 
> 
> Greetings,
> 
> I'm no Geodeexpert, but perhaps I can help.
> 
> Typically at powerup, the adress space at ffff0000 - ffffffff is mapped
> to
> f0000:0000 (top of real mode memory at 1M). The CPU will start up at
> f0000:fff0.
> 
> The practical upshot is that the end of your romimage should be line up
> at
> ffffffff to get the power on jmp vector in the right place.
> 
> G'day,
> sjames
> 
> Happy New Year LinuxBIOS
> 
> 
> 
> Quoting Adam Bezanson <bezanson at netaudiotech.com>:
> 
> > Hi guys,
> >
> > I've finally built linuxbios for my SC1200 based board.
> > I've written my own flash programming utility so I can program
> > the "romimage" file produced into my flash part from Linux command
> > line.
> > This all seems to work fine. On my board, I have the ability (with a
> > jumper)
> > to direct the ROMCS# signal to one of 3 chips on the board. One is a
> > Disk on Chip which currently has a DOS filesystem on it, one is a
> 2Mbit
> > flash chip which has the original Insyde BIOS, and the 3rd is a
> 16Mbit
> > flash part soldered on the board where I'm trying to put linuxbios.
> >
> > This 3rd chip is at 0xffe00000 - 0xffffffff, in order to enable this
> > addressing I must hit bit 2 in F0 offset 0x52 to enable the Upper ROM
> > size
> > based on the ROM Mask at F0 offset 0x6e. This isn't enabled by
> default
> > so
> > I think as the chip comes up only 0xfffc0000 - 0xffffffff is visible.
> > I'm not 100% sure, but I assume as the chip comes up it starts trying
> > to fetch instructions from 0xfffc0000, is this true?
> >
> > My question is, where should I program the "romimage" file that comes
> > out of the build process? It would seem to me that the linuxbios.rom
> > part
> > would have to
> > start at 0xfffc0000.
> >
> > Other notes: I've set up my PMR and MCR registers correctly for my
> > target. I
> > figured them
> > out by hand and then verified their values when I run with the Insyde
> > BIOS.
> > So I'm 100% sure
> > the values I'm using are correct for my target.
> >
> > I've set the SCx200_DOCCS_BASE to 0xffe00000 for the moment
> > and the CTRL to 0x070007ff
> > I'm not sure if the BASE value is correct due to the questions I pose
> > above.
> >
> > All of my efforts have resulted in nothing happening at startup.
> Nothing
> > out
> > of the
> > serial port nor are the Port 80 codes moving after the board is
> reset.
> >
> > Any ideas/help would be appreciated.
> >
> > Thanks and have a happy new year.
> >
> > Adam
> >
> >
> >
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
> >
> 
> 
> 
> ----------------------------steven james, director of research, linux
> labs
> 
> LinuxBIOS Cluster Solutions                   230 peachtree st nw ste
> 2705
> 
> High-Speed Colocation, Hosting,                        atlanta.ga.us
> 30303
> 
> Linux Hardware, Development & Support            
> http://www.linuxlabs.com
> 
> * Visit us at SuperComputing 2002, Booth 1441 *   office/fax
> 404.577.7747/3
> 
> --------------------------------------------------------------------------
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------












From sivakumar.subramani at wipro.com  Thu Jan  2 03:56:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan  2 03:56:01 2003
Subject: Help Needed.
Message-ID: <1041498441.12714.17.camel@Jasmine>

Hi,

I want to understand the flow of the following piece fo the code. It is
for copying the Linuxbios image from Flash ROM to RAM.

Here I want to what is the value of the _liseg, _iseg, _eliseg  segment
address. Can any one explain the following code.

My system hangs in this part of code (i.e. at rep and movsb instruction.
As per the Ron's SUGGESTION I also used spd to get the value for RAM
intialization.

But still it loop at this point

	jz      .Lnocopy
        movl    $EXT(_eliseg), %ecx
        CONSOLE_DEBUG_TX_HEX32(%ecx)
        subl    %esi, %ecx
        jz      .Lnocopy                /* should not happen */
        rep
        movsb
        CONSOLE_DEBUG_TX_STRING($siva_debug5)
.Lnocopy:
	

Thanks,
Siva.S


 /*
         *      Copy data into RAM and clear the BSS. Since these
segments
         *      isn\'t really that big we just copy/clear using bytes,
not
         *      double words.
         */
        CONSOLE_DEBUG_TX_STRING($siva_debug1)
        intel_chip_post_macro(0x11)             /* post 11 */

        cld                             /* clear direction flag */

        /* copy linuxBIOS from it's initial load location to
         * the location it is compiled to run at.
         * Normally this is copying from FLASH ROM to RAM.
         */
        leal    EXT(_liseg), %esi
        leal    EXT(_iseg), %edi
        cmpl    %esi, %edi
        jz      .Lnocopy
        movl    $EXT(_eliseg), %ecx
        CONSOLE_DEBUG_TX_HEX32(%ecx)
        subl    %esi, %ecx
        jz      .Lnocopy                /* should not happen */
        rep
        movsb
        CONSOLE_DEBUG_TX_STRING($siva_debug5)
.Lnocopy:
        CONSOLE_DEBUG_TX_STRING($siva_debug6)
        intel_chip_post_macro(0x12)             /* post 12 */

        /** clear stack */
        leal    EXT(_stack), %edi
        movl    $EXT(_estack), %ecx
        subl    %edi, %ecx
        xorl    %eax, %eax
        rep
        stosb

        /** clear bss */
        leal    EXT(_bss), %edi
        movl    $EXT(_ebss), %ecx
        subl    %edi, %ecx
        jz      .Lnobss
        xorl    %eax, %eax
        rep
        stosb



-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From dkotian3 at vsnl.net  Thu Jan  2 04:10:01 2003
From: dkotian3 at vsnl.net (dkotian3 at vsnl.net)
Date: Thu Jan  2 04:10:01 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it supported
Message-ID: <20030102094832.F1D1E1FACF@bom6.vsnl.net.in>

An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030102/409db741/attachment.ksh>

From nick-linuxbios at bostonimportcenter.com  Thu Jan  2 06:21:00 2003
From: nick-linuxbios at bostonimportcenter.com (Nicholas Mistry)
Date: Thu Jan  2 06:21:00 2003
Subject: VIA EPIA up!
In-Reply-To: <Pine.LNX.4.44.0212211920430.11546-100000@lxplus065.cern.ch>
References: <Pine.LNX.4.33.0212211039050.10195-100000@hydrogen.leitl.org>
        <Pine.LNX.4.44.0212211920430.11546-100000@lxplus065.cern.ch>
Message-ID: <2267.66.30.63.6.1041507084.squirrel@65.85.27.130>

> It is an EPAI5000 - I did not realise that DOC was an option on these
> boards. Mine doesn't have this.
> A bit frustrating to see the empty space on the board.
>
> Does anyone know how to specify this option, and what the extra cost is?

I posted a while back w/ my frustrations trying to find out more about the
DOC pad on the EPIA5000 and 6000 and C3-800 boards.   Through several
channels VIA replied back "this feature is discontinued and unsupported".

As soon as my SMT soldering kit comes in i want to try and mount a DOC on
the pad, move the jumper, power up and prey that i dont smell smoke.. 
Aparantly from what i have read elsewhere (i forget exactly where), the
early rev of the EPIA bios for these motherboards still contains the code
to use the DOC.   So if all goes well, i should have more to tell in a few
weeks.

If things dont go well, i might have to revert to following the traces on
the motherboard.  UGH.  Anyone got xray vision?

And I agree, such a promising void must be filled!  =)

-N






From jallen at integraltech.com  Thu Jan  2 07:24:01 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan  2 07:24:01 2003
Subject: Help NS Geode experts
Message-ID: <3E1431C5.30109@integraltech.com>

Adam,
I am also working on a board that integrates the Geode SC2200/SC1200 
chip.  I am not sure if I can answer your questiuon, but I am 
interrested in how you programed your flash.  I was planning on trying 
the /dev/bios utility before I attemted to do it on my own.  Have you 
look at this utility?
http://www.freiburg.linux.de/OpenBIOS/development/devbios.html
John



From jf1 at IMERGE.co.uk  Thu Jan  2 07:30:01 2003
From: jf1 at IMERGE.co.uk (James Finnie)
Date: Thu Jan  2 07:30:01 2003
Subject: Help NS Geode experts
Message-ID: <C0D45ABB3F45D5118BBC00508BC292DB9D438E@imgserv04>

Hi guys,

I currently use the /dev/bios work for flashing BIOS in a production
evironment on a GX1+5530A platform. It works great.  It may not work out of
the box for SC2200/SC1200 (I have no experience on these platforms), but it
would be well worth getting it working - it supports a large number of
different flash parts and provides a great interface.  Sounds like Adam has
already done the hard bit!

James


> -----Original Message-----
> From: John Allen [mailto:jallen at integraltech.com]
> Sent: 02 January 2003 12:34
> To: linuxbios at clustermatic.org; bezanson at netaudiotech.com
> Subject: Re: Help NS Geode experts
> 
> 
> Adam,
> I am also working on a board that integrates the Geode SC2200/SC1200 
> chip.  I am not sure if I can answer your questiuon, but I am 
> interrested in how you programed your flash.  I was planning 
> on trying 
> the /dev/bios utility before I attemted to do it on my own.  Have you 
> look at this utility?
> http://www.freiburg.linux.de/OpenBIOS/development/devbios.html
> John
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Imerge Limited                          Tel :- +44 (0)1954 783600 
Unit 6 Bar Hill Business Park           Fax :- +44 (0)1954 783601 
Saxon Way                               Web :- http://www.imerge.co.uk 
Bar Hill 
Cambridge 
CB3 8SL 
United Kingdom 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 




From jallen at integraltech.com  Thu Jan  2 07:57:00 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan  2 07:57:00 2003
Subject: Documentation
Message-ID: <3E1439A1.9050401@integraltech.com>

All,
I have been working with LinuxBIOS on my Geode for several weeks now.  I 
would first like to say, "I love it!".  If does what it is intended to 
do very well.  The only drawback I see is documentation.  After watching 
the mailing lists for these past few weeks, I believe that most issues 
could be solved with some updated and decent docs.  As a LinuxBIOS 
newbie, myself, I found trying to determine the correct option flags 
nearly impossible.  It would be great to at least have something that 
described what each option did.  For example, BOOT_IDE, BOOT_TFTP, 
USE_ELF_BOOT, USE_GENERIC_ROM, and others could be grouped together to 
decribe where LinuxBIOS gets the kernel image.  

I would be willing to help get the docs inorder, but as a relative 
newbie to LinuxBIOS, I probably know only a handful of options anyway. 
 Any Thoughts?
John



From aip at cwlinux.com  Thu Jan  2 08:11:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Thu Jan  2 08:11:01 2003
Subject: VIA EPIA
In-Reply-To: <9FA210D7CF79564D8CCE1528F303933409308A@mail.SiteLite-Dublin.local>; from Sorin Suciu on Tue, Dec 31, 2002 at 09:25:57PM -0000
References: <9FA210D7CF79564D8CCE1528F303933409308A@mail.SiteLite-Dublin.local>
Message-ID: <20030102212114.A14664@mail.cwlinux.com>

Basically you need flash_rom to flash romimage.  It can be built from cvs
tree(freebios/util/flash_and_burn).  Here is the step to flash,

1. enable flash writable
$ setpci -s 0:11.0  40.b=54
2. flash romimage
$ flash_rom romimage

Hope this help.

-Andrew

On Tue, Dec 31, 2002 at 09:25:57PM -0000, Sorin Suciu wrote:
> Hi,
> Can anyone help me with the procedures needed to setup LinuxBios for a VIA EPIA?
> Got the rom image and the kernel. I need to flash it but I haven't got the software. Is this process documented somewhere (as www.linuxbios.org ) does not seem to work and www.cwlinux.com 
> documentation is not very explicit in this direction. Any help, suggestion would be greatly appreciated..
> Thanks
> SS
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030102/a3a79843/attachment.sig>

From sivakumar.subramani at wipro.com  Thu Jan  2 08:26:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan  2 08:26:00 2003
Subject: Documentation
In-Reply-To: <3E1439A1.9050401@integraltech.com>
References: <3E1439A1.9050401@integraltech.com>
Message-ID: <1041514674.12714.95.camel@Jasmine>

I too feel that it would be good, if we have good documentation for the
LInuxBIOS code. Atleast for the generic code like startup and bootstrap
codes...

I too fighting with the linuxbios code for past one month, I feel that
we can have group of people (who ever interested) and the start
documentation for the code and the problem they faced while bring up the
Linuxbios. It would be realy helpful for newbie.

As my contribution, I will start the documentation on the  intial part
of the Linuxbios code (i.e., Bootstrap code and the Ram initialization)
Though the RAM initialization is not common for all the motherboard, I
will try to list out the points need to taken care for RAM
initialization.

Thanks
Siva
On Thu, 2003-01-02 at 18:37, John Allen wrote:
> All,
> I have been working with LinuxBIOS on my Geode for several weeks now.  I 
> would first like to say, "I love it!".  If does what it is intended to 
> do very well.  The only drawback I see is documentation.  After watching 
> the mailing lists for these past few weeks, I believe that most issues 
> could be solved with some updated and decent docs.  As a LinuxBIOS 
> newbie, myself, I found trying to determine the correct option flags 
> nearly impossible.  It would be great to at least have something that 
> described what each option did.  For example, BOOT_IDE, BOOT_TFTP, 
> USE_ELF_BOOT, USE_GENERIC_ROM, and others could be grouped together to 
> decribe where LinuxBIOS gets the kernel image.  
> 
> I would be willing to help get the docs inorder, but as a relative 
> newbie to LinuxBIOS, I probably know only a handful of options anyway. 
>  Any Thoughts?
> John
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From bezanson at netaudiotech.com  Thu Jan  2 08:30:01 2003
From: bezanson at netaudiotech.com (Adam Bezanson)
Date: Thu Jan  2 08:30:01 2003
Subject: Help NS Geode experts
In-Reply-To: <3E1431C5.30109@integraltech.com>
Message-ID: <NNEHJEGKOBOALJLKPJLDKEEBCCAA.bezanson@netaudiotech.com>

Hi,

No actually I haven't looked at this utility.
National provides a Linux kernel device driver to talk to flash
on my development board. Their own utilities use this driver.
It provides lseek, read, and write calls to access the flash devices.
I ended up putting Linux on my development board using the 
original Insyde BIOS and then wrote a Linux user space program
that utilizes that driver to program the Flash myself from the linux
command line. 

I've switched to Elfboot now and still not quite right.
Does the zkernel_start have to point to the beginning of the 
romimage in flash where the kernel actually is?

Here's an excerpt:

Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.2

   200:init_bytes() - zkernel_start:0xffe00000  zkernel_mask:0x0000ffff
Searching for 16 byte tags
    63:rom_read_bytes() - overflowed source buffer. max_block = 31
init_bytes found 0 tags
Cannot Load ELF Image

Thanks for all the help so far,

Adam


-----Original Message-----
From: John Allen [mailto:jallen at integraltech.com]
Sent: Thursday, January 02, 2003 7:34 AM
To: linuxbios at clustermatic.org; bezanson at netaudiotech.com
Subject: Re: Help NS Geode experts


Adam,
I am also working on a board that integrates the Geode SC2200/SC1200 
chip.  I am not sure if I can answer your questiuon, but I am 
interrested in how you programed your flash.  I was planning on trying 
the /dev/bios utility before I attemted to do it on my own.  Have you 
look at this utility?
http://www.freiburg.linux.de/OpenBIOS/development/devbios.html
John






From justin at street-vision.com  Thu Jan  2 10:35:01 2003
From: justin at street-vision.com (Justin Cormack)
Date: Thu Jan  2 10:35:01 2003
Subject: booting from usb?
In-Reply-To: <3E136A12.4090800@GameBox.net>
References: <1140.66.30.63.6.1041456950.squirrel@65.85.27.130> 
	<3E136A12.4090800@GameBox.net>
Message-ID: <1041522212.7158.177.camel@lotte>

On Wed, 2003-01-01 at 22:22, Lee Causier wrote:
> I would say that you would need to use a linux kernel with usb support 
> in to either (depending on what you're aiming at) load another kernel 
> and initrd from a USB device, the bootstrap that (more flexible) or just 
> boot, mounting the appropriate USB device as / - safer I would guess 
> (not sure) as you can always put in a CD with a working software set,
> 
> Bear in mind I may be wrong on this, I'm no expert, so as always, YMMV.
> Nicholas Mistry wrote:
> 
> >As being a novice when it comes to linuxbios, i was wondering what would
> >need to be done to have linuxbios be able to boot from a usb device?
> >
> >IE:  usb cdrom, usb HD, usb CF reader, usb pen drive, etc....
> >
> >Is this something that would have to be done (or would be better
> >accomplished) after linux loads its usb drivers, etc.. ?

If you can, do it after Linux has booted, when it should be easy. But if
necessary you could write a usb storage driver for etherboot. I dont
know enough about usb to know how much of a minimal driver you need (can
you write a polled only driver?).




From rminnich at lanl.gov  Thu Jan  2 10:47:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 10:47:01 2003
Subject: Help Needed.
In-Reply-To: <1041498441.12714.17.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301020851250.2461-100000@carotid.ccs.lanl.gov>

I would suggest you use the dumpnorth code in:
 src/bios/freebios/src/ram/dump_northbridge.inc

and check each step of your northbridge configuration. 

To do this, in your config you will have this in your config:
mainboardinit ram/dump_northbridge.inc

To use it: 

      CALLSP(dumpnorth)

at various places. 

the file src/bios/freebios/src/northbridge/intel/430tx/raminit.inc
shows some uses of this function. We found it very handy for getting that 
part up.

ron




From rminnich at lanl.gov  Thu Jan  2 10:47:08 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 10:47:08 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it supported
In-Reply-To: <20030102094832.F1D1E1FACF@bom6.vsnl.net.in>
Message-ID: <Pine.LNX.4.44.0301020857340.2461-100000@carotid.ccs.lanl.gov>

what is the motherboard name and type? how about sending an lspci output?

lspci
lspci -xxx
lspci -v

ron



From rminnich at lanl.gov  Thu Jan  2 10:49:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 10:49:01 2003
Subject: Help NS Geode experts
In-Reply-To: <3E1431C5.30109@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301020858430.2461-100000@carotid.ccs.lanl.gov>

on all the geodes I have I use the flash_rom program in 
freebios/util/flash_and_burn.

ron



From rminnich at lanl.gov  Thu Jan  2 10:51:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 10:51:00 2003
Subject: Documentation
In-Reply-To: <3E1439A1.9050401@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301020900050.2461-100000@carotid.ccs.lanl.gov>

we need docs. 

For a start, we need updated howto's for motherboards, but more important 
we need a "generic HOWTO" for new motherboards. 

I'm not even sure where to start, I've tried a few times but it is hard.

ron



From rminnich at lanl.gov  Thu Jan  2 11:59:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 11:59:01 2003
Subject: Documentation
In-Reply-To: <1041514674.12714.95.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301021007210.2461-100000@carotid.ccs.lanl.gov>

On 2 Jan 2003, sivakumar wrote:

> I too feel that it would be good, if we have good documentation for the
> LInuxBIOS code. Atleast for the generic code like startup and bootstrap
> codes...

the first question I have is; have you tried
make documentation

in your build directory?

In the end I would like to have this produce a little manual for a given 
mainboard. There is lots of documentaiton missing for this, however.

ron



From ivan at sixfold.com  Thu Jan  2 13:34:01 2003
From: ivan at sixfold.com (Ivan Pulleyn)
Date: Thu Jan  2 13:34:01 2003
Subject: Help Needed.
In-Reply-To: <1041498441.12714.17.camel@Jasmine>
Message-ID: <Pine.LNX.4.33.0301021218130.14699-100000@localhost.localdomain>


Hi, This may have nothing to do with your questions, but shouldn't
there be a 'cld' statement before the 'rep movsb'?

Ivan...





On 2 Jan 2003, sivakumar wrote:

> Hi,
> 
> I want to understand the flow of the following piece fo the code. It is
> for copying the Linuxbios image from Flash ROM to RAM.
> 
> Here I want to what is the value of the _liseg, _iseg, _eliseg  segment
> address. Can any one explain the following code.
> 
> My system hangs in this part of code (i.e. at rep and movsb instruction.
> As per the Ron's SUGGESTION I also used spd to get the value for RAM
> intialization.
> 
> But still it loop at this point
> 
> 	jz      .Lnocopy
>         movl    $EXT(_eliseg), %ecx
>         CONSOLE_DEBUG_TX_HEX32(%ecx)
>         subl    %esi, %ecx
>         jz      .Lnocopy                /* should not happen */
>         rep
>         movsb
>         CONSOLE_DEBUG_TX_STRING($siva_debug5)
> .Lnocopy:
> 	
> 
> Thanks,
> Siva.S
> 
> 
>  /*
>          *      Copy data into RAM and clear the BSS. Since these
> segments
>          *      isn\'t really that big we just copy/clear using bytes,
> not
>          *      double words.
>          */
>         CONSOLE_DEBUG_TX_STRING($siva_debug1)
>         intel_chip_post_macro(0x11)             /* post 11 */
> 
>         cld                             /* clear direction flag */
> 
>         /* copy linuxBIOS from it's initial load location to
>          * the location it is compiled to run at.
>          * Normally this is copying from FLASH ROM to RAM.
>          */
>         leal    EXT(_liseg), %esi
>         leal    EXT(_iseg), %edi
>         cmpl    %esi, %edi
>         jz      .Lnocopy
>         movl    $EXT(_eliseg), %ecx
>         CONSOLE_DEBUG_TX_HEX32(%ecx)
>         subl    %esi, %ecx
>         jz      .Lnocopy                /* should not happen */
>         rep
>         movsb
>         CONSOLE_DEBUG_TX_STRING($siva_debug5)
> .Lnocopy:
>         CONSOLE_DEBUG_TX_STRING($siva_debug6)
>         intel_chip_post_macro(0x12)             /* post 12 */
> 
>         /** clear stack */
>         leal    EXT(_stack), %edi
>         movl    $EXT(_estack), %ecx
>         subl    %edi, %ecx
>         xorl    %eax, %eax
>         rep
>         stosb
> 
>         /** clear bss */
>         leal    EXT(_bss), %edi
>         movl    $EXT(_ebss), %ecx
>         subl    %edi, %ecx
>         jz      .Lnobss
>         xorl    %eax, %eax
>         rep
>         stosb
> 
> 
> 
> 

-- 

----------------------------------------------------------------------
Ivan Pulleyn
Sixfold Technologies, LLC
Chicago Technology Park
2201 West Campbell Drive
Chicago, IL 60612

email:    ivan at sixfold.com
voice:    (866) 324-5460 x601
fax:      (312) 421-0388
----------------------------------------------------------------------



From jallen at integraltech.com  Thu Jan  2 15:57:00 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan  2 15:57:00 2003
Subject: DMA on the SC2200 Geode
Message-ID: <3E14AA26.7030708@integraltech.com>

I just noticed that the harddrive on my Geode sc2200 system is running 
in pio mode.  What do I need to do to turn on dma support for this chip?
John



From bari at onelabs.com  Thu Jan  2 16:18:00 2003
From: bari at onelabs.com (Bari Ari)
Date: Thu Jan  2 16:18:00 2003
Subject: DMA on the SC2200 Geode
References: <3E14AA26.7030708@integraltech.com>
Message-ID: <3E14AFCA.5030508@onelabs.com>

John Allen wrote:

> I just noticed that the harddrive on my Geode sc2200 system is running 
> in pio mode.  What do I need to do to turn on dma support for this chip?
> John


Pages 148 - 151, 267 - 272 in the NSC SC2200 data sheet have the
Ultra DMA/33 and IDE Controller Register info and settings.

Bari




From rminnich at lanl.gov  Thu Jan  2 16:28:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  2 16:28:01 2003
Subject: DMA on the SC2200 Geode
In-Reply-To: <3E14AFCA.5030508@onelabs.com>
Message-ID: <Pine.LNX.4.44.0301021438000.4021-100000@carotid.ccs.lanl.gov>

On Thu, 2 Jan 2003, Bari Ari wrote:

> Pages 148 - 151, 267 - 272 in the NSC SC2200 data sheet have the
> Ultra DMA/33 and IDE Controller Register info and settings.

where should we set these? in the mainboard setup? in linux? 

ron



From ebiederman at lnxi.com  Thu Jan  2 17:20:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Jan  2 17:20:01 2003
Subject: ["xu xuning" <xuning1979@hotmail.com>] 
Message-ID: <m3of6z2n79.fsf@lnxi.com>

An embedded message was scrubbed...
From: "xu xuning" <xuning1979 at hotmail.com>
Subject: no subject
Date: Thu, 02 Jan 2003 17:42:40 +0800
Size: 1987
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030102/9d3083dc/attachment.mht>

From stuge-linuxbios at cdy.org  Thu Jan  2 20:47:00 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu Jan  2 20:47:00 2003
Subject: Help NS Geode experts
In-Reply-To: <C0D45ABB3F45D5118BBC00508BC292DB9D438E@imgserv04>
References: <C0D45ABB3F45D5118BBC00508BC292DB9D438E@imgserv04>
Message-ID: <20030103014943.GA3655@foo.birdnet.se>

On Thu, Jan 02, 2003 at 12:40:37PM -0000, James Finnie wrote:
> I currently use the /dev/bios work for flashing BIOS in a production
> evironment on a GX1+5530A platform. It works great.  It may not work out of
> the box for SC2200/SC1200 (I have no experience on these platforms), but it
> would be well worth getting it working - it supports a large number of
> different flash parts and provides a great interface.  Sounds like Adam has
> already done the hard bit!

One issue might be that most SCx2xx-platforms probably wire up the flash CE
and WE differently, and they need to be enabled before any writing to the
flash will work.  Register hunt, anyone?

OTOH, if you're working on flashing LinuxBIOS on a platform you might
already have access to the neccessary documentation, it's needed for
tweaking the configuration as well.


//Peter


From dkotian3 at vsnl.net  Thu Jan  2 22:33:00 2003
From: dkotian3 at vsnl.net (dkotian3 at vsnl.net)
Date: Thu Jan  2 22:33:00 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it supported
Message-ID: <20030103041208.F3CF71FAB6@bom6.vsnl.net.in>

An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030102/2673ea95/attachment.ksh>

From sivakumar.subramani at wipro.com  Thu Jan  2 23:36:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan  2 23:36:01 2003
Subject: Specification for 440gx (northbridge)
Message-ID: <1041569253.12714.785.camel@Jasmine>

Hi all,

Where can I get the specification for the 440gx northbridge?
I am using 440gx as my reference, So I need the specification for 440gx
northbrige.


Thanks,
Siva
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From sivakumar.subramani at wipro.com  Thu Jan  2 23:41:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan  2 23:41:00 2003
Subject: Documentation
In-Reply-To: <Pine.LNX.4.44.0301021007210.2461-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301021007210.2461-100000@carotid.ccs.lanl.gov>
Message-ID: <1041569557.12715.790.camel@Jasmine>

Yes, I agree that using doxygen for documentation is good idea. But we
need to add enough description of the code in source code so that
doxygen will come up with good documentation. 

- Siva

On Thu, 2003-01-02 at 22:39, Ronald G. Minnich wrote:
> On 2 Jan 2003, sivakumar wrote:
> 
> > I too feel that it would be good, if we have good documentation for the
> > LInuxBIOS code. Atleast for the generic code like startup and bootstrap
> > codes...
> 
> the first question I have is; have you tried
> make documentation
> 
> in your build directory?
> 
> In the end I would like to have this produce a little manual for a given 
> mainboard. There is lots of documentaiton missing for this, however.
> 
> ron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From Matthim at t-online.de  Fri Jan  3 04:24:00 2003
From: Matthim at t-online.de (Matthias Mueller)
Date: Fri Jan  3 04:24:00 2003
Subject: Specification for 440gx (northbridge)
In-Reply-To: <1041569253.12714.785.camel@Jasmine>
References: <1041569253.12714.785.camel@Jasmine>
Message-ID: <20030103093431.GB1044@Enterprise>

Hi Siva,

I worked with the 440GX. All the docs I used were available on the
Intel-Site. I noticed that they removed all the docs from there
site. Is the 440GX still available ? Only the 440BX is supported which
is very similar. Maybe someone on the list can give you the docs (they
are all PDF files). I left that company very quickly and do not have
access to the docs :-(. Did you ask an Intel distributor about these
docs ? They must know.

Good luck
Matthias

* sivakumar <sivakumar.subramani at wipro.com> [030103 09:36]:
> Hi all,
> 
> Where can I get the specification for the 440gx northbridge?
> I am using 440gx as my reference, So I need the specification for 440gx
> northbrige.
> 
> 
> Thanks,
> Siva
> -- 
> sivakumar <sivakumar.subramani at wipro.com>
> wipro
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


From sivakumar.subramani at wipro.com  Fri Jan  3 04:35:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Fri Jan  3 04:35:00 2003
Subject: Specification for 440gx (northbridge)
In-Reply-To: <20030103093431.GB1044@Enterprise>
References: <1041569253.12714.785.camel@Jasmine>
	 <20030103093431.GB1044@Enterprise>
Message-ID: <1041587179.12714.801.camel@Jasmine>

Hi,

I got the document from the following link:
ftp://download.intel.com/design/chipsets/datashts/29063801.pdf

Thanks,
Siva
On Fri, 2003-01-03 at 15:04, Matthias Mueller wrote:
> Hi Siva,
> 
> I worked with the 440GX. All the docs I used were available on the
> Intel-Site. I noticed that they removed all the docs from there
> site. Is the 440GX still available ? Only the 440BX is supported which
> is very similar. Maybe someone on the list can give you the docs (they
> are all PDF files). I left that company very quickly and do not have
> access to the docs :-(. Did you ask an Intel distributor about these
> docs ? They must know.
> 
> Good luck
> Matthias
> 
> * sivakumar <sivakumar.subramani at wipro.com> [030103 09:36]:
> > Hi all,
> > 
> > Where can I get the specification for the 440gx northbridge?
> > I am using 440gx as my reference, So I need the specification for 440gx
> > northbrige.
> > 
> > 
> > Thanks,
> > Siva
> > -- 
> > sivakumar <sivakumar.subramani at wipro.com>
> > wipro
> > 
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From jallen at integraltech.com  Fri Jan  3 06:58:01 2003
From: jallen at integraltech.com (John Allen)
Date: Fri Jan  3 06:58:01 2003
Subject: DMA on the SC2200 Geode
References: <Pine.LNX.4.44.0301021438000.4021-100000@carotid.ccs.lanl.gov>
Message-ID: <3E157D4B.5070605@integraltech.com>

I don't think we should wait until the kernel loads.  For instance, I 
sometimes load the kernel from the hard drive with BOOT_IDE.  The drive 
and controller should be in dma mode beofre this.  Mainboard setup 
sounds good..
John

Ronald G. Minnich wrote:

>On Thu, 2 Jan 2003, Bari Ari wrote:
>
>  
>
>>Pages 148 - 151, 267 - 272 in the NSC SC2200 data sheet have the
>>Ultra DMA/33 and IDE Controller Register info and settings.
>>    
>>
>
>where should we set these? in the mainboard setup? in linux? 
>
>ron
>
>
>  
>



From rminnich at lanl.gov  Fri Jan  3 10:08:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan  3 10:08:00 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it supported
In-Reply-To: <20030103041208.F3CF71FAB6@bom6.vsnl.net.in>
Message-ID: <Pine.LNX.4.44.0301030817520.10976-100000@carotid.ccs.lanl.gov>

I don't know of any support for the 82810 north bridge. 

ron



From rminnich at lanl.gov  Fri Jan  3 10:09:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan  3 10:09:00 2003
Subject: Documentation
In-Reply-To: <1041569557.12715.790.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301030818270.10976-100000@carotid.ccs.lanl.gov>

On 3 Jan 2003, sivakumar wrote:

> Yes, I agree that using doxygen for documentation is good idea. But we
> need to add enough description of the code in source code so that
> doxygen will come up with good documentation. 

agree. Anything you write will be a huge help.

ron



From rminnich at lanl.gov  Fri Jan  3 10:10:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan  3 10:10:01 2003
Subject: Specification for 440gx (northbridge)
In-Reply-To: <1041569253.12714.785.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301030818570.10976-100000@carotid.ccs.lanl.gov>

On 3 Jan 2003, sivakumar wrote:

> Where can I get the specification for the 440gx northbridge?

developer.intel.com

ron



From rminnich at lanl.gov  Fri Jan  3 10:18:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan  3 10:18:00 2003
Subject: DMA on the SC2200 Geode
In-Reply-To: <3E157D4B.5070605@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301030828090.10976-100000@carotid.ccs.lanl.gov>

On Fri, 3 Jan 2003, John Allen wrote:

> I don't think we should wait until the kernel loads.  For instance, I 
> sometimes load the kernel from the hard drive with BOOT_IDE.  The drive 
> and controller should be in dma mode beofre this.  Mainboard setup 
> sounds good..

send code or patch, I will apply.

ron



From dkotian3 at vsnl.net  Fri Jan  3 12:52:01 2003
From: dkotian3 at vsnl.net (Deepak Kotian)
Date: Fri Jan  3 12:52:01 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it supported
References: <Pine.LNX.4.44.0301030817520.10976-100000@carotid.ccs.lanl.gov>
Message-ID: <001401c2b352$76971c20$303e41db@vsnl.net>

Hi,

Thanks for the information.
But any idea, how can one go about it , please let me know.
Any literature on it would help.
Please let me know your views.

Thanks and Regards
Deepak

----- Original Message -----
From: "Ronald G. Minnich" <rminnich at lanl.gov>
To: <dkotian3 at vsnl.net>
Cc: <linuxbios at clustermatic.org>
Sent: Friday, January 03, 2003 8:48 PM
Subject: Re:About Linuxbios on VIA chipset(VIA C processor) , is it
supported


> I don't know of any support for the 82810 north bridge.
>
> ron
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>




From rminnich at lanl.gov  Fri Jan  3 13:14:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan  3 13:14:00 2003
Subject: About Linuxbios on VIA chipset(VIA C processor) , is it
 supported
In-Reply-To: <001401c2b352$76971c20$303e41db@vsnl.net>
Message-ID: <Pine.LNX.4.44.0301031124010.15902-100000@carotid.ccs.lanl.gov>

you can look at some of our port guides. See 
http://www.acl.lanl.gov/linuxbios/developer/portguides/index.html

ron
p.s. the rlx 800i should be in there too, I'll see why it is not.



From jerj at coplanar.net  Sat Jan  4 15:00:01 2003
From: jerj at coplanar.net (Jeremy Jackson)
Date: Sat Jan  4 15:00:01 2003
Subject: Recommended dual Athlon motherboards
Message-ID: <1041711081.10702.2.camel@contact.kennet.coplanar.net>

Are there any recommended motherboards that work might work with a bit
of effort?  I'm thinking 760MPX, are there other chipsets?

Thanks,

Jeremy



From pyro at linuxlabs.com  Sat Jan  4 18:00:01 2003
From: pyro at linuxlabs.com (Steven James)
Date: Sat Jan  4 18:00:01 2003
Subject: Recommended dual Athlon motherboards
In-Reply-To: <1041711081.10702.2.camel@contact.kennet.coplanar.net>
References: <1041711081.10702.2.camel@contact.kennet.coplanar.net>
Message-ID: <1041721841.3e1769f1796ee@zax.linuxlabs.com>

Greetings,

760MPX is promising. I have found that the Tyan/Guiness LinuxBIOS can nearly do
it. There will need to be some mods to the initialization though. It gets all
the way through LinuxBIOS only right after booting from the OEM BIOS.

I haven't seen anything else for dual Athlon.
G'day,
sjames


Quoting Jeremy Jackson <jerj at coplanar.net>:

> Are there any recommended motherboards that work might work with a bit
> of effort?  I'm thinking 760MPX, are there other chipsets?
> 
> Thanks,
> 
> Jeremy
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------












From jerj at coplanar.net  Sat Jan  4 23:36:00 2003
From: jerj at coplanar.net (Jeremy Jackson)
Date: Sat Jan  4 23:36:00 2003
Subject: Recommended dual Athlon motherboards
In-Reply-To: <1041721841.3e1769f1796ee@zax.linuxlabs.com>
References: <1041711081.10702.2.camel@contact.kennet.coplanar.net>
	 <1041721841.3e1769f1796ee@zax.linuxlabs.com>
Message-ID: <1041742054.10704.32.camel@contact.kennet.coplanar.net>

Hi,

Thanks for the info.  I've been looking at the Tyan Tiger MPX (S2466). 
What is Guiness referring to?

Might a comparison of PCI config registers or MSRs after OEM BIOS init
and cold boot reveal something?  Power management actually helps, since
all registers must be read/write (as opposed to write only - like VGA
Pallette snoop) so PM can save context on suspend.  Does LinuxBIOS go
far enough to get the serial port working?

I'm going to buy a board, is there any chance it can be done without an
ICE?

Regards,

Jeremy

On Sat, 2003-01-04 at 18:10, Steven James wrote:
> Greetings,
> 
> 760MPX is promising. I have found that the Tyan/Guiness LinuxBIOS can nearly do
> it. There will need to be some mods to the initialization though. It gets all
> the way through LinuxBIOS only right after booting from the OEM BIOS.
> 
> I haven't seen anything else for dual Athlon.
> G'day,
> sjames
> 
> 
> Quoting Jeremy Jackson <jerj at coplanar.net>:
> 
> > Are there any recommended motherboards that work might work with a bit
> > of effort?  I'm thinking 760MPX, are there other chipsets?
> > 
> > Thanks,
> > 
> > Jeremy




From ebiederman at lnxi.com  Sun Jan  5 00:20:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Sun Jan  5 00:20:01 2003
Subject: Recommended dual Athlon motherboards
In-Reply-To: <1041742054.10704.32.camel@contact.kennet.coplanar.net>
References: <1041711081.10702.2.camel@contact.kennet.coplanar.net>
	<1041721841.3e1769f1796ee@zax.linuxlabs.com>
	<1041742054.10704.32.camel@contact.kennet.coplanar.net>
Message-ID: <m33co89mxu.fsf@lnxi.com>

Jeremy Jackson <jerj at coplanar.net> writes:

> Hi,
> 
> Thanks for the info.  I've been looking at the Tyan Tiger MPX (S2466). 
> What is Guiness referring to?

It was a code name of the Tyan S2462.

> Might a comparison of PCI config registers or MSRs after OEM BIOS init
> and cold boot reveal something?  Power management actually helps, since
> all registers must be read/write (as opposed to write only - like VGA
> Pallette snoop) so PM can save context on suspend.  Does LinuxBIOS go
> far enough to get the serial port working?
> 

I suspect more than anything the warm reboot case is more luck than
anything else.  I remember there are some checks in the code that will
skip a practically all of the early setup in assembly if the machine
is already operational.

> I'm going to buy a board, is there any chance it can be done without an
> ICE?

I haven't used one yet...  

And we currently have a mostly working port, though I don't
know where we are on the release cycle for that.  

>From what I have seen of it the differences are almost totally due to the
different southbridge.  The AMD2466 vs AMD2468.

Eric



From ebiederman at lnxi.com  Sun Jan  5 00:27:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Sun Jan  5 00:27:01 2003
Subject: Why bios(generic) is slow?
In-Reply-To: <8470181DABD5D511B3E700D0B7A8AC4A9CD612@cms3.etri.re.kr>
References: <8470181DABD5D511B3E700D0B7A8AC4A9CD612@cms3.etri.re.kr>
Message-ID: <m3y960885o.fsf@lnxi.com>

hcyun at etri.re.kr writes:

> Hi 
> 
> Can you tell me why generic bios is so slow compared to linuxbios. 
> In other word, why linuxbios is fast? 
> I think "do little thing" is not enough to explain x10 time difference. 
> What does bios do other than linuxbios does and where it spend so much
> time? 

I have wondered that and looked, and on some desktop systems boot up
with a standard BIOS is something like the time LinuxBIOS takes.  But
for server systems, and other lower volume systems I suspect someone
just does a lousy job.

Beyond that.  The easy things to mess up are things like the MTRRs.
If they are not turned on at the appropriate time you can easily get
a 10x slowdown.

Eric



From ebiederman at lnxi.com  Sun Jan  5 00:33:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Sun Jan  5 00:33:00 2003
Subject: DMA on the SC2200 Geode
In-Reply-To: <3E157D4B.5070605@integraltech.com>
References: <Pine.LNX.4.44.0301021438000.4021-100000@carotid.ccs.lanl.gov>
	<3E157D4B.5070605@integraltech.com>
Message-ID: <m3u1go87t0.fsf@lnxi.com>

John Allen <jallen at integraltech.com> writes:

> I don't think we should wait until the kernel loads.  For instance, I sometimes
> load the kernel from the hard drive with BOOT_IDE.  The drive and controller
> should be in dma mode beofre this.  Mainboard setup sounds good..

Put it in the southbridge code, and only call it from mainboard_setup if
you can.

I don't have a large problem with IDE setup in LinuxBIOS but for the most
part I think  it is wasted effort, and quite possibly wasted time
during boot up.  DMA setup is not as easy as just turning on DMA.  You
have to probe the IDE channel, and  verify the drive/drives supports
the kind of DMA you wan to do.   And even in PIO mode you get 3MB/s.

Also look at the etherboot IDE code.  It was initially derived from
what is in LinuxBIOS but I think it is a little cleaner.  At the very
least I haven't run across a drive it has spin up issues with.  

For the most part if you can get/write a Linux driver for this kind of
things and it is satisfactory I don't see a problem.

Eric



From christer at weinigel.se  Sun Jan  5 07:10:01 2003
From: christer at weinigel.se (Christer Weinigel)
Date: Sun Jan  5 07:10:01 2003
Subject: DMA on the SC2200 Geode
In-Reply-To: <3E14AA26.7030708@integraltech.com>
References: <3E14AA26.7030708@integraltech.com>
Message-ID: <m33co7wzy1.fsf@localhost.localdomain>

John Allen <jallen at integraltech.com> writes:

> I just noticed that the harddrive on my Geode sc2200 system is running
> in pio mode.  What do I need to do to turn on dma support for this
> chip?

You need support for the SC2200 DMA engine in your Linux kernel.
Download a recent 2.5 kernel or Alan Cox' linux-2.2.20-ac2 kernel and
turn on:

   CONFIG_BLK_DEV_SC1200

I don't know how well it works though, I just got back after christmas
and haven't had time to test it out yet.

 /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer at weinigel.se>  http://www.weinigel.se


From christer at weinigel.se  Sun Jan  5 07:25:01 2003
From: christer at weinigel.se (Christer Weinigel)
Date: Sun Jan  5 07:25:01 2003
Subject: Help NS Geode experts
In-Reply-To: <NNEHJEGKOBOALJLKPJLDIEDMCCAA.bezanson@netaudiotech.com>
References: <NNEHJEGKOBOALJLKPJLDIEDMCCAA.bezanson@netaudiotech.com>
Message-ID: <m3y95zvko7.fsf@localhost.localdomain>

[cathing up on my mail :-)]

"Adam Bezanson" <bezanson at netaudiotech.com> writes:

> Hi guys,
> 
> I've finally built linuxbios for my SC1200 based board.
> I've written my own flash programming utility so I can program
> the "romimage" file produced into my flash part from Linux command line.
> This all seems to work fine. On my board, I have the ability (with a jumper)
> to direct the ROMCS# signal to one of 3 chips on the board. One is a
> Disk on Chip which currently has a DOS filesystem on it, one is a 2Mbit
> flash chip which has the original Insyde BIOS, and the 3rd is a 16Mbit
> flash part soldered on the board where I'm trying to put linuxbios.
> 
> This 3rd chip is at 0xffe00000 - 0xffffffff, in order to enable this
> addressing I must hit bit 2 in F0 offset 0x52 to enable the Upper ROM size
> based on the ROM Mask at F0 offset 0x6e. This isn't enabled by default so
> I think as the chip comes up only 0xfffc0000 - 0xffffffff is visible.
> I'm not 100% sure, but I assume as the chip comes up it starts trying
> to fetch instructions from 0xfffc0000, is this true?

I think this is correct yes.  If you get the ROMCS mapping to work you
should either be able to use the MTD drivers (see if you can use the
physmap driver in the Linux kernel), or use the devbios driver:

    http://openbios.ph-freiburg.de/cgi-dom/viewcvs.cgi/devbios/

> My question is, where should I program the "romimage" file that comes
> out of the build process? It would seem to me that the linuxbios.rom part
> would have to
> start at 0xfffc0000.

What I do is that I have the following options in my config file for
LinuxBIOS:

    payload /dev/null

    option USE_GENERIC_ROM=1
    option USE_ELF_BOOT=1
    option ZKERNEL_START=0xfffe0000

    option _ROMBASE=0xffff0000

Then I place linuxbios.rom in the last 64kByte of the BIOS chip (the
CPU starts executing at linear address 0xfffffff0 with a magic segment
selector in CS that starts at 0xffff0000) and additionally I place an
etherboot image starting 128kBytes before the end of the BIOS chip.
So with a 512kByte device with 128kByte pages that's accessible with
the Linux MTD physmap driver I do:

    modprobe -a physmap mtdchar

    ./erase /dev/mtd3 0x60000
    dd if=natsemi.elf of=/dev/mtd3 bs=64k seek=2
    dd if=linuxbios.rom of=/dev/mtd3 bs=64k seek=3

erase is a tool from the mtd utilities that erase a sector of a mtd
device.  natsemi.elf is the etherboot image that I've gotten by doing
"make bin32/natsemi.elf".

So physically this means that linuxbios.rom is programmed at address
0xffff0000 and natsemi.elf is programmed at 0xfffe0000.  Ah, yes, one
more thing, I've added the attached patch that enables RAM from
0xe0000 to 0xfffff.

I hope this helps a bit.

  /Christer

--- northbridge/nsc/gx1/Config	16 Mar 2002 22:38:59 -0000	1.1
+++ northbridge/nsc/gx1/Config	5 Jan 2003 12:33:23 -0000
@@ -2,6 +2,8 @@
 # Copyright (c) 2002 Christer Weinigel <wingel at hack.org>
 # Configuration for the National Semiconductor GX1 processors
 
+option CONFIG_COMPRESS=1
+
 mainboardinit northbridge/nsc/gx1/cpu_setup.inc
 mainboardinit northbridge/nsc/gx1/gx_setup.inc
 mainboardinit northbridge/nsc/gx1/northbridge_setup.inc
Index: northbridge/nsc/gx1/gx_setup.inc
===================================================================
RCS file: /cvsroot/freebios/freebios/src/northbridge/nsc/gx1/gx_setup.inc,v
retrieving revision 1.1
diff -u -r1.1 gx_setup.inc
--- northbridge/nsc/gx1/gx_setup.inc	16 Mar 2002 22:39:00 -0000	1.1
+++ northbridge/nsc/gx1/gx_setup.inc	5 Jan 2003 12:33:23 -0000
@@ -32,7 +32,7 @@
 	.long	BC_DRAM_TOP, 0x3fffffff
 	.long	BC_XMAP_1, 0x60
 	.long	BC_XMAP_2, 0
-	.long	BC_XMAP_3, 0
+	.long	BC_XMAP_3, 0x77777777	/* Enable RAM from e0000-FFFFF */
 
 	.long	MC_BANK_CFG, 0x00700070	/* No DIMMS installed */
 	.long	MC_MEM_CNTRL1, XBUSARB

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer at weinigel.se>  http://www.weinigel.se


From christer at weinigel.se  Sun Jan  5 07:31:01 2003
From: christer at weinigel.se (Christer Weinigel)
Date: Sun Jan  5 07:31:01 2003
Subject: Help NS Geode experts
In-Reply-To: <C0D45ABB3F45D5118BBC00508BC292DB9D438E@imgserv04>
References: <C0D45ABB3F45D5118BBC00508BC292DB9D438E@imgserv04>
Message-ID: <m3u1gnvkiy.fsf@localhost.localdomain>

James Finnie <jf1 at imerge.co.uk> writes:

> Hi guys,
> 
> I currently use the /dev/bios work for flashing BIOS in a production
> evironment on a GX1+5530A platform. It works great.  It may not work out of
> the box for SC2200/SC1200 (I have no experience on these platforms), but it
> would be well worth getting it working - it supports a large number of
> different flash parts and provides a great interface.  Sounds like Adam has
> already done the hard bit!

devbios works fine for me too and I've tried it on one SC2200 board
and a lot of GX1+CS5530 boards.  I've had to add definitions for a few
new chip ID's every now but that's all.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer at weinigel.se>  http://www.weinigel.se


From pyro at linuxlabs.com  Sun Jan  5 09:20:01 2003
From: pyro at linuxlabs.com (Steven James)
Date: Sun Jan  5 09:20:01 2003
Subject: Recommended dual Athlon motherboards
In-Reply-To: <1041742054.10704.32.camel@contact.kennet.coplanar.net>
References: <1041711081.10702.2.camel@contact.kennet.coplanar.net>  <1041721841.3e1769f1796ee@zax.linuxlabs.com> <1041742054.10704.32.camel@contact.kennet.coplanar.net>
Message-ID: <1041777044.3e184194432ec@zax.linuxlabs.com>

Greetings,

Guiness is AKA TigerMP. I expect that the comparisons will be helpful, I just
haven't had the time to finish that yet. The datasheets are available from AMD
which is also a help. The Northbridge is the same for 760 and 760MPX chipset.

Serial comes up only on the first boot of LinuxBIOS (after OEM BIOS has done
some setup). I don't expect too much trouble fixing that. The rest will be
reletivly easy after that.

An ICE should not be required (which is good since I don't have one), but extra
flash chips will be essential.

G'day,
sjames




Quoting Jeremy Jackson <jerj at coplanar.net>:

> Hi,
> 
> Thanks for the info.  I've been looking at the Tyan Tiger MPX (S2466). 
> What is Guiness referring to?
> 
> Might a comparison of PCI config registers or MSRs after OEM BIOS init
> and cold boot reveal something?  Power management actually helps, since
> all registers must be read/write (as opposed to write only - like VGA
> Pallette snoop) so PM can save context on suspend.  Does LinuxBIOS go
> far enough to get the serial port working?
> 
> I'm going to buy a board, is there any chance it can be done without an
> ICE?
> 
> Regards,
> 
> Jeremy
> 
> On Sat, 2003-01-04 at 18:10, Steven James wrote:
> > Greetings,
> > 
> > 760MPX is promising. I have found that the Tyan/Guiness LinuxBIOS can
> nearly do
> > it. There will need to be some mods to the initialization though. It
> gets all
> > the way through LinuxBIOS only right after booting from the OEM BIOS.
> > 
> > I haven't seen anything else for dual Athlon.
> > G'day,
> > sjames
> > 
> > 
> > Quoting Jeremy Jackson <jerj at coplanar.net>:
> > 
> > > Are there any recommended motherboards that work might work with a
> bit
> > > of effort?  I'm thinking 760MPX, are there other chipsets?
> > > 
> > > Thanks,
> > > 
> > > Jeremy
> 
> 



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------












From jallen at integraltech.com  Mon Jan  6 07:02:01 2003
From: jallen at integraltech.com (John Allen)
Date: Mon Jan  6 07:02:01 2003
Subject: DMA on the SC2200 Geode
References: <Pine.LNX.4.44.0301021438000.4021-100000@carotid.ccs.lanl.gov>	<3E157D4B.5070605@integraltech.com> <m3u1go87t0.fsf@lnxi.com>
Message-ID: <3E1972C6.8030106@integraltech.com>

Eric,
You raise a good point.  We would have to determine if the drives 
support the dma mode we want.  I have done a little experimentation and 
found that it is probably best to let the kernel handle the dma setup. 
 After all, having LinuxBIOS do the minimal initialization is the goal 
of LinuxBIOS.
John

Eric W. Biederman wrote:

>John Allen <jallen at integraltech.com> writes:
>
>  
>
>>I don't think we should wait until the kernel loads.  For instance, I sometimes
>>load the kernel from the hard drive with BOOT_IDE.  The drive and controller
>>should be in dma mode beofre this.  Mainboard setup sounds good..
>>    
>>
>
>Put it in the southbridge code, and only call it from mainboard_setup if
>you can.
>
>I don't have a large problem with IDE setup in LinuxBIOS but for the most
>part I think  it is wasted effort, and quite possibly wasted time
>during boot up.  DMA setup is not as easy as just turning on DMA.  You
>have to probe the IDE channel, and  verify the drive/drives supports
>the kind of DMA you wan to do.   And even in PIO mode you get 3MB/s.
>
>Also look at the etherboot IDE code.  It was initially derived from
>what is in LinuxBIOS but I think it is a little cleaner.  At the very
>least I haven't run across a drive it has spin up issues with.  
>
>For the most part if you can get/write a Linux driver for this kind of
>things and it is satisfactory I don't see a problem.
>
>Eric
>
>
>  
>



From sivakumar.subramani at wipro.com  Mon Jan  6 08:58:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Mon Jan  6 08:58:01 2003
Subject: Configuring DRAM register using SPD.
Message-ID: <001501c2b58d$4d7d51f0$970806c0@siva>

Hi,

I am using spd_82801.c file to get the SPD values of the my DDR SDRAM. I have checked the values and it seem to be correct.
Now I want to program the DRAM registers. When I was browsing the 440gx code, I could found that these SPD values are not used directly to
get the DRAM register value. 

I could not  understand the step used to calculate the DRAM register values. In the specification I could see only the description of DRAM register, not the 
steps to calculate the value of DRAM register. Where can I find those steps? How do you get to know for the 440gx ? Is it ok to hardcode the values ?
I am going for this option because our system is a embedded system, so the configuration will not change.

Also while browsing the 440gx code, I found that  most of the register are left with default values. Can any one giving some idea about the set of registers which I need to 
program. I have attached the output of the SPD program. But how to calculate the DRAM register values like DRB, DRT, DRC,FDHC and etc., 


The Output of the SPD_82801.c file on my DDR SDRAM:

[root at wipro2 scanspd]# ./spd_82801ba
dev=1f, fn=3
IO_BASE=5000
After reset status 0x40
SLOT 0
After reset status 0x40
Number of bytes used by module manufacturer 0x80
After reset status 0x40
Memory Type 0x07 ---------------> DDR SDRAM
After reset status 0x40
Number of Row Address bits 0x0d
After reset status 0x40
Number of Column Address bits 0x0a
After reset status 0x40
Number of Sides 0x01
After reset status 0x40
DIMM Configuratio type 0x00
After reset status 0x40
Refresh Rate 0x82-------------------------------> refresh rate is 7.8 micro sec
After reset status 0x40
Number of Banks 0xa0
After reset status 0x40
Module Bank Density 0x40
After reset status 0x40
SPD Revision Code 0x00
After reset status 0x40
CAS # Latency 0x0c               -----------------------> 2.5
After reset status 0x40
Min Row Precharge 0x50
After reset status 0x40
Min RAS to CAS Delay 0x50 ------------------------------> 20 ns
After reset status 0x40
Min RAS Pulse Width 0x2d
[root at wipro2 scanspd]#


Thanks,
Siva



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030106/5859f6a7/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030106/5859f6a7/attachment.txt>

From marc.miller at amd.com  Mon Jan  6 09:13:01 2003
From: marc.miller at amd.com (marc.miller at amd.com)
Date: Mon Jan  6 09:13:01 2003
Subject: Recommended dual Athlon motherboards
Message-ID: <858788618A93D111B45900805F85267A062BC15D@caexmta3.amd.com>

Guinness is actually the code name of the Tyan Thunder K7.  Tiger came later.

-----Original Message-----
From: Steven James [mailto:pyro at linuxlabs.com]
Sent: Sunday, January 05, 2003 6:31 AM
To: Jeremy Jackson
Cc: linuxbios at clustermatic.org
Subject: Re: Recommended dual Athlon motherboards


Greetings,

Guiness is AKA TigerMP. I expect that the comparisons will be helpful, I just
haven't had the time to finish that yet. The datasheets are available from AMD
which is also a help. The Northbridge is the same for 760 and 760MPX chipset.

Serial comes up only on the first boot of LinuxBIOS (after OEM BIOS has done
some setup). I don't expect too much trouble fixing that. The rest will be
reletivly easy after that.

An ICE should not be required (which is good since I don't have one), but extra
flash chips will be essential.

G'day,
sjames




Quoting Jeremy Jackson <jerj at coplanar.net>:

> Hi,
> 
> Thanks for the info.  I've been looking at the Tyan Tiger MPX (S2466). 
> What is Guiness referring to?
> 
> Might a comparison of PCI config registers or MSRs after OEM BIOS init
> and cold boot reveal something?  Power management actually helps, since
> all registers must be read/write (as opposed to write only - like VGA
> Pallette snoop) so PM can save context on suspend.  Does LinuxBIOS go
> far enough to get the serial port working?
> 
> I'm going to buy a board, is there any chance it can be done without an
> ICE?
> 
> Regards,
> 
> Jeremy
> 
> On Sat, 2003-01-04 at 18:10, Steven James wrote:
> > Greetings,
> > 
> > 760MPX is promising. I have found that the Tyan/Guiness LinuxBIOS can
> nearly do
> > it. There will need to be some mods to the initialization though. It
> gets all
> > the way through LinuxBIOS only right after booting from the OEM BIOS.
> > 
> > I haven't seen anything else for dual Athlon.
> > G'day,
> > sjames
> > 
> > 
> > Quoting Jeremy Jackson <jerj at coplanar.net>:
> > 
> > > Are there any recommended motherboards that work might work with a
> bit
> > > of effort?  I'm thinking 760MPX, are there other chipsets?
> > > 
> > > Thanks,
> > > 
> > > Jeremy
> 
> 



----------------------------steven james, director of research, linux labs

LinuxBIOS Cluster Solutions                   230 peachtree st nw ste 2705

High-Speed Colocation, Hosting,                        atlanta.ga.us 30303

Linux Hardware, Development & Support             http://www.linuxlabs.com

* Visit us at SuperComputing 2002, Booth 1441 *   office/fax 404.577.7747/3

--------------------------------------------------------------------------










_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From sivakumar.subramani at wipro.com  Mon Jan  6 09:25:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Mon Jan  6 09:25:00 2003
Subject: Building LinuxBIOS
Message-ID: <006601c2b591$04ddb800$970806c0@siva>

Hi,

While build the Linuxbios image, first step is copying of 
/vobs/elinux/LinuxBIOS/freebios/src/arch/i386/config/crt0.base to crt0.S.
Do I need to modify some thing that is specific to motherboard in crt0.base file?
Do I need have any private setting for motherboard in crt0.base file?

Thanks,
Siva.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030106/6e7b6a68/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030106/6e7b6a68/attachment.txt>

From rminnich at lanl.gov  Mon Jan  6 11:10:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Jan  6 11:10:01 2003
Subject: Configuring DRAM register using SPD.
In-Reply-To: <001501c2b58d$4d7d51f0$970806c0@siva>
Message-ID: <Pine.LNX.4.44.0301060920570.18157-100000@carotid.ccs.lanl.gov>

On Mon, 6 Jan 2003, sivakumar wrote:

> I could not understand the step used to calculate the DRAM register
> values. In the specification I could see only the description of DRAM
> register, not the steps to calculate the value of DRAM register. Where
> can I find those steps? How do you get to know for the 440gx ? Is it ok
> to hardcode the values ? I am going for this option because our system
> is a embedded system, so the configuration will not change.

you are just going to have to dig a bit harder, sorry to say. It's in 
there. I agree it is kind of confusing, but it is in there.

ron



From christer at weinigel.se  Mon Jan  6 14:41:00 2003
From: christer at weinigel.se (Christer Weinigel)
Date: Mon Jan  6 14:41:00 2003
Subject: Geode sc2200 vga
In-Reply-To: <87of7royfo.fsf@zoo.weinigel.se>
References: <3DF8BF29.7000801@integraltech.com>
	<87of7royfo.fsf@zoo.weinigel.se>
Message-ID: <m3isx2kqe3.fsf@localhost.localdomain>

Christer Weinigel <christer at weinigel.se> writes:

> John Allen <jallen at integraltech.com> writes:
> 
> > I have successfully built LinuxBIOS to load a kernel from my IDE drive 
> > and boot using a serial console.  Now I would like to test the VGA 
> > funtionality of my board.  Has anyone had any experience getting the VGA 
> > to turn on and work within LinuxBIOS and/or Linux?
> > John
> 
> <cut'n'paste>
>     There is no video support in LinuxBIOS itself, so you won't get
>     any video until you have loaded the NatSemi Geode Linux
>     framebuffer driver (can be found at www.linux4.tv under the
>     heading SP1SC10 Platform Image).
> </cut'n'paste>
> 
> Go fetch the NatSemi driver, that will give you video in Linux.
> 
>   /Christer (who _definitely_ has to write a FAQ soon)

<confession time>

Ok, I downloaded the linux4.tv driver again and tried it on my SC2200
board and I can't get it to work either.  Very strange, since I had it
working with LinuxBIOS a couple of months ago.  It might be that I had
to turn on some clock or PLL by hand.  

</confession time>

Oh well, I'll try to see if I can find a backup of the kernel I used
then and see if I can get it running again.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer at weinigel.se>  http://www.weinigel.se


From christer at weinigel.se  Mon Jan  6 17:32:01 2003
From: christer at weinigel.se (Christer Weinigel)
Date: Mon Jan  6 17:32:01 2003
Subject: Geode sc2200 vga
In-Reply-To: <m3isx2kqe3.fsf@localhost.localdomain>
References: <3DF8BF29.7000801@integraltech.com>
	<87of7royfo.fsf@zoo.weinigel.se>
	<m3isx2kqe3.fsf@localhost.localdomain>
Message-ID: <m3n0mdlx1i.fsf@localhost.localdomain>

Christer Weinigel <christer at weinigel.se> writes:

> <confession time>
> 
> Ok, I downloaded the linux4.tv driver again and tried it on my SC2200
> board and I can't get it to work either.  Very strange, since I had it
> working with LinuxBIOS a couple of months ago.  It might be that I had
> to turn on some clock or PLL by hand.  
> 
> </confession time>
> 
> Oh well, I'll try to see if I can find a backup of the kernel I used
> then and see if I can get it running again.

Following up to myself... Backups are a good thing :-)

This patch initializes a few registers on the SC2200 that the geodefb
code from linux4.tv doesn't seem to touch.  The values I'm storing
into the registers are read from a system running with the XpressROM
BIOS.  Now I can see the penguin when booting Linux from LinuxBIOS.
The timing for the video mode seems strange, my monitor has some
trouble syncing on this signal, but at least I get some kind of video.
I guess that something similar is needed to get video from a CS5530
based system.

I think I'll give up on this for the moment, I'm not all that
interested in video myself, I just wanted to know why it didn't work
when I knew that I had had it running before.  If anyone needs video
to work on a SC2200, make a dump of the F4BAR1 registers and the GCR
registers and compare them with a working system (booted from
XPressROM) and look in the data sheets to see if the differences seem
significant.  

  /Christer (off to sleep)

diff -ur linux-2.4.19/drivers/video/geode/geodefb.c.orig linux-2.4.19/drivers/video/geode/geodefb.c
--- linux-2.4.19/drivers/video/geode/geodefb.c.orig	Tue Apr 10 17:09:01 2001
+++ linux-2.4.19/drivers/video/geode/geodefb.c	Mon Jan  6 23:27:31 2003
@@ -182,6 +182,8 @@
 #include <linux/init.h>
 #include <linux/devfs_fs_kernel.h>
 
+#include <linux/pci.h>
+
 #include <asm/io.h>
 #include <asm/mtrr.h>
 
@@ -1350,6 +1352,36 @@
         return(-EBUSY);
     }
 
+    if (1)			/* wingel */
+    {
+	struct pci_dev *pdev;
+	u8 *video;
+
+	if ((pdev = pci_find_device(PCI_VENDOR_ID_NS, 
+				    PCI_DEVICE_ID_NS_SCx200_VIDEO,
+				    NULL)) == NULL) {
+	    printk("can't find scx200\n");
+	} else if (!(video = ioremap(pci_resource_start(pdev, 1), 0x1000))) {
+	    printk(KERN_ERR "unable to ioremap video\n");
+	} else {
+	    writel(0x00001000, gfx_virt_regptr + 0x8308); /* disable timing generator */
+
+	    writel(0x0020030f, video + 0x04);
+	    writel(0x00001000, video + 0x28);
+	    writel(0x0070e00c, video + 0x2c);
+	    
+	    writel(0x00000100, video + 0x44);
+	    writel(0x00000156, video + 0x48);
+	    writel(0x00060000, video + 0x4c);
+	    writel(0x00ffffff, video + 0x50);
+	    writel(0x00ffffff, video + 0x54);
+	    
+	    writel(0x1000102f, gfx_virt_regptr + 0x8308);
+
+	    iounmap(video);
+	}
+    }
+
     geode_create_galdevice();
     
     strcpy(gen.info.modename, geodefb_name);


-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer at weinigel.se>  http://www.weinigel.se


From rminnich at lanl.gov  Mon Jan  6 20:51:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Jan  6 20:51:00 2003
Subject: Building LinuxBIOS
In-Reply-To: <006601c2b591$04ddb800$970806c0@siva>
Message-ID: <Pine.LNX.4.44.0301060825280.18157-100000@carotid.ccs.lanl.gov>

On Mon, 6 Jan 2003, sivakumar wrote:

> While build the Linuxbios image, first step is copying of
> /vobs/elinux/LinuxBIOS/freebios/src/arch/i386/config/crt0.base to
> crt0.S. Do I need to modify some thing that is specific to motherboard
> in crt0.base file? Do I need have any private setting for motherboard in
> crt0.base file?

definitely NOT. That is a generic file. 

ron



From rminnich at lanl.gov  Mon Jan  6 20:57:36 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Jan  6 20:57:36 2003
Subject: DMA on the SC2200 Geode
In-Reply-To: <3E1972C6.8030106@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301060823050.18157-100000@carotid.ccs.lanl.gov>

On Mon, 6 Jan 2003, John Allen wrote:

> You raise a good point.  We would have to determine if the drives
> support the dma mode we want.  I have done a little experimentation and
> found that it is probably best to let the kernel handle the dma setup.  
> After all, having LinuxBIOS do the minimal initialization is the goal of
> LinuxBIOS.

Well I am glad to hear you say this, as I did not like the idea of putting 
all that DMA support into linuxbios -- the kernel can always do a better 
job of configuring IDE, I think.

ron



From xuning1979 at hotmail.com  Mon Jan  6 21:18:00 2003
From: xuning1979 at hotmail.com (xu xuning)
Date: Mon Jan  6 21:18:00 2003
Subject: (no subject)
Message-ID: <F174ZGYmXvmmKtrM0mk000093bb@hotmail.com>

hello, I use the pre-made images from http://www.cwlinux.com/download/,and 
my mainboard is winfast6300 MA Pro.then i have several problems:
  1.
    In this system don't support ide and usb memory,and how to do about 
these? i know there were no related drivers in the system ,but i don't know 
how to do it?
  2.
    in http://www.cwlinux.com/download/ ,i find some files and their name 
is *.rom.but how to use these files? the "readme" isn't detailed for me.
           thanks                                           




_________________________________________________________________
??????????????? MSN Hotmail? http://www.hotmail.com 



From jerj at coplanar.net  Tue Jan  7 16:47:00 2003
From: jerj at coplanar.net (Jeremy Jackson)
Date: Tue Jan  7 16:47:00 2003
Subject: PCI-X Board or Chipset recommendataions
Message-ID: <1041976734.1993.67.camel@contact.kennet.coplanar.net>

Anything in the PCI-X category with LinuxBIOS potential?
-- 
Jeremy Jackson <jerj at coplanar.net>



From rminnich at lanl.gov  Tue Jan  7 18:49:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Jan  7 18:49:01 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <1041976734.1993.67.camel@contact.kennet.coplanar.net>
Message-ID: <Pine.LNX.4.44.0301071659340.30286-100000@carotid.ccs.lanl.gov>

On 7 Jan 2003, Jeremy Jackson wrote:

> Anything in the PCI-X category with LinuxBIOS potential?

yes, look in the mainboard/supermicro directory, the p4dp series all have 
pci-x slot(s).

ron



From dveatch at woh.rr.com  Tue Jan  7 19:38:00 2003
From: dveatch at woh.rr.com (Dennis Veatch)
Date: Tue Jan  7 19:38:00 2003
Subject: 440BX - Worth the time?
Message-ID: <200301071949.50985.dveatch@woh.rr.com>

I'm thinking about a switch to Linuxbios for this mobo. The status page on the 
website says unstable but there is no current date of this status. I looked 
through the archives and must have overlooked any references to this chipset. 
So would this board be a good candidate? A few notes about it. 

1) currently a 400MHz PII that I plan on bumping up to a 700MHz PIII (slot 1).
2) the SCSI is an Adaptec 2940/7881.
3) the video card is an ATI Radeon 9000.

Attached is the output of lspci -vvv. Any pointers will be most appreciated.


Thanks
-- 
Registered Linux User - 193414

Sig for OSS: Never be afraid to try something yourself, remember amateurs 
built the Ark, professionals built the Titanic.


From dveatch at woh.rr.com  Tue Jan  7 19:48:01 2003
From: dveatch at woh.rr.com (Dennis Veatch)
Date: Tue Jan  7 19:48:01 2003
Subject: Fwd: 440BX - Worth the time?
Message-ID: <200301071959.05161.dveatch@woh.rr.com>

Opps forgot the file.

----------  Forwarded Message  ----------

Subject: 440BX - Worth the time?
Date: Tuesday 07 January 2003 07:49 pm
From: Dennis Veatch <dveatch at woh.rr.com>
To: linuxbios at clustermatic.org

I'm thinking about a switch to Linuxbios for this mobo. The status page on
 the website says unstable but there is no current date of this status. I
 looked through the archives and must have overlooked any references to this
 chipset. So would this board be a good candidate? A few notes about it.

1) currently a 400MHz PII that I plan on bumping up to a 700MHz PIII (slot
 1). 2) the SCSI is an Adaptec 2940/7881.
3) the video card is an ATI Radeon 9000.

Attached is the output of lspci -vvv. Any pointers will be most appreciated.


Thanks
-- 
Registered Linux User - 193414


Sig for OSS: Never be afraid to try something yourself, remember amateurs 
built the Ark, professionals built the Titanic.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lspcilist.gz
Type: application/x-gzip
Size: 1251 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030107/a5ada526/attachment.gz>

From terryc at tyanchina.com  Tue Jan  7 19:51:00 2003
From: terryc at tyanchina.com (Terry B. Chen)
Date: Tue Jan  7 19:51:00 2003
Subject: about E7501
Message-ID: <441383BA85E81D48964152E537886C9D23029D@mail.sh.corp.tyan.com>

Is anyone interested in E7501? 
What is the difference between FSB 533 and 400 in Northbridge? I have a thought to port E7501 to E7500. 
Someone give me some suggestions!
 
Thank you !
 
 
 
Best Regards
Terry Chen
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030107/a225d853/attachment.html>

From lawrence at tyanchina.com  Tue Jan  7 19:53:01 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Tue Jan  7 19:53:01 2003
Subject: Boot from etherboot - blocked by INT 10
Message-ID: <441383BA85E81D48964152E537886C9D23029F@mail.sh.corp.tyan.com>

Hi,

When I try Linux bios to boot from Ethernet, I find it will be blocked by an instruction of INT 10.
The kernel downloaded from TFTP server has the INT 10 instruction, while INT 10 has not been realized in Linux bios.
So it is stopped. How can I resolve the problem?

Thanks,
Lawrence


From aip at cwlinux.com  Wed Jan  8 01:50:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Wed Jan  8 01:50:01 2003
Subject: [COMMIT] fix for EPIA performace problem from Kevin Hester
Message-ID: <20030108150108.A31416@mail.cwlinux.com>


checkedin
northbridge/via/vt8601/northbridge.c
northbridge/via/vt694/northbridge.c
mainboard/via/epia/mainboard.c

These fix network and ide performance problem.  I have verified the patch.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030108/a86387ad/attachment.sig>

From alesan at manoweb.com  Wed Jan  8 09:33:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Wed Jan  8 09:33:00 2003
Subject: beginner's question
Message-ID: <3E1C39DD.3040404@manoweb.com>

Hi, this is not the first time I write but in the past months I was too 
busy and I had no time to build a nice linuxbios-box!

However now I'm going to buy a pchips motheboard so I can start to 
experiment.

I've read the useful guide on the web; however I have some doubts:

what about that disc on chip device: how much does it cost more or less? 
Why can't we use a normal FLASH memory like the ones used to store a 
standard BIOS? I can think those chips provide particular features, but 
which ones exactly? Aren't common flash/eeprom chips much easier to find 
and cheaper to buy? An external programmer could be needed (like for the 
eproms of etherboot) but most people could have access to such a device.

Bye bye and thank you!
as

P.S. I've read just now that on the pchips motherboard for athlon cpus 
the L2 cache is not working. Is it true? As the cache is on the 
processor and not on the mainboard, I thought this wouldn't be a problem...







From alesan at manoweb.com  Wed Jan  8 09:36:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Wed Jan  8 09:36:00 2003
Subject: what is a disc on chip? - beginner's question
Message-ID: <3E1C3A0C.6010700@manoweb.com>

Hi, this is not the first time I write but in the past months I was too
busy and I had no time to build a nice linuxbios-box!

However now I'm going to buy a pchips motheboard so I can start to
experiment.

I've read the useful guide on the web; however I have some doubts:

what about that disc on chip device: how much does it cost more or less?
Why can't we use a normal FLASH memory like the ones used to store a
standard BIOS? I can think those chips provide particular features, but
which ones exactly? Aren't common flash/eeprom chips much easier to find
and cheaper to buy? An external programmer could be needed (like for the
eproms of etherboot) but most people could have access to such a device.

Bye bye and thank you!
as

P.S. I've read just now that on the pchips motherboard for athlon cpus
the L2 cache is not working. Is it true? As the cache is on the
processor and not on the mainboard, I thought this wouldn't be a problem...








From pyro at linuxlabs.com  Wed Jan  8 09:51:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Wed Jan  8 09:51:01 2003
Subject: about E7501
In-Reply-To: <441383BA85E81D48964152E537886C9D23029D@mail.sh.corp.tyan.com>
Message-ID: <Pine.LNX.4.21.0301081000400.11840-100000@ucontrol.mobiledns.com>

Greetings,

I am definatly interested is E7501. I have a developer board on it's way
to me now.

The primary difference I am interested in is the performance boost
(hopefully) from the 533 FSB.

G'day,
sjames




On Wed, 8 Jan 2003, Terry B. Chen wrote:

> Is anyone interested in E7501? 
> What is the difference between FSB 533 and 400 in Northbridge? I have a thought to port E7501 to E7500. 
> Someone give me some suggestions!
>  
> Thank you !
>  
>  
>  
> Best Regards
> Terry Chen
>  
>  
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From rsmith at bitworks.com  Wed Jan  8 12:21:01 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Wed Jan  8 12:21:01 2003
Subject: Fwd: 440BX - Worth the time?
In-Reply-To: <200301071959.05161.dveatch@woh.rr.com>
Message-ID: <MDAEMON-F200301081048.AA483075MD45230@bitworks.com>

On Tue, 7 Jan 2003 19:59:05 -0500, Dennis Veatch wrote:


> I'm thinking about a switch to Linuxbios for this mobo. The status page on
>  the website says unstable but there is no current date of this status. I
>  looked through the archives and must have overlooked any references to this
>  chipset. So would this board be a good candidate? A few notes about it.

Dennis,

Suposedly the 440BX is supposed to work.  Some of the mainboards in
the mainbord directory are 440xx based and people claim they work. 
We have a 440bx based SBC that I tried linuxbios on briefly but I was
never able to get it to turn on the ram properly.  

IIRC I could see the SPD read command issued on the bus and then see
the info return but the value read from the data register was zero.

So I'm very interested in any testing that you do.  

I've attached the config file I was using for my testing.  There
isn't anything special or specific to our board so this should be
fine for any BX based board.

One thing to look at though would be the DEVFN of the PIIX4 and make
sure its the same as the config file.  Thats where the I2C bridge is
and it needs that address to set up and talk to the RAM SPD.

Also I haven't worked on this in 6-8 months so this config file may
be really out of date.  If for some reason it won't build then thats
why.

We are about to spin a new rev of this board and this version _will_
run linuxbios.  So I'm going to have to fix this at some point in the
near future and I would be happy to have some help.

--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Config
Type: application/octet-stream
Size: 815 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030108/45d5a515/attachment.obj>

From rminnich at lanl.gov  Wed Jan  8 12:41:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  8 12:41:01 2003
Subject: Fwd: 440BX - Worth the time?
In-Reply-To: <MDAEMON-F200301081048.AA483075MD45230@bitworks.com>
Message-ID: <Pine.LNX.4.44.0301081052500.3624-100000@carotid.ccs.lanl.gov>

I do have linuxbios working fine with SPD support on the digital logic 
smartcore piii -- that is a 440bx box.

ron



From jerj at coplanar.net  Wed Jan  8 13:47:00 2003
From: jerj at coplanar.net (Jeremy Jackson)
Date: Wed Jan  8 13:47:00 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <Pine.LNX.4.44.0301071659340.30286-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301071659340.30286-100000@carotid.ccs.lanl.gov>
Message-ID: <1042052373.4765.16.camel@contact.kennet.coplanar.net>

How LinuxBIOS friendly are the e7500/Xeons for LinuxBIOS?  Any NDA
issues like AMD MSRs or similar?

Also, I'm looking at the p4dpl-m, which has different bus layout than
either of the p4dp's in cvs, and wondering how difficult to support.

Thanks,

Jeremy

On Tue, 2003-01-07 at 19:00, Ronald G. Minnich wrote:
> On 7 Jan 2003, Jeremy Jackson wrote:
> 
> > Anything in the PCI-X category with LinuxBIOS potential?
> 
> yes, look in the mainboard/supermicro directory, the p4dp series all have 
> pci-x slot(s).
> 
> ron
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
-- 
Jeremy Jackson <jerj at coplanar.net>



From pyro at linuxlabs.com  Wed Jan  8 14:35:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Wed Jan  8 14:35:00 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <1042052373.4765.16.camel@contact.kennet.coplanar.net>
Message-ID: <Pine.LNX.4.21.0301081445210.3346-100000@ucontrol.mobiledns.com>

Greetings,

I'm having good success with the Intel Clearwater boards w/ dual Xeon.

G'day,
sjames


On 8 Jan 2003, Jeremy Jackson wrote:

> How LinuxBIOS friendly are the e7500/Xeons for LinuxBIOS?  Any NDA
> issues like AMD MSRs or similar?
> 
> Also, I'm looking at the p4dpl-m, which has different bus layout than
> either of the p4dp's in cvs, and wondering how difficult to support.
> 
> Thanks,
> 
> Jeremy
> 
> On Tue, 2003-01-07 at 19:00, Ronald G. Minnich wrote:
> > On 7 Jan 2003, Jeremy Jackson wrote:
> > 
> > > Anything in the PCI-X category with LinuxBIOS potential?
> > 
> > yes, look in the mainboard/supermicro directory, the p4dp series all have 
> > pci-x slot(s).
> > 
> > ron
> > 
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From rminnich at lanl.gov  Wed Jan  8 14:49:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  8 14:49:00 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <1042052373.4765.16.camel@contact.kennet.coplanar.net>
Message-ID: <Pine.LNX.4.44.0301081252300.5337-100000@carotid.ccs.lanl.gov>

On 8 Jan 2003, Jeremy Jackson wrote:

> How LinuxBIOS friendly are the e7500/Xeons for LinuxBIOS?  Any NDA
> issues like AMD MSRs or similar?

no nda issues whatsoever. Intel has been extremely helpful on this 
chipset. In fact there was a glitch a few months ago and Intel did what 
needed to be done to get it fixed.

> Also, I'm looking at the p4dpl-m, which has different bus layout than
> either of the p4dp's in cvs, and wondering how difficult to support.


send an lspci.

ron



From stutts at innocon.com  Wed Jan  8 14:58:01 2003
From: stutts at innocon.com (Christopher Stutts)
Date: Wed Jan  8 14:58:01 2003
Subject: Fwd: 440BX - Worth the time?
In-Reply-To: <200301071959.05161.dveatch@woh.rr.com>
References: <200301071959.05161.dveatch@woh.rr.com>
Message-ID: <1042056620.8415.8.camel@powerbrick.innocon.com>

I'm using the BX with mobile PIIIs.  No SMBUS, just hardcoded SDRAM
init.  Old LinuxBIOS tarball, and there were a couple minor PCI config
issues.  BX PCI config regs not in the standard BAR locations.  But it's
solid.  Memory tests passed after tweeking SDRAM drive strength
settings.



From pyro at linuxlabs.com  Wed Jan  8 15:10:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Wed Jan  8 15:10:00 2003
Subject: [COMMIT] Intel Clearwater
Message-ID: <Pine.LNX.4.21.0301081517560.3346-100000@ucontrol.mobiledns.com>

Greetings,

Just committed a small change to Config for Intel Clearwater.
The change makes ZKERNEL_START = 0xfff00000 for a failover inage and
0xfff10000 for a primary. 

This change allows for two copies of bootselect. The one at 0xfff00000
should be considered part of the failover.

G'day,
sjames


-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From alesan at manoweb.com  Wed Jan  8 16:23:01 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Wed Jan  8 16:23:01 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's
 question
Message-ID: <3E1C9A14.3060007@manoweb.com>

Hi, this is not the first time I write but in the past months I was too
busy and I had no time to build a nice linuxbios-box!

However now I'm going to buy a pchips motheboard so I can start to
experiment.

I've read the useful guide on the web; however I have some doubts:

what about that disc on chip device: how much does it cost more or less?
Why can't we use a normal FLASH memory like the ones used to store a
standard BIOS? I can think those chips provide particular features, but
which ones exactly? Aren't common flash/eeprom chips much easier to find
and cheaper to buy? An external programmer could be needed (like for the
eproms of etherboot) but most people could have access to such a device.

Bye bye and thank you!
as

P.S. I've read just now that on the pchips motherboard for athlon cpus
the L2 cache is not working. Is it true? As the cache is on the
processor and not on the mainboard, I thought this wouldn't be a problem...









From Antony at Soft-Solutions.co.uk  Wed Jan  8 16:45:00 2003
From: Antony at Soft-Solutions.co.uk (Antony Stone)
Date: Wed Jan  8 16:45:00 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
Message-ID: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there>

On Wednesday 08 January 2003 9:37 pm, Alessio Sangalli wrote:

> what about that disc on chip device: how much does it cost more or less?

In the UK they cost about GBP20 - so I guess that's about EUR30 / USD30 in
the rest of the world...

> Why can't we use a normal FLASH memory like the ones used to store a
> standard BIOS?

Because they do not have a large enough capacity.   Standard BIOS chips are
2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.

> I can think those chips provide particular features, but
> which ones exactly?

The main thing which DoC does which you can't do with standard Flash Roms is
to format them as a Silicon Disc, and put a file system into them.

> Aren't common flash/eeprom chips much easier to find
> and cheaper to buy?

Yes, but they're too small.

> An external programmer could be needed (like for the
> eproms of etherboot) but most people could have access to such a device.

You can program a Flash Rom chip on your motherboard - no external programmer
needed - that's how you upgrade the BIOS even if you're not doing anything
with LinuxBIOS.

Antony.

--

If you want to be happy for an hour, get drunk.
If you want to be happy for a year, get married.
If you want to be happy for a lifetime, get a garden.


From alesan at manoweb.com  Wed Jan  8 17:33:01 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Wed Jan  8 17:33:01 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there>
References: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there>
Message-ID: <3E1CAA4C.9020806@manoweb.com>

Antony Stone wrote:

> In the UK they cost about GBP20 - so I guess that's about EUR30 / USD30 in
> the rest of the world...

Is there a web-seller or something?


> Because they do not have a large enough capacity.   Standard BIOS 
> chips are
> 2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.

256KB perhaps?

And how many mbits are those disc-on-chip?

> >I can think those chips provide particular features, but
> >which ones exactly?
>
>
> The main thing which DoC does which you can't do with standard Flash 
> Roms is
> to format them as a Silicon Disc, and put a file system into them.

So even if I have a flash big enough to store a complete kernel, I won't 
be able to use it with linuxbios? Only for diskless boxes perhaps? What 
if I do have an hard disk in the system?


> >Aren't common flash/eeprom chips much easier to find
> >and cheaper to buy?
>
>
> Yes, but they're too small.

I'm surprised, I though it was easy to find few megaBYTES flash chips 
nowadays. Isn't it possible to use my 8MB compact-flash card? ehhehe


> You can program a Flash Rom chip on your motherboard - no external 
> programmer
> needed - that's how you upgrade the BIOS even if you're not doing anything
> with LinuxBIOS.


yes, I know; however I thought that burning several megabits non 
standard flash chips could have required an external device or 
something. But it was only a supposition.


However, I must say the price of a DoC is quite high... very comparable 
to the cost of a pcchips motherboard, which I can find for as low as 
45EUR... 30 (plus shipping!) for the DoC is much...

There is no other possible solution about this? I will have an IDE hard 
disk in the system... perhaps it's possible to have a working LB without 
a DoC?


bye, thank you
as







From Antony at Soft-Solutions.co.uk  Wed Jan  8 18:43:00 2003
From: Antony at Soft-Solutions.co.uk (Antony Stone)
Date: Wed Jan  8 18:43:00 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <3E1CAA4C.9020806@manoweb.com>
References: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there> <3E1CAA4C.9020806@manoweb.com>
Message-ID: <20030108235417.MCAK5233.mta07-svc.ntlworld.com@there>

On Wednesday 08 January 2003 10:46 pm, Alessio Sangalli wrote:

> Antony Stone wrote:

> > Because they do not have a large enough capacity.   Standard BIOS
> > chips are
> > 2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.
>
> 256KB perhaps?

Sorry - yes, 256kbytes is correct.

> And how many mbits are those disc-on-chip?

The ones most people use (MD-2800-D08) are 8 megabytes.

> So even if I have a flash big enough to store a complete kernel, I won't
> be able to use it with linuxbios? Only for diskless boxes perhaps? What
> if I do have an hard disk in the system?

If you have a flash chip big enough fro a kernel I don't think it'll fit into 
the normal 32 pin socket used by 2 mbit BIOS chips.

However, if you can get a kernel into a chip, then you can certainly have 
your root fs on a hard drive or across a network.

> I'm surprised, I though it was easy to find few megaBYTES flash chips
> nowadays. Isn't it possible to use my 8MB compact-flash card? ehhehe

Yes, it is.   You can get IDE to compact flash adapters, and this will let 
you boot your machine from CF without needing LinuxBIOS.

> However, I must say the price of a DoC is quite high... very comparable
> to the cost of a pcchips motherboard, which I can find for as low as
> 45EUR... 30 (plus shipping!) for the DoC is much...

Please tell me where to get a PC-Chips motherboard for 45 Euro.   I like the 
sound of this.

> There is no other possible solution about this? I will have an IDE hard
> disk in the system... perhaps it's possible to have a working LB without
> a DoC?

You can get LinuxBIOS + etherboot into a 2 Mbit Flash chip if you can boot a 
kernel across the network.

Regards,

Antony.

-- 

Abandon hope, all ye who enter here.
You'll feel much better about things once you do.


From rminnich at lanl.gov  Wed Jan  8 19:40:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  8 19:40:00 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there>
Message-ID: <Pine.LNX.4.44.0301081750270.7468-100000@carotid.ccs.lanl.gov>

On Wed, 8 Jan 2003, Antony Stone wrote:

> Because they do not have a large enough capacity.   Standard BIOS chips are
> 2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.

no 2 megabits is 256 kbytes. Still not enough for a kernel. Plenty for 
etherboot however. 

> You can program a Flash Rom chip on your motherboard - no external programmer
> needed - that's how you upgrade the BIOS even if you're not doing anything
> with LinuxBIOS.

my flash programmer has been on a shelf for two years now.

ron



From rminnich at lanl.gov  Wed Jan  8 19:43:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  8 19:43:01 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <3E1CAA4C.9020806@manoweb.com>
Message-ID: <Pine.LNX.4.44.0301081754150.7468-100000@carotid.ccs.lanl.gov>

On Wed, 8 Jan 2003, Alessio Sangalli wrote:

> 
> Antony Stone wrote:
> 
> > In the UK they cost about GBP20 - so I guess that's about EUR30 / USD30 in
> > the rest of the world...
> 
> Is there a web-seller or something?

if you are a beginner and somewhat confused ... go to cwlinux.com and buy 
a pc chips 810 board which will come with DoC installed AND an SDK.

I have some of these and they work well.

ron



From spyro at f2s.com  Wed Jan  8 20:33:01 2003
From: spyro at f2s.com (Ian Molton)
Date: Wed Jan  8 20:33:01 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <Pine.LNX.4.44.0301081750270.7468-100000@carotid.ccs.lanl.gov>
References: <20030108215634.DGLP20174.mta06-svc.ntlworld.com@there>
	<Pine.LNX.4.44.0301081750270.7468-100000@carotid.ccs.lanl.gov>
Message-ID: <20030109014627.576c79e8.spyro@f2s.com>

On Wed, 8 Jan 2003 17:51:16 -0700 (MST)
"Ronald G. Minnich" <rminnich at lanl.gov> wrote:

> 
> no 2 megabits is 256 kbytes. Still not enough for a kernel. Plenty for
> 
> etherboot however. 

I bet its /possible/ to get a kernel into there...


From pyro at linuxlabs.com  Wed Jan  8 20:46:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Wed Jan  8 20:46:00 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <20030108235417.MCAK5233.mta07-svc.ntlworld.com@there>
Message-ID: <Pine.LNX.4.21.0301082047420.3346-100000@ucontrol.mobiledns.com>

Greetings,

For many mainboards, 256K is the limit due to not having all of the pins
connected. 512 is a harder limit imposed by the 32 available pins on the
flash chip. DoC gets around that by having page flipping built in (sort of
like EMM from back in the 8088 days).

Newer chipsets and motherboards get around the address line limit using
either LPC interface (a serialization of ISA into a much smaller pin
count), or firmware hub (more or less Intel's take on LPC).

It is quite possible to get LinuxBIOS and a loader such as Etherboot into
a conventional flash. From there the options for loading the kernel
include network, IDE drive, or CF. A little work will allow floppy or
CDROM.

G'day,
sjames

On Wed, 8 Jan 2003, Antony Stone wrote:

> On Wednesday 08 January 2003 10:46 pm, Alessio Sangalli wrote:
> 
> > Antony Stone wrote:
> 
> > > Because they do not have a large enough capacity.   Standard BIOS
> > > chips are
> > > 2megabits (= 32 kilobytes), which is not neough to hold a Linux kernel.
> >
> > 256KB perhaps?
> 
> Sorry - yes, 256kbytes is correct.
> 
> > And how many mbits are those disc-on-chip?
> 
> The ones most people use (MD-2800-D08) are 8 megabytes.
> 
> > So even if I have a flash big enough to store a complete kernel, I won't
> > be able to use it with linuxbios? Only for diskless boxes perhaps? What
> > if I do have an hard disk in the system?
> 
> If you have a flash chip big enough fro a kernel I don't think it'll fit into 
> the normal 32 pin socket used by 2 mbit BIOS chips.
> 
> However, if you can get a kernel into a chip, then you can certainly have 
> your root fs on a hard drive or across a network.
> 
> > I'm surprised, I though it was easy to find few megaBYTES flash chips
> > nowadays. Isn't it possible to use my 8MB compact-flash card? ehhehe
> 
> Yes, it is.   You can get IDE to compact flash adapters, and this will let 
> you boot your machine from CF without needing LinuxBIOS.
> 
> > However, I must say the price of a DoC is quite high... very comparable
> > to the cost of a pcchips motherboard, which I can find for as low as
> > 45EUR... 30 (plus shipping!) for the DoC is much...
> 
> Please tell me where to get a PC-Chips motherboard for 45 Euro.   I like the 
> sound of this.
> 
> > There is no other possible solution about this? I will have an IDE hard
> > disk in the system... perhaps it's possible to have a working LB without
> > a DoC?
> 
> You can get LinuxBIOS + etherboot into a 2 Mbit Flash chip if you can boot a 
> kernel across the network.
> 
> Regards,
> 
> Antony.
> 
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From rminnich at lanl.gov  Wed Jan  8 20:49:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan  8 20:49:00 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <20030109014627.576c79e8.spyro@f2s.com>
Message-ID: <Pine.LNX.4.44.0301081900280.7890-100000@carotid.ccs.lanl.gov>

On Thu, 9 Jan 2003, Ian Molton wrote:

> > no 2 megabits is 256 kbytes. Still not enough for a kernel. Plenty for
> > 
> > etherboot however. 
> 
> I bet its /possible/ to get a kernel into there...

I'll believe it when I see it, many have tried but all have failed :-)

ron



From aod at unisys.com.br  Thu Jan  9 00:58:00 2003
From: aod at unisys.com.br (Andre Dias)
Date: Thu Jan  9 00:58:00 2003
Subject: inicialization sequence for SIS 630 VGA graphics
Message-ID: <4.3.0.20030109040746.02c6f530@mail.unisys.com.br>

Does anyone knows the proper inicialization sequence for SIS 630 VGA 
graphics, so I can use it with linuxbios?
andre
http://usuarios.uninet.com.br/~aod
----------------------------------------------



From ollie at sis.com.tw  Thu Jan  9 01:40:01 2003
From: ollie at sis.com.tw (ollie lho)
Date: Thu Jan  9 01:40:01 2003
Subject: inicialization sequence for SIS 630 VGA graphics
In-Reply-To: <4.3.0.20030109040746.02c6f530@mail.unisys.com.br>
References: <4.3.0.20030109040746.02c6f530@mail.unisys.com.br>
Message-ID: <1042094921.1495.18.camel@ollie>

On Thu, 2003-01-09 at 15:09, Andre Dias wrote:
> Does anyone knows the proper inicialization sequence for SIS 630 VGA 
> graphics, so I can use it with linuxbios?
> andre
> http://usuarios.uninet.com.br/~aod

Did you tried the SiSFB Lite coming along with the SiS patch
in the src/kernel_patch directory.

The real init sequence is a little bit complicated and you generally 
need some NDA document to get the whole picture.
  
-- 
ollie lho <ollie at sis.com.tw>



From alesan at manoweb.com  Thu Jan  9 03:49:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Thu Jan  9 03:49:00 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <Pine.LNX.4.44.0301081754150.7468-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301081754150.7468-100000@carotid.ccs.lanl.gov>
Message-ID: <3E1D3AA4.7030109@manoweb.com>

Ronald G. Minnich wrote:

 > if you are a beginner and somewhat confused ... go to cwlinux.com and buy
 > a pc chips 810 board which will come with DoC installed AND an SDK.


ok, I see there is a kit:

Localdisk version features

      * 1 x LinuxBIOS compatiable mainboard (Intel/AMD based)
      * 1 x FlashRom with LinuxBIOS which is configured to boot from hda1
      * 1 x BIOS Savior for bios selection
      * Sample ELF kernel images

(the bios savior thing is cool eheh)

I think to understand that a DoC is not required if I have a local disk
in my system; I can put linuxbios and no other software on a normal
bios-like flash (2mbit should be enough) then load a kernel and operate
on a file system on my hard disk (which could even be a CF card,
inserted in the proper cd-to-ide adapter)...

The point is that I want linuxbios to powerup my living-room computer in
the shortest possible time: it is a satellite digital videorecorder (and
it has a big hard disk for this reason) which by now takes far too much
time to powerup (43seconds, many taken by the BIOS). How much time
should I expect for a 'local disk' init 1 linuxbios boot?

bye, thank you
as






From aip at cwlinux.com  Thu Jan  9 05:17:00 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Thu Jan  9 05:17:00 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <3E1D3AA4.7030109@manoweb.com>; from Alessio Sangalli on Thu, Jan 09, 2003 at 10:02:28AM +0100
References: <Pine.LNX.4.44.0301081754150.7468-100000@carotid.ccs.lanl.gov> <3E1D3AA4.7030109@manoweb.com>
Message-ID: <20030109182838.A19182@mail.cwlinux.com>

> The point is that I want linuxbios to powerup my living-room computer in
> the shortest possible time: it is a satellite digital videorecorder (and
> it has a big hard disk for this reason) which by now takes far too much
> time to powerup (43seconds, many taken by the BIOS). How much time
> should I expect for a 'local disk' init 1 linuxbios boot?
It takes about 1 sec from power up to loading kernel from localdisk.  With CF 
card, you don't even worry about harddisk spin-up.  To speed up everything, you
can even remove ide driver which takes about couple sec to load, from the 
kernel.  Then, mount your rootfs as ramdisk.  It can be done by mkelfImage.
However, you can't modify any data with this config.  I guess it is ok for vdr.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030109/be6d2937/attachment.sig>

From rminnich at lanl.gov  Thu Jan  9 10:02:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan  9 10:02:01 2003
Subject: Intel A, B, etc. nomenclature (fwd)
Message-ID: <Pine.LNX.4.44.0301090813220.12985-100000@carotid.ccs.lanl.gov>

interesting  note on intel speeds that I never noticed.

ron

---------- Forwarded message ----------
Date: Thu, 09 Jan 2003 08:45:26 -0500
From: JOHN DEGOOD <jdegood at sarnoff.com>
To: rminnich at lanl.gov
Subject: Intel A, B, etc. nomenclature

When Intel does a die turn the speed range of the new processor sometimes
overlaps with the earlier die, so to distinguish the chips they use "2.0 GHz",
"2.0A GHz", "2.0B GHz", etc.  The functionality often is significantly
different, e.g. the P4 "1.8 GHz" has 256K cache, while the P4 "1.8A GHz" has
512K cache, so the "1.8A" benchmarks much better.

John




From rsmith at bitworks.com  Thu Jan  9 11:36:00 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Thu Jan  9 11:36:00 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <20030108235417.MCAK5233.mta07-svc.ntlworld.com@there>
Message-ID: <MDAEMON-F200301091043.AA433437MD46483@bitworks.com>

On Wed, 8 Jan 2003 23:54:14 +0000, Antony Stone wrote:

> 
> If you have a flash chip big enough fro a kernel I don't think it'll fit into 
> the normal 32 pin socket used by 2 mbit BIOS chips.
> 

A 29F040b is a 4 m-bit (512k) part and is a std jdec 32 pin pacakge. 
I have managed to get a bios (commercial) + kernel in that.  No root
disk though.  Had to use a 2nd chip for that. (It was a custom board)

The real issue is for commercial MBs is if they brought all the
address lines out to the chip.


--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   




From rsmith at bitworks.com  Thu Jan  9 11:43:00 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Thu Jan  9 11:43:00 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <Pine.LNX.4.44.0301081252300.5337-100000@carotid.ccs.lanl.gov>
Message-ID: <MDAEMON-F200301091051.AA510685MD46494@bitworks.com>

On Wed, 8 Jan 2003 13:00:46 -0700 (MST), Ronald G. Minnich wrote:

> On 8 Jan 2003, Jeremy Jackson wrote:
> 
> > How LinuxBIOS friendly are the e7500/Xeons for LinuxBIOS?  Any NDA
> > issues like AMD MSRs or similar?
> 
> no nda issues whatsoever. Intel has been extremely helpful on this 
> chipset. In fact there was a glitch a few months ago and Intel did what 
> needed to be done to get it fixed.
> 

Wow. thats quite a different story that what I got.  Intel is so
inconsistent sometimes.  I tried to get the register documentation
for the 440MX (note MX not BX which I already have) and not only do
you have to be under the standard NDA you have to go get a under an
extra double-dog-secret NDA which my Intel rep said "is quite
difficult to get"  So we bailed on the 440MX and are going to respin
our BX version.

Any possibility you could put me in touch with your Intel contact? 
Perhaps he could shed some light on why the 440MX is so shrouded.

--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   




From Antony at Soft-Solutions.co.uk  Thu Jan  9 12:02:00 2003
From: Antony at Soft-Solutions.co.uk (Antony Stone)
Date: Thu Jan  9 12:02:00 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <MDAEMON-F200301091043.AA433437MD46483@bitworks.com>
References: <MDAEMON-F200301091043.AA433437MD46483@bitworks.com>
Message-ID: <200301091713.h09HDZA19839@vulcan.rissington.net>

On Thursday 09 January 2003 4:43 pm, Richard A. Smith wrote:

> On Wed, 8 Jan 2003 23:54:14 +0000, Antony Stone wrote:
> > If you have a flash chip big enough fro a kernel I don't think it'll fit
> > into the normal 32 pin socket used by 2 mbit BIOS chips.
>
> A 29F040b is a 4 m-bit (512k) part and is a std jdec 32 pin pacakge.
> I have managed to get a bios (commercial) + kernel in that.  No root
> disk though.  Had to use a 2nd chip for that. (It was a custom board)

How did you get a kernel into <512kbytes?   What version did you start from?

Antony.

-- 

Anyone that's normal doesn't really achieve much.

 - Mark Blair, Australian rocket engineer


From jerj at coplanar.net  Thu Jan  9 16:21:01 2003
From: jerj at coplanar.net (Jeremy Jackson)
Date: Thu Jan  9 16:21:01 2003
Subject: WANTED: LinuxBIOS capable rack mount servers
Message-ID: <1042147955.1523.13.camel@contact.kennet.coplanar.net>

Where can I buy 6 rackmount servers 1GHz+ with LinuxBIOS potential?
They are for production website, so must be *stable*, if none available
with LinuxBIOS then it's back to the old (BIOS) grind.  It's just that I
have the opportunity to build this from scratch, and I'd like to go
LinuxBIOS if possible.

2 need 3 ethernet + DOC roof fs + no disk - router/apache load bal
2 need 2 ethernet + load kernel over net and do NFS root ) webservers
2 need at least 2 disks hotswap SCSI (small database)

It would be wonderful to have all 6 the same chassis/motherboard, with
the difference being cards/disk plugged in.  Also nice would be ability
to fall back to vendor bios in case of trouble in testing phase.

Delivery must be in 2 weeks at most.

Thanks,

Jeremy



From alesan at manoweb.com  Thu Jan  9 19:14:01 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Thu Jan  9 19:14:01 2003
Subject: linuxbios binaries
Message-ID: <3E1E1388.7090109@manoweb.com>

Hi, I was wondering if there were avaiable prepackaged binaries for 
Linuxbios ROMs. I don't want rpm of course (!) but I think that a 
linuxbios image configured to boot from hda(1?) for a specific 
motherboard (the pcchips one seems to be quite popular) may be very 
useful; perhaps there are many configuration parameters, but I guess 
resoanable defaults can be set and one would recompile everything only 
if specific customizations are needed.


bye, thank you
as






From ebiederman at lnxi.com  Fri Jan 10 00:05:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:05:00 2003
Subject: Boot from etherboot - blocked by INT 10
In-Reply-To: <441383BA85E81D48964152E537886C9D23029F@mail.sh.corp.tyan.com>
References: <441383BA85E81D48964152E537886C9D23029F@mail.sh.corp.tyan.com>
Message-ID: <m3r8bla87n.fsf@lnxi.com>

"Lawrence LL. Dai" <lawrence at tyanchina.com> writes:

> Hi,
> 
> When I try Linux bios to boot from Ethernet, I find it will be blocked by an
> instruction of INT 10.
> 
> The kernel downloaded from TFTP server has the INT 10 instruction, while INT 10
> has not been realized in Linux bios.
> 
> So it is stopped. How can I resolve the problem?

You need to use mkelfImage instead of mknbi...

Eric



From ebiederman at lnxi.com  Fri Jan 10 00:13:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:13:00 2003
Subject: about E7501
In-Reply-To: <441383BA85E81D48964152E537886C9D23029D@mail.sh.corp.tyan.com>
References: <441383BA85E81D48964152E537886C9D23029D@mail.sh.corp.tyan.com>
Message-ID: <m3n0m9a84x.fsf@lnxi.com>

"Terry B. Chen" <terryc at tyanchina.com> writes:

> Is anyone interested in E7501? 
> What is the difference between FSB 533 and 400 in Northbridge? I have a thought
> to port E7501 to E7500.

Hey before you do that could you give me a copy of your E7501 port?
Sorry I could not resist.  I doubt the differences are especially large
but I have not gone through the documents and looked closely yet.

Eric



From ebiederman at lnxi.com  Fri Jan 10 00:20:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:20:01 2003
Subject: PCI-X Board or Chipset recommendataions
In-Reply-To: <1042052373.4765.16.camel@contact.kennet.coplanar.net>
References: <Pine.LNX.4.44.0301071659340.30286-100000@carotid.ccs.lanl.gov>
	<1042052373.4765.16.camel@contact.kennet.coplanar.net>
Message-ID: <m3hecha7hz.fsf@lnxi.com>

Jeremy Jackson <jerj at coplanar.net> writes:

> How LinuxBIOS friendly are the e7500/Xeons for LinuxBIOS?  Any NDA
> issues like AMD MSRs or similar?

There are no hang ups like what slowed the AMD port, and the AMD port
does not suffer from them any longer.

If you are doing serious work it does pay to go through the NDA
process with intel and get all of their documentation.  While there is
a large amount of overlap between their public and more restricted
documents the information in their private documents is easier to use,
and with an NDA you can earlier access to hardware bug reports.

> Also, I'm looking at the p4dpl-m, which has different bus layout than
> either of the p4dp's in cvs, and wondering how difficult to support.

I'm not familiar with that one.  Assuming it has the PCIH2 it should
just be a matter of tracking down the irq assignments.  Though I can
be surprised.

If you have any non-trivial changes to the bootstrap be careful.  On
the p4dpr I had to navigate my way through 3 pretty serious hardware
bugs.

Eric



From terryc at tyanchina.com  Fri Jan 10 00:29:00 2003
From: terryc at tyanchina.com (Terry B. Chen)
Date: Fri Jan 10 00:29:00 2003
Subject: about E7501
Message-ID: <441383BA85E81D48964152E537886C9D23043A@mail.sh.corp.tyan.com>

Sorry, I do not mean I have finished the porting, I just read the raminit.inc about E7500, now I am reading E7501 and E7500 Intel bios specification. I try to find the difference between two chipsets. But I am raw in ram initialization. The part is so complex. I want to get help from you.


Best Regards
Terry Chen
 

-----Original Message-----
From: Eric W. Biederman [mailto:ebiederman at lnxi.com] 
Sent: Friday, January 10, 2003 1:26 PM
To: Terry B. Chen
Cc: linuxbios at clustermatic.org
Subject: Re: about E7501

"Terry B. Chen" <terryc at tyanchina.com> writes:

> Is anyone interested in E7501? 
> What is the difference between FSB 533 and 400 in Northbridge? I have a thought
> to port E7501 to E7500.

Hey before you do that could you give me a copy of your E7501 port?
Sorry I could not resist.  I doubt the differences are especially large
but I have not gone through the documents and looked closely yet.

Eric



From ebiederman at lnxi.com  Fri Jan 10 00:35:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:35:01 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <Pine.LNX.4.21.0301082047420.3346-100000@ucontrol.mobiledns.com>
References: <Pine.LNX.4.21.0301082047420.3346-100000@ucontrol.mobiledns.com>
Message-ID: <m3adi9a6z8.fsf@lnxi.com>

steven james <pyro at linuxlabs.com> writes:

> Greetings,
> 
> For many mainboards, 256K is the limit due to not having all of the pins
> connected. 512 is a harder limit imposed by the 32 available pins on the
> flash chip. DoC gets around that by having page flipping built in (sort of
> like EMM from back in the 8088 days).
> 
> Newer chipsets and motherboards get around the address line limit using
> either LPC interface (a serialization of ISA into a much smaller pin
> count), or firmware hub (more or less Intel's take on LPC).

Currently in the LPC/firmware hub form factor I have seen chips as large
as 8mbit == 1MByte.  And theoretical limit is something like 4GB.  So
as larger flash chips become available we can use them.
 
> It is quite possible to get LinuxBIOS and a loader such as Etherboot into
> a conventional flash. From there the options for loading the kernel
> include network, IDE drive, or CF. A little work will allow floppy or
> CDROM.

Actually there is already a floppy driver in etherboot, though it
could probably use some stabilizing.  Only a CDROM drive requires some
real work.

Eric



From ebiederman at lnxi.com  Fri Jan 10 00:41:03 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:41:03 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <200301091713.h09HDZA19839@vulcan.rissington.net>
References: <MDAEMON-F200301091043.AA433437MD46483@bitworks.com>
	<200301091713.h09HDZA19839@vulcan.rissington.net>
Message-ID: <m365sxa6xr.fsf@lnxi.com>

Antony Stone <Antony at Soft-Solutions.co.uk> writes:

> On Thursday 09 January 2003 4:43 pm, Richard A. Smith wrote:
> 
> > On Wed, 8 Jan 2003 23:54:14 +0000, Antony Stone wrote:
> > > If you have a flash chip big enough fro a kernel I don't think it'll fit
> > > into the normal 32 pin socket used by 2 mbit BIOS chips.
> >
> > A 29F040b is a 4 m-bit (512k) part and is a std jdec 32 pin pacakge.
> > I have managed to get a bios (commercial) + kernel in that.  No root
> > disk though.  Had to use a 2nd chip for that. (It was a custom board)
> 
> How did you get a kernel into <512kbytes?   What version did you start from?

It is not to terribly hard to get a minimal 2.4.x kernel into 360KB or so.

Eric



From ebiederman at lnxi.com  Fri Jan 10 00:48:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 00:48:01 2003
Subject: about E7501
In-Reply-To: <441383BA85E81D48964152E537886C9D23043A@mail.sh.corp.tyan.com>
References: <441383BA85E81D48964152E537886C9D23043A@mail.sh.corp.tyan.com>
Message-ID: <m3adi97dez.fsf@lnxi.com>

"Terry B. Chen" <terryc at tyanchina.com> writes:

> Sorry, I do not mean I have finished the porting, I just read the raminit.inc
> about E7500, now I am reading E7501 and E7500 Intel bios specification. I try to
> find the difference between two chipsets. But I am raw in ram
> initialization. The part is so complex. I want to get help from you.

You missed the smiley :)

So you don't get daunted actual ram initialization is not particularly hard. 

The hard parts are:
- The code must be in assembly
- computing the timing parameters from SPD EEPROMs on the DIMMs.
- handling arbitrary DIMMs

My hunch is there will not need to be too many changes except in the places
the DIMMs give their timing information in nanoseconds, and the chipset wants
that information in clock cycles.

Eric



From rminnich at lanl.gov  Fri Jan 10 00:56:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 00:56:01 2003
Subject: WANTED: LinuxBIOS capable rack mount servers
In-Reply-To: <1042147955.1523.13.camel@contact.kennet.coplanar.net>
Message-ID: <Pine.LNX.4.44.0301092305080.18552-100000@carotid.ccs.lanl.gov>

On 9 Jan 2003, Jeremy Jackson wrote:

> Where can I buy 6 rackmount servers 1GHz+ with LinuxBIOS potential?

linuxlabs.com, lnxi.com sell such nodes with linuxbios installed. 

promicro is making an effort to be linuxbios capable but I don't know if 
they are there yet. 

ron



From ebiederman at lnxi.com  Fri Jan 10 02:19:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 10 02:19:01 2003
Subject: Boot from etherboot - blocked by INT 10
In-Reply-To: <441383BA85E81D48964152E537886C9D23044C@mail.sh.corp.tyan.com>
References: <441383BA85E81D48964152E537886C9D23044C@mail.sh.corp.tyan.com>
Message-ID: <m3adi94fq7.fsf@lnxi.com>

"Lawrence LL. Dai" <lawrence at tyanchina.com> writes:

> Hi, Eric 
> 
> 	I suppose that mknbi and mkelf would also cause this problem.Because
> they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux
> needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but
> vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?)

The difference is mknbi/mkelf that come standard with etherboot when
the process the linux kernel start the kernel in 16bit mode and run
it's BIOS code,  mkelfImage  simulates the effect of the 16bit BIOS
code by reading LinuxBIOS tables or making the needed BIOS calls
itself, and then it enters Linux at it's unofficial 32bit entry
point. 

mkelfImage can take either a bzImage or a vmlinux.

Eric



From lawrence at tyanchina.com  Fri Jan 10 02:25:00 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Fri Jan 10 02:25:00 2003
Subject: Boot from etherboot - blocked by INT 10
Message-ID: <441383BA85E81D48964152E537886C9D230465@mail.sh.corp.tyan.com>

Thanks a lot! I will try it! :)
Lawrence

-----Original Message-----
From: Eric W. Biederman [mailto:ebiederman at lnxi.com] 
Sent: 2003?1?10? 15:38
To: LinuxBIOS
Cc: Lawrence LL. Dai
Subject: Re: Boot from etherboot - blocked by INT 10

"Lawrence LL. Dai" <lawrence at tyanchina.com> writes:

> Hi, Eric 
> 
> 	I suppose that mknbi and mkelf would also cause this problem.Because
> they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux
> needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but
> vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?)

The difference is mknbi/mkelf that come standard with etherboot when
the process the linux kernel start the kernel in 16bit mode and run
it's BIOS code,  mkelfImage  simulates the effect of the 16bit BIOS
code by reading LinuxBIOS tables or making the needed BIOS calls
itself, and then it enters Linux at it's unofficial 32bit entry
point. 

mkelfImage can take either a bzImage or a vmlinux.

Eric



From sxpert at esitcom.org  Fri Jan 10 08:48:00 2003
From: sxpert at esitcom.org (Amaury Jacquot)
Date: Fri Jan 10 08:48:00 2003
Subject: current status of the Via EPIA
Message-ID: <1042207226.29015.3.camel@fali>

Hi,
I own a via EPIA mobo that I use for GPS/music playing in my car.
It currently takes about 50 seconds to boot into my program
http://sxpert.esitcom.org/projects/navsys/
I am wondering if linux bios would help me in accelerating the boot time
Sincerely

Amaury



From tulonja at koti.soon.fi  Fri Jan 10 08:57:01 2003
From: tulonja at koti.soon.fi (Jarmo Tulonen)
Date: Fri Jan 10 08:57:01 2003
Subject: AMD 760MPX
Message-ID: <200301101411.h0AEBjA20436@smtp2.sooninternet.net>

Hi,

What is the present status of LinuxBIOS for this chip set ?
I think someone was working on it.
We should make an implementation for Tyan Tiger MPX (S2466),
so we are interested in what already exists (especially for the
southbridge). And also if there is something we can help with.

Regards

Jarmo


From aip at cwlinux.com  Fri Jan 10 09:09:00 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Fri Jan 10 09:09:00 2003
Subject: linuxbios binaries
In-Reply-To: <3E1E1388.7090109@manoweb.com>; from Alessio Sangalli on Fri, Jan 10, 2003 at 01:27:52AM +0100
References: <3E1E1388.7090109@manoweb.com>
Message-ID: <20030110222044.A4536@mail.cwlinux.com>

Alessio,

> Hi, I was wondering if there were avaiable prepackaged binaries for 
> Linuxbios ROMs. I don't want rpm of course (!) but I think that a 
> linuxbios image configured to boot from hda(1?) for a specific 
> motherboard (the pcchips one seems to be quite popular) may be very 
> useful; perhaps there are many configuration parameters, but I guess 
> resoanable defaults can be set and one would recompile everything only 
> if specific customizations are needed.
Here are some sample images.  See README for details.
ftp.cwlinux.com:/pub/downloads/linuxbios-sdk/images/romimages/

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030110/4abb4130/attachment.sig>

From aip at cwlinux.com  Fri Jan 10 09:11:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Fri Jan 10 09:11:01 2003
Subject: current status of the Via EPIA
In-Reply-To: <1042207226.29015.3.camel@fali>; from Amaury Jacquot on Fri, Jan 10, 2003 at 03:00:26PM +0100
References: <1042207226.29015.3.camel@fali>
Message-ID: <20030110222316.B4536@mail.cwlinux.com>

Amaury,

> I own a via EPIA mobo that I use for GPS/music playing in my car.
> It currently takes about 50 seconds to boot into my program
> http://sxpert.esitcom.org/projects/navsys/
> I am wondering if linux bios would help me in accelerating the boot time
It takes about 1 sec to get to kernel loading.  Also, IRQ is fixed fixed.  If 
you don't need vga support, LinuxBIOS is a very good alternative.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030110/400ed222/attachment.sig>

From rminnich at lanl.gov  Fri Jan 10 09:32:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 09:32:01 2003
Subject: current status of the Via EPIA
In-Reply-To: <1042207226.29015.3.camel@fali>
Message-ID: <Pine.LNX.4.44.0301100743310.21789-100000@carotid.ccs.lanl.gov>

On 10 Jan 2003, Amaury Jacquot wrote:

> I own a via EPIA mobo that I use for GPS/music playing in my car. It
> currently takes about 50 seconds to boot into my program
> http://sxpert.esitcom.org/projects/navsys/ I am wondering if linux bios
> would help me in accelerating the boot time Sincerely

sure. I think cwlinux.com may soon be distributing linuxbios for these. 
But they do boot fast with linuxbios.

ron



From sxpert at esitcom.org  Fri Jan 10 11:22:00 2003
From: sxpert at esitcom.org (Amaury Jacquot)
Date: Fri Jan 10 11:22:00 2003
Subject: Via EPIA frame buffer stuff
Message-ID: <1042216475.29015.9.camel@fali>

dunno if this would be useful in any way, but there is some available
code here

http://epiafb.sourceforge.net/

Sincerely
Amaury



From rsmith at bitworks.com  Fri Jan 10 12:11:01 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Fri Jan 10 12:11:01 2003
Subject: are there problems with this email? - what is a disc on chip? - beginner's question
In-Reply-To: <200301091713.h09HDZA19839@vulcan.rissington.net>
Message-ID: <MDAEMON-F200301101121.AA213516MD47824@bitworks.com>

On Thu, 9 Jan 2003 17:13:27 +0000, Antony Stone wrote:

> On Thursday 09 January 2003 4:43 pm, Richard A. Smith wrote:
> 
> > On Wed, 8 Jan 2003 23:54:14 +0000, Antony Stone wrote:
> > > If you have a flash chip big enough fro a kernel I don't think it'll fit
> > > into the normal 32 pin socket used by 2 mbit BIOS chips.
> >
> > A 29F040b is a 4 m-bit (512k) part and is a std jdec 32 pin pacakge.
> > I have managed to get a bios (commercial) + kernel in that.  No root
> > disk though.  Had to use a 2nd chip for that. (It was a custom board)
> 
> How did you get a kernel into <512kbytes?   What version did you start from?
> 

2.4.2.  You just have to turn off everything but the essentials. 
Works out to 480k or so.

--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   






From slava at microway.com  Fri Jan 10 12:28:01 2003
From: slava at microway.com (Yaroslav Klyukin)
Date: Fri Jan 10 12:28:01 2003
Subject: Intel Clearwater motherboard.
Message-ID: <844AF1C6-24C2-11D7-813E-000393A810CE@microway.com>

Hello everybody!
I have just subscribed to this mailing list.
I am new to linuxbios and this project seems to have good prospectives.

I have just built romimage for Intel Clearwater motherboard and tried to
flash it into the bios, but  Intel flash utility (phlash) refused to do 
that.
I failed to find any procedure or documentation for this motherboard on 
how to make this motherboard work with linuxbios.
All i have right now is sources, which i have been examining during the 
past several days. They seem to compile ok, so i want to flash at this 
point.
I know that common practice is to use disk on chip, but this motherboard 
has zif flash socket instead of dip one.

Please, tell me how to flash romimage into flash.

Thank you in advance.

Yaroslav Klyukin, Linux Systems Administrator - slava at microway.com
Microway Inc., High Performance Computing - http://www.microway.com/



From rminnich at lanl.gov  Fri Jan 10 13:18:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 13:18:01 2003
Subject: are there problems with this email? - what is a disc on chip?
 - beginner's question
In-Reply-To: <MDAEMON-F200301101121.AA213516MD47824@bitworks.com>
Message-ID: <Pine.LNX.4.44.0301101130220.23236-100000@carotid.ccs.lanl.gov>

On Thu, 9 Jan 2003, Richard A. Smith wrote:

> 2.4.2.  You just have to turn off everything but the essentials. 
> Works out to 480k or so.

I'd like to see that on 2.4.19 ...

ron



From pyro at linuxlabs.com  Fri Jan 10 14:20:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Fri Jan 10 14:20:01 2003
Subject: Intel Clearwater motherboard.
In-Reply-To: <844AF1C6-24C2-11D7-813E-000393A810CE@microway.com>
Message-ID: <Pine.LNX.4.21.0301101430480.5488-100000@ucontrol.mobiledns.com>

Greetings,

I am working on a versatile flash tool for this board. For now, the util
in util/flash_and_burn can do it.

G'day,
sjames


On Fri, 10 Jan 2003, Yaroslav Klyukin wrote:

> Hello everybody!
> I have just subscribed to this mailing list.
> I am new to linuxbios and this project seems to have good prospectives.
> 
> I have just built romimage for Intel Clearwater motherboard and tried to
> flash it into the bios, but  Intel flash utility (phlash) refused to do 
> that.
> I failed to find any procedure or documentation for this motherboard on 
> how to make this motherboard work with linuxbios.
> All i have right now is sources, which i have been examining during the 
> past several days. They seem to compile ok, so i want to flash at this 
> point.
> I know that common practice is to use disk on chip, but this motherboard 
> has zif flash socket instead of dip one.
> 
> Please, tell me how to flash romimage into flash.
> 
> Thank you in advance.
> 
> Yaroslav Klyukin, Linux Systems Administrator - slava at microway.com
> Microway Inc., High Performance Computing - http://www.microway.com/
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From slava at microway.com  Fri Jan 10 14:55:00 2003
From: slava at microway.com (Yaroslav Klyukin)
Date: Fri Jan 10 14:55:00 2003
Subject: Intel Clearwater motherboard.
In-Reply-To: <Pine.LNX.4.21.0301101430480.5488-100000@ucontrol.mobiledns.com>
Message-ID: <18326E68-24D7-11D7-813E-000393A810CE@microway.com>

On Friday, January 10, 2003, at 02:32  PM, steven james wrote:


Thank you for response.

I have tried it already, but it said "EEPROM not found"
Eeprom type is: Intel N82802AC8 A2210847 (c)'96'98
It is 8Mbit flash.

Is there any other way to do it?
>
> I am working on a versatile flash tool for this board. For now, the util
> in util/flash_and_burn can do it.



From rminnich at lanl.gov  Fri Jan 10 15:09:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 15:09:01 2003
Subject: Intel Clearwater motherboard.
In-Reply-To: <18326E68-24D7-11D7-813E-000393A810CE@microway.com>
Message-ID: <Pine.LNX.4.44.0301101320320.23660-100000@carotid.ccs.lanl.gov>

On Fri, 10 Jan 2003, Yaroslav Klyukin wrote:

> I have tried it already, but it said "EEPROM not found"
> Eeprom type is: Intel N82802AC8 A2210847 (c)'96'98
> It is 8Mbit flash.
> 
> Is there any other way to do it?

we'll need to upgrade the flash tool for this part. I don't have one 
however, so you're going to have to tell me that parts that matter.

ron



From slava at microway.com  Fri Jan 10 15:42:00 2003
From: slava at microway.com (Yaroslav Klyukin)
Date: Fri Jan 10 15:42:00 2003
Subject: Intel Clearwater motherboard.
In-Reply-To: <Pine.LNX.4.44.0301101320320.23660-100000@carotid.ccs.lanl.gov>
Message-ID: <A0BB8AC6-24DD-11D7-813E-000393A810CE@microway.com>

On Friday, January 10, 2003, at 03:20  PM, Ronald G. Minnich wrote:

>> I have tried it already, but it said "EEPROM not found"
>> Eeprom type is: Intel N82802AC8 A2210847 (c)'96'98
>> It is 8Mbit flash.
>>
>> Is there any other way to do it?
>
> we'll need to upgrade the flash tool for this part. I don't have one
> however, so you're going to have to tell me that parts that matter.

Sorry, i have not quite understood. Do you want me to provide some 
information about this flash part to you?
The only information i have is what is written on it...
If any other information is needed i will be glad to help.

>
Yaroslav Klyukin, Linux Systems Administrator - slava at microway.com
Microway Inc., High Performance Computing - http://www.microway.com/



From nathanael at gnat.ca  Fri Jan 10 15:46:01 2003
From: nathanael at gnat.ca (Nathanael Noblet)
Date: Fri Jan 10 15:46:01 2003
Subject: VIA EPIA questions
Message-ID: <32426D15-24DE-11D7-BE8A-0003931B4D6A@gnat.ca>

So I've been following the developments of this board a little. If I'm 
not mistaken, the board now works right?
If that is the case then I only have a few questions. I have a project 
where it would be nice to not have to get LinuxBIOS working on our own 
boards (which we are in the process of doing). Though we need a flash 
root directory, I guess I can have a CF in an IDE connector but was 
hoping that with this board it was possible to use a DoC type solution. 
Is it?

-- 
Nathanael Noblet
Gnat Solutions
4604 Monterey Ave NW
Calgary, AB
T3B 5K4

T/F 403.288.5360
C 403.809.5368

http://www.gnat.ca/



From vincent at ulyssis.org  Fri Jan 10 16:14:01 2003
From: vincent at ulyssis.org (Vincent Touquet)
Date: Fri Jan 10 16:14:01 2003
Subject: buying linuxbios boards
Message-ID: <20030110212541.GG11619@lea.ulyssis.org>

I found some on cwlinux.com, any others ?

regards,
Vincent


From rminnich at lanl.gov  Fri Jan 10 16:55:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 16:55:01 2003
Subject: VIA EPIA questions
In-Reply-To: <32426D15-24DE-11D7-BE8A-0003931B4D6A@gnat.ca>
Message-ID: <Pine.LNX.4.44.0301101506220.23660-100000@carotid.ccs.lanl.gov>

On Fri, 10 Jan 2003, Nathanael Noblet wrote:

> So I've been following the developments of this board a little. If I'm 
> not mistaken, the board now works right?

yes. 

> If that is the case then I only have a few questions. I have a project 
> where it would be nice to not have to get LinuxBIOS working on our own 
> boards (which we are in the process of doing). Though we need a flash 
> root directory, I guess I can have a CF in an IDE connector but was 
> hoping that with this board it was possible to use a DoC type solution. 

no support on this board for DoC, it seems.

ron



From P.Lister at sychron.com  Fri Jan 10 17:05:01 2003
From: P.Lister at sychron.com (Peter Lister)
Date: Fri Jan 10 17:05:01 2003
Subject: Booting from floppy 
In-Reply-To: Your message of "09 Dec 2002 00:20:31 MST."
             <m3d6obslog.fsf@lnxi.com> 
Message-ID: <E18LhyD-0006qn-00@big-guy.sychron.com>

> > It's Ron's privilege to name the project as he sees fit, but when
> > people first see "LinuxBIOS", misinterpretation does seem to be
> > common. "LinuxBIOS" does *not* mean "a BIOS for Linux" - for one
> > thing, Linux does needs no BIOS. 
> 
> Bogus.
> Linux needs a BIOS, to initialize the platform. Which we have shown 
> the hard way.  Linux simply needs not any help after it gets
> except on poorly designed ports.

Umm... OK - definition problem, I think. Everything needs firmware for
hardware initialisation, maybe other housekeeping and booting the main
OS: after that the main OS takes over. But that firmware isn't a "BIOS"
- aka Basic Input Output System, which is what DOS originally need to
run at all, and MS OSes need at least to boot.  A BIOS, as I have always
understood it (and how any halfway knowledgeable people I speak to have
treated it), is precisely that firmware needed even after the main OS
has taken over, but BIOS has come to mean "all firmware" in many
people's minds.

Sun's have firmware - but it is not referred to as a "BIOS" (except, as
mentioned, insofar as the acronym is used as shorthand for firmware). So
I think it reasonable to say "Linux needs no BIOS" - most OSs don't, but
the ones which have evolved on Intel didn't have much alternative. I
understand that even the MS OSes are becoming more self sufficient.

The main feature of the LinuxBIOS code base is really hardware
initialisation: everything else has been about extending the features of
Linux (or Etherboot, Bochs). And that's as it should be.




From robn at verdi.et.tudelft.nl  Fri Jan 10 17:05:58 2003
From: robn at verdi.et.tudelft.nl (Rob van Nieuwkerk)
Date: Fri Jan 10 17:05:58 2003
Subject: Geode sc2200 vga 
In-Reply-To: Your message of "Thu, 12 Dec 2002 10:01:42 PST."
             <BPEDILBPDCBCGKGGANJLIEEEECAA.steve@nexpath.com> 
Message-ID: <200212121812.gBCICuZ05937@verdi.et.tudelft.nl>

> > I have successfully built LinuxBIOS to load a kernel from my IDE drive
> > and boot using a serial console.  Now I would like to test the VGA
> > funtionality of my board.  Has anyone had any experience getting the VGA
> > to turn on and work within LinuxBIOS and/or Linux?
> > John
> 
> From my previos posts of the last few days:
> 
> --------------------
> I have the code to set the legacy registers to start VGA for a vga console,
> integrated into linuxbios, working on two different integrated chips, the
> stpc cpu/chipset, and the sis 630 chipset.  It sets the registers for
> 640x400 std text vga, and also 640x480x4 graphics.  I was working on the
> display of a .pcx graphics file when I had to get onto something else, but
> it was all working the last time I tried it.
> 
> The only reason this hasn't been integrated into linuxbios codebase at this
> point is partly lack of interest (I think) in this group, since most use the
> serial console, and partly that I have been off on other things lately.

Hi Steve,

Well, just to let you know: I'm *VERY* intersted in having VGA on my Geode
GX1 boards (the sc2200 is, as I understand it, compatible with the GX1) !
:-)

I haven't used linuxbios yet, but somewhere in the next weeks I'll
start experimenting with it.

	greetings,
	Rob van Nieuwkerk


From gnat at gnat.ca  Fri Jan 10 17:07:01 2003
From: gnat at gnat.ca (gnat at gnat.ca)
Date: Fri Jan 10 17:07:01 2003
Subject: missing _estack
Message-ID: <1040697958.3e07ca66d3717@www.gnat.ca>

Hello,
I've been trying to figure out how these things are setup. If I use one of the 
sis5xx mainboard configs, I get an error stating that _estack is undefined. 
Where is it supposed to be? Obviously, it has something to do with setting up a 
stack. I just don't understand where it is supposed to come from. Since I'm 
patterning my mainboard (sis530 based) on those as examples. This causes a 
small problem. Can anyone help me?


-- 
Nathanael Noblet



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


From jatorvin at ees2.oulu.fi  Fri Jan 10 17:08:00 2003
From: jatorvin at ees2.oulu.fi (Jarmo Torvinen)
Date: Fri Jan 10 17:08:00 2003
Subject: via epia 800
Message-ID: <Pine.SOL.4.44.0212281459570.28984-100000@stekt55>

Hi all,

I'm building a (multimedia) set-top-box using Via epia 800-mainboard.
The system works fine with linux except the bios boot-delay is too long.

I was hoping if someone could point me to a simple documentation howto
setup linuxbios for this board for reduced boot time?

I have downloaded the rom-image from
http://www.cwlinux.com/downloads/linuxbios-sdk/images/romimages/epia.rom

but I'm still wondering if it is good for booting from hda1? Does the
kernel installed in hda1 have to be the cwlinux-patched version or may I
use my own vanilla-kernel?


I think there will be lot of questions regarding this matter in the future
because of the numerous people building around this mobo, so maybe someone
who got it working could write a simple HowTo or FAQ of this "issue".


Jarmo Torvinen




From bms at spc.org  Fri Jan 10 17:09:01 2003
From: bms at spc.org (Bruce M Simpson)
Date: Fri Jan 10 17:09:01 2003
Subject: FreeBSD/LinuxBIOS coupling document
In-Reply-To: <3E0FE5D0.A77F56B6@mindspring.com>
References: <3E0FE5D0.A77F56B6@mindspring.com>
Message-ID: <20030102100223.GR16068@spc.org>

Terry,

If you could get a chance to review the document below or pass it on to
the appropriate party that would be great. (I believe you were the one who
asked for it originally?)

> > I have done this work. The results can be seen at:
> > 
> > http://www.incunabulum.com/code/projects/freebsd/freebsd-bios-interaction.txt
> > 
> > I have also rewritten boot0.s to use the BIOS COM Port Services (INT 14h):
> > 
> > http://www.incunabulum.com/code/projects/freebsd/boot0sio.s
> > 

BMS


From rminnich at lanl.gov  Fri Jan 10 17:26:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 10 17:26:01 2003
Subject: Booting from floppy 
In-Reply-To: <E18LhyD-0006qn-00@big-guy.sychron.com>
Message-ID: <Pine.LNX.4.44.0301101531180.23660-100000@carotid.ccs.lanl.gov>

On Tue, 10 Dec 2002, Peter Lister wrote:

> Umm... OK - definition problem, I think. Everything needs firmware for
> hardware initialisation, maybe other housekeeping and booting the main
> OS: after that the main OS takes over. But that firmware isn't a "BIOS"
> - aka Basic Input Output System, which is what DOS originally need to
> run at all, and MS OSes need at least to boot.  A BIOS, as I have always
> understood it (and how any halfway knowledgeable people I speak to have
> treated it), is precisely that firmware needed even after the main OS
> has taken over, but BIOS has come to mean "all firmware" in many
> people's minds.

Exactly correct. The idea of a BIOS goes back to CP/M, and back then an OS 
could not do I/O -- it asked the BIOS to do I/O. The BIOS also insulated 
the OS -- which only ran in a few K -- from the vagaries of all the 
hardware. 

[[ I am pretty sure the term BIOS was invented by Gary Kildall, although 
there is no question that systems were built that had a BIOS-like ROM]]

So LinuxBIOS is not a BIOS in the traditional sense. But most people
nowadays are not aware of this history and probably don't even care to
know it. For most PC users, the BIOS is the thing that turns on the
machine, sets up hardware, and starts the OS -- nothing more.

I call LinuxBIOS a BIOS because this distinction just isn't that important
any more.

ron



From pyro at linuxlabs.com  Fri Jan 10 18:17:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Fri Jan 10 18:17:00 2003
Subject: AMD 760MPX
In-Reply-To: <200301101411.h0AEBjA20436@smtp2.sooninternet.net>
Message-ID: <Pine.LNX.4.21.0301101828110.5488-100000@ucontrol.mobiledns.com>

Greetings,

I have one booting into Linux now. I will get the commit together over the
weekend.

Currently, it's working decently, except that the ethernet isn't coming
up. I believe that's just a matter of configuring the new bridge better.

G'day,
sjames



On Fri, 10 Jan 2003, Jarmo Tulonen wrote:

> Hi,
> 
> What is the present status of LinuxBIOS for this chip set ?
> I think someone was working on it.
> We should make an implementation for Tyan Tiger MPX (S2466),
> so we are interested in what already exists (especially for the
> southbridge). And also if there is something we can help with.
> 
> Regards
> 
> Jarmo
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From pyro at linuxlabs.com  Fri Jan 10 18:27:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Fri Jan 10 18:27:01 2003
Subject: AMD 760MPX
In-Reply-To: <Pine.LNX.4.21.0301101828110.5488-100000@ucontrol.mobiledns.com>
Message-ID: <Pine.LNX.4.21.0301101837370.5488-100000@ucontrol.mobiledns.com>

Greetings,

Nothing like replying to myself, eh?

I just got a solid boot w/ the ethernet up and running.
I will commit as I clean up the mess I made in one or two places.

Once it's up, I would appreciate testing and reports.

G'day,
sjames


On Fri, 10 Jan 2003, steven james wrote:

> Greetings,
> 
> I have one booting into Linux now. I will get the commit together over the
> weekend.
> 
> Currently, it's working decently, except that the ethernet isn't coming
> up. I believe that's just a matter of configuring the new bridge better.
> 
> G'day,
> sjames
> 
> 
> 
> On Fri, 10 Jan 2003, Jarmo Tulonen wrote:
> 
> > Hi,
> > 
> > What is the present status of LinuxBIOS for this chip set ?
> > I think someone was working on it.
> > We should make an implementation for Tyan Tiger MPX (S2466),
> > so we are interested in what already exists (especially for the
> > southbridge). And also if there is something we can help with.
> > 
> > Regards
> > 
> > Jarmo
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
> > 
> 
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From bezanson at netaudiotech.com  Fri Jan 10 18:31:01 2003
From: bezanson at netaudiotech.com (Adam Bezanson)
Date: Fri Jan 10 18:31:01 2003
Subject: Geode debugging
Message-ID: <NNEHJEGKOBOALJLKPJLDEEGPCCAA.bezanson@netaudiotech.com>

Anyone know what is typically used for debugging a Geode 
x200 based design? By this I mean a JTAG/BDM or ICE for
debugging say, LinuxBIOS and the Linux Kernel/Linux device drivers.
I think this would be needed to support audio (VSA/SMM support)
since getting it working without an ICE of some kind would be
next to impossible.
I can't really find any info on the web about it
other then here: http://www.fs2.com
they make an ISA-GEODE but it only seems to support GX2 based
processors.

Any suggestions?

Thanks,
Adam



From stuge-linuxbios at cdy.org  Sat Jan 11 03:10:01 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Sat Jan 11 03:10:01 2003
Subject: Geode debugging
In-Reply-To: <NNEHJEGKOBOALJLKPJLDEEGPCCAA.bezanson@netaudiotech.com>
References: <NNEHJEGKOBOALJLKPJLDEEGPCCAA.bezanson@netaudiotech.com>
Message-ID: <20030111081334.GA31569@foo.birdnet.se>

On Fri, Jan 10, 2003 at 06:43:30PM -0500, Adam Bezanson wrote:
> Anyone know what is typically used for debugging a Geode 
> x200 based design? By this I mean a JTAG/BDM or ICE for
> debugging say, LinuxBIOS and the Linux Kernel/Linux device drivers.
> I think this would be needed to support audio (VSA/SMM support)
> since getting it working without an ICE of some kind would be
> next to impossible.
> I can't really find any info on the web about it
> other then here: http://www.fs2.com
> they make an ISA-GEODE but it only seems to support GX2 based
> processors.

My humble opinion is that implementing VSA2 wouldn't be that difficult with
access to the right docs and previous knowledge about the platform.

And once LinuxBIOS has VSA2, just plug the BLDT .rom-files into it and
you're done.


//Peter


From adam at cfar.umd.edu  Sat Jan 11 03:19:00 2003
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Sat Jan 11 03:19:00 2003
Subject: Geode debugging
In-Reply-To: <20030111081334.GA31569@foo.birdnet.se>
Message-ID: <20030111033930.U62306-100000@www.missl.cs.umd.edu>

> My humble opinion is that implementing VSA2 wouldn't be that difficult with
> access to the right docs and previous knowledge about the platform.
>
> And once LinuxBIOS has VSA2, just plug the BLDT .rom-files into it and
> you're done.

umm isn't that like a step backward? from a binary-only bios back to
binary only modules?

-- 
Adam Sulmicki
http://www.eax.com 	The Supreme Headquarters of the 32 bit registers



From stuge-linuxbios at cdy.org  Sat Jan 11 03:38:01 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Sat Jan 11 03:38:01 2003
Subject: Geode debugging
In-Reply-To: <20030111033930.U62306-100000@www.missl.cs.umd.edu>
References: <20030111081334.GA31569@foo.birdnet.se> <20030111033930.U62306-100000@www.missl.cs.umd.edu>
Message-ID: <20030111084043.GC31569@foo.birdnet.se>

On Sat, Jan 11, 2003 at 03:40:12AM -0500, Adam Sulmicki wrote:
> > And once LinuxBIOS has VSA2, just plug the BLDT .rom-files into it and
> > you're done.
> 
> umm isn't that like a step backward? from a binary-only bios back to
> binary only modules?

Well, at least the VSA2 implementation is open source.  :)

Problem is that the VSA2 modules aren't distributed in source form,
anywhere.  They are however distributed under some royalty-free license in
binary form, which will do just fine for most users wanting the
functionality.  Compare with 3Com 3CR990 with specially licensed binary
image (firmware for 3com chip) inside driver..


//Peter


From sivakumar.subramani at wipro.com  Sat Jan 11 09:04:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Sat Jan 11 09:04:01 2003
Subject: Option Parameters for Linuxbios.
Message-ID: <1042294618.1888.6.camel@Jasmine>

Hi all,

Can any one help me in understanding the following parameter used for
the configuration of the LinuxBIOS.

biosbase 0xffff0000
rambase 0x00000800
option XIP_ROM_BASE=0xffff0000
option XIP_ROM_SIZE=0x10000
option STACK_SIZE=0x2000
option ZKERNEL_START=0xfff40000
option ZKERNEL_MASK=0x3ed



Also I have one more query,
When executing the linuxbios, it is executing the instrcution twice
(i.e., I am getting output twice). I have attached the serial console
output below. How to get rid of this?

LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4
(four)starting...
Ram1
Ram2
Ram3
Ram Enable 1
Ram Enable 2
Ram Enable 3
Ram Enable 4
000001d0Ram Enable 5

Ram Enable 6

Content of CAPPTR
04Content of BCC
06Ram4
Ram5
Ram6
Copying LinuxBIOS to ram.
00000800ffff0f80
 ecx value during image copy
00000000Jumping to LinuxBIOS.
Calling hardwaremain ...


LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4
(four)starting...
Ram1
Ram2
Ram3
Ram Enable 1
Ram Enable 2
Ram Enable 3
Ram Enable 4
000001d0Ram Enable 5

Ram Enable 6

Content of CAPPTR
04Content of BCC
06Ram4
Ram5
Ram6
Copying LinuxBIOS to ram.
00000800ffff0f80
 ecx value during image copy
00000000Jumping to LinuxBIOS.
Calling hardwaremain ...

Thanks,
Siva

-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From tkarthikbalaguru at yahoo.co.in  Sat Jan 11 10:08:00 2003
From: tkarthikbalaguru at yahoo.co.in (=?iso-8859-1?q?Karthik=20Bala=20Guru?=)
Date: Sat Jan 11 10:08:00 2003
Subject: motherboards in indian chennai markets
In-Reply-To: <1042294618.1888.6.camel@Jasmine>
Message-ID: <20030111152038.40950.qmail@web8204.mail.in.yahoo.com>

Hi all,
i want to get some cheap indian motherboards
that support linuxbios in chennai .

Do u know some brands or atleast some comps/vendors
dealing with such motherboards ???

I am upto just start and taste linuxbios ...
do support and encourage linuxbios usage

Do reply,
karthik bala guru

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com


From sivakumar.subramani at wipro.com  Sat Jan 11 10:18:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Sat Jan 11 10:18:00 2003
Subject: motherboards in indian chennai markets
In-Reply-To: <20030111152038.40950.qmail@web8204.mail.in.yahoo.com>
References: <20030111152038.40950.qmail@web8204.mail.in.yahoo.com>
Message-ID: <1042299022.1887.71.camel@Jasmine>

Hi,

I have no idea about the motherboard vendor in India chennai.
One fine thing that I would suggest is that you can find the list of
mainboard supported by linuxbios in the mainboard directory of the
linxubios source directory.

Buy those motherboard that is already suppoted by linuxbios and try it 
your self.

Have fun with linuxbios.

-Siva

On Sat, 2003-01-11 at 20:50, Karthik Bala Guru wrote:
> Hi all,
> i want to get some cheap indian motherboards
> that support linuxbios in chennai .
> 
> Do u know some brands or atleast some comps/vendors
> dealing with such motherboards ???
> 
> I am upto just start and taste linuxbios ...
> do support and encourage linuxbios usage
> 
> Do reply,
> karthik bala guru
> 
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
>        visit http://in.tv.yahoo.com
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From aip at cwlinux.com  Sat Jan 11 11:16:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Sat Jan 11 11:16:01 2003
Subject: via epia 800
In-Reply-To: <Pine.SOL.4.44.0212281459570.28984-100000@stekt55>; from Jarmo Torvinen on Sat, Dec 28, 2002 at 03:08:44PM +0200
References: <Pine.SOL.4.44.0212281459570.28984-100000@stekt55>
Message-ID: <20030112002833.B18066@mail.cwlinux.com>

Jarmo,

> but I'm still wondering if it is good for booting from hda1? Does the
> kernel installed in hda1 have to be the cwlinux-patched version or may I
> use my own vanilla-kernel?
It doesn't have to be our kernel.  You can use your own, but don't forget to run
mkelfImage.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030111/38269ded/attachment.sig>

From pyro at linuxlabs.com  Sat Jan 11 11:55:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Sat Jan 11 11:55:01 2003
Subject: missing _estack
In-Reply-To: <1040697958.3e07ca66d3717@www.gnat.ca>
Message-ID: <Pine.LNX.4.21.0301111143430.5488-100000@ucontrol.mobiledns.com>

Greetings,

I'm not up to speed on those boards, but _estack is normally defined in
the linker scripts (.ld files). It is used by the assembly code in
arch/i386/lib/c_start.S to set up the stack for the C code.

G'day,
sjames



On Mon, 23 Dec 2002 gnat at gnat.ca wrote:

> Hello,
> I've been trying to figure out how these things are setup. If I use one of the 
> sis5xx mainboard configs, I get an error stating that _estack is undefined. 
> Where is it supposed to be? Obviously, it has something to do with setting up a 
> stack. I just don't understand where it is supposed to come from. Since I'm 
> patterning my mainboard (sis530 based) on those as examples. This causes a 
> small problem. Can anyone help me?
> 
> 
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From pyro at linuxlabs.com  Sat Jan 11 12:36:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Sat Jan 11 12:36:01 2003
Subject: Option Parameters for Linuxbios.
In-Reply-To: <1042294618.1888.6.camel@Jasmine>
Message-ID: <Pine.LNX.4.21.0301111233530.5488-100000@ucontrol.mobiledns.com>

Greetings,

reply inline below:


On 11 Jan 2003, sivakumar wrote:

> Hi all,
> 
> Can any one help me in understanding the following parameter used for
> the configuration of the LinuxBIOS.
> 
> biosbase 0xffff0000

The BIOS image will begin at the biosbase address in the CPU's memory
space

> rambase 0x00000800
Once RAM is set up, the C portion of LinuxBIOS will be uncompressed and
loaded to rambase in system memory.

> option XIP_ROM_BASE=0xffff0000

same as biosbase

> option XIP_ROM_SIZE=0x10000

The rom size for LinuxBIOS is this size (a 64K blockmany cases)

> option STACK_SIZE=0x2000

This is the size of RAM allocated for the stack used by the C code

> option ZKERNEL_START=0xfff40000

This is where the payload (such as etherboot) will be located in the
memory space (as part of the flash).

> option ZKERNEL_MASK=0x3ed

Near as I can tell, this is just a legacy now.
> 
> 
> 
> Also I have one more query,
> When executing the linuxbios, it is executing the instrcution twice
> (i.e., I am getting output twice). I have attached the serial console
> output below. How to get rid of this?
> 
> LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4
> (four)starting...
> Ram1
> Ram2
> Ram3
> Ram Enable 1
> Ram Enable 2
> Ram Enable 3
> Ram Enable 4
> 000001d0Ram Enable 5
> 
> Ram Enable 6
> 
> Content of CAPPTR
> 04Content of BCC
> 06Ram4
> Ram5
> Ram6
> Copying LinuxBIOS to ram.
> 00000800ffff0f80
>  ecx value during image copy
> 00000000Jumping to LinuxBIOS.
> Calling hardwaremain ...
> 
> 
> LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4
> (four)starting...
> Ram1
> Ram2
> Ram3
> Ram Enable 1
> Ram Enable 2
> Ram Enable 3
> Ram Enable 4
> 000001d0Ram Enable 5
> 
> Ram Enable 6
> 
> Content of CAPPTR
> 04Content of BCC
> 06Ram4
> Ram5
> Ram6
> Copying LinuxBIOS to ram.
> 00000800ffff0f80
>  ecx value during image copy
> 00000000Jumping to LinuxBIOS.
> Calling hardwaremain ...
> 
> Thanks,
> Siva
> 
> 

My first guess is that the initial RAM setup is wrong and when it jumps
into ram the CPU triple faults (or a watchdog timer expires) and so
resets. The second time around, it succeeds and so all goes through.

Perhaps something being set up in the wrong order? Something needs a delay
to settle or complete in hardware? Just lucky?

G'day,
sjames


-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From pyro at linuxlabs.com  Sat Jan 11 14:59:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Sat Jan 11 14:59:00 2003
Subject: [commit] Support for Tyan TigerMPX (amd760MPX)
Message-ID: <Pine.LNX.4.21.0301111505350.5488-100000@ucontrol.mobiledns.com>

Greetings,

I have made the initial commit for this board/chipset

Currently, I have it booting into Linux with everything appearing to
work. Early next week will be testing, getting primary/fallback builds
working and general cleanup.

G'day,
sjames


-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From steve at nexpath.com  Sat Jan 11 16:13:00 2003
From: steve at nexpath.com (Steve M. Gehlbach)
Date: Sat Jan 11 16:13:00 2003
Subject: Geode sc2200 vga 
In-Reply-To: <200212121812.gBCICuZ05937@verdi.et.tudelft.nl>
Message-ID: <BPEDILBPDCBCGKGGANJLIEDCEDAA.steve@nexpath.com>

> Well, just to let you know: I'm *VERY* intersted in having VGA on my Geode
> GX1 boards (the sc2200 is, as I understand it, compatible with the GX1) !
> :-)
>
> I haven't used linuxbios yet, but somewhere in the next weeks I'll
> start experimenting with it.
>
> 	greetings,
> 	Rob van Nieuwkerk


The vga code has now been integrated into the linuxbios codebase.  Look at
the code in /src/northsouthbridge/sis/630 for examples to extending it to
the Geode.  This is all legacy text mode, or in the case of the splash
screen, simple legacy graphics mode.  If you are interested in the linux
framebuffer, that would be different matter.

-Steve



From stuge-linuxbios at cdy.org  Sat Jan 11 21:27:01 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Sat Jan 11 21:27:01 2003
Subject: Option Parameters for Linuxbios.
In-Reply-To: <Pine.LNX.4.21.0301111233530.5488-100000@ucontrol.mobiledns.com>
References: <1042294618.1888.6.camel@Jasmine> <Pine.LNX.4.21.0301111233530.5488-100000@ucontrol.mobiledns.com>
Message-ID: <20030112022952.GB20992@foo.birdnet.se>

Hi, I've been confused by these commands and options too.  Below are some
suggested namechanges followed by some reasoning about documentation in
general.


On Sat, Jan 11, 2003 at 12:48:06PM -0500, steven james wrote:
> > biosbase 0xffff0000
> 
> The BIOS image will begin at the biosbase address in the CPU's memory
> space

imagephysaddr
or
stage1physaddr


> > rambase 0x00000800
> Once RAM is set up, the C portion of LinuxBIOS will be uncompressed and
> loaded to rambase in system memory.

cportionramaddr
or
stage2ramaddr


> > option XIP_ROM_BASE=0xffff0000
> 
> same as biosbase

XIP_IMAGE_PHYS_ADDR

Why is there both a command and an option for this?  And what is XIP?


> > option XIP_ROM_SIZE=0x10000
> 
> The rom size for LinuxBIOS is this size (a 64K blockmany cases)

XIP_IMAGE_SIZE  # if this accounts for the payload
or
XIP_LINUXBIOS_SIZE  # if not

Reading some Config files this doesn't seem to be the whole story, caching
is mentioned.  What's up?


> > option STACK_SIZE=0x2000
> 
> This is the size of RAM allocated for the stack used by the C code

C_STACK_SIZE  # for cportionramaddr
or
STAGE2_STACK_SIZE  # for stage2ramaddr

Already pretty good the way it is but adding the context should help.


> > option ZKERNEL_START=0xfff40000
> 
> This is where the payload (such as etherboot) will be located in the
> memory space (as part of the flash).

PAYLOAD_PHYS_ADDR

Does LinuxBIOS require this to be aligned in any way?


> > option ZKERNEL_MASK=0x3ed
> 
> Near as I can tell, this is just a legacy now.

Great, then it can be removed.  :)  What has it been used for?


I'd be happy to make these changes.

What about general documentation, e.g. regarding current LinuxBIOS structure?
I know I've read about the different parts of LinuxBIOS somewhere but it
might have been here on the mailing list.  I'm thinking of the stage1/stage2
names I used above, is it a good idea to establish a stage 1 and a stage 2
(or similar) of LinuxBIOS or should it just continue to be "in assembly"
and "in C" ?

Also, I would very much like a complete documenatation of the Config files,
I'm thinking about doing something along the lines of a Capabilities or
Options file that specifies all possible (used) options for that particular
directory, along with sane default values where possible.  It might only
apply to mainboards but would be useful for learning the structure, when
porting to new mainboards and for the web Config creator.  Thoughts?


//Peter


From stuge-linuxbios at cdy.org  Sat Jan 11 21:35:01 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Sat Jan 11 21:35:01 2003
Subject: Option Parameters for Linuxbios.
In-Reply-To: <20030112022952.GB20992@foo.birdnet.se>
References: <1042294618.1888.6.camel@Jasmine> <Pine.LNX.4.21.0301111233530.5488-100000@ucontrol.mobiledns.com> <20030112022952.GB20992@foo.birdnet.se>
Message-ID: <20030112023834.GD20992@foo.birdnet.se>

On Sun, Jan 12, 2003 at 03:29:52AM +0100, Peter Stuge wrote:
> On Sat, Jan 11, 2003 at 12:48:06PM -0500, steven james wrote:
> > > biosbase 0xffff0000
> > 
> > The BIOS image will begin at the biosbase address in the CPU's memory
> > space
> 
> imagephysaddr
> or
> stage1physaddr

Doh, forget I wrote stage1physaddr there.  Sorry.


//Peter


From pyro at linuxlabs.com  Sat Jan 11 21:53:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Sat Jan 11 21:53:00 2003
Subject: Option Parameters for Linuxbios.
In-Reply-To: <20030112022952.GB20992@foo.birdnet.se>
Message-ID: <Pine.LNX.4.21.0301112150200.5488-100000@ucontrol.mobiledns.com>

Greetings,

The terms should at least be documented. They are spread all over the
place, so might take some doing to change.

XIP = eXecute In Place.

As for the division of stages, generally, the assembly is serial setup,
initial CPU setup, RAM setup, and decompress the C portion (plus a short
startup in asm to get the stack ready) into ram.

In a number of cases (I'm guilty here), Config files still have unneeded
or useless options either due to legacy or from using older configs as a
template for new boards.

G'day,
sjames


On Sun, 12 Jan 2003, Peter Stuge wrote:

> Hi, I've been confused by these commands and options too.  Below are some
> suggested namechanges followed by some reasoning about documentation in
> general.
> 
> 
> On Sat, Jan 11, 2003 at 12:48:06PM -0500, steven james wrote:
> > > biosbase 0xffff0000
> > 
> > The BIOS image will begin at the biosbase address in the CPU's memory
> > space
> 
> imagephysaddr
> or
> stage1physaddr
> 
> 
> > > rambase 0x00000800
> > Once RAM is set up, the C portion of LinuxBIOS will be uncompressed and
> > loaded to rambase in system memory.
> 
> cportionramaddr
> or
> stage2ramaddr
> 
> 
> > > option XIP_ROM_BASE=0xffff0000
> > 
> > same as biosbase
> 
> XIP_IMAGE_PHYS_ADDR
> 
> Why is there both a command and an option for this?  And what is XIP?
> 
> 
> > > option XIP_ROM_SIZE=0x10000
> > 
> > The rom size for LinuxBIOS is this size (a 64K blockmany cases)
> 
> XIP_IMAGE_SIZE  # if this accounts for the payload
> or
> XIP_LINUXBIOS_SIZE  # if not
> 
> Reading some Config files this doesn't seem to be the whole story, caching
> is mentioned.  What's up?
> 
> 
> > > option STACK_SIZE=0x2000
> > 
> > This is the size of RAM allocated for the stack used by the C code
> 
> C_STACK_SIZE  # for cportionramaddr
> or
> STAGE2_STACK_SIZE  # for stage2ramaddr
> 
> Already pretty good the way it is but adding the context should help.
> 
> 
> > > option ZKERNEL_START=0xfff40000
> > 
> > This is where the payload (such as etherboot) will be located in the
> > memory space (as part of the flash).
> 
> PAYLOAD_PHYS_ADDR
> 
> Does LinuxBIOS require this to be aligned in any way?
> 
> 
> > > option ZKERNEL_MASK=0x3ed
> > 
> > Near as I can tell, this is just a legacy now.
> 
> Great, then it can be removed.  :)  What has it been used for?
> 
> 
> I'd be happy to make these changes.
> 
> What about general documentation, e.g. regarding current LinuxBIOS structure?
> I know I've read about the different parts of LinuxBIOS somewhere but it
> might have been here on the mailing list.  I'm thinking of the stage1/stage2
> names I used above, is it a good idea to establish a stage 1 and a stage 2
> (or similar) of LinuxBIOS or should it just continue to be "in assembly"
> and "in C" ?
> 
> Also, I would very much like a complete documenatation of the Config files,
> I'm thinking about doing something along the lines of a Capabilities or
> Options file that specifies all possible (used) options for that particular
> directory, along with sane default values where possible.  It might only
> apply to mainboards but would be useful for learning the structure, when
> porting to new mainboards and for the web Config creator.  Thoughts?
> 
> 
> //Peter
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From sivakumar.subramani at wipro.com  Sun Jan 12 05:40:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Sun Jan 12 05:40:01 2003
Subject: DDR SDRAM Initialization.
Message-ID: <1042368765.1888.161.camel@Jasmine>

Hi,

I want to support DDR SDRAM in linuxbios. When was browsing the code, I
found only the SDRAM support. Also  I found from the specification that
Initialization sequence of DDR SDRAM and SDRAM are different.
 
Have any one coded for initialization of DDR SDRAM. Currently I am
writing the code to support the DDR SDRAM using DDR SDRAM spec. I am
facing some problem with that.

Can any send me the DDR SDRAM initialization sample code for reference ,
if you have?

Thanks,
Siva.S


-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From rminnich at lanl.gov  Sun Jan 12 18:25:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Jan 12 18:25:00 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <1042368765.1888.161.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>

On 12 Jan 2003, sivakumar wrote:

> I want to support DDR SDRAM in linuxbios. When was browsing the code, I
> found only the SDRAM support. Also  I found from the specification that
> Initialization sequence of DDR SDRAM and SDRAM are different.

DDR is in there, see the 7500 port.

kron



From ollie at sis.com.tw  Sun Jan 12 20:08:00 2003
From: ollie at sis.com.tw (ollie lho)
Date: Sun Jan 12 20:08:00 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <1042368765.1888.161.camel@Jasmine>
References: <1042368765.1888.161.camel@Jasmine>
Message-ID: <1042420714.1495.40.camel@ollie>

On Sun, 2003-01-12 at 18:52, sivakumar wrote:
> 
> Can any send me the DDR SDRAM initialization sample code for reference ,
> if you have?
> 

Init of DDR SDRAM is not much more difficult than SDR if you get 
familiar to the spec. You can read and compare the 630/ipl.S which
support SDR and 635/ipl.S which support DDR.

-- 
ollie lho <ollie at sis.com.tw>



From sivakumar.subramani at wipro.com  Mon Jan 13 00:23:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Mon Jan 13 00:23:00 2003
Subject: regarding flash ROM
In-Reply-To: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>
Message-ID: <1042436122.26324.20.camel@Jasmine>

Before asking this question , I have gone through some of the old mails
in this group. I am bit confused after that ;-(


OK the question is as follow:

I have 256 KB flash ROM. I have built the linuxbios image
(linuxbios.strip file) and burned the image on the ROM at
0x30000 to 0x40000 (Image size 64 KB)

Do I need to load any thing else in the flash ROM ?
I don't want to have kernel image on the ROM,


Regarding the kernel image, I want to have IDE connected Harddisk where
the linux Operating system is installed. i.e., I want to enable the IDE
option and boot from the OS present on the hard disk.

Is it possible to do it using 256KB? 


Thanks,
Siva

My Makefile.seting file (Not complete):

export PAYLOAD_SIZE:=458752
export ROM_IMAGE_SIZE:=65536
export STACK_SIZE:=0x2000
export XIP_ROM_BASE:=0xffff0000
export XIP_ROM_SIZE:=0x10000
export ZKERNEL_MASK:=0x3ed
export ZKERNEL_START:=0xfff40000
export _RAMBASE:=0x00000800
export _ROMBASE:=0xffff0000








 

On Mon, 2003-01-13 at 05:07, Ronald G. Minnich wrote:
> On 12 Jan 2003, sivakumar wrote:
> 
> > I want to support DDR SDRAM in linuxbios. When was browsing the code, I
> > found only the SDRAM support. Also  I found from the specification that
> > Initialization sequence of DDR SDRAM and SDRAM are different.
> 
> DDR is in there, see the 7500 port.
> 
> kron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From sivakumar.subramani at wipro.com  Mon Jan 13 08:45:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Mon Jan 13 08:45:00 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>
Message-ID: <1042466238.30200.26.camel@Jasmine>

Thanks for the information.

I have gone through the code and have following query.
Following is the one of the step in Initialization of DDR SDRAM.

-Next a MODE REGISTER SET command should be issued for the Extended
 Mode Register to enable the DLL,

        /* 5. Issue EMRS to enable DLL */
        SET_RAM_COMMAND(RAM_COMMAND_EMRS)
        movl (0x0000<<MD_SHIFT), %eax
        DO_DELAY

First we are setting the Mode select bit of DRAM controller Mode
Register to Extended Mode Register Set Enable. 

>From DDR spec, it is given that zero bit of EMRS will enable the DLL.

Here I want to know how by moving the (0x0000 << MD_SHIFT) to eax
register, we are writting to Extended mode register.

Can any one explain this?

Thanks,
Siva

On Mon, 2003-01-13 at 05:07, Ronald G. Minnich wrote:
> On 12 Jan 2003, sivakumar wrote:
> 
> > I want to support DDR SDRAM in linuxbios. When was browsing the code, I
> > found only the SDRAM support. Also  I found from the specification that
> > Initialization sequence of DDR SDRAM and SDRAM are different.
> 
> DDR is in there, see the 7500 port.
> 
> kron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From rminnich at lanl.gov  Mon Jan 13 09:04:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Jan 13 09:04:01 2003
Subject: regarding flash ROM
In-Reply-To: <1042436122.26324.20.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301130715560.25226-100000@carotid.ccs.lanl.gov>

On 13 Jan 2003, sivakumar wrote:

> Regarding the kernel image, I want to have IDE connected Harddisk where
> the linux Operating system is installed. i.e., I want to enable the IDE
> option and boot from the OS present on the hard disk.

> Is it possible to do it using 256KB? 

yes. I have done this. It is not a problem at all. You just tell linuxbios 
to use the IDE for the boot. If that has problems with IDE, then use 
etherboot to load from IDE.




ron



From pyro at linuxlabs.com  Mon Jan 13 16:41:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Mon Jan 13 16:41:00 2003
Subject: [commit] TigerMPX (760MPX)
Message-ID: <Pine.LNX.4.21.0301131652510.5488-100000@ucontrol.mobiledns.com>

Greetings,

Primary and fallback images are working with this commit. It's looking
fairly solid.

G'day,
sjames


-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From ebiederman at lnxi.com  Mon Jan 13 18:59:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Mon Jan 13 18:59:01 2003
Subject: [ANNOUNCE] mkelfImage 2.0
Message-ID: <m3adi4vb0b.fsf@lnxi.com>

After a long and tedious grind I am pleased to announce version 2.0 of mkelfImage.
New features.
- One single binary
- Itanium support
- All of the code is in C.
- New and exciting easter eggs (err bugs can you find them before I do?...)


Available at: ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.0.tar.gz

rpms can be built with rpm -ta mkelfImage-2.0.tar.gz
alien will make perfectly serviceable debs from those...

The decision to go with pure C is that it is both relatively portable,
and it reduces maintenance when I add a feature.  I tried perl and it
handles the interesting code only with the utmost protest.  Adding
checksums and other interesting pieces is much easier if it only needs
to be both coded in one language, and usually the C implementation is
much easier than the perl.  Plus C is fast :)

Have fun,

Eric





From kevinh at ispiri.com  Mon Jan 13 20:22:01 2003
From: kevinh at ispiri.com (Kevin Hester)
Date: Mon Jan 13 20:22:01 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
Message-ID: <E18YFwn-0000Il-00@bumpy>

Hi all,

I think I've noticed a general linux-BIOS problem: Some PCI devices are not 
being enabled for bus mastery!  Let me more clearly explain the context:

1) According to my handy PCI book: All bus master capable PCI devices must 
implement bit 2 of the command register.
2) Most devices that implement this bit power up default to 1.  This is good, 
because linuxbios has not been setting this bit to 1.
3) A user reported a problem with a 802.11b card, and upon investigation I 
discovered the chip used on this card does not default to a 1 for bus master 
enable.  (See attached lspci output)

After some testing, I realized that the same card on a non LinuxBIOS based 
machine works correctly - i.e. by the time the kernel is up I see that this 
bus master enable bit is 1.  I know that the Award BIOS on this second 
machine must have set this bus master enable bit - because the kernel and 
drivers are identical.  I verified this by dumping the appropriate config 
registers early on in kernel start-up.

My theory is that the Award BIOS is doing something that we are not: During 
the IO/Mem space assignment process it is setting the bus master bit for most 
devices.  By "most devices" I mean any device that is not behind a bridge 
that inhibits bus mastery.  My PCI Sys Arch book (by Shanley and Anderson) 
says that some crummy bridges may not support bus mastery (i.e. they have a 
bit 2 of the command register that always reads as zero).  If a device is 
behind a bridge that does not support mastery, it must have its mastery bit 
cleared.

Does anyone have a copy of the $$$ PCI architecture spec so they can check 
this?  My PCI System Architecture book is vague on the topic.

My proposed fix:

* Add pci_enable_bus_masters() that does the following:
  * Calls pci_enable_bus_master(0) to enable devices directly connected to 
the host bridge

* Add pci_enable_bus_master(devfn) that does the following:
  * Try to enable bus mastery for this device.
  * If the device is a bridge:
    * If the write of master enable fails, then write zero to all "bus master 
enable" bits for devices behind that bridge (including all subordinate buses)
    * If the write of master enable succeeds, then call pci_enable_bus_master 
for all devices on the secondary bus behind this bridge.  (i.e. not for all 
subordinate busses)

I've added these functions and called them after the standard linuxbios PCI 
setup.  The problem card now works as well as it did with Award BIOS.  What 
to ya'll think?  I'm particularly interested in quotes from the PCI 
architecture spec.

Kevin

---

On a linux BIOS machine:

00:14.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01)
        Subsystem: D-Link System Inc: Unknown device 3501
        Flags: medium devsel, IRQ 5
        Memory at feb00000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
00: 60 12 73 38 02 00 90 02 01 00 80 02 08 40 00 00
10: 08 00 b0 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35
30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 00 00
40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

On a non linux BIOS machine:

00:0a.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01)
        Subsystem: D-Link System Inc: Unknown device 3501
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at ee000000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
00: 60 12 73 38 07 00 90 02 01 00 80 02 08 20 00 00
10: 08 00 00 ee 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 00 00
40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


From ollie at sis.com.tw  Mon Jan 13 20:36:01 2003
From: ollie at sis.com.tw (ollie lho)
Date: Mon Jan 13 20:36:01 2003
Subject: [ANNOUNCE] mkelfImage 2.0
In-Reply-To: <m3adi4vb0b.fsf@lnxi.com>
References: <m3adi4vb0b.fsf@lnxi.com>
Message-ID: <1042508807.1495.44.camel@ollie>

On Tue, 2003-01-14 at 08:19, Eric W. Biederman wrote:
> After a long and tedious grind I am pleased to announce version 2.0 of mkelfImage.
> New features.
> - One single binary
> - Itanium support
> - All of the code is in C.
> - New and exciting easter eggs (err bugs can you find them before I do?...)
> 
> 
> Available at: ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.0.tar.gz
> 
> rpms can be built with rpm -ta mkelfImage-2.0.tar.gz
> alien will make perfectly serviceable debs from those...
> 
> The decision to go with pure C is that it is both relatively portable,
> and it reduces maintenance when I add a feature.  I tried perl and it
> handles the interesting code only with the utmost protest.  Adding
> checksums and other interesting pieces is much easier if it only needs
> to be both coded in one language, and usually the C implementation is
> much easier than the perl.  Plus C is fast :)

Eric,
	Something off topic, the elfImage made by mkelfImage 1.1x can 
not be recognized by 'objdump' but can be dumped by 'readelf'. Is there
any reason for this ? Is this fixed by ver. 2.0 ?
 
-- 
ollie lho <ollie at sis.com.tw>



From ollie at sis.com.tw  Mon Jan 13 21:25:00 2003
From: ollie at sis.com.tw (ollie lho)
Date: Mon Jan 13 21:25:00 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
In-Reply-To: <E18YFwn-0000Il-00@bumpy>
References: <E18YFwn-0000Il-00@bumpy>
Message-ID: <1042511709.1495.68.camel@ollie>

On Tue, 2003-01-14 at 09:32, Kevin Hester wrote:
> Hi all,
> 
> I think I've noticed a general linux-BIOS problem: Some PCI devices are not 
> being enabled for bus mastery!  Let me more clearly explain the context:
> 
> 1) According to my handy PCI book: All bus master capable PCI devices must 
> implement bit 2 of the command register.
> 2) Most devices that implement this bit power up default to 1.  This is good, 
> because linuxbios has not been setting this bit to 1.
> 3) A user reported a problem with a 802.11b card, and upon investigation I 
> discovered the chip used on this card does not default to a 1 for bus master 
> enable.  (See attached lspci output)
> 

According to PCI Spec Rev. 2.2:
	Bit 2: Controls a device's ability to act as a master on the PCI 	bus.
A value of 0 diable the device from generating PCI accesses
	A value of 1 allows the device to behave as a bus master. State
	after RST# is 0.

So, if bit 2 of a device has power up default value of 1, it is 
implemented incorrectly.

> After some testing, I realized that the same card on a non LinuxBIOS based 
> machine works correctly - i.e. by the time the kernel is up I see that this 
> bus master enable bit is 1.  I know that the Award BIOS on this second 
> machine must have set this bus master enable bit - because the kernel and 
> drivers are identical.  I verified this by dumping the appropriate config 
> registers early on in kernel start-up.
> 

It is a bug of the the device driver. Take a look at other well behaved
drivers (like sis900.c). The driver have to call pci_set_master by
itself during the driver init phase.

> My theory is that the Award BIOS is doing something that we are not: During 
> the IO/Mem space assignment process it is setting the bus master bit for most 
> devices.  By "most devices" I mean any device that is not behind a bridge 
> that inhibits bus mastery.  My PCI Sys Arch book (by Shanley and Anderson) 
> says that some crummy bridges may not support bus mastery (i.e. they have a 
> bit 2 of the command register that always reads as zero).  If a device is 
> behind a bridge that does not support mastery, it must have its mastery bit 
> cleared.
> 

If the bridge can not forward bus master cycle, there is virtually no 
way for the bus master devices behind it to work properly. Those devices
does not have both "pio" and "dma" modes generally.

> Does anyone have a copy of the $$$ PCI architecture spec so they can check 
> this?  My PCI System Architecture book is vague on the topic.
> 

The spec is vague on this too. 

-- 
ollie lho <ollie at sis.com.tw>



From xuning1979 at hotmail.com  Tue Jan 14 01:10:01 2003
From: xuning1979 at hotmail.com (xu xuning)
Date: Tue Jan 14 01:10:01 2003
Subject: help!
Message-ID: <F67REVzm0kMccv5FPhT000037b4@hotmail.com>

     Hi, I have success to boot from my doc by using the pre-made images 
from http://www.cwlinux.com/download/,but now i want to know how to boot 
from IDE drive?
    BTW,how to use winfast6300-etherboot.rom and winfast6300-ide.rom?
    





_________________________________________________________________
??????????????? MSN Hotmail? http://www.hotmail.com 



From rminnich at lanl.gov  Tue Jan 14 09:42:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Jan 14 09:42:00 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
In-Reply-To: <1042511709.1495.68.camel@ollie>
Message-ID: <Pine.LNX.4.44.0301140752010.1818-100000@carotid.ccs.lanl.gov>

we don't turn on bus master as that could be very hazardous to your health 
-- imagine an unitialized PCI device coming up with bus master enabled. It 
is at that point allowed to do DMA cycles to RAM without having been 
initialized by a driver. OUCH. 

In my opinion if the driver is not turning on bus master it is a buggy 
driver. If the device comes up with bus master enabled it is a buggy 
device. Ollie has pointed this out too. There's a lot of buggy PCI 
hardware in existence. 

I think the Award BIOS is buggy, possibly intentionally, to deal with 
buggy drivers (there are lots of BIOS patches that are in there, I am 
told, to fix buggy device drivers in Windows). 

I would recommend fixing the 802.11 driver, rather than modifying 
LinuxBIOS. But let's see what other people say.

ron



From sivakumar.subramani at wipro.com  Tue Jan 14 10:31:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Tue Jan 14 10:31:00 2003
Subject: Jumping to LinuxBIOS
Message-ID: <1042559046.5610.26.camel@Jasmine>

Hi,
My image boots up to the following serial output message,

Ram5
Ram6
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.


It says that it is jumpimg to LinuxBIOS, that means it has copied the
images to RAM. So next step is to CALL(harwaremain). It is not jumping
in to hardwaremain function.

>From the linuxbios.map I found that address of hardwaremain function is
00000904 T hardwaremain

I have checked my DDR SDRAM register programming and initialization
progams with specification. It looks ok to me. If you want I can send it
for reference.

I want to verify that following option that I am using are correct are
not,

Some configuration I am using are as follow,

I am not currently enabling MTRR. Currently I am look with the
performance. 

I am not supporting SMP now.

I also verified some of the DDR SDRAM register by read it back.

I am using 256 KB Flash ROM and 256 MB RAM. While burning the Flash I am
burning the 65 KB linuxbios.strip file on FLASH ROM.

I have attached the makefile.settings along with this mail.


Can any one help me in resolving the problem ;-(

-Siva









-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile.settings
Type: text/x-makefile
Size: 2531 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030114/461f1eb1/attachment.bin>

From ebiederman at lnxi.com  Tue Jan 14 10:43:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Tue Jan 14 10:43:00 2003
Subject: [ANNOUNCE] mkelfImage 2.0
In-Reply-To: <1042508807.1495.44.camel@ollie>
References: <m3adi4vb0b.fsf@lnxi.com> <1042508807.1495.44.camel@ollie>
Message-ID: <m3of6jafbs.fsf@lnxi.com>

ollie lho <ollie at sis.com.tw> writes:

> Eric,
> 	Something off topic, the elfImage made by mkelfImage 1.1x can 
> not be recognized by 'objdump' but can be dumped by 'readelf'. Is there
> any reason for this ? 

Yes.  This is a bug in some versions of objdump.  On my current
system this bug does not occur.  It can be worked around by putting
in a dummy symbol table, but this increases the size by a few bytes.
Possibly a problem in an embedded situation.

>Is this fixed by ver. 2.0 ?

No.

And my version objdump which does not show the problem is:

eric at maxwell:~$ objdump --version
GNU objdump 2.13.90.0.10 20021010 Debian GNU/Linux
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no
warranty.

Eric



From rminnich at lanl.gov  Tue Jan 14 10:45:27 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Jan 14 10:45:27 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <1042559046.5610.26.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301140855330.2241-100000@carotid.ccs.lanl.gov>

On 14 Jan 2003, sivakumar wrote:

> I have checked my DDR SDRAM register programming and initialization
> progams with specification. It looks ok to me. If you want I can send it
> for reference.

use dumpnorth to dump the northbridge, and compare your settings to the 
original BIOS settings. 

I think you've got something wrong in your DRAM programming.

ron



From ebiederman at lnxi.com  Tue Jan 14 10:50:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Tue Jan 14 10:50:00 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
In-Reply-To: <Pine.LNX.4.44.0301140752010.1818-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301140752010.1818-100000@carotid.ccs.lanl.gov>
Message-ID: <m3k7h7af1h.fsf@lnxi.com>

"Ronald G. Minnich" <rminnich at lanl.gov> writes:

> we don't turn on bus master as that could be very hazardous to your health 
> -- imagine an unitialized PCI device coming up with bus master enabled. It 
> is at that point allowed to do DMA cycles to RAM without having been 
> initialized by a driver. OUCH. 
> 
> In my opinion if the driver is not turning on bus master it is a buggy 
> driver. If the device comes up with bus master enabled it is a buggy 
> device. Ollie has pointed this out too. There's a lot of buggy PCI 
> hardware in existence. 
> 
> I think the Award BIOS is buggy, possibly intentionally, to deal with 
> buggy drivers (there are lots of BIOS patches that are in there, I am 
> told, to fix buggy device drivers in Windows). 

I am not totally certain that it is buggy.  There are places this
can be reasonable behavior.  Experience with etherboot shows that
normally boot devices at least have bus master set by the BIOS.
Though not often enough to do something reasonable with it.
 
> I would recommend fixing the 802.11 driver, rather than modifying 
> LinuxBIOS. But let's see what other people say.

Agreed.  Not all BIOSes enable bus mastering on all networking hardware.
So changing the LinuxBIOS behavior will not necessarily help.

Eric



From rminnich at lanl.gov  Tue Jan 14 10:55:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Jan 14 10:55:01 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
In-Reply-To: <m3k7h7af1h.fsf@lnxi.com>
Message-ID: <Pine.LNX.4.44.0301140906180.2362-100000@carotid.ccs.lanl.gov>

On 14 Jan 2003, Eric W. Biederman wrote:

> I am not totally certain that it is buggy.  There are places this
> can be reasonable behavior.  Experience with etherboot shows that
> normally boot devices at least have bus master set by the BIOS.

I can see how they would do this, but I still find it worrisome. I would 
guess that if the BIOS knows about a particular device it sets bus master, 
but it is hard to say. I would still not want to take standard BIOS 
behavior as a rule, given how many things that standard BIOSes seem to get 
wrong :-)

ron




From pyro at linuxlabs.com  Tue Jan 14 11:08:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Tue Jan 14 11:08:01 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <1042559046.5610.26.camel@Jasmine>
Message-ID: <Pine.LNX.4.21.0301141118590.5488-100000@ucontrol.mobiledns.com>

Greetings,

Have a look at src/ram/ramtest.inc
It is probably worthwhile to insert that before the uncompress and call it
to see if the ram is REALLY there. The copy/uncompress to RAM does it
blindly, so will happily 'succeed' even if there's no RAM there.

G'day,
sjames


On 14 Jan 2003, sivakumar wrote:

> Hi,
> My image boots up to the following serial output message,
> 
> Ram5
> Ram6
> Copying LinuxBIOS to ram.
> Jumping to LinuxBIOS.
> 
> 
> It says that it is jumpimg to LinuxBIOS, that means it has copied the
> images to RAM. So next step is to CALL(harwaremain). It is not jumping
> in to hardwaremain function.
> 
> >From the linuxbios.map I found that address of hardwaremain function is
> 00000904 T hardwaremain
> 
> I have checked my DDR SDRAM register programming and initialization
> progams with specification. It looks ok to me. If you want I can send it
> for reference.
> 
> I want to verify that following option that I am using are correct are
> not,
> 
> Some configuration I am using are as follow,
> 
> I am not currently enabling MTRR. Currently I am look with the
> performance. 
> 
> I am not supporting SMP now.
> 
> I also verified some of the DDR SDRAM register by read it back.
> 
> I am using 256 KB Flash ROM and 256 MB RAM. While burning the Flash I am
> burning the 65 KB linuxbios.strip file on FLASH ROM.
> 
> I have attached the makefile.settings along with this mail.
> 
> 
> Can any one help me in resolving the problem ;-(
> 
> -Siva
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From kevinh at ispiri.com  Tue Jan 14 13:13:00 2003
From: kevinh at ispiri.com (Kevin Hester)
Date: Tue Jan 14 13:13:00 2003
Subject: Wow!  A hole in linuxbios PCI mastery setup?
In-Reply-To: <Pine.LNX.4.44.0301140752010.1818-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301140752010.1818-100000@carotid.ccs.lanl.gov>
Message-ID: <E18YVjD-00007P-00@bumpy>

Smart.  I'll fix the driver rather than doing the Award work around.  Ollie, 
thanks for checking the spec.

On Tuesday 14 January 2003 06:54, Ronald G. Minnich wrote:
> we don't turn on bus master as that could be very hazardous to your health
> -- imagine an unitialized PCI device coming up with bus master enabled. It
> is at that point allowed to do DMA cycles to RAM without having been
> initialized by a driver. OUCH.
>
> In my opinion if the driver is not turning on bus master it is a buggy
> driver. If the device comes up with bus master enabled it is a buggy
> device. Ollie has pointed this out too. There's a lot of buggy PCI
> hardware in existence.
>
> I think the Award BIOS is buggy, possibly intentionally, to deal with
> buggy drivers (there are lots of BIOS patches that are in there, I am
> told, to fix buggy device drivers in Windows).
>
> I would recommend fixing the 802.11 driver, rather than modifying
> LinuxBIOS. But let's see what other people say.
>
> ron


From sivakumar.subramani at wipro.com  Wed Jan 15 02:30:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Wed Jan 15 02:30:00 2003
Subject: Latest source code of LinuxBIOS.
Message-ID: <1042616604.5609.40.camel@Jasmine>

Hi,
I have downloaded the source code tar from the following link,
http://sourceforge.net/project/showfiles.php?group_id=3206&release_id=42674

But it seems to br one year old. I am not able to connect to CVS
respository. Where can I get the latest tar ball of the Linuxbios source
code.


Thanks,
Siva

-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From lawrence at tyanchina.com  Wed Jan 15 03:36:00 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Wed Jan 15 03:36:00 2003
Subject: Boot from etherboot - blocked by INT 10
Message-ID: <441383BA85E81D48964152E537886C9D2306EF@mail.sh.corp.tyan.com>

Hi, All

I have made my image download the kernel from the server and boot up successfully. But an error comes out at the end of the serial output:
... ...
Kernel command line:  bz.elf -retaddr 0X000940A4
... ...
VFS: Cannot open root device "" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00

Compare with the normal Linux output:
... ...
Kernel command line: auto BOOT_IMAGE=linux ro root=301 BOOT_FILE=/boot/vmlinuz-2
.4.18-3 console=tty0 console=ttyS0,9600n8 
... ...
So I have tried the followings: 
1. Add the option (--command-line= "root= ..." or --append="root= ...") when I mkelfimage.
2. Try the latest version 2.0 of mkelfimage 
3. Add command line ="root = ..." in Linux bios CONFIG file

But the error does exit. How can I fix it? 

Thanks,
Lawrence
-----Original Message-----
From: Eric W. Biederman [mailto:ebiederman at lnxi.com] 
Sent: 2003?1?10? 15:38
To: LinuxBIOS
Cc: Lawrence LL. Dai
Subject: Re: Boot from etherboot - blocked by INT 10

"Lawrence LL. Dai" <lawrence at tyanchina.com> writes:

> Hi, Eric 
> 
> 	I suppose that mknbi and mkelf would also cause this problem.Because
> they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux
> needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but
> vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?)

The difference is mknbi/mkelf that come standard with etherboot when
the process the linux kernel start the kernel in 16bit mode and run
it's BIOS code,  mkelfImage  simulates the effect of the 16bit BIOS
code by reading LinuxBIOS tables or making the needed BIOS calls
itself, and then it enters Linux at it's unofficial 32bit entry
point. 

mkelfImage can take either a bzImage or a vmlinux.

Eric



From rminnich at lanl.gov  Wed Jan 15 09:24:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan 15 09:24:00 2003
Subject: Latest source code of LinuxBIOS.
In-Reply-To: <1042616604.5609.40.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301150737040.10806-100000@carotid.ccs.lanl.gov>

I'll try to get you one. Our web pages are in transition at the moment 
(long story) so things will be disordered for the next week, esp. status 
pages.

ron



From sivakumar.subramani at wipro.com  Wed Jan 15 22:03:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Wed Jan 15 22:03:00 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <Pine.LNX.4.44.0301140855330.2241-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301140855330.2241-100000@carotid.ccs.lanl.gov>
Message-ID: <1042686942.5610.47.camel@Jasmine>

Hi, 

use dumpnorth to dump the northbridge, and compare your settings to the 
> original BIOS settings. 

I have used dumpnorth in my code and got the REGISTER back.

Original BIOS settings means setting of some other BIOS other then
LinuxBIOS. Is it possible to get the DRAM register values from Othe
BIOS. I have AOPEN bios for my system.


dump northbridge:
00: 86 80 30 1a 06 00 90 20 04 00 00 06 00 00 00 00
10: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 e4 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 15 00 00
60: 08 08 08 08 08 08 08 08 00 00 00 00 00 00 00 00
70: 10 00 00 00 00 00 00 00 05 02 03 00 00 00 00 00
80: 00 00 82 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 41 19 00 00 00 02 38 00
a0: 02 00 20 00 17 02 00 1f 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 44 40 50 11 00 01 05 08 00 00 00 00 00 00 00 00
d0: 02 28 00 0e 0b 00 00 33 af 01 31 b5 00 00 00 00
e0: 00 00 00 00 09 a0 04 91 00 00 00 00 00 00 00 00
f0: 00 00 00 00 74 f8 20 80 38 0f 00 00 04 00 00 00
Done.

THanks,
SIVA



On Tue, 2003-01-14 at 21:26, Ronald G. Minnich wrote:
> On 14 Jan 2003, sivakumar wrote:
> 
> > I have checked my DDR SDRAM register programming and initialization
> > progams with specification. It looks ok to me. If you want I can send it
> > for reference.
> 
> use dumpnorth to dump the northbridge, and compare your settings to the 
> original BIOS settings. 
> 
> I think you've got something wrong in your DRAM programming.
> 
> ron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From rminnich at lanl.gov  Wed Jan 15 23:59:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed Jan 15 23:59:01 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <1042686942.5610.47.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301152211100.16619-100000@carotid.ccs.lanl.gov>

On 16 Jan 2003, sivakumar wrote:

> Original BIOS settings means setting of some other BIOS other then
> LinuxBIOS. Is it possible to get the DRAM register values from Othe
> BIOS. I have AOPEN bios for my system.
> 

to get the original BIOS settings, boot linux under the original BIOS 
and
lspci -xxx -s 0:0.0

when I wrote dump_northbridge I made the output just like lspci -xxx to 
make diff easier.

ron



From sivakumar.subramani at wipro.com  Thu Jan 16 00:01:02 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan 16 00:01:02 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <Pine.LNX.4.44.0301152211100.16619-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301152211100.16619-100000@carotid.ccs.lanl.gov>
Message-ID: <1042694047.5609.49.camel@Jasmine>

Thanks you !!
I am already in that process.

-Siva

On Thu, 2003-01-16 at 10:41, Ronald G. Minnich wrote:
> On 16 Jan 2003, sivakumar wrote:
> 
> > Original BIOS settings means setting of some other BIOS other then
> > LinuxBIOS. Is it possible to get the DRAM register values from Othe
> > BIOS. I have AOPEN bios for my system.
> > 
> 
> to get the original BIOS settings, boot linux under the original BIOS 
> and
> lspci -xxx -s 0:0.0
> 
> when I wrote dump_northbridge I made the output just like lspci -xxx to 
> make diff easier.
> 
> ron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From sivakumar.subramani at wipro.com  Thu Jan 16 00:43:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan 16 00:43:00 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <Pine.LNX.4.44.0301152211100.16619-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301152211100.16619-100000@carotid.ccs.lanl.gov>
Message-ID: <1042696576.5609.57.camel@Jasmine>

Hi,

Do I need to initialize the PAM (Programmable Attribute Map Register)?

Actually this register is used to do some memory mapping functionality. 

When I was browsing the source code tree (in 440gx also) I found that in
all the Northbridge raminit.inc , we are setting this register to
default values (i.e., 0x00)

That means we are not worrying about the PAM during the RAM
initialization. Is my assumption is correct?

Thanks,
Siva


On Thu, 2003-01-16 at 10:41, Ronald G. Minnich wrote:
> On 16 Jan 2003, sivakumar wrote:
> 
> > Original BIOS settings means setting of some other BIOS other then
> > LinuxBIOS. Is it possible to get the DRAM register values from Othe
> > BIOS. I have AOPEN bios for my system.
> > 
> 
> to get the original BIOS settings, boot linux under the original BIOS 
> and
> lspci -xxx -s 0:0.0
> 
> when I wrote dump_northbridge I made the output just like lspci -xxx to 
> make diff easier.
> 
> ron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From erto at katamail.com  Thu Jan 16 06:20:01 2003
From: erto at katamail.com (erto at katamail.com)
Date: Thu Jan 16 06:20:01 2003
Subject: subscription
Message-ID: <127.0.0.1+DThDao6fjcRmYePxdLhp0s@hal-2.inet.it>

Hi!

Please UNSUBSCRIBE my address.


Best Regards


From femur at femur.pl  Thu Jan 16 07:00:01 2003
From: femur at femur.pl (=?iso-8859-2?Q?Pawe=B3_Wojtal?=)
Date: Thu Jan 16 07:00:01 2003
Subject: quick start
Message-ID: <004d01c2bd58$aa84d940$0504a8c0@radio.nasze.pl>

Hi!

Is there somewhere a site, I can find an idiot-image(s) of linuxbios ready
to flash into rom? Any kind of support: ide0 boot, or dhcp or others... any
board (I will find any board on second-hand market). I need to temporary
decrease my frustration with compiling from sources and start to play with
anything ;-))).

Excuse my English, please. Thanks.
femur



From jallen at integraltech.com  Thu Jan 16 08:38:01 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan 16 08:38:01 2003
Subject: warm reboot Geode
Message-ID: <3E26B8C2.2050804@integraltech.com>

When I use the reboot command on my Dorado demo board from National 
(with their BIOS), It will successfully warm boot the machine.  When I 
use my LinuxBIOS image on the Dorado or my Geode machine, the machine 
just stalls at the point where the reset should occur.  It seems to me 
that Linux is performing a BIOS Int function that is not implemented in 
my build of LinuxBIOS.  Anyone had any luck with this?

John



From daniel at dmhome.net  Thu Jan 16 09:17:00 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Thu Jan 16 09:17:00 2003
Subject: sdram on board
Message-ID: <1042727400.3e26c1e8c833e@www.mailshell.com>

I am trying to get an embedded pc board to run with linuxbios. The board is an arbor emcore6352 and is (almost) identical to the technoland  sbc710 from the CVS tree. The onboard ethernet is an intel chipset however, and the cpu is a low power pentium iii. 

* Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...  
Any tips where I can start looking? 

* The other thing , is that the board has it's sdram (128mb) soldered on the pcb, and there's no serial eeprom to read the stuff that usually comes from the smbus. 
So far the only way to get linuxbios to come up is to plug in extra sdram(in an sodimm socket) that DOES have the usual serial eeprom to do spd. 
I have the datasheets of the sdram components, so I guess it's a matter of hardcoding the information about those chips somewhere? Could you please give me a hint as to where would be the best place to insert this code into the source tree? 
Or any useful links about (basics) of sdram initialization, since I am a total newbie with this stuff. 
 

Thanks  





From aip at cwlinux.com  Thu Jan 16 09:34:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Thu Jan 16 09:34:01 2003
Subject: sdram on board
In-Reply-To: <1042727400.3e26c1e8c833e@www.mailshell.com>; from daniel@dmhome.net on Thu, Jan 16, 2003 at 06:30:00AM -0800
References: <1042727400.3e26c1e8c833e@www.mailshell.com>
Message-ID: <20030116224721.A31811@mail.cwlinux.com>

> * Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...  
> Any tips where I can start looking? 
It could be src/config/Config's CONFIG_COMPRESS is set to 1.  Try to set it to
0.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030116/91f15ef4/attachment.sig>

From aip at cwlinux.com  Thu Jan 16 09:38:00 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Thu Jan 16 09:38:00 2003
Subject: warm reboot Geode
In-Reply-To: <3E26B8C2.2050804@integraltech.com>; from John Allen on Thu, Jan 16, 2003 at 08:50:58AM -0500
References: <3E26B8C2.2050804@integraltech.com>
Message-ID: <20030116225141.B31811@mail.cwlinux.com>

John,

> When I use the reboot command on my Dorado demo board from National 
> (with their BIOS), It will successfully warm boot the machine.  When I 
> use my LinuxBIOS image on the Dorado or my Geode machine, the machine 
> just stalls at the point where the reset should occur.  It seems to me 
> that Linux is performing a BIOS Int function that is not implemented in 
> my build of LinuxBIOS.  Anyone had any luck with this?
Kenerl doesn't support it by default.  Basically you need to add a reset routine
for cs5530.  Here is my patch which works for me.  It is for 2.4.17, but
shouldn't be too hard to patch it on 2.4.20.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
diff -Nur linux/arch/i386/kernel/process.c linux-geode.reset/arch/i386/kernel/process.c
--- linux/arch/i386/kernel/process.c	Fri Oct  5 09:42:54 2001
+++ linux-geode.reset/arch/i386/kernel/process.c	Fri Jul 19 15:17:49 2002
@@ -49,6 +49,153 @@
 
 #include <linux/irq.h>
 
+#define CONFIG_LINUXBIOS_PM
+#ifdef CONFIG_LINUXBIOS_PM
+#include <linux/pci.h>
+void
+cs5530_reset(struct pci_dev *dev)
+{
+	struct pci_dev *dev;
+
+	printk(KERN_ERR __FUNCTION__ ": starting reset operation. \n");
+
+	dev = pci_find_device(PCI_VENDOR_ID_CYRIX, \
+			PCI_DEVICE_ID_CYRIX_5530_LEGACY, 0);
+
+	if (dev == NULL) {
+		printk(KERN_ERR __FUNCTION__ ": can't find device!!!\n");
+	}
+
+	/* Execute system wide reset by doing X-Bus Warm Start*/
+	pci_write_config_byte(dev, 0x44, 0x1);
+
+	printk(KERN_ERR __FUNCTION__ ": We should reset soon. \n");
+}
+
+void
+sis503_reset(struct pci_dev *dev)
+{
+	unsigned char b;
+	unsigned short acpi_base;
+
+	printk(KERN_ERR __FUNCTION__ ": starting reset operation. \n");
+
+	/* Enable ACPI by set B7 on Reg 0x40, LPC */
+	pci_read_config_byte(dev, 0x40, &b);
+	pci_write_config_byte(dev, 0x40, b | 0x80);
+	printk(KERN_ERR __FUNCTION__ ": enabled ACPI. \n");
+
+	/* get the ACPI base address for register 0x74,0x75 of LPC */
+	pci_read_config_word(dev, 0x74, &acpi_base);	
+	printk(KERN_ERR __FUNCTION__ ":acpi base: %x\n", acpi_base);
+
+	/* Set software watchdog timer init value */
+	outb(0x03, 0x4a + acpi_base);
+	printk(KERN_ERR __FUNCTION__ ": set the dog. \n");
+
+	printk(KERN_ERR __FUNCTION__ ": enabling dog. \n");
+	/* Software watchdog enable, issue PCIRST# when time expire */
+	outb(0x8f, 0x4b + acpi_base);
+
+	printk(KERN_ERR __FUNCTION__ ": We should reset soon. \n");
+}
+
+void
+sis503_off(struct pci_dev *dev)
+{
+	unsigned char b;
+	unsigned short acpi_base;
+
+	printk(KERN_ERR __FUNCTION__ ": starting reset operation. \n");
+	/* Enable ACPI by set B7 on Reg 0x40, LPC */
+	pci_read_config_byte(dev, 0x40, &b);
+	pci_write_config_byte(dev, 0x40, b | 0x80);
+	printk(KERN_ERR __FUNCTION__ ": enabled ACPI. \n");
+
+        /* get the ACPI base address for register 0x74,0x75 of LPC */
+	pci_read_config_word(dev, 0x74, &acpi_base);
+	printk (KERN_ERR __FUNCTION__ ":acpi base: %x\n", acpi_base);
+
+	/* ACPI Register 5, Bit 10-12, Sleeping Type,
+	   set to 101 -> S5, soft_off */
+	outb(0x14, 0x05 + acpi_base);
+	printk(KERN_ERR __FUNCTION__ ": DONE setting sleep type. \n");
+
+	/* ACPI Register 5, Bit 13, Sleep Enable */
+	outb(0x20 | 0x14, 0x05 + acpi_base);
+	printk(KERN_ERR __FUNCTION__ ": DONE sleep enable. \n");
+}
+
+struct pci_dev * pci_find_device(unsigned int vendor, unsigned int device, 
+				 const struct pci_dev *from);
+
+struct linuxbios_control {
+	u_short vendor, device;
+	void (*poweroff)(struct pci_dev *);
+	void (*reset)(struct pci_dev *);
+};
+
+struct linuxbios_control controls[] = {
+	{PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_503, sis503_off, sis503_reset},
+	{PCI_VENDOR_ID_CYRIX, PCI_DEVICE_ID_CYRIX_5530_LEGACY, NULL, cs5530_reset}
+};
+
+struct linuxbios_control *findcontrol(struct pci_dev **d)
+{
+	struct linuxbios_control *lb = controls, *retval = 0;
+	int i;
+
+	printk(KERN_ERR __FUNCTION__ ": Find vendor 0x%x device 0x%x\n", 
+	       lb->vendor, lb->device);
+	for(lb = controls, i = 0; 
+	    (i < sizeof(controls)/sizeof(controls[0])) && (! retval); 
+	    i++, lb++)
+	{
+		*d = pci_find_device(lb->vendor, lb->device, 0);
+		if (*d)
+			retval = lb;
+	}
+
+	printk(KERN_ERR __FUNCTION__ ": result of find is %p\n", retval);
+	return retval;
+}
+
+void
+linuxbios_poweroff(void)
+{
+	struct linuxbios_control *lb = 0;
+	struct pci_dev *dev;
+
+	printk(KERN_ERR __FUNCTION__ ": find an lb\n");
+	lb = findcontrol(&dev);
+
+	printk(KERN_ERR __FUNCTION__ ": found lb %p, call %p\n", 
+	       lb, lb ? lb->poweroff : 0);
+	if (lb && (lb->poweroff))
+		lb->poweroff(dev);
+	printk(KERN_ERR __FUNCTION__ ": Returning? Can't happen, I thought?\n");
+}
+
+void
+linuxbios_reset(void)
+{
+	struct linuxbios_control *lb = 0;
+	struct pci_dev *dev;
+
+	printk(KERN_ERR __FUNCTION__ ": find an lb\n");
+	lb = findcontrol(&dev);
+
+	printk(KERN_ERR __FUNCTION__ ": found lb %p, call %p\n", 
+	       lb, lb ? lb->reset : 0);
+	if (lb && (lb->reset))
+		lb->reset(dev);
+
+	printk(KERN_ERR __FUNCTION__ ": Returning? Can't happen, I thought?\n");
+}
+
+#endif
+
+
 asmlinkage void ret_from_fork(void) __asm__("ret_from_fork");
 
 int hlt_counter;
@@ -399,6 +546,9 @@
 	 */
 	smp_send_stop();
 	disable_IO_APIC();
+#endif
+#ifdef CONFIG_LINUXBIOS_PM
+	linuxbios_reset();
 #endif
 
 	if(!reboot_thru_bios) {
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030116/4e26c69b/attachment.sig>

From rminnich at lanl.gov  Thu Jan 16 09:54:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 09:54:01 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <1042696576.5609.57.camel@Jasmine>
Message-ID: <Pine.LNX.4.44.0301160806140.20312-100000@carotid.ccs.lanl.gov>

On 16 Jan 2003, sivakumar wrote:

> Do I need to initialize the PAM (Programmable Attribute Map Register)?

it's a good idea. Some chipsets don't set to reasonable values and bad 
things can happen. At the same time I doubt this is your problem.

> Actually this register is used to do some memory mapping functionality. 

it's really for DOS memory layout compatibility.

> That means we are not worrying about the PAM during the RAM
> initialization. Is my assumption is correct?

yes but it doesn't hurt to set it.

I think you're getting the idea of how to do this.

ron



From rminnich at lanl.gov  Thu Jan 16 09:56:02 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 09:56:02 2003
Subject: quick start
In-Reply-To: <004d01c2bd58$aa84d940$0504a8c0@radio.nasze.pl>
Message-ID: <Pine.LNX.4.44.0301160807450.20312-100000@carotid.ccs.lanl.gov>

On Thu, 16 Jan 2003, [iso-8859-2] Pawe? Wojtal wrote:

> Is there somewhere a site, I can find an idiot-image(s) of linuxbios ready
> to flash into rom? Any kind of support: ide0 boot, or dhcp or others... any
> board (I will find any board on second-hand market). I need to temporary
> decrease my frustration with compiling from sources and start to play with
> anything ;-))).

go to cwlinux.com. If you can buy a board, buy a board from them too, they 
come pre-loaded with linuxbios, and for now, they're the only vendor I 
know of doing this.

ron



From rminnich at lanl.gov  Thu Jan 16 09:57:14 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 09:57:14 2003
Subject: warm reboot Geode
In-Reply-To: <3E26B8C2.2050804@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301160808270.20312-100000@carotid.ccs.lanl.gov>

On Thu, 16 Jan 2003, John Allen wrote:

> When I use the reboot command on my Dorado demo board from National 
> (with their BIOS), It will successfully warm boot the machine.  When I 
> use my LinuxBIOS image on the Dorado or my Geode machine, the machine 
> just stalls at the point where the reset should occur.  It seems to me 
> that Linux is performing a BIOS Int function that is not implemented in 
> my build of LinuxBIOS.  Anyone had any luck with this?

I am still missing the docs on how to do this, so have not made it work. 

I have hints from people but not a single hint has worked yet.

ron



From jallen at integraltech.com  Thu Jan 16 10:00:00 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan 16 10:00:00 2003
Subject: rom image dates
Message-ID: <3E26CC29.4050004@integraltech.com>

I noticed that the romimage files created by the linuxBIOS build do not 
have a date in the last few bytes of the image.  I believe that most rom 
images use this area to identify the date the rom was compiled.  Is 
there a tool in the LinuxBIOS "arsenal" that can add the date to the 
correct file, say linuxbios.rom, before performing the cat to get romimage?

John



From sivakumar.subramani at wipro.com  Thu Jan 16 10:24:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Thu Jan 16 10:24:00 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <Pine.LNX.4.44.0301160806140.20312-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301160806140.20312-100000@carotid.ccs.lanl.gov>
Message-ID: <1042731415.1465.5.camel@Jasmine>

> Do I need to initialize the PAM (Programmable Attribute Map Register)?
> 
> it's a good idea. Some chipsets don't set to reasonable values and bad 
> things can happen. At the same time I doubt this is your problem.

> I think you're getting the idea of how to do this.

I haven't gone through the PAM register throughly,  I need to read the specification
Any tips on how to set the PAM register.

Also I have one question, along with this, I have some more registers like AGPCMD, AGPSTAT and etc..
to set the properties of the AGP port. Do I need to take care of these while configuring the DDR SDRAM.

-Siva



On Thu, 2003-01-16 at 20:37, Ronald G. Minnich wrote:
> On 16 Jan 2003, sivakumar wrote:
> 
> > Do I need to initialize the PAM (Programmable Attribute Map Register)?
> 
> it's a good idea. Some chipsets don't set to reasonable values and bad 
> things can happen. At the same time I doubt this is your problem.
> 
> > Actually this register is used to do some memory mapping functionality. 
> 
> it's really for DOS memory layout compatibility.
> 
> > That means we are not worrying about the PAM during the RAM
> > initialization. Is my assumption is correct?
> 
> yes but it doesn't hurt to set it.
> 
> I think you're getting the idea of how to do this.
> 
> ron
-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From jefight at hotmail.com  Thu Jan 16 10:40:00 2003
From: jefight at hotmail.com (Jeffrey Knight)
Date: Thu Jan 16 10:40:00 2003
Subject: Newbie install question
Message-ID: <F69VGkadYX8bszzlimY00018831@hotmail.com>


Hi all:
I'm looking for a linux version/distribution that will boot as fast as 
possible.
I have a PII intel motherboard, and am interested in trying to get linuxBIOS 
on it (the Phoenix BIOS alone take a good 15+ seconds).

My questions are:
do I need any special *hardware* to install linuxBIOS?
In reading the FAQ's on the website, I'm a bit confused by "burning a flash 
ROM" using a flash burner.
and
is there any documentation on installing linuxBIOS other than the FAQ's?

Although I'm very familiar with linux, a lot of this is new to me.
Thanks!
Jeff


_________________________________________________________________
Help STOP SPAM: Try the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail



From rminnich at lanl.gov  Thu Jan 16 11:43:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 11:43:00 2003
Subject: rom image dates
In-Reply-To: <3E26CC29.4050004@integraltech.com>
Message-ID: <Pine.LNX.4.44.0301160956170.21068-100000@carotid.ccs.lanl.gov>

On Thu, 16 Jan 2003, John Allen wrote:

> I noticed that the romimage files created by the linuxBIOS build do not 
> have a date in the last few bytes of the image.  I believe that most rom 
> images use this area to identify the date the rom was compiled.  Is 
> there a tool in the LinuxBIOS "arsenal" that can add the date to the 
> correct file, say linuxbios.rom, before performing the cat to get romimage?

If you want to send me the script to do it I'll set it up in the tree.

ron



From jallen at integraltech.com  Thu Jan 16 14:02:00 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan 16 14:02:00 2003
Subject: rom image dates
References: <Pine.LNX.4.44.0301160956170.21068-100000@carotid.ccs.lanl.gov>
Message-ID: <3E2704C8.10705@integraltech.com>

Ron, I whipped together this little script to add the date to 
linuxbios.rom. Its ugly but it seems to work.

#!/bin/sh
#rom_add_date

date +%D > date.bin
dd if=/dev/zero of=two.bin bs=2 count=1
dd if=linuxbios.rom of=linuxbios_pre_date.bin bs=`expr $1 - 11` count=1
rm -f linuxbios.rom
cat linuxbios_pre_date.bin date.bin two.bin > linuxbios.rom
rm -f two.bin
rm -f date.bin
rm -f linuxbios_pre_date.bin


I also have added a line under the linuxbios.rom heading in the makefile 
as follows.

linuxbios.rom: linuxbios.strip
   
    export size=`ls -l linuxbios.strip | (read p c u g size r ; echo 
$$size)` ; \
    echo $$size ; \
    dd if=linuxbios.strip of=linuxbios.rom bs=1 seek=`expr 
$(ROM_IMAGE_SIZE) - $$size`
    ./rom_add_date $(ROM_IMAGE_SIZE)

Do with it what you want. Its all yours.

John

Ronald G. Minnich wrote:

>On Thu, 16 Jan 2003, John Allen wrote:
>
>  
>
>>I noticed that the romimage files created by the linuxBIOS build do not 
>>have a date in the last few bytes of the image.  I believe that most rom 
>>images use this area to identify the date the rom was compiled.  Is 
>>there a tool in the LinuxBIOS "arsenal" that can add the date to the 
>>correct file, say linuxbios.rom, before performing the cat to get romimage?
>>    
>>
>
>If you want to send me the script to do it I'll set it up in the tree.
>
>ron
>
>
>  
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rom_add_date
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030116/37cb4046/attachment.ksh>

From ebiederman at lnxi.com  Thu Jan 16 14:23:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Jan 16 14:23:01 2003
Subject: rom image dates
In-Reply-To: <3E2704C8.10705@integraltech.com>
References: <Pine.LNX.4.44.0301160956170.21068-100000@carotid.ccs.lanl.gov>
	<3E2704C8.10705@integraltech.com>
Message-ID: <m3y95kyj60.fsf@lnxi.com>

John Allen <jallen at integraltech.com> writes:

> Ron, I whipped together this little script to add the date to linuxbios.rom. Its
> 
> ugly but it seems to work.

For what it is worth the build date is already recorded in the version string
of LinuxBIOS, and is in the LinuxBIOS table.   At the end of the romimage
if you include id.inc and id.lds you get the motherboard manufacturer and model
at the end of the romimage.

I would suggest simply prepending the date in the form to the data already
present in id.inc, if you want to be able to get at it that way...

Eric



From ebiederman at lnxi.com  Thu Jan 16 14:26:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Jan 16 14:26:01 2003
Subject: Jumping to LinuxBIOS
In-Reply-To: <1042731415.1465.5.camel@Jasmine>
References: <Pine.LNX.4.44.0301160806140.20312-100000@carotid.ccs.lanl.gov>
	<1042731415.1465.5.camel@Jasmine>
Message-ID: <m3u1g8yj06.fsf@lnxi.com>

sivakumar <sivakumar.subramani at wipro.com> writes:

> > Do I need to initialize the PAM (Programmable Attribute Map Register)?
> > 
> > it's a good idea. Some chipsets don't set to reasonable values and bad 
> > things can happen. At the same time I doubt this is your problem.
> 
> > I think you're getting the idea of how to do this.
> 
> I haven't gone through the PAM register throughly, I need to read the
> specification
> 
> Any tips on how to set the PAM register.

Say that all memory is RAM.  Except for possibly the legacy video hole.
0xa0000 - 0xc0000

> Also I have one question, along with this, I have some more registers like
> AGPCMD, AGPSTAT and etc..
> 
> to set the properties of the AGP port. Do I need to take care of these while
> configuring the DDR SDRAM.

It should not be necessary.



From ebiederman at lnxi.com  Thu Jan 16 14:30:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu Jan 16 14:30:00 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <1042466238.30200.26.camel@Jasmine>
References: <Pine.LNX.4.44.0301121637000.19693-100000@carotid.ccs.lanl.gov>
	<1042466238.30200.26.camel@Jasmine>
Message-ID: <m3ptqwyisz.fsf@lnxi.com>

sivakumar <sivakumar.subramani at wipro.com> writes:

> Thanks for the information.
> 
> I have gone through the code and have following query.
> Following is the one of the step in Initialization of DDR SDRAM.
> 
> -Next a MODE REGISTER SET command should be issued for the Extended
>  Mode Register to enable the DLL,
> 
>         /* 5. Issue EMRS to enable DLL */
>         SET_RAM_COMMAND(RAM_COMMAND_EMRS)
>         movl (0x0000<<MD_SHIFT), %eax
>         DO_DELAY
> 
> First we are setting the Mode select bit of DRAM controller Mode
> Register to Extended Mode Register Set Enable. 
> 
> >From DDR spec, it is given that zero bit of EMRS will enable the DLL.
> 
> Here I want to know how by moving the (0x0000 << MD_SHIFT) to eax
> register, we are writting to Extended mode register.
> 
> Can any one explain this?

It is performing a memory read.   A memory read in intel chipsets
when the command register is set properly causes commands to be sent
to memory.  Reads seem to work a little bit more reliably than writes
in my experience.

Eric



From jallen at integraltech.com  Thu Jan 16 14:55:00 2003
From: jallen at integraltech.com (John Allen)
Date: Thu Jan 16 14:55:00 2003
Subject: rom image dates
References: <Pine.LNX.4.44.0301160956170.21068-100000@carotid.ccs.lanl.gov>	<3E2704C8.10705@integraltech.com> <m3y95kyj60.fsf@lnxi.com>
Message-ID: <3E27114B.6010503@integraltech.com>

I am following a specific format used in most rom images where the date 
is in MM/DD/YY format starting 11 bytes from the end of the romimage.

Eric W. Biederman wrote:

>John Allen <jallen at integraltech.com> writes:
>
>  
>
>>Ron, I whipped together this little script to add the date to linuxbios.rom. Its
>>
>>ugly but it seems to work.
>>    
>>
>
>For what it is worth the build date is already recorded in the version string
>of LinuxBIOS, and is in the LinuxBIOS table.   At the end of the romimage
>if you include id.inc and id.lds you get the motherboard manufacturer and model
>at the end of the romimage.
>
>I would suggest simply prepending the date in the form to the data already
>present in id.inc, if you want to be able to get at it that way...
>
>Eric
>
>
>  
>



From rminnich at lanl.gov  Thu Jan 16 15:49:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 15:49:01 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <m3ptqwyisz.fsf@lnxi.com>
Message-ID: <Pine.LNX.4.44.0301161401360.22570-100000@carotid.ccs.lanl.gov>

On 16 Jan 2003, Eric W. Biederman wrote:

> It is performing a memory read.   A memory read in intel chipsets
> when the command register is set properly causes commands to be sent
> to memory.  Reads seem to work a little bit more reliably than writes
> in my experience.
> 

except on 430TX, where due to a seeming bug in the chipset you have to 
write :-)

ron



From rminnich at lanl.gov  Thu Jan 16 15:55:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 15:55:00 2003
Subject: sdram on board
In-Reply-To: <1042727400.3e26c1e8c833e@www.mailshell.com>
Message-ID: <Pine.LNX.4.44.0301160811140.20312-100000@carotid.ccs.lanl.gov>

On Thu, 16 Jan 2003 daniel at dmhome.net wrote:

> I am trying to get an embedded pc board to run with linuxbios. The board
> is an arbor emcore6352 and is (almost) identical to the technoland
> sbc710 from the CVS tree. The onboard ethernet is an intel chipset
> however, and the cpu is a low power pentium iii.

did you run getpir? Run getpir under the normal bios and see if it matches 
what is in the bios you are building. I bet it doesn't. 

I think it might be a good idea to add the emcore to the tree, so if you 
can help me get this worked out we will add it.

Also folks I'm trying to get the STATUS pages up to date but our web site 
is in transition so give us a week or so.

ron
> 
> * Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...  

Send me the dmesg output.


> * The other thing , is that the board has it's sdram (128mb) soldered on
> the pcb, and there's no serial eeprom to read the stuff that usually
> comes from the smbus.  So far the only way to get linuxbios to come up
> is to plug in extra sdram(in an sodimm socket) that DOES have the usual
> serial eeprom to do spd.  I have the datasheets of the sdram components,
> so I guess it's a matter of hardcoding the information about those chips
> somewhere? 

yes, I guess so. I would build a custom raminit.inc for this motherboard. 

Let's start by getting it into the tree, this will make your life a LOT 
easier.

ron



From pyro at linuxlabs.com  Thu Jan 16 18:26:01 2003
From: pyro at linuxlabs.com (steven james)
Date: Thu Jan 16 18:26:01 2003
Subject: CVS problem?
Message-ID: <Pine.LNX.4.21.0301161837180.5488-100000@ucontrol.mobiledns.com>

Greetings,

Does anyone know what's up with CVS?
The checkout hangs up on RON_GA6-BXC. The CVS browser on the web page just
refuses connections.

G'day,
sjames


-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From rminnich at lanl.gov  Thu Jan 16 19:05:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 16 19:05:00 2003
Subject: CVS problem?
In-Reply-To: <Pine.LNX.4.21.0301161837180.5488-100000@ucontrol.mobiledns.com>
Message-ID: <Pine.LNX.4.44.0301161717440.23808-100000@carotid.ccs.lanl.gov>

On Thu, 16 Jan 2003, steven james wrote:

> Does anyone know what's up with CVS?
> The checkout hangs up on RON_GA6-BXC. The CVS browser on the web page just
> refuses connections.

sourceforge seems to be really messed up. I don't know what to do about 
this one. 

If any of the committers know how to get rid of the empty directories that 
would help.

ron



From hansolofalcon at worldnet.att.net  Thu Jan 16 19:34:00 2003
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Thu Jan 16 19:34:00 2003
Subject: CVS problem?
In-Reply-To: <Pine.LNX.4.44.0301161717440.23808-100000@carotid.ccs.lanl.gov>
Message-ID: <000201c2bdc2$262ec6a0$886a580c@who5>

Hello from Gregg C Levine
My sources tell me, that something has gone wrong, within the
Sourceforge set ups for regular CVS, and for the HTTP based viewers.
So they've disabled them. It came up, on the Bochs mailing list,
earlier today. Hopefully it should be working by the weekend. If not,
I plan on firing a proton torpedo at the first Sourceforge rep I see
at LWE next week, and then asking him about it.  And Steven it is not
your fault that there's a Charlie-Fox running inside that setup. Nor
is it the fault of anyone within this project. I suspect it started
with one project, and spread outward from there.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."? Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> admin at clustermatic.org] On Behalf Of Ronald G. Minnich
> Sent: Thursday, January 16, 2003 7:18 PM
> To: steven james
> Cc: LinusBIOS mailing list
> Subject: Re: CVS problem?
> 
> On Thu, 16 Jan 2003, steven james wrote:
> 
> > Does anyone know what's up with CVS?
> > The checkout hangs up on RON_GA6-BXC. The CVS browser on the web
page
> just
> > refuses connections.
> 
> sourceforge seems to be really messed up. I don't know what to do
about
> this one.
> 
> If any of the committers know how to get rid of the empty
directories that
> would help.
> 
> ron
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios



From daniel at dmhome.net  Thu Jan 16 22:36:00 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Thu Jan 16 22:36:00 2003
Subject: sdram on board
In-Reply-To: <Pine.LNX.4.44.0301160811140.20312-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301160811140.20312-100000@carotid.ccs.lanl.gov>
Message-ID: <20030117033503.25888.qmail@mailshell.com>

On Fri, 2003-01-17 at 05:08, Ronald G. Minnich wrote:
 
> did you run getpir? Run getpir under the normal bios and see if it matches 
> what is in the bios you are building. I bet it doesn't. 
Actually I did run getpir before , then make test, altered the checksum
in pirq_tables.c , tried again, this didn't help. 

The error seems to occur in  verify_copy_pirq_routing_table, could that
be a memory problem? Is it actually necessary that this copying pirq is
verified in order for the kernel to be able to get irq's ?   

> 
> I think it might be a good idea to add the emcore to the tree, so if you 
> can help me get this worked out we will add it.
OK. The emcore 6352 is my first cut at this linuxbios - to get into it
and study the code. It should be simple for this board, since all of
it's chips are supported already by previous eforts. If it works out I
can buy myself project time to provide more boards and work on new
stuff. 
How would I proceed later to add stuff to the tree? CVS commit, or do I
send in diffs ? 



> > * Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...  
> 
> Send me the dmesg output.
> 
> 
attached


Thank you, 


-------------- next part --------------

Jumping to boot code
Linux version 2.4.20 (root at susebox) (gcc version 2.95.3 20010315 (SuSE)) #7 Thu Jan 16 10:29:50 CST 2003
BIOS-provided physical RAM map:
 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
 BIOS-e801: 0000000000100000 - 0000000001f00000 (usable)
31MB LOWMEM available.
On node 0 totalpages: 7936
zone(0): 4096 pages.
zone(1): 3840 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda2 console=ttyS0,115200
Local APIC disabled by BIOS -- reenabling.
Could not enable APIC!
Initializing CPU#0
Detected 501.146 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 999.42 BogoMIPS
Memory: 29000k/31744k available (1115k kernel code, 2356k reserved, 509k data, 124k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch at atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: Using configuration type 1
PCI: Probing PCI hardware
Scanning bus 00
Found 00:00 [8086/7190] 000600 00
Found 00:08 [8086/7191] 000604 01
Found 00:38 [8086/7110] 000601 00
Found 00:39 [8086/7111] 000101 00
PCI: IDE base address fixup for 00:07.1
Found 00:3a [8086/7112] 000c03 00
Found 00:3b [8086/7113] 000680 00
Found 00:68 [125d/1969] 000401 00
Found 00:70 [8086/1229] 000200 00
Fixups for bus 00
PCI: Scanning for ghost devices on bus 0
Scanning behind PCI bridge 00:01.0, config 010100, pass 0
Scanning bus 01
Found 01:00 [102c/00c0] 000300 00
Fixups for bus 01
PCI: Scanning for ghost devices on bus 1
Bus scan for 01 returning with max=01
Scanning behind PCI bridge 00:01.0, config 010100, pass 1
Bus scan for 00 returning with max=01
PCI: IRQ init
PCI: IRQ fixup
PCI: Allocating resources
PCI: Resource e0000000-efffffff (f=1208, d=0, p=0)
PCI: Resource 000010a0-000010af (f=101, d=0, p=0)
PCI: Resource 00001080-0000109f (f=101, d=0, p=0)
PCI: Resource 00001000-0000103f (f=101, d=0, p=0)
PCI: Resource 000010b0-000010bf (f=101, d=0, p=0)
PCI: Resource 000010c0-000010cf (f=101, d=0, p=0)
PCI: Resource 000010d0-000010d3 (f=101, d=0, p=0)
PCI: Resource 000010e0-000010e3 (f=101, d=0, p=0)
PCI: Resource f1100000-f1100fff (f=200, d=0, p=0)
PCI: Resource 00001040-0000107f (f=101, d=0, p=0)
PCI: Resource f1000000-f10fffff (f=200, d=0, p=0)
PCI: Resource f0000000-f0ffffff (f=200, d=0, p=0)
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch at atnf.csiro.au)
devfs: boot_options: 0x1
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
keyboard: Timeout - AT keyboard not present?(ed)
keyboard: Timeout - AT keyboard not present?(f4)
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x10a0-0x10a7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x10a8-0x10af, BIOS settings: hdc:pio, hdd:pio
hda: C/H/S=0/0/0 from BIOS ignored
hdb: C/H/S=0/0/0 from BIOS ignored
hda: QUANTUM FIREBALL ST1.6A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
blk: queue c02e3c84, I/O limit 4095Mb (mask 0xffffffff)
hda: 3153024 sectors (1614 MB) w/81KiB Cache, CHS=3128/16/63, UDMA(33)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: [PTBL] [782/64/63] p1 p2
Floppy drive(s): fd0 is unknown type 9 (usb?), fd1 is unknown type 13 (usb?)
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw at saw.sw.com.sg> and others
PCI: No IRQ known for interrupt pin A of device 00:0e.0. Please try using pci=biosirq.
PCI: Enabling bus mastering for device 00:0e.0
eth0: OEM i82557/i82558 10/100 Ethernet, 00:05:B7:00:14:57, IRQ 0.
  Board assembly 618106-021, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
Possible DiskOnChip with unknown ChipID FF found at 0xc8000
Possible DiskOnChip with unknown ChipID FF found at 0xca000
Possible DiskOnChip with unknown ChipID FF found at 0xcc000
Possible DiskOnChip with unknown ChipID FF found at 0xce000
DiskOnChip Millennium found at address 0xD0000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
1 flash chips found. Total DiskOnChip size: 8 MiB
Ignoring DiskOnChip 2000 at 0xD2000 - already configured
Ignoring DiskOnChip 2000 at 0xD4000 - already configured
Ignoring DiskOnChip 2000 at 0xD6000 - already configured
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID 04 found at 0xe0000
Possible DiskOnChip with unknown ChipID D2 found at 0xe2000
Possible DiskOnChip with unknown ChipID B4 found at 0xe4000
Possible DiskOnChip with unknown ChipID 34 found at 0xe6000
Possible DiskOnChip with unknown ChipID 5D found at 0xe8000
Possible DiskOnChip with unknown ChipID EB found at 0xea000
Possible DiskOnChip with unknown ChipID 00 found at 0xec000
Possible DiskOnChip with unknown ChipID 00 found at 0xee000
NFTL driver: nftlcore.c $Revision: 1.85 $, nftlmount.c $Revision: 1.25 $
Could not find valid boot record
Could not mount NFTL device
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: No IRQ known for interrupt pin D of device 00:07.2. Please try using pci=biosirq.
uhci.c: found UHCI device with no IRQ assigned. check BIOS settings!
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 2048)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 124k freed
INIT: version 2.84 booting
Started device management daemon v1.3.25 for /dev


From daniel at dmhome.net  Thu Jan 16 23:58:00 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Thu Jan 16 23:58:00 2003
Subject: sdram on board
In-Reply-To: <20030116224721.A31811@mail.cwlinux.com>
References: <1042727400.3e26c1e8c833e@www.mailshell.com> 
	<20030116224721.A31811@mail.cwlinux.com>
Message-ID: <20030117051147.1318.qmail@mailshell.com>

On Thu, 2003-01-16 at 22:47, Andrew Ip wrote:
> > * Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...  
> > Any tips where I can start looking? 
> It could be src/config/Config's CONFIG_COMPRESS is set to 1.  Try to set it to
> 0.
Thank you very much, it worked ! This clears up a lot of things for me! 

 



From lawrence at tyanchina.com  Fri Jan 17 04:01:01 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Fri Jan 17 04:01:01 2003
Subject: Irq_table not loaded when boot from etherboot
Message-ID: <441383BA85E81D48964152E537886C9D230887@mail.sh.corp.tyan.com>

Hi All:

	I have tried to boot from network with linuxbios and failed. The output showed:

"PCI: No IRQ known for interrupt pin A of device 04:01.0. Probably buggy MP table"

	Will the irq_table only be loaded in hardwaremain() which is not called in etherboot? 
Who can give me some help? Thanks.

Ps: the attached is the output.

Best wishes,
Lawrence
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: nfs3_1.7_2.4.20.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030117/3ed567c1/attachment.txt>

From akohlsmith-linuxbios at benshaw.com  Fri Jan 17 08:14:01 2003
From: akohlsmith-linuxbios at benshaw.com (Andrew Kohlsmith)
Date: Fri Jan 17 08:14:01 2003
Subject: DDR SDRAM Initialization.
In-Reply-To: <Pine.LNX.4.44.0301161401360.22570-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301161401360.22570-100000@carotid.ccs.lanl.gov>
Message-ID: <200301170826.37643@-mixdown.ca>

> except on 430TX, where due to a seeming bug in the chipset you have to
> write :-)

Shh!  I don't want to hear about 430TX bugs!  :-)

Regards,
Andrew


From pyro at linuxlabs.com  Fri Jan 17 09:35:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Fri Jan 17 09:35:00 2003
Subject: Irq_table not loaded when boot from etherboot
In-Reply-To: <441383BA85E81D48964152E537886C9D230887@mail.sh.corp.tyan.com>
Message-ID: <Pine.LNX.4.21.0301170943060.5488-100000@ucontrol.mobiledns.com>

Greetings,

Actually, hardwaremain is called when etherboot is used. LinuxBIOS itself
leaves the mptable in memory for the kernel to find later based on
signature.

Your kernel definatly found the table.

You'll need to boot the board with the OEM BIOS and use the util/mptable
utility to dump an MP table that works for that board.

G'day,
sjames



On Fri, 17 Jan 2003, Lawrence LL. Dai wrote:

> Hi All:
> 
> 	I have tried to boot from network with linuxbios and failed. The output showed:
> 
> "PCI: No IRQ known for interrupt pin A of device 04:01.0. Probably buggy MP table"
> 
> 	Will the irq_table only be loaded in hardwaremain() which is not called in etherboot? 
> Who can give me some help? Thanks.
> 
> Ps: the attached is the output.
> 
> Best wishes,
> Lawrence
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From rminnich at lanl.gov  Fri Jan 17 09:48:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 17 09:48:00 2003
Subject: sdram on board
In-Reply-To: <20030117051147.1318.qmail@mailshell.com>
Message-ID: <Pine.LNX.4.44.0301170800550.29353-100000@carotid.ccs.lanl.gov>

On 17 Jan 2003 daniel at dmhome.net wrote:

> Thank you very much, it worked ! This clears up a lot of things for me! 

so how far are you booting now?

ron



From rminnich at lanl.gov  Fri Jan 17 09:52:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 17 09:52:00 2003
Subject: Irq_table not loaded when boot from etherboot
In-Reply-To: <441383BA85E81D48964152E537886C9D230887@mail.sh.corp.tyan.com>
Message-ID: <Pine.LNX.4.44.0301170805290.29353-100000@carotid.ccs.lanl.gov>

either you PIRQ table or your MPTABLE or both are wrong. You will need to 
fix this.

ron



From daniel at dmhome.net  Fri Jan 17 11:24:01 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Fri Jan 17 11:24:01 2003
Subject: sdram on board
In-Reply-To: <Pine.LNX.4.44.0301170800550.29353-100000@carotid.ccs.lanl.gov>
Message-ID: <1042821449.3e283149de6da@www.mailshell.com>

> 
> so how far are you booting now?
> 
> ron

The board has a plcc socket that supports up to 512kb flash + a dip doc socket mapped to the usual doc address. 
I have done two tests: 
1. linuxbios + a minimal 2.5 kernel with kexec in the flash,  that executes a 2.4 kernel from an ide harddrive.
2. linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as described in the config file of the technoland board. 

I can boot into the rootfilesystem and did some network testing. The floppy drive doesn't work, but I suspect it is because it is still setup to use the winbond floppy and not the one from the chipset (??? am just guessing here now)
All is over serial console. 
As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )

And then there is still the onboard sdram issue.  


Greetings,

Daniel 


From rsmith at bitworks.com  Fri Jan 17 12:07:01 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Fri Jan 17 12:07:01 2003
Subject: sdram on board
In-Reply-To: <1042821449.3e283149de6da@www.mailshell.com>
Message-ID: <MDAEMON-F200301171119.AA191543MD55849@bitworks.com>

On Fri, 17 Jan 2003 08:37:29 -0800, daniel at dmhome.net wrote:

> As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
> 

If you search hard enough there is a fb driver for the 69000. 
However, last I looked it had not been worked on in a long while and
it didn't really work that well.  Chances are it probally won't
compile anymore with the current fb stuff.  But it might not be that
much work to fix.  The X 69000 driver works great so you might be
able to get a lot of code/settings from it if you tried.

I'm intersted in helping you get the C&T video bios working since our
system has 2 69000's on it and I'd like them to vga on boot rather
than wait for  fb or X.

Course I have to get SDRAM working first.  *grin*



--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   




From jallen at integraltech.com  Fri Jan 17 13:34:01 2003
From: jallen at integraltech.com (John Allen)
Date: Fri Jan 17 13:34:01 2003
Subject: warm reboot Geode
References: <Pine.LNX.4.44.0301160808270.20312-100000@carotid.ccs.lanl.gov>
Message-ID: <3E284FB8.6020006@integraltech.com>

Ron, I found that writing a 1 to bit 0 of pci config space F0 index 0x44 
causes the xbus to reset.  BTW thanks Andrew!

John

Ronald G. Minnich wrote:

>On Thu, 16 Jan 2003, John Allen wrote:
>
>  
>
>>When I use the reboot command on my Dorado demo board from National 
>>(with their BIOS), It will successfully warm boot the machine.  When I 
>>use my LinuxBIOS image on the Dorado or my Geode machine, the machine 
>>just stalls at the point where the reset should occur.  It seems to me 
>>that Linux is performing a BIOS Int function that is not implemented in 
>>my build of LinuxBIOS.  Anyone had any luck with this?
>>    
>>
>
>I am still missing the docs on how to do this, so have not made it work. 
>
>I have hints from people but not a single hint has worked yet.
>
>ron
>
>
>  
>



From rminnich at lanl.gov  Fri Jan 17 15:59:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 17 15:59:00 2003
Subject: sdram on board
In-Reply-To: <1042821449.3e283149de6da@www.mailshell.com>
Message-ID: <Pine.LNX.4.44.0301171325500.31229-100000@carotid.ccs.lanl.gov>

On Fri, 17 Jan 2003 daniel at dmhome.net wrote:

> 1. linuxbios + a minimal 2.5 kernel with kexec in the flash, that
> executes a 2.4 kernel from an ide harddrive.

you got a 2.5 kernel + kexec into 512KB?

Send me kernel version and .config :-)


> 2. linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
> described in the config file of the technoland board.

that works too? 


I thiink you need to get your on-board SDRAM working first. Then let's 
talk about floppy etc. 

I would also like to get a source tree for this board into the linuxbios 
cvs. 

ron




From sivakumar.subramani at wipro.com  Sun Jan 19 22:44:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Sun Jan 19 22:44:01 2003
Subject: Linuxbios web cvs / site is down 
Message-ID: <000a01c2c038$26c743d0$2a0806c0@siva>

Hi,

Linuxbios web site is down for past three days. I want to 
download the latest code from the cvs server. Can any one help me  in resolving the issue.

Thanks,
Siva.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030119/f0316e9d/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030119/f0316e9d/attachment.txt>

From aip at cwlinux.com  Sun Jan 19 22:57:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Sun Jan 19 22:57:01 2003
Subject: Linuxbios web cvs / site is down
In-Reply-To: <000a01c2c038$26c743d0$2a0806c0@siva>; from sivakumar on Mon, Jan 20, 2003 at 09:28:07AM +0530
References: <000a01c2c038$26c743d0$2a0806c0@siva>
Message-ID: <20030120121042.A12763@mail.cwlinux.com>

Siva,

> Linuxbios web site is down for past three days. I want to 
> download the latest code from the cvs server. Can any one help me  in resolving the issue.
I think it is up now.  Or else, I can send you a copy.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030119/687eaa2f/attachment.sig>

From rminnich at lanl.gov  Sun Jan 19 23:25:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Jan 19 23:25:01 2003
Subject: Linuxbios web cvs / site is down 
In-Reply-To: <000a01c2c038$26c743d0$2a0806c0@siva>
Message-ID: <Pine.LNX.4.44.0301192138380.29251-100000@carotid.ccs.lanl.gov>

On Mon, 20 Jan 2003, sivakumar wrote:

> Linuxbios web site is down for past three days. I want to download the
> latest code from the cvs server. Can any one help me in resolving the
> issue.

yea, sorry about this, we're in the middle of getting this fixed but 
network solutions is hanging up the transfer. 

The cvs you can get from the sourceforge; I asked them to fix the problem 
and they did fix it almost instantaneously. 

ron



From sivakumar.subramani at wipro.com  Sun Jan 19 23:34:01 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Sun Jan 19 23:34:01 2003
Subject: Linuxbios web cvs / site is down 
References: <Pine.LNX.4.44.0301192138380.29251-100000@carotid.ccs.lanl.gov>
Message-ID: <005501c2c03f$0b83e0e0$2a0806c0@siva>

Thanks Ron.
I got the cvs from Sourceforge.

-Siva
----- Original Message -----
From: "Ronald G. Minnich" <rminnich at lanl.gov>
To: "sivakumar" <sivakumar.subramani at wipro.com>
Cc: <linuxbios at clustermatic.org>
Sent: Monday, January 20, 2003 10:09 AM
Subject: Re: Linuxbios web cvs / site is down


> On Mon, 20 Jan 2003, sivakumar wrote:
>
> > Linuxbios web site is down for past three days. I want to download the
> > latest code from the cvs server. Can any one help me in resolving the
> > issue.
>
> yea, sorry about this, we're in the middle of getting this fixed but
> network solutions is hanging up the transfer.
>
> The cvs you can get from the sourceforge; I asked them to fix the problem
> and they did fix it almost instantaneously.
>
> ron
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030119/70a63a18/attachment.txt>

From daniel at dmhome.net  Mon Jan 20 03:24:00 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Mon Jan 20 03:24:00 2003
Subject: emcore6352
In-Reply-To: <Pine.LNX.4.44.0301171325500.31229-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301171325500.31229-100000@carotid.ccs.lanl.gov>
Message-ID: <20030120015441.14843.qmail@mailshell.com>

On Sat, 2003-01-18 at 05:13, Ronald G. Minnich wrote:
> On Fri, 17 Jan 2003 daniel at dmhome.net wrote:
> 
> > 1. linuxbios + a minimal 2.5 kernel with kexec in the flash, that
> > executes a 2.4 kernel from an ide harddrive.
> 
> you got a 2.5 kernel + kexec into 512KB?
> 
> Send me kernel version and .config :-)
The latest at that time 2.5.56. Those 2.5 series are not so easy to
compile without networking are they ? It took me several 2.5 versions
and kexec patch combinations before I could get it to compile. 
--------------------------------------------------------
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General setup
#
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_LOG_BUF_SHIFT_17 is not set
# CONFIG_LOG_BUF_SHIFT_16 is not set
# CONFIG_LOG_BUF_SHIFT_15 is not set
CONFIG_LOG_BUF_SHIFT_14=y
# CONFIG_LOG_BUF_SHIFT_13 is not set
# CONFIG_LOG_BUF_SHIFT_12 is not set
CONFIG_LOG_BUF_SHIFT=14

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_PREFETCH=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_KEXEC=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
CONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not set
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_ONLYDISK=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
# CONFIG_NET is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# ISDN subsystem
#

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
# CONFIG_SERIO is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Hardware Sensors Mainboard support
#

#
# I2C Hardware Sensors Chip support
#

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_AMD_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_FAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_TMPFS is not set
CONFIG_RAMFS=y
# CONFIG_ISO9660_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_MINIX_FS=y
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_EXT2_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_XFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Graphics support
#
# CONFIG_FB is not set

#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_KALLSYMS is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_BIOS_REBOOT=y
-------------------------------------------------------------------

> 
> 
> > 2. linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
> > described in the config file of the technoland board.
> 
> that works too? 
Yes, it boots fine. 
Is it true to say that this could work with a doc2000 also? 
If I dd to the beginning of a doc2000 is that still offset zero , or
should I skip for the (read-only) ipl?  
   
> 
> 
> I thiink you need to get your on-board SDRAM working first. Then let's 
> talk about floppy etc. 
> 
> I would also like to get a source tree for this board into the linuxbios 
> cvs. 

I will do my best to get the onboard ram to work as soon as possible. Or
do you want to add it before that? If you do let me know, then I will
clean it up and send it - cause I am going on a two-weeks vacation
starting from this Thursday. 


Greetings, 

Daniel Toussaint 



From daniel at dmhome.net  Mon Jan 20 03:36:01 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Mon Jan 20 03:36:01 2003
Subject: C&T vga
In-Reply-To: <MDAEMON-F200301171119.AA191543MD55849@bitworks.com>
References: <MDAEMON-F200301171119.AA191543MD55849@bitworks.com>
Message-ID: <20030120020244.4710.qmail@mailshell.com>

On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
> On Fri, 17 Jan 2003 08:37:29 -0800, daniel at dmhome.net wrote:
> 
> > As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
> > 
> 
> If you search hard enough there is a fb driver for the 69000. 
> However, last I looked it had not been worked on in a long while and
> it didn't really work that well.  Chances are it probally won't
> compile anymore with the current fb stuff.  But it might not be that
> much work to fix.  The X 69000 driver works great so you might be
> able to get a lot of code/settings from it if you tried.
> 
> I'm intersted in helping you get the C&T video bios working since our
> system has 2 69000's on it and I'd like them to vga on boot rather
> than wait for  fb or X.
I'm using this :  

option CONFIG_VGABIOS=1
option CONFIG_REALMODE_IDT=1
option CONFIG_PCIBIOS=1

but now it doesn't compile anymore with this error: 

linuxbios_c.o: In function `biosint':
linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'

The makefile doesn't seem to have any references to it after running
NLBconfig, so I will try to add it manually. Any other tips ? 

Thanks , 

Daniel





From daniel at dmhome.net  Mon Jan 20 05:17:00 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Mon Jan 20 05:17:00 2003
Subject: emcore6352
In-Reply-To: <Pine.LNX.4.44.0301171325500.31229-100000@carotid.ccs.lanl.gov>
References: <Pine.LNX.4.44.0301171325500.31229-100000@carotid.ccs.lanl.gov>
Message-ID: <20030120094325.24310.qmail@mailshell.com>

On Sat, 2003-01-18 at 05:13, Ronald G. Minnich wrote:
> On Fri, 17 Jan 2003 daniel at dmhome.net wrote:
> 
> > 1. linuxbios + a minimal 2.5 kernel with kexec in the flash, that
> > executes a 2.4 kernel from an ide harddrive.
> 
> you got a 2.5 kernel + kexec into 512KB?
> 
> Send me kernel version and .config :-)
The latest at that time 2.5.56. Those 2.5 series are not so easy to
compile without networking are they ? It took me several 2.5 versions
and kexec patch combinations before I could get it to compile. 
--------------------------------------------------------
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General setup
#
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_LOG_BUF_SHIFT_17 is not set
# CONFIG_LOG_BUF_SHIFT_16 is not set
# CONFIG_LOG_BUF_SHIFT_15 is not set
CONFIG_LOG_BUF_SHIFT_14=y
# CONFIG_LOG_BUF_SHIFT_13 is not set
# CONFIG_LOG_BUF_SHIFT_12 is not set
CONFIG_LOG_BUF_SHIFT=14

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_PREFETCH=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_KEXEC=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
CONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not set
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_ONLYDISK=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
# CONFIG_NET is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# ISDN subsystem
#

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
# CONFIG_SERIO is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Hardware Sensors Mainboard support
#

#
# I2C Hardware Sensors Chip support
#

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_AMD_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_FAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_TMPFS is not set
CONFIG_RAMFS=y
# CONFIG_ISO9660_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_MINIX_FS=y
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_EXT2_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_XFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Graphics support
#
# CONFIG_FB is not set

#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_KALLSYMS is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_BIOS_REBOOT=y
-------------------------------------------------------------------

> 
> 
> > 2. linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
> > described in the config file of the technoland board.
> 
> that works too? 
Yes, it boots fine. 
Is it true to say that this could work with a doc2000 also? 
If I dd to the beginning of a doc2000 is that still offset zero , or
should I skip for the (read-only) ipl?  
   
> 
> 
> I thiink you need to get your on-board SDRAM working first. Then let's 
> talk about floppy etc. 
> 
> I would also like to get a source tree for this board into the linuxbios 
> cvs. 

I will do my best to get the onboard ram to work as soon as possible. Or
do you want to add it before that? If you do let me know, then I will
clean it up and send it - cause I am going on a two-weeks vacation
starting from this Thursday. 


Greetings, 

Daniel Toussaint 



From daniel at dmhome.net  Mon Jan 20 05:24:32 2003
From: daniel at dmhome.net (daniel at dmhome.net)
Date: Mon Jan 20 05:24:32 2003
Subject: C&T vga
In-Reply-To: <MDAEMON-F200301171119.AA191543MD55849@bitworks.com>
References: <MDAEMON-F200301171119.AA191543MD55849@bitworks.com>
Message-ID: <20030120094340.8717.qmail@mailshell.com>

On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
> On Fri, 17 Jan 2003 08:37:29 -0800, daniel at dmhome.net wrote:
> 
> > As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
> > 
> 
> If you search hard enough there is a fb driver for the 69000. 
> However, last I looked it had not been worked on in a long while and
> it didn't really work that well.  Chances are it probally won't
> compile anymore with the current fb stuff.  But it might not be that
> much work to fix.  The X 69000 driver works great so you might be
> able to get a lot of code/settings from it if you tried.
> 
> I'm intersted in helping you get the C&T video bios working since our
> system has 2 69000's on it and I'd like them to vga on boot rather
> than wait for  fb or X.
I'm using this :  

option CONFIG_VGABIOS=1
option CONFIG_REALMODE_IDT=1
option CONFIG_PCIBIOS=1

but now it doesn't compile anymore with this error: 

linuxbios_c.o: In function `biosint':
linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'

The makefile doesn't seem to have any references to it after running
NLBconfig, so I will try to add it manually. Any other tips ? 

Thanks , 

Daniel





From sivakumar.subramani at wipro.com  Mon Jan 20 21:51:00 2003
From: sivakumar.subramani at wipro.com (sivakumar)
Date: Mon Jan 20 21:51:00 2003
Subject: APM support in linuxbios.
Message-ID: <1043118286.3054.16.camel@Jasmine>

Hi,

When I was reading a document about the APM, it is mentioned that we
need to have BIOS support to have APM on the machine. Also it is
mentioned that if the BIOS is not properly supported it will lead the
APM to crash the system.

So I want to know about APM support in the case of LINUXBIOS.
Can any one help me out?


Also yesterday I have downloaded the latest code of the Linuxbios. Still
now I was working with old source base from sourceforge.net. After
compiling with the new code, I found some new file like c_start.s and
linuxbios_c.*.

what I have to do with these file?

Thanks,
Siva

-- 
sivakumar <sivakumar.subramani at wipro.com>
wipro



From p.richards at overclockers.cl  Tue Jan 21 18:52:01 2003
From: p.richards at overclockers.cl (Paulo Richards)
Date: Tue Jan 21 18:52:01 2003
Subject: Linuxbios on amibios chip
Message-ID: <1043193915.17467.6.camel@Valkyrie>

Hi, i'm interesed in put linux bios but i don't have a DoC, I downloaded
an image for pc chips  (810-ide.rom) from cwlinux.com, i think it is
ready to burn on bios. am I right? I have a pc chips 810 with amibios, I
tried with the program to burn flash images from the pc chips web page
and using the ami program to burn th image, but it doesn't work. My
question is: can I burn a bios with this image using the mainboard (or
do i need a bios burner?)

Thanx

Paulo Richards



From p.richards at overclockers.cl  Tue Jan 21 18:56:00 2003
From: p.richards at overclockers.cl (Paulo Richards)
Date: Tue Jan 21 18:56:00 2003
Subject: Linuxbios on amibios chip
Message-ID: <1043194161.17608.0.camel@Valkyrie>

Hi, i'm interesed in put linux bios but i don't have a DoC, I downloaded
an image for pc chips  (810-ide.rom) from cwlinux.com, i think it is
ready to burn on bios. am I right? I have a pc chips 810 with amibios, I
tried with the program to burn flash images from the pc chips web page
and using the ami program to burn th image, but it doesn't work. My
question is: can I burn a bios with this image using the mainboard (or
do i need a bios burner?)

Thanx

Paulo Richards



From aip at cwlinux.com  Tue Jan 21 21:07:00 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Tue Jan 21 21:07:00 2003
Subject: Linuxbios on amibios chip
In-Reply-To: <1043194161.17608.0.camel@Valkyrie>; from Paulo Richards on Tue, Jan 21, 2003 at 09:09:21PM -0300
References: <1043194161.17608.0.camel@Valkyrie>
Message-ID: <20030122102142.A7097@mail.cwlinux.com>

Paulo,

> Hi, i'm interesed in put linux bios but i don't have a DoC, I downloaded
> an image for pc chips  (810-ide.rom) from cwlinux.com, i think it is
> ready to burn on bios. am I right? I have a pc chips 810 with amibios, I
> tried with the program to burn flash images from the pc chips web page
> and using the ami program to burn th image, but it doesn't work. My
> question is: can I burn a bios with this image using the mainboard (or
> do i need a bios burner?)
You can flash it under Linux.
1. download 
ftp://www.cwlinux.com/pub/downloads/linuxbios-sdk/RPMS/linuxbios-utils-cvs-020906.i386.rpm 
2. install package
$ rpm -Uvh linuxbios-utils-cvs-020906.i386.rpm
3 turn on flash write enable
$ flash_on
4 flash rom
$ flash_rom m810-ide.rom

Hope this help.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030121/dcc60e91/attachment.sig>

From aip at cwlinux.com  Tue Jan 21 21:11:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Tue Jan 21 21:11:01 2003
Subject: APM support in linuxbios.
In-Reply-To: <1043118286.3054.16.camel@Jasmine>; from sivakumar on Tue, Jan 21, 2003 at 08:34:46AM +0530
References: <1043118286.3054.16.camel@Jasmine>
Message-ID: <20030122102544.B7097@mail.cwlinux.com>

Sivakumar,

> When I was reading a document about the APM, it is mentioned that we
> need to have BIOS support to have APM on the machine. Also it is
> mentioned that if the BIOS is not properly supported it will lead the
> APM to crash the system.
> So I want to know about APM support in the case of LINUXBIOS.
> Can any one help me out?
It is not supported.

> Also yesterday I have downloaded the latest code of the Linuxbios. Still
> now I was working with old source base from sourceforge.net. After
> compiling with the new code, I found some new file like c_start.s and
> linuxbios_c.*.
> what I have to do with these file?
I think your code is pretty old.  These files are required.  You also 
probably need to regenerate your build directory to reflect the new
change.

-Andrew

-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030121/82b0b17c/attachment.sig>

From lawrence at tyanchina.com  Wed Jan 22 01:27:01 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Wed Jan 22 01:27:01 2003
Subject: Irq_table not loaded when boot from etherboot
Message-ID: <441383BA85E81D48964152E537886C9D230A72@mail.sh.corp.tyan.com>

Hi,

	I have dumped the two files from my system, but I still have several puzzles:

1. How can replace the "conforms" with "MP_IRQ_TRIGGER_EDGE|MP_IRQ_POLARITY_HIGH" in the mptable.c? Should I ask the hardware Engineer for help?

2. Shall I change following strings in mptable.c to instruction as "smp_write_intsrc(mc, mp_NMI, conforms|conforms, 0x0, 0x0, MP_APIC_ALL, 0x1)" ? If should, how can I do this?
MP Config Extended Table Entries:
--
System Address Space
 bus ID: 0 address type: I/O address
 address base: 0xc000
 address range: 0x3000

	Could you help me to check the files attached? Please teach me how to fix them.

Best Regards,
Lawrence

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: 2003?1?17? 23:06
To: Lawrence LL. Dai
Cc: linuxbios at clustermatic.org
Subject: Re: Irq_table not loaded when boot from etherboot

either you PIRQ table or your MPTABLE or both are wrong. You will need to 
fix this.

ron

-------------- next part --------------
A non-text attachment was scrubbed...
Name: irq_tables.c
Type: application/octet-stream
Size: 1801 bytes
Desc: irq_tables.c
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030122/2cb2acf8/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mptable.c
Type: application/octet-stream
Size: 5629 bytes
Desc: mptable.c
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030122/2cb2acf8/attachment-0001.obj>

From sungeun at lanl.gov  Wed Jan 22 14:30:00 2003
From: sungeun at lanl.gov (Sung-Eun Choi)
Date: Wed Jan 22 14:30:00 2003
Subject: temporary move for the web pages..
Message-ID: <15918.62623.966389.108289@carotid.ccs.lanl.gov>

we've moved the LinuxBIOS web pages off-site for better service, but
we're having some trouble transfering the domain name (long story)
and a few other things.

anyway, in the interim, the web page can be found at:

	http://www.clustermatic.org/lb/

sorry for the inconvenience...

-- Sung


From bari at onelabs.com  Thu Jan 23 03:12:00 2003
From: bari at onelabs.com (Bari Ari)
Date: Thu Jan 23 03:12:00 2003
Subject: Open BIOS for XBox
Message-ID: <3E2FA782.9040100@onelabs.com>

There is an interesting story on Slashdot

http://slashdot.org/

about an open source BIOS for the XBox

http://sourceforge.net/project/showfiles.php?group_id=54192

They say they don't have the video up yet, but it's on the list. Very 
interesting since they seem to have worked out the BIOS for the NVidia 
chipset without any data sheets.

Bari




From sxpert at esitcom.org  Thu Jan 23 08:41:01 2003
From: sxpert at esitcom.org (Amaury Jacquot)
Date: Thu Jan 23 08:41:01 2003
Subject: Trident Cyberblade information
Message-ID: <1043330239.23814.13.camel@fali>

I have the complete trident cyberblade i1 (as implemented in the VT8601
north bridge on my web site.
Also of interest, is the VT1621[M] TV out chip documentation

http://sxpert.esitcom.org

Sincerely

Amaury



From rminnich at lanl.gov  Thu Jan 23 10:35:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 23 10:35:00 2003
Subject: Trident Cyberblade information
In-Reply-To: <1043330239.23814.13.camel@fali>
Message-ID: <Pine.LNX.4.44.0301230849130.28109-100000@carotid.ccs.lanl.gov>

On 23 Jan 2003, Amaury Jacquot wrote:

> I have the complete trident cyberblade i1 (as implemented in the VT8601
> north bridge on my web site. Also of interest, is the VT1621[M] TV out
> chip documentation

Is this non-NDA material? 

ron



From john-at-thinman at nyc.rr.com  Thu Jan 23 12:58:00 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Thu Jan 23 12:58:00 2003
Subject: C&T vga - newbie quests
In-Reply-To: <20030120020244.4710.qmail@mailshell.com>
Message-ID: <BC25EB3F-2FC7-11D7-8ABF-003065F15622@nyc.rr.com>

Hello -> confused newbie here !!

The linuxbios chat, I can follow but I am very intrigued by the vgabios 
since it will help linux on the nanofront and advance my own thinman 
model ***

I am writing a glossary right now and I need to know the difference 
between:

vgabios, framebuffer and X

My understanding is that X is compiled into the vgabios and that a 
framebuffer is a vga card (sun systems)

TIA, yeah.. I know

** I have an organization called the Linux Society, right now at 
http://yahoogroups.com/group/linux-society.  We will soon be a postnuke 
site and will be offering a lot of integration products based on 
completely new ways of booting linux.  Devil-Linux is our standard OS 
install.  The ThinMan is a trademark for a device network that seeks to 
collect pennies from 6 billion humans rather than thousands from a 
hundred million (microsoft)


On Sunday, January 19, 2003, at 09:07 PM, daniel at dmhome.net wrote:

> On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
>> On Fri, 17 Jan 2003 08:37:29 -0800, daniel at dmhome.net wrote:
>> I'm intersted in helping you get the C&T video bios working since our
>> system has 2 69000's on it and I'd like them to vga on boot rather
>> than wait for  fb or X.
> I'm using this :
>
> option CONFIG_VGABIOS=1
> option CONFIG_REALMODE_IDT=1
> option CONFIG_PCIBIOS=1
>
> but now it doesn't compile anymore with this error:
>
> linuxbios_c.o: In function `biosint':
> linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'
>
> The makefile doesn't seem to have any references to it after running
> NLBconfig, so I will try to add it manually. Any other tips ?
>
> Thanks ,
>
> Daniel
>
>
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>



From stuge-linuxbios at cdy.org  Thu Jan 23 20:07:00 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu Jan 23 20:07:00 2003
Subject: C&T vga - newbie quests
In-Reply-To: <BC25EB3F-2FC7-11D7-8ABF-003065F15622@nyc.rr.com>
References: <20030120020244.4710.qmail@mailshell.com> <BC25EB3F-2FC7-11D7-8ABF-003065F15622@nyc.rr.com>
Message-ID: <20030124011119.GC9452@foo.birdnet.se>

On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
> I am writing a glossary right now and I need to know the difference 
> between:
> 
> vgabios, framebuffer and X

Wow, ok, not that this is the best place, but ok.

LinuxBIOS is currently mostly operational on what's commonly referred to as
the PC platform.  The last standardized graphics controller on this platform
was the VGA. (Video Graphics Array)  This VGA card had a BIOS that would
initialize the card when the main system BIOS traversed all expansion cards
looking for any BIOSes on them.

The VGA BIOS knows the details of how to program the graphics card.  The VGA
BIOS is closely tied to every single hardware.  Different graphics chipset -
different VGA BIOS.  Graphics chipset makers are often reluctant to release
detailed programming information for their chipsets, but a VGA BIOS is
always included with the card.  So if LinuxBIOS can make use of the VGA BIOS
it is trivial to use the computer screen e.g. for startup debugging.

'framebuffer' has a couple of different meanings.  One is the video memory
on the graphics card.  Another is the Linux drivers for accessing the said
memory.  Writing a Linux framebuffer driver requires the same detailed
programming information as for a VGA BIOS.  Framebuffer drivers aren't all
that common, it has become sort of a niche, used frequently for Set-Top-Box
and other embedded systems.  (Reference: DirectFB.)  Think of the
framebuffer drivers as a VGA BIOS in Linux for Linux, it allows Linux to
know all (or at least a lot) about the graphics controller in the system.

X is usually short for X-Windows which is the windowing system providing
core GUI functionality in almost all available Unix systems.  When open
source people say X or X server they're often talking about XFree86, an open
source X-Windows server.  The X server also needs detailed knowledge about
graphics chipsets, in order to provide and perform the desired functions in
an efficient manner.


Short summary:

The VGA BIOS, a framebuffer driver and the X server all need detailed info
on programming the graphics controller.  They differ in whom they provide
services for.

The VGA BIOS provides services mainly meant for MS-DOS and
other "classical" textmode applications like LILO and Linux itself.

The framebuffer driver provides services mainly meant for Linux and is also
a part of Linux.

The X server provides services to X clients and/or the window manager.  All
programs run in X are X clients.


Hope this clears it up.


//Peter


From stuge-linuxbios at cdy.org  Thu Jan 23 20:14:00 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu Jan 23 20:14:00 2003
Subject: C&T vga - newbie quests
In-Reply-To: <BC25EB3F-2FC7-11D7-8ABF-003065F15622@nyc.rr.com>
References: <20030120020244.4710.qmail@mailshell.com> <BC25EB3F-2FC7-11D7-8ABF-003065F15622@nyc.rr.com>
Message-ID: <20030124011422.GD9452@foo.birdnet.se>

On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
> 
> Hello -> confused newbie here !!
> 
> The linuxbios chat, I can follow but I am very intrigued by the vgabios 
> since it will help linux on the nanofront and advance my own thinman 
> model ***
> 
> I am writing a glossary right now and I need to know the difference 
> between:
> 
> vgabios, framebuffer and X

I wonder why you didn't google for these first, btw.  Would've given you a
big part of what I wrote in the other mail.


//Peter


From john-at-thinman at nyc.rr.com  Thu Jan 23 22:04:00 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Thu Jan 23 22:04:00 2003
Subject: C&T vga - newbie quests
In-Reply-To: <20030124011119.GC9452@foo.birdnet.se>
Message-ID: <A08E0800-2F4A-11D7-A7C7-003065F15622@nyc.rr.com>

Thanks Peter, but... maybe i should have said:

...In relation to LinuxBIOS...

We know what X and a vgabios are -- what I am asking about are 
references on this mailing list to writing X into a vgabios -- maybe 
VIA -- using code from the bochs vgabios -- or something like that -- 
along w/ Xfree86

Framebuffers are new to me, never really thot about them, I am looking 
of DirectFB right now and it really seems like an acceleration process, 
so I  am wondering why it keeps appearing in LinuxBIOS mailing lists.

What is envisioned for getting X running from LinuxBIOS ??  Clusters 
obviously have no need for them, but there are huge hungry embedded 
people out there.  I would like to join the fray with some useful 
information.

Only part of the need is being kewl, the more important issue becomes 
getting proprietary code out of the PC completely, as dictated by the 
GNU religion, and gaining support among the youth.








On Thursday, January 23, 2003, at 08:11 PM, Peter Stuge wrote:

> On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
>> I am writing a glossary right now and I need to know the difference
>> between:
>>
>> vgabios, framebuffer and X
>
> Wow, ok, not that this is the best place, but ok.
>
> LinuxBIOS is currently mostly operational on what's commonly referred 
> to as
> the PC platform.  The last standardized graphics controller on this 
> platform
> was the VGA. (Video Graphics Array)  This VGA card had a BIOS that would
> initialize the card when the main system BIOS traversed all expansion 
> cards
> looking for any BIOSes on them.
>
> The VGA BIOS knows the details of how to program the graphics card.  
> The VGA
> BIOS is closely tied to every single hardware.  Different graphics 
> chipset -
> different VGA BIOS.  Graphics chipset makers are often reluctant to 
> release
> detailed programming information for their chipsets, but a VGA BIOS is
> always included with the card.  So if LinuxBIOS can make use of the VGA 
> BIOS
> it is trivial to use the computer screen e.g. for startup debugging.
>
> 'framebuffer' has a couple of different meanings.  One is the video 
> memory
> on the graphics card.  Another is the Linux drivers for accessing the 
> said
> memory.  Writing a Linux framebuffer driver requires the same detailed
> programming information as for a VGA BIOS.  Framebuffer drivers aren't 
> all
> that common, it has become sort of a niche, used frequently for 
> Set-Top-Box
> and other embedded systems.  (Reference: DirectFB.)  Think of the
> framebuffer drivers as a VGA BIOS in Linux for Linux, it allows Linux to
> know all (or at least a lot) about the graphics controller in the 
> system.
>
> X is usually short for X-Windows which is the windowing system providing
> core GUI functionality in almost all available Unix systems.  When open
> source people say X or X server they're often talking about XFree86, an 
> open
> source X-Windows server.  The X server also needs detailed knowledge 
> about
> graphics chipsets, in order to provide and perform the desired 
> functions in
> an efficient manner.
>
>
> Short summary:
>
> The VGA BIOS, a framebuffer driver and the X server all need detailed 
> info
> on programming the graphics controller.  They differ in whom they 
> provide
> services for.
>
> The VGA BIOS provides services mainly meant for MS-DOS and
> other "classical" textmode applications like LILO and Linux itself.
>
> The framebuffer driver provides services mainly meant for Linux and is 
> also
> a part of Linux.
>
> The X server provides services to X clients and/or the window manager.  
> All
> programs run in X are X clients.
>
>
> Hope this clears it up.
>
>
> //Peter
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From stuge-linuxbios at cdy.org  Fri Jan 24 06:46:01 2003
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Fri Jan 24 06:46:01 2003
Subject: C&T vga - newbie quests
In-Reply-To: <A08E0800-2F4A-11D7-A7C7-003065F15622@nyc.rr.com>
References: <20030124011119.GC9452@foo.birdnet.se> <A08E0800-2F4A-11D7-A7C7-003065F15622@nyc.rr.com>
Message-ID: <20030124115006.GB20827@foo.birdnet.se>

On Thu, Jan 23, 2003 at 10:19:19PM -0500, John van Vlaaderen wrote:
> Thanks Peter, but... maybe i should have said:
> 
> ...In relation to LinuxBIOS...
> 
> We know what X and a vgabios are -- what I am asking about are 
> references on this mailing list to writing X into a vgabios -- maybe 
> VIA -- using code from the bochs vgabios -- or something like that -- 
> along w/ Xfree86

XFree86 v4 have some provisions for using a VGA BIOS.  If you have a VGA
BIOS in the system you can get XFree86 running.  (Although not at the
highest possible speed with the highest possible resolution or colour
depth.)


> Framebuffers are new to me, never really thot about them, I am looking 
> of DirectFB right now and it really seems like an acceleration process, 
> so I  am wondering why it keeps appearing in LinuxBIOS mailing lists.

Many people are used to having a standard keyboard and a monitor attached to
their computer system, a console.  Because VGA BIOSes often rely heavily on
legacy BIOS services (sorry, should've mentioned this part yesterday) these
VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS doesn't
provide these legacy BIOS services (interrupt services, int 15h etc.  Search
Ralph Brown's interrupt.lst for the keyword BIOS. :) yet.  There is work
underway to add needed parts from the Bochs project's GPL legacy BIOS to
LinuxBIOS, which would also allow all VGA BIOSes to work.

The VGA BIOS and the framebuffer driver serve the same purpose, to activate
the monitor connected to the graphics adapter in the system.  This is more
relevant in some cases than other.  For a GPL desktop system you'd want it. 
For a cluster node you couldn't care less.

The VGA BIOS has an advantage over the framebuffer in that it will be
initialized somewhat earlier, on the other hand I suspect that much of
LinuxBIOS's hard work will already be done when the VGA BIOS gets
initialized so LinuxBIOS debugging will still be best made through the
serial port.  The VGA BIOS is also closed source, of course, which is to
it's disadvantage.


> What is envisioned for getting X running from LinuxBIOS ??  Clusters 
> obviously have no need for them, but there are huge hungry embedded 
> people out there.  I would like to join the fray with some useful 
> information.

If all you want is X and don't care about the Linux text console, you'll
need either a VGA BIOS or a native graphics chipset driver in the X server.
If all you have is the VGA BIOS the X server will have pretty poor
performance.


> Only part of the need is being kewl, the more important issue becomes 
> getting proprietary code out of the PC completely, as dictated by the 
> GNU religion, and gaining support among the youth.

It's coming.  It's just taking some time.  The PC architecture is about 20
years worth of kludges on top of each other.


//Peter


From adam at cfar.umd.edu  Fri Jan 24 06:57:00 2003
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri Jan 24 06:57:00 2003
Subject: C&T vga - newbie quests
In-Reply-To: <20030124115006.GB20827@foo.birdnet.se>
Message-ID: <20030124072312.E35781-100000@www.missl.cs.umd.edu>

> Many people are used to having a standard keyboard and a monitor attached to
> their computer system, a console.  Because VGA BIOSes often rely heavily on
> legacy BIOS services (sorry, should've mentioned this part yesterday) these
> VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS doesn't
> provide these legacy BIOS services (interrupt services, int 15h etc.  Search
> Ralph Brown's interrupt.lst for the keyword BIOS. :) yet.  There is work
> underway to add needed parts from the Bochs project's GPL legacy BIOS to
> LinuxBIOS, which would also allow all VGA BIOSes to work.

It is been already done.

linuxbios supports both standard pc bios services as well as vga bios
(although vga bios is in the binary only form so far).

-- 
Adam Sulmicki
http://www.eax.com 	The Supreme Headquarters of the 32 bit registers



From john-at-thinman at nyc.rr.com  Fri Jan 24 09:16:01 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Fri Jan 24 09:16:01 2003
Subject: C&T vga - newbie quests
In-Reply-To: <20030124072312.E35781-100000@www.missl.cs.umd.edu>
Message-ID: <789CE3EF-2FA8-11D7-A29F-003065F15622@nyc.rr.com>

Thanks Peter and Adam -- now I am no longer an idiot !!

Ps, going to post this on my Linux Society mailing list.  I will have a 
PostNuke site up pretty soon to support news dicussion on this and also 
server side topics.

Pps, Just for reference, my star product has been a cross compiling gcc 
which automated security compiles of various packages, tgz packaging and 
ssh tar-in/tar-out delivery systems where the only OS mods were links 
from /etc/ startup files to local /opt/<app-name>/etc files.  I have 
hoped to make an independent product out of it, based on the highly 
dependable Devil-Linux.org.  (DL is text only by design)

Hence my ingnorace in PC h/w issues ;)  Will anybody be at LinuxWorld 
today at Javits ??

john

On Friday, January 24, 2003, at 07:24 AM, Adam Sulmicki wrote:

>> Many people are used to having a standard keyboard and a monitor 
>> attached to
>> their computer system, a console.  Because VGA BIOSes often rely 
>> heavily on
>> legacy BIOS services (sorry, should've mentioned this part yesterday) 
>> these
>> VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS 
>> doesn't
>> provide these legacy BIOS services (interrupt services, int 15h etc.  
>> Search
>> Ralph Brown's interrupt.lst for the keyword BIOS. :) yet.  There is 
>> work
>> underway to add needed parts from the Bochs project's GPL legacy BIOS 
>> to
>> LinuxBIOS, which would also allow all VGA BIOSes to work.
>
> It is been already done.
>
> linuxbios supports both standard pc bios services as well as vga bios
> (although vga bios is in the binary only form so far).
>
> --
> Adam Sulmicki
> http://www.eax.com 	The Supreme Headquarters of the 32 bit registers
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From ebiederman at lnxi.com  Fri Jan 24 09:41:01 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri Jan 24 09:41:01 2003
Subject: C&T vga - newbie quests
In-Reply-To: <789CE3EF-2FA8-11D7-A29F-003065F15622@nyc.rr.com>
References: <789CE3EF-2FA8-11D7-A29F-003065F15622@nyc.rr.com>
Message-ID: <m3ptqmsikf.fsf@lnxi.com>

John van Vlaaderen <john-at-thinman at nyc.rr.com> writes:

> Thanks Peter and Adam -- now I am no longer an idiot !!
> 
> Ps, going to post this on my Linux Society mailing list.  I will have
> a PostNuke site up pretty soon to support news dicussion on this and
> also server side topics.
> 
> Pps, Just for reference, my star product has been a cross compiling
> gcc which automated security compiles of various packages, tgz
> packaging and ssh tar-in/tar-out delivery systems where the only OS
> mods were links from /etc/ startup files to local /opt/<app-name>/etc
> files.  I have hoped to make an independent product out of it, based
> on the highly dependable Devil-Linux.org.  (DL is text only by design)
> 
> Hence my ingnorace in PC h/w issues ;)  Will anybody be at LinuxWorld
> today at Javits ??

Sorry I just got back.  But there is a 10 node LinuxBIOS cluster
(configure to boot verbosely at 9600 baud instead of fast)  in the
LinuxNetworX display at the intel booth.

Eric



From alesan at manoweb.com  Fri Jan 24 14:13:01 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Fri Jan 24 14:13:01 2003
Subject: best motherboard for linuxbios
Message-ID: <3E319442.3080100@manoweb.com>

Hi. We will have to install linuxbios on a number of systems for 
multimedia applications. Reading the page

http://www.clustermatic.org/lb/status/index.html

it seems that pc-chips motherboards aren't so well supported as I 
thought at first; which socketA mobo would you suggest me for the best 
compatibility with linuxbios? elitegroup k7sem perhaps?


bye & thank you
as






From rminnich at lanl.gov  Fri Jan 24 14:30:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri Jan 24 14:30:00 2003
Subject: best motherboard for linuxbios
In-Reply-To: <3E319442.3080100@manoweb.com>
Message-ID: <Pine.LNX.4.44.0301241243410.6725-100000@carotid.ccs.lanl.gov>

On Fri, 24 Jan 2003, Alessio Sangalli wrote:

> http://www.clustermatic.org/lb/status/index.html
> 
> it seems that pc-chips motherboards aren't so well supported as I 
> thought at first; which socketA mobo would you suggest me for the best 
> compatibility with linuxbios? elitegroup k7sem perhaps?

no, the problem is our status page is way out of date. What pcchips board 
do you want to use? have you considered buying a board from cwlinux.com?

BTW we will in 24 hours have the new web site at the new location.

ron



From thomas at wehrspann.de  Sat Jan 25 06:46:01 2003
From: thomas at wehrspann.de (Thomas Wehrspann)
Date: Sat Jan 25 06:46:01 2003
Subject: best motherboard for linuxbios
References: <3E319442.3080100@manoweb.com>
Message-ID: <009b01c2c469$71e776c0$152ea8c0@lenor>

> it seems that pc-chips motherboards aren't so well supported as I
> thought at first; which socketA mobo would you suggest me for the best
> compatibility with linuxbios? elitegroup k7sem perhaps?

I have no problems with the elitegroup K7SEM for my VDR system.
It runs about half a year now with framebuffer support, network, dvb and no
harddisks.
But harddisks should also work.

Thomas




From niko at isl.net.mx  Sat Jan 25 09:05:01 2003
From: niko at isl.net.mx (Nikolai Vladychevski)
Date: Sat Jan 25 09:05:01 2003
Subject: best motherboard for linuxbios
In-Reply-To: <009b01c2c469$71e776c0$152ea8c0@lenor> 
References: <3E319442.3080100@manoweb.com>
            <009b01c2c469$71e776c0$152ea8c0@lenor>
Message-ID: <20030125011951.5046.qmail@qis>

Thomas Wehrspann writes: 

>> it seems that pc-chips motherboards aren't so well supported as I
>> thought at first; which socketA mobo would you suggest me for the best
>> compatibility with linuxbios? elitegroup k7sem perhaps?
> 
> I have no problems with the elitegroup K7SEM for my VDR system.
> It runs about half a year now with framebuffer support, network, dvb and no

the problem with k7sem is that is discontinued already , so I don't know 
where would you get it. 


nikolai


From john-at-thinman at nyc.rr.com  Sat Jan 25 10:59:01 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Sat Jan 25 10:59:01 2003
Subject: Linux Expo @ Javits
In-Reply-To: <m3ptqmsikf.fsf@lnxi.com>
Message-ID: <13442486-3080-11D7-B47B-003065F15622@nyc.rr.com>

Hi all,

My friends had fun there, but I was disappointed.  I thought all the 
intensity of the past was gone, the big boys profiting  what used to be 
an  independent  domain.

Bout half the cluster companies didnt know what LinuxBIOS is ...

I earned my goodies by evangelizing your work ;)

John

On Friday, January 24, 2003, at 09:56 AM, Eric W. Biederman wrote:

> John van Vlaaderen <john-at-thinman at nyc.rr.com> writes:
>
>> Thanks Peter and Adam -- now I am no longer an idiot !!
>>
>> Ps, going to post this on my Linux Society mailing list.  I will have
>> a PostNuke site up pretty soon to support news dicussion on this and
>> also server side topics.
>>
>> Pps, Just for reference, my star product has been a cross compiling
>> gcc which automated security compiles of various packages, tgz
>> packaging and ssh tar-in/tar-out delivery systems where the only OS
>> mods were links from /etc/ startup files to local /opt/<app-name>/etc
>> files.  I have hoped to make an independent product out of it, based
>> on the highly dependable Devil-Linux.org.  (DL is text only by design)
>>
>> Hence my ingnorace in PC h/w issues ;)  Will anybody be at LinuxWorld
>> today at Javits ??
>
> Sorry I just got back.  But there is a 10 node LinuxBIOS cluster
> (configure to boot verbosely at 9600 baud instead of fast)  in the
> LinuxNetworX display at the intel booth.
>
> Eric
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From john-at-thinman at nyc.rr.com  Sat Jan 25 11:27:00 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Sat Jan 25 11:27:00 2003
Subject: best motherboard for linuxbios
In-Reply-To: <20030125011951.5046.qmail@qis>
Message-ID: <E40CBC70-3083-11D7-B47B-003065F15622@nyc.rr.com>

This has got to be it !!

http://www.mini-itx.com/projects/spacecase/page7.asp

Quiet -- no fans, available from cwlinux, all it needs is datasheets for 
the VgaBIOS ;)

GFX:
Integrated AGP2X with 2D/3D Graphics Acceleration
Motion Compensation for DVD playback
VIP port for video overlay function

PWR:
A company called morex in aisa somewhere makes a power supply that 
converts from AC, you supply the external source.  Car battery, if you 
please ( I do ).

MORE:
http://www.hitechmods.com/reviews/motherboards/VIA_EPIA/via_epia.shtml

http://www.cwlinux.com/eng/products/products_sbc.php


On Friday, January 24, 2003, at 08:19 PM, Nikolai Vladychevski wrote:

> Thomas Wehrspann writes:
>>> it seems that pc-chips motherboards aren't so well supported as I
>>> thought at first; which socketA mobo would you suggest me for the best
>>> compatibility with linuxbios? elitegroup k7sem perhaps?
>> I have no problems with the elitegroup K7SEM for my VDR system.
>> It runs about half a year now with framebuffer support, network, dvb 
>> and no
>
> the problem with k7sem is that is discontinued already , so I don't 
> know where would you get it.
>
> nikolai
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From hansolofalcon at worldnet.att.net  Sat Jan 25 19:48:00 2003
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Sat Jan 25 19:48:00 2003
Subject: Preferences and distributions
Message-ID: <000001c2c4d6$af300340$5bae580c@who5>

Hello again from Gregg C Levine
Just for the sake of argument, and any other supporting reasons, does
anyone have a preference, regarding the distributions that they use?
I, myself, prefer Slackware for most things, and indeed I've been
using it since starting my interests in Linux. But I'm rapidly
reaching the decision that I should use others as well. The next time
a box goes live here, it'll be wearing Debian, instead. So? What does
everyone prefer?
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."? Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )






From john-at-thinman at nyc.rr.com  Sat Jan 25 21:08:00 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Sat Jan 25 21:08:00 2003
Subject: Preferences and distributions
In-Reply-To: <000001c2c4d6$af300340$5bae580c@who5>
Message-ID: <1DCA68B0-30D5-11D7-B47B-003065F15622@nyc.rr.com>

RedHat 8.0 makes the most sense since it is the most common.  Everything 
is available in RH rpm files.

Debian is really good tho... the apt-get function rules, loads packages 
right over the internet.  You can get an image over the net and use it 
load the rest.

I have been hacking Devil-Linux.org into a product called eLSD.  
Devil-Linux is a security product that runs from a CD, many packages.  
Check it out its great.  Mine is an install based on it.  I want to move 
it right into the BIOS :)



On Saturday, January 25, 2003, at 08:02 PM, Gregg C Levine wrote:

> Hello again from Gregg C Levine
> Just for the sake of argument, and any other supporting reasons, does
> anyone have a preference, regarding the distributions that they use?
> I, myself, prefer Slackware for most things, and indeed I've been
> using it since starting my interests in Linux. But I'm rapidly
> reaching the decision that I should use others as well. The next time
> a box goes live here, it'll be wearing Debian, instead. So? What does
> everyone prefer?
> -------------------
> Gregg C Levine hansolofalcon at worldnet.att.net
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."? Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
>
>
>
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From rminnich at lanl.gov  Sat Jan 25 21:43:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Jan 25 21:43:01 2003
Subject: Preferences and distributions
In-Reply-To: <000001c2c4d6$af300340$5bae580c@who5>
Message-ID: <Pine.LNX.4.44.0301251957360.17886-100000@carotid.ccs.lanl.gov>

DOE is kind of a Red Hat outfit. 

You should take a look at gentoo, which is a source-based distribution 
with something like FreeBSD's "ports collection". very neat.

ron



From rminnich at lanl.gov  Sat Jan 25 21:58:59 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Jan 25 21:58:59 2003
Subject: linuxbios (fwd)
Message-ID: <Pine.LNX.4.44.0301251958340.17886-100000@carotid.ccs.lanl.gov>

anyone else seeing this? another sourceforge glitch?

ron
---------- Forwarded message ----------
Date: Sat, 25 Jan 2003 18:43:00 -0700
From: Greg Watson <gwatson at lanl.gov>
To: rminnich at lanl.gov
Subject: linuxbios

Ron,

When I try and checkout the linuxbios source from sourceforge, I get 
the following message:

cvs [checkout aborted]: could not chdir to 
freebios/src/arch/alpha/config: Not a directory


Any ideas?

Greg



From joe at swelltech.com  Sat Jan 25 22:06:46 2003
From: joe at swelltech.com (Joe Cooper)
Date: Sat Jan 25 22:06:46 2003
Subject: Preferences and distributions
In-Reply-To: <000001c2c4d6$af300340$5bae580c@who5>
References: <000001c2c4d6$af300340$5bae580c@who5>
Message-ID: <3E334F01.4000004@swelltech.com>

I'd prefer the list stay on-topic and away from distro flamewars.

Gregg C Levine wrote:
> Hello again from Gregg C Levine
> Just for the sake of argument, and any other supporting reasons, does
> anyone have a preference, regarding the distributions that they use?
> I, myself, prefer Slackware for most things, and indeed I've been
> using it since starting my interests in Linux. But I'm rapidly
> reaching the decision that I should use others as well. The next time
> a box goes live here, it'll be wearing Debian, instead. So? What does
> everyone prefer?

-- 
Joe Cooper <joe at swelltech.com>
Web caching appliances and support.
http://www.swelltech.com



From rminnich at lanl.gov  Sat Jan 25 22:15:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat Jan 25 22:15:01 2003
Subject: Preferences and distributions
In-Reply-To: <1DCA68B0-30D5-11D7-B47B-003065F15622@nyc.rr.com>
Message-ID: <Pine.LNX.4.44.0301251959400.17886-100000@carotid.ccs.lanl.gov>

On Sat, 25 Jan 2003, John van Vlaaderen wrote:

> I have been hacking Devil-Linux.org into a product called eLSD.  
> Devil-Linux is a security product that runs from a CD, many packages.  
> Check it out its great.  Mine is an install based on it.  I want to move 
> it right into the BIOS :)

how much space does it need?

ron



From lawrence at tyanchina.com  Sat Jan 25 22:23:24 2003
From: lawrence at tyanchina.com (Lawrence LL. Dai)
Date: Sat Jan 25 22:23:24 2003
Subject: linuxbios (fwd)
Message-ID: <441383BA85E81D48964152E537886C9D230CCA@mail.sh.corp.tyan.com>

Maybe you use wincvs to check the source code in Windows, the "config" directory and "Config" file together in the same directory will generate conflict.

Lawrence
-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: 2003?1?26? 10:59
To: linuxbios at clustermatic.org
Subject: linuxbios (fwd)


anyone else seeing this? another sourceforge glitch?

ron
---------- Forwarded message ----------
Date: Sat, 25 Jan 2003 18:43:00 -0700
From: Greg Watson <gwatson at lanl.gov>
To: rminnich at lanl.gov
Subject: linuxbios

Ron,

When I try and checkout the linuxbios source from sourceforge, I get 
the following message:

cvs [checkout aborted]: could not chdir to 
freebios/src/arch/alpha/config: Not a directory


Any ideas?

Greg

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From klos1980 at sina.com  Sat Jan 25 22:39:00 2003
From: klos1980 at sina.com (??)
Date: Sat Jan 25 22:39:00 2003
Subject: linuxbios (fwd)
In-Reply-To: <Pine.LNX.4.44.0301251958340.17886-100000@carotid.ccs.lanl.gov>
Message-ID: <000001c2c4ee$8335b1f0$7ca8a8c0@sh.corp.tyan.com>

I met the problem before,
You must checkout the cvs in linux environment!
Or you can download the cvs package first, then checkout it !

Best Regards
Terry Chen
 

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Ronald G. Minnich
Sent: Sunday, January 26, 2003 10:59 AM
To: linuxbios at clustermatic.org
Subject: linuxbios (fwd)


anyone else seeing this? another sourceforge glitch?

ron
---------- Forwarded message ----------
Date: Sat, 25 Jan 2003 18:43:00 -0700
From: Greg Watson <gwatson at lanl.gov>
To: rminnich at lanl.gov
Subject: linuxbios

Ron,

When I try and checkout the linuxbios source from sourceforge, I get 
the following message:

cvs [checkout aborted]: could not chdir to 
freebios/src/arch/alpha/config: Not a directory


Any ideas?

Greg

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios





From rsmith at bitworks.com  Sat Jan 25 23:43:00 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Sat Jan 25 23:43:00 2003
Subject: 440bx build failure
In-Reply-To: <E40CBC70-3083-11D7-B47B-003065F15622@nyc.rr.com>
Message-ID: <MDAEMON-F200301252253.AA533405MD65275@bitworks.com>

I'm finally getting back around to trying to make LinuxBIOS boot on
our 440bx based boards.  I updated my tree to the latest CVS.

Now mu original config file fails to build.

I get undefined reference to 'console_tx_al' and 'console_tx_hex8'

digging around I found the macro where these get called in
'arch/intel.h' 
for 'intel_chip_post_macro()' 

Its wrapped in a 'ifndef SERIAL_POST'  but of course SERIAL_POST is
now always defined.  If I rework the #ifndef to a #if and set
SERIAL_POST to 0 then it builds again.

So this appears to perhaps be a legacy option problem?  Pre the
option bla=1 era.

Looking through things I see that lots has changed in this stuff
since I last looked at it.  I'm not really sure what the right fix is
to make the post codes go out the serial port again.

Attempting to determine whats going on and where things are getting
called from is still a little confusing to me.

What do I need to change to make it work and be a proper config item?

--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   





From rminnich at lanl.gov  Sun Jan 26 01:37:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Jan 26 01:37:00 2003
Subject: linuxbios (fwd)
In-Reply-To: <441383BA85E81D48964152E537886C9D230CCA@mail.sh.corp.tyan.com>
Message-ID: <Pine.LNX.4.44.0301252351440.19224-100000@carotid.ccs.lanl.gov>

On Sun, 26 Jan 2003, Lawrence LL. Dai wrote:

> Maybe you use wincvs to check the source code in Windows, the "config"
> directory and "Config" file together in the same directory will generate
> conflict.

uh oh. I hope there are no committers out there using wincvs ...

ron



From rminnich at lanl.gov  Sun Jan 26 01:47:00 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Jan 26 01:47:00 2003
Subject: 440bx build failure
In-Reply-To: <MDAEMON-F200301252253.AA533405MD65275@bitworks.com>
Message-ID: <Pine.LNX.4.44.0301252355140.19224-100000@carotid.ccs.lanl.gov>

richard, here is a known-good config file for the digital logic 
smartcore-p3, a known-good platform. Just try building with this and see 
how the errors work out :-)

Also what mainboard are you using?


ron



target smartcore-p3

mainboard digitallogic/smartcore-p3

# Enable Serial Console for debugging
option SERIAL_CONSOLE=1
option NO_KEYBOARD=1 
option INBUF_COPY=1
option DEFAULT_CONSOLE_LOGLEVEL=8
option MAXIMUM_CONSOLE_LOGLEVEL=8
option DEBUG=1
option USE_GENERIC_ROM=1

# MEMORY TESTING USING MEMTEST
option USE_ELF_BOOT=1
option RAMTEST=0
option CONFIG_COMPRESS=0
#payload ../eepro100-5.07.ebi
#payload ../memtest86.ebi
#payload ../82559er.ebi 
payload ../memtest




From rsmith at bitworks.com  Sun Jan 26 02:19:00 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Sun Jan 26 02:19:00 2003
Subject: 440bx build failure
In-Reply-To: <Pine.LNX.4.44.0301252355140.19224-100000@carotid.ccs.lanl.gov>
Message-ID: <MDAEMON-F200301260128.AA283513MD65497@bitworks.com>

On Sat, 25 Jan 2003 23:55:56 -0700 (MST), Ronald G. Minnich wrote:

> richard, here is a known-good config file for the digital logic 
> smartcore-p3, a known-good platform. Just try building with this and see 
> how the errors work out :-)
>

Not good... I get nothing.  It built though so I guess thats a step
up.

> Also what mainboard are you using?

The Bitworks IMS board.  Its a custom board we designed.  Looks
really close to the Intel reference design for the 440bx.  We are
using a NSC pc87351 for the superio.  I added that into the p3 config
instead of the SMC but no luck. 

With out SERIAL_POST=1 my config generates output but the ramtest
fails.  So I'm going to start looking at the differences between the
p3 and my IMS config.  Perhaps something will show up.


 
--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   






From rsmith at bitworks.com  Sun Jan 26 03:22:00 2003
From: rsmith at bitworks.com (Richard A. Smith)
Date: Sun Jan 26 03:22:00 2003
Subject: 440bx build failure
In-Reply-To: <Pine.LNX.4.44.0301252355140.19224-100000@carotid.ccs.lanl.gov>
Message-ID: <MDAEMON-F200301260232.AA322119MD65531@bitworks.com>

On Sat, 25 Jan 2003 23:55:56 -0700 (MST), Ronald G. Minnich wrote:

> richard, here is a known-good config file for the digital logic 

Man there is some serious lag from when I send a post and when it
finally hits the list.  I sent a response over an hour ago and its
still not there.

Well anyway.  I got the smartcore-p3 config to do something. 
Actually it worked the first time I just didn't have my serial cable
plugged back in.  Duh!.

The bad news is it dosen't do anything different than my config file.
 When it jumps to Linuxbios in ram it crashes.  

Which is really not suprising since my config file and the smarcore
are pretty much identical.  I didn't have the L440BX option set but
grepping the tree dosen't show that option as doing anything.  The
only place it shows up is in a compiler flag setting in the intel
mainboard dir which isn't called.

I think I'm going to try and hardcode some conservative memory
settings and see if I can get something going,


--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               479.846.5777 x104                        
Sr. Design Engineer        http://www.bitworks.com   




From rminnich at lanl.gov  Sun Jan 26 14:45:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun Jan 26 14:45:01 2003
Subject: 440bx build failure
In-Reply-To: <MDAEMON-F200301260232.AA322119MD65531@bitworks.com>
Message-ID: <Pine.LNX.4.44.0301261300030.1790-100000@carotid.ccs.lanl.gov>

consider putting some dumpnorth calls in your sdram setup code to see 
what's going on.

ron



From tulonja at koti.soon.fi  Mon Jan 27 08:56:01 2003
From: tulonja at koti.soon.fi (Jarmo Tulonen)
Date: Mon Jan 27 08:56:01 2003
Subject: Tiger MPX
Message-ID: <200301271413.h0REDlA13663@smtp2.sooninternet.net>

Hello

I've been testing LinuxBIOS on Tyan's Tiger MPX, using etherboot as 
payload, but with no luck so far. Nothing is output to the serial port and 
nothing sent to the ethernet so I guess I must have something fundamentally
wrong.

Steven : I used as configuration the file "example-normal.config" that you
provided, just replacing the path to etherboot, and the files under 
.../mainboard/tyan/TigerMPX without modification.
I've understood that you tested it on a similar board (or was it the "-4M" 
version ?)

Any ideas how to proceed ?

Jarmo


From jschildt at ahoyhoy.org  Mon Jan 27 12:07:01 2003
From: jschildt at ahoyhoy.org (jschildt at ahoyhoy.org)
Date: Mon Jan 27 12:07:01 2003
Subject: LNXI linuxBIOS ftp site
Message-ID: <1043688133.3e356ac5873f2@my-tools.thenewpush.com>

All,

Packages for LinuxBIOS and our management utilities are now available on our ftp
site->  ftp://ftp.lnxi.com/pub/src/linuxbios

Current boards include:
Supermicro: p4dpr, p4dpe
Tyan: s2466

Utilites: (detailed man pages included)
lbflash - initial flash and BIOS update utility.
cmos_util - CMOS management utility.
bios_copy - creating a backup of the factoryBIOS.
 
I've made them available in RPM, SRPM package format and included a tarball as
well.  It's suggested that you read the NEWS file for the latest update and
feature information on each release.

New revs and board releases will be made available as we develop them.  

--jason--

jschildt at lnxi.com
Software Engineer
LinuxNetworX
_____________________________________________
webmail by http://www.thenewpush.com and IMP
TheNewPush, home for your secure web services


From pyro at linuxlabs.com  Mon Jan 27 13:14:00 2003
From: pyro at linuxlabs.com (steven james)
Date: Mon Jan 27 13:14:00 2003
Subject: Tiger MPX
In-Reply-To: <200301271413.h0REDlA13663@smtp2.sooninternet.net>
Message-ID: <Pine.LNX.4.21.0301271326510.2949-100000@ucontrol.mobiledns.com>

Greetings,

It's confusion over the image names. The fallback image is the one you
want. Fallback has the actual power on reset vector. When normal boot is
configured in CMOS, the fallback image jumps into the 'normal' image early
in the setup. Should that image fail, the next time through, fallback does
it all itself. I should document this!

G'day,
sjames




On Mon, 27 Jan 2003, Jarmo Tulonen wrote:

> Hello
> 
> I've been testing LinuxBIOS on Tyan's Tiger MPX, using etherboot as 
> payload, but with no luck so far. Nothing is output to the serial port and 
> nothing sent to the ethernet so I guess I must have something fundamentally
> wrong.
> 
> Steven : I used as configuration the file "example-normal.config" that you
> provided, just replacing the path to etherboot, and the files under 
> .../mainboard/tyan/TigerMPX without modification.
> I've understood that you tested it on a similar board (or was it the "-4M" 
> version ?)
> 
> Any ideas how to proceed ?
> 
> Jarmo
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 

-- 
-------------------------steven james, director of research, linux labs
... ........ ..... ....                     230 peachtree st nw ste 701
the original linux labs                             atlanta.ga.us 30303
      -since 1995                              http://www.linuxlabs.com
                                   office 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------




From sungeun at lanl.gov  Mon Jan 27 17:28:01 2003
From: sungeun at lanl.gov (Sung-Eun Choi)
Date: Mon Jan 27 17:28:01 2003
Subject: web page back..
Message-ID: <15925.46638.919263.910239@carotid.ccs.lanl.gov>

we finally got our web hosting issues sorted out, so the web pages are
again available at www.linuxbios.org.  if you had any bookmarks into
the original site, they will probably be broken -- sorry about that..

-- Sung


From p.richards at overclockers.cl  Mon Jan 27 19:34:01 2003
From: p.richards at overclockers.cl (Paulo Richards)
Date: Mon Jan 27 19:34:01 2003
Subject: problems with pchips 810lmr
Message-ID: <1043714978.1584.15.camel@Valkyrie>

Hi, i need help about linux bios
I have a 810lmr with an athlon xp 1500+ cpu, and 160MB of ram.
Also i get a DoC to put linux bios on it, i follow the sis630 guide from
the linuxbios website and the Antony Stone's personal experience guide,
i follow every single step, and it's seems to be ok, but when i reboot
the mainboard there's no output on the monitor (don't even a blink), the
keyboard leds (caps lock and scroll lock) start to blink and the hard
drive seems to work (it make noise).
So, i hook up a serial cable for listening the serial port and this is
what i get (attached file).

It's seems to be fine for me, but i don't really know what exactly
means...

There's anyone could help me?
What i did wrong?

Thanks

Paulo Richards 

-------------- next part --------------
LinuxBIOS-1.0.0 Mon Jan 27 19:49:10 CLST 2003 starting...
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.0.0 Mon Jan 27 19:49:10 CLST 2003 booting...
Finding PCI configuration type.
PCI: Using configuration type 1
handle_superio start, nsuperio 1
handle_superio Pass 0, check #0, s 0000ba00 s->super 0000bcb8
handle_superio: Pass 0, Superio SiS 950
handle_superio  port 0x0, defaultport 0x2e
handle_superio  Using port 0x2e
handle_superio Pass 0, done #0
handle_superio done
Scanning PCI bus...PCI: pci_scan_bus for bus 0
PCI: 00:00.0 [1039/0730]
PCI: 00:00.1 [1039/5513]
PCI: 00:01.0 [1039/0008]
PCI: 00:01.1 [1039/0900]
PCI: 00:01.2 [1039/7001]
PCI: 00:01.3 [1039/7001]
PCI: 00:01.4 [1039/7018]
PCI: 00:01.6 [1039/7013]
PCI: 00:02.0 [1039/0001]
PCI: 00:0b.0 [1105/8300]
PCI: pci_scan_bus for bus 1
PCI: 01:00.0 [1039/6300]
PCI: pci_scan_bus returning with max=01
PCI: pci_scan_bus returning with max=01
done
Allocating PCI resources...
ASSIGN RESOURCES, bus 0
PCI: 00:00.0 10 <- [0xf8000000 - 0xfbffffff] mem
PCI: 00:00.1 10 <- [0x00002c90 - 0x00002c93] io
PCI: 00:00.1 14 <- [0x00002ca0 - 0x00002ca3] io
PCI: 00:00.1 18 <- [0x00002cb0 - 0x00002cb3] io
PCI: 00:00.1 1c <- [0x00002cc0 - 0x00002cc3] io
PCI: 00:00.1 20 <- [0x00002c80 - 0x00002c8f] io
PCI: 00:01.1 10 <- [0x00002000 - 0x000020ff] io
PCI: 00:01.1 14 <- [0xfc200000 - 0xfc200fff] mem
PCI: 00:01.2 10 <- [0xfc201000 - 0xfc201fff] mem
PCI: 00:01.3 10 <- [0xfc202000 - 0xfc202fff] mem
PCI: 00:01.4 10 <- [0x00002400 - 0x000024ff] io
PCI: 00:01.4 14 <- [0xfc203000 - 0xfc203fff] mem
PCI: 00:01.6 10 <- [0x00002800 - 0x000028ff] io
PCI: 00:01.6 14 <- [0x00002c00 - 0x00002c7f] io
PCI: 00:02.0 1c <- [0x00001000 - 0x00001fff] bus 1 io
PCI: 00:02.0 24 <- [0xf0000000 - 0xf7ffffff] bus 1 prefmem
PCI: 00:02.0 20 <- [0xfc000000 - 0xfc0fffff] bus 1 mem
ASSIGN RESOURCES, bus 1
PCI: 01:00.0 10 <- [0xf0000000 - 0xf7ffffff] prefmem
PCI: 01:00.0 14 <- [0xfc000000 - 0xfc01ffff] mem
PCI: 01:00.0 18 <- [0x00001000 - 0x0000107f] io
ASSIGNED RESOURCES, bus 1
PCI: 00:0b.0 10 <- [0xfc100000 - 0xfc1fffff] mem
ASSIGNED RESOURCES, bus 0
Allocating VGA resource
done.
Enabling PCI resourcess...PCI: 00:00.0 cmd <- 07
PCI: 00:00.1 cmd <- 01
PCI: 00:01.0 cmd <- 0c
PCI: 00:01.1 cmd <- 03
PCI: 00:01.2 cmd <- 02
PCI: 00:01.3 cmd <- 02
PCI: 00:01.4 cmd <- 03
PCI: 00:01.6 cmd <- 01
PCI: 00:02.0 cmd <- 27
PCI: 00:0b.0 cmd <- 02
PCI: 01:00.0 cmd <- 03
done.
Initializing PCI devices...
PCI devices initialized
totalram: 152M
Initializing CPU #0
Enabling cache...
Setting fixed MTRRs(0-88) type: UC
Setting fixed MTRRs(0-16) type: WB
DONE fixed MTRRs
Setting variable MTRR 0, base:    0MB, range:  128MB, type WB
Setting variable MTRR 1, base:  128MB, range:   16MB, type WB
Setting variable MTRR 2, base:  144MB, range:    8MB, type WB
DONE variable MTRRs
Clear out the extra MTRR's
call intel_enable_fixed_mtrr()
call intel_enable_var_mtrr()
Leave setup_mtrrs
done.

Max cpuid index    : 1
Vendor ID          : AuthenticAMD
Processor Type     : 0x00
Processor Family   : 0x06
Processor Model    : 0x03
Processor Mask     : 0x00
Processor Stepping : 0x01
Feature flags      : 0x0183f9ff


MTRR check
Fixed MTRRs   : Enabled
Variable MTRRs: Enabled

Disabling local apic...done.
CPU #0 Initialized
Enabled in SIS 503 regs 0x40 and 0x45
Shadow memory disabled in SiS 730
handle_superio start, nsuperio 1
handle_superio Pass 1, check #0, s 0000ba00 s->super 0000bcb8
handle_superio: Pass 1, Superio SiS 950
handle_superio  port 0x2e, defaultport 0x2e
handle_superio  Using port 0x2e
handle_superio Pass 1, done #0
handle_superio done
PCCHIPS M810LMR (and similar)...Entering the initregs process
Southbridge fixup done for SIS 503
handle_superio start, nsuperio 1
handle_superio Pass 2, check #0, s 0000ba00 s->super 0000bcb8
handle_superio: Pass 2, Superio SiS 950
handle_superio  port 0x2e, defaultport 0x2e
handle_superio  Using port 0x2e
  Call finishup
handle_superio Pass 2, done #0
handle_superio done
Copying IRQ routing tables to 0xf0000...done.
Verifing priq routing tables copy at 0xf0000...succeed
Wrote linuxbios table at: 00000500 - 00000664  checksum cba
Jumping to linuxbiosmain()...

Welcome to start32, the open sourced starter.
This space will eventually hold more diagnostic information.

January 2000, James Hendricks, Dale Webster, and Ron Minnich.
Version 0.1

init_bytes
Gunzip setup
gunzip_setup
output data is 0x00100000
Gunzipping boot code
    43:fill_inbuf() - ram buffer:0x00018b70
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00010000  block_count:0
inbuf[0] is 0x1f
flush 0x00100000 count 0x00008000
flush 0x00108000 count 0x00008000
flush 0x00110000 count 0x00008000
flush 0x00118000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00020000  block_count:1
inbuf[0] is 0x3c
flush 0x00120000 count 0x00008000
flush 0x00128000 count 0x00008000
flush 0x00130000 count 0x00008000
flush 0x00138000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00030000  block_count:2
inbuf[0] is 0x4d
flush 0x00140000 count 0x00008000
flush 0x00148000 count 0x00008000
flush 0x00150000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00040000  block_count:3
inbuf[0] is 0x94
flush 0x00158000 count 0x00008000
flush 0x00160000 count 0x00008000
flush 0x00168000 count 0x00008000
flush 0x00170000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00050000  block_count:4
inbuf[0] is 0xd7
flush 0x00178000 count 0x00008000
flush 0x00180000 count 0x00008000
flush 0x00188000 count 0x00008000
flush 0x00190000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00060000  block_count:5
inbuf[0] is 0xc5
flush 0x00198000 count 0x00008000
flush 0x001a0000 count 0x00008000
flush 0x001a8000 count 0x00008000
flush 0x001b0000 count 0x00008000
flush 0x001b8000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00070000  block_count:6
inbuf[0] is 0x74
flush 0x001c0000 count 0x00008000
flush 0x001c8000 count 0x00008000
flush 0x001d0000 count 0x00008000
flush 0x001d8000 count 0x00008000
done memcpy_from_doc_mil
    53:fill_inbuf() - nvram:0x00080000  block_count:7
inbuf[0] is 0xc2
flush 0x001e0000 count 0x00008000
flush 0x001e8000 count 0x00008000
flush 0x001f0000 count 0x00008000
flush 0x001f8000 count 0x00008000
flush 0x00200000 count 0x00008000
flush 0x00208000 count 0x00005f00
<983> fini_bytes

command line - [root=/dev/hda1 console=ttyS0,115200 console=tty0 single]
Jumping to boot code

From rminnich at lanl.gov  Mon Jan 27 19:53:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Mon Jan 27 19:53:01 2003
Subject: problems with pchips 810lmr
In-Reply-To: <1043714978.1584.15.camel@Valkyrie>
Message-ID: <Pine.LNX.4.44.0301271808170.11840-100000@carotid.ccs.lanl.gov>

my best guess is your payload is no good. How did you build the payload to 
put into DoC for linuxbios to load?

ron



From hcyun at etri.re.kr  Mon Jan 27 20:55:01 2003
From: hcyun at etri.re.kr (hcyun at etri.re.kr)
Date: Mon Jan 27 20:55:01 2003
Subject: Introducing Qplus Embedded Linux. 
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A9CD652@cms3.etri.re.kr>

Hello, 

I think many people in this list are working on embedded system. 
So I introduce our open-source embedded linux distribution and toolkit
which can compete with commercial embedded linux product such as MontaVista
or Embedix linux. 

It provides intergrated configuration system of kernel and rootfilesystem.
And entire component can be built very easily. If your are trying to make
an small embedded linux system, I think this can be very helpful for you.
Moreover, it's an open-source project. 

If you want to know more about qplus see following links. 

Review of qplus at LinuxDevices.com  
- http://www.linuxdevices.com/articles/AT5640843706.html. 

Sourceforge 
- http://sourceforge.net/projects/qplus

Main homepage
- http://qplus.etri.re.kr/qplus-p/

-
HeeChul Yun,          
Embedded S/W Team at ETRI
phone: +82-42-860-1673

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030127/26076cd6/attachment.html>

From drwho8 at worldnet.att.net  Tue Jan 28 00:34:00 2003
From: drwho8 at worldnet.att.net (Gregg C Levine)
Date: Tue Jan 28 00:34:00 2003
Subject: web page back..
References: <15925.46638.919263.910239@carotid.ccs.lanl.gov>
Message-ID: <3E361A09.F8715C4A@worldnet.att.net>

Hello from Gregg C Levine
Well most of them are. I just tried to access a part of the FAQ, on the
subject of code, and the page in question was indeed brought up, but not
the highlighted word code. That page wasn't found. I'll keep trying.
Gregg C Levine drwho8 at worldnet.att.net
"Gravity and government stop here!"

Sung-Eun Choi wrote:
> 
> we finally got our web hosting issues sorted out, so the web pages are
> again available at www.linuxbios.org.  if you had any bookmarks into
> the original site, they will probably be broken -- sorry about that..
> 
> -- Sung
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


From ebiederman at lnxi.com  Tue Jan 28 00:48:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Tue Jan 28 00:48:00 2003
Subject: [ANNOUNCE] mkelfImage-2.1
Message-ID: <m33cnd7qt8.fsf@lnxi.com>

mkelfImage-2.1 is now released.

mkeflImage is a tool for generating bootable ELF executables suitable
for feeding to LinuxBIOS and etherboot.  Currently it supports the
linux kernel on both the Itanium and x86 architectures.

ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.1.tar.gz
ftp://download.lnxi.com/pub/src/mkelfImage/mkelfImage-2.1.tar.gz

- Broken binutils version available with Redhat 7 are now detected,
  at runtime and an error results instead of broken images.
  Anyone want to update the autoconf script so this fails at build time?
- gzipped kernels are now supported.
- Minor cleanups.

And of course mkelfImage-2.1 is completely in C so it builds images
much faster than mkelfImage-1.x.

Eric



From john-at-thinman at nyc.rr.com  Tue Jan 28 10:36:01 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Tue Jan 28 10:36:01 2003
Subject: IDE H/D Support
In-Reply-To: <m3ptqmsikf.fsf@lnxi.com>
Message-ID: <709BFC9C-32D8-11D7-B633-003065F15622@nyc.rr.com>

Hi, Folks :)

Frigid here in NY !!  Longest cold snap since 1890 -- looks like war on 
the horizon -- probably be pretty quick -- Saddam hottails it to 
Sudan -- or some such.  Market should climb out of the present hole -- 
leaving the likes of us to CPR the global economy.

My big question of the day:

Will LinuxBIOS be able to support several IDE cards ??  I actually used 
to have a PCI IDE harddrive controller.  These days one would by the 
3ware (linux friendly) mirroring card.

For a consumer portal and home support system, this would be 
fantastic -- passing down the savings on 200GB disks that are only 
slightly more expensive than 20GB disks.


On Friday, January 24, 2003, at 09:56 AM, Eric W. Biederman wrote:

> John van Vlaaderen <john-at-thinman at nyc.rr.com> writes:
>
>> Thanks Peter and Adam -- now I am no longer an idiot !!
>>
>> Ps, going to post this on my Linux Society mailing list.  I will have
>> a PostNuke site up pretty soon to support news dicussion on this and
>> also server side topics.
>>
>> Pps, Just for reference, my star product has been a cross compiling
>> gcc which automated security compiles of various packages, tgz
>> packaging and ssh tar-in/tar-out delivery systems where the only OS
>> mods were links from /etc/ startup files to local /opt/<app-name>/etc
>> files.  I have hoped to make an independent product out of it, based
>> on the highly dependable Devil-Linux.org.  (DL is text only by design)
>>
>> Hence my ingnorace in PC h/w issues ;)  Will anybody be at LinuxWorld
>> today at Javits ??
>
> Sorry I just got back.  But there is a 10 node LinuxBIOS cluster
> (configure to boot verbosely at 9600 baud instead of fast)  in the
> LinuxNetworX display at the intel booth.
>
> Eric
>
>
  CXN, Inc. Contact: john at thinman.com
President, The Linux Society
http://groups.yahoo.com/group/linux-society
linux society distro -> http://www.thinman.com/eLSD/readme
ThinMan is a registered trademark of CXN, Inc.



From rminnich at lanl.gov  Tue Jan 28 11:01:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue Jan 28 11:01:01 2003
Subject: IDE H/D Support
In-Reply-To: <709BFC9C-32D8-11D7-B633-003065F15622@nyc.rr.com>
Message-ID: <Pine.LNX.4.44.0301280914010.17459-100000@carotid.ccs.lanl.gov>

On Tue, 28 Jan 2003, John van Vlaaderen wrote:

> Will LinuxBIOS be able to support several IDE cards ??  I actually used 
> to have a PCI IDE harddrive controller.  These days one would by the 
> 3ware (linux friendly) mirroring card.

The current complexity of the IDE drivers in Linux is something I would 
rather avoid in linuxbios. But demand has always been the driver, note 
that we can even boot over serial nowadays (!).

However it seems more sensible to Let Etherboot Do It, or Steve Jame's 
Forth boot code that he had at SC 2002, or even Linux with a big enough 
Flash. I still most prefer Linux as my boot loader as that has had the 
fewest hardware glitches across the 10 or so platforms I currently 
directly use.

ron



From jschildt at ahoyhoy.org  Tue Jan 28 12:26:00 2003
From: jschildt at ahoyhoy.org (jschildt at ahoyhoy.org)
Date: Tue Jan 28 12:26:00 2003
Subject: [ANNOUNCE] mkelfImage-2.1
In-Reply-To: <m33cnd7qt8.fsf@lnxi.com>
References: <m33cnd7qt8.fsf@lnxi.com>
Message-ID: <1043775694.3e36c0ce517ad@my-tools.thenewpush.com>

For those of you wanting the fixed binutils, the following are available:

ftp://ftp.lnxi.com/pub/src/linuxbios/binutils-2.12.90.0.9-1.src.rpm
ftp://ftp.lnxi.com/pub/src/linuxbios/binutils-2.12.90.0.9-1.i386.rpm

--jason--

Quoting "Eric W. Biederman" <ebiederman at lnxi.com>:

> 
> mkelfImage-2.1 is now released.
> 
> mkeflImage is a tool for generating bootable ELF executables suitable
> for feeding to LinuxBIOS and etherboot.  Currently it supports the
> linux kernel on both the Itanium and x86 architectures.
> 
> ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.1.tar.gz
> ftp://download.lnxi.com/pub/src/mkelfImage/mkelfImage-2.1.tar.gz
> 
> - Broken binutils version available with Redhat 7 are now detected,
>   at runtime and an error results instead of broken images.
>   Anyone want to update the autoconf script so this fails at build time?
> - gzipped kernels are now supported.
> - Minor cleanups.
> 
> And of course mkelfImage-2.1 is completely in C so it builds images
> much faster than mkelfImage-1.x.
> 
> Eric
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



_____________________________________________
webmail by http://www.thenewpush.com and IMP
TheNewPush, home for your secure web services


From alesan at manoweb.com  Tue Jan 28 14:28:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Tue Jan 28 14:28:00 2003
Subject: ECS K7SOM - sis 740
Message-ID: <3E36DDC3.5020307@manoweb.com>

Hi. They gave to me a motherboard ECS K7SOM (socket A (Athlon 2000+), 
svga audio lan 56k) with _DDR_ memory. The nb is sis 740.

I need IDE boot. Is it possible to have it working with linuxbios?


bye, thank you
as





From john-at-thinman at nyc.rr.com  Wed Jan 29 10:14:01 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Wed Jan 29 10:14:01 2003
Subject: Testbios, Emulator ?? -- for uClibc/Busybox distro
In-Reply-To: <13442486-3080-11D7-B47B-003065F15622@nyc.rr.com>
Message-ID: <81B018FD-339E-11D7-AE84-003065F15622@nyc.rr.com>

Hi Folks -- I am getting ready to automate a busybox/uClib nano-distro 
building kit.

I will be testing the distro in Bochs -- as soon as I get it working -- 
but I am wondering if there is some way to develop it for LinuxBIOS in 
an emulator as well.

Its purpose is to create a front-end boot linux to support CDs Initrd 
where the boot linux builds up the system safely to possibly hand-over 
to another linux, including a new kernel.

That would enable a snazzy step-by-step install process which uses a 
legitimate linux to build a more-legitimate linux from net-modules -- or 
other OS.  The distro should be able to live in the bios as well.

The purpose of the distro would be defined by the needs of the 
particular users, but I would be most pleased to be able to consistently 
supply a fresh uClibc and Busybox environment, especially for newer 
developers.

Thanks, John



From ebiederman at lnxi.com  Wed Jan 29 17:29:00 2003
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed Jan 29 17:29:00 2003
Subject: [fb-d] (no subject)
In-Reply-To: <000a01c2c7e5$2c5fa8a0$4c1c1f41@insight.rr.com>
References: <000a01c2c7e5$2c5fa8a0$4c1c1f41@insight.rr.com>
Message-ID: <m3lm13wp4z.fsf@lnxi.com>

"JAson Hensler" <omegadraconis at insight.rr.com> writes:

> Hey,
> I'm i was wondering if the i440 bx chipsets are supported. 
Yes, there are motherboards using the 440bx chipset in the tree.

> My mb is an asus pbp. I have 256ram(read as only 128 for some
> reason) and am looking to clear this problem up thanks,

Dig into the code and have fun.

The primary discussion list is linuxbios at clustermatic.org

Eric



From p.richards at overclockers.cl  Wed Jan 29 20:07:00 2003
From: p.richards at overclockers.cl (Paulo Richards)
Date: Wed Jan 29 20:07:00 2003
Subject: keyboard problem
Message-ID: <1043889756.2498.15.camel@Valkyrie>

Hi, i finally succeeded burning the DoC, with linuxbios and my custom
kernel, loading the root file system on hda1.. it works almost perfect,
but i can't get keyboard working, I searched on the web, but i found
nothing useful (i made what Antony Stone wrote on his guide, but still
don't work), I don't Know if is problem of the kernel or my linuxbios
configuration.

Any idea how can i fix it?

There are attached the linuxbios and kernel configs files, if you want
to take a look, please tell me if anything is missing or are something
wrong.

Thanks

Paulo Richards

PD: i'm working with a pcchips 810lmr
-------------- next part --------------
#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_SMP is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set

#
# General setup
#
# CONFIG_NET is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
CONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not set
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PM is not set
# CONFIG_ACPI is not set
# CONFIG_APM is not set

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CHAR=m
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
CONFIG_NFTL=m
CONFIG_NFTL_RW=y

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
# CONFIG_MTD_GEN_PROBE is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
# CONFIG_MTD_SC520CDP is not set
# CONFIG_MTD_NETSC520 is not set
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_ELAN_104NC is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_MIXMEM is not set
# CONFIG_MTD_OCTAGON is not set
# CONFIG_MTD_VMAX is not set
# CONFIG_MTD_L440GX is not set
# CONFIG_MTD_AMD766ROM is not set
# CONFIG_MTD_ICH2ROM is not set
# CONFIG_MTD_PCI is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
# CONFIG_MTD_DOC1000 is not set
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADVANCED=y
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_DOCPROBE_HIGH=y
# CONFIG_MTD_DOCPROBE_55AA is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CMD680 is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# ISDN subsystem
#

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=m
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_PHILIPSPAR is not set
# CONFIG_I2C_ELV is not set
# CONFIG_I2C_VELLEMAN is not set
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_PROC is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_MOUSE is not set

#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_AMD_RNG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_MSDOS_FS is not set
# CONFIG_UMSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_MINIX_FS=y
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_SMB_FS is not set
# CONFIG_ZISOFS_FS is not set
# CONFIG_ZLIB_FS_INFLATE is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_RIVA is not set
# CONFIG_FB_CLGEN is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_HGA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set

#
# SiSFB Lite support
#
CONFIG_FB_SIS=y
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
# CONFIG_FB_SIS_VIDEO is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB32=y
# CONFIG_FBCON_FONTWIDTH8_ONLY is not set
# CONFIG_FBCON_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set

#
# LinuxBIOS
#
CONFIG_LINUXBIOS=y

#
# Linuxbios Options
#
CONFIG_LINUXBIOS_PM=y
CONFIG_LINUXBIOS_PM_SIS503=y
# CONFIG_LINUXBIOS_PM_PIIX4E is not set
-------------- next part --------------
# Sample config file for PCCHIPS M810LMR with DoC Millennium (as root)
# This will make a target directory of ./pcchips
target pcchips

# PCCHIPS M810LMR mainboard
mainboard pcchips/m810lmr

# Enable Serial Console for debugging
option SERIAL_CONSOLE=1

# use DOC MIL
option USE_DOC_MIL=1
docipl northsouthbridge/sis/730/ipl.S

# Use the internal VGA frame buffer device
option HAVE_FRAMEBUFFER=1

# Path to your kernel (vmlinux)
linux /usr/src/linux

# Kernel command line parameters
commandline root=/dev/hda1 console=ttyS0,115200 console=tty0 single

cpu k7


From bonomo at sal.wisc.edu  Wed Jan 29 20:30:01 2003
From: bonomo at sal.wisc.edu (Richard Bonomo)
Date: Wed Jan 29 20:30:01 2003
Subject: BIOS replacement Intel '486
Message-ID: <200301281811.h0SIBp8128596@maddog.sal.wisc.edu>

Hello!

I am working with a Real Time Devices PC-104
standard system equipped with a '486DX processor,
and.  In order to decrease boot time to our OS
(which is QNX/Neutrino) I would like to eliminate
the BIOS, replacing it with my own code which does
minimal initialization, and then loads the OS 
immediately (the OS is not dependent on BIOS
calls).  If anyone who has done this sort of thing
before is willing to spend a few minutes on the telephone 
with me, I'd be most appreciative.  Roy Minnich
of LANL appears willing, but he is out for a number
of days.

Thank you.

Richard B. 

P.S. please reply direct.

-- 
************************************************
Richard Bonomo
UW Space Astronomy Laboratory
ph: (608) 263-4683 telefacsimile: (608) 263-0361
SAL-related email: bonomo at sal.wisc.edu
all other email: bonomo at ece.wisc.edu
web page URL: http://www.cae.wisc.edu/~bonomo
************************************************


From sivakumar.subramani at wipro.com  Thu Jan 30 03:55:01 2003
From: sivakumar.subramani at wipro.com (siva)
Date: Thu Jan 30 03:55:01 2003
Subject: APM /  ACPI support in linuxbios.
References: <1043118286.3054.16.camel@Jasmine> <20030122102544.B7097@mail.cwlinux.com>
Message-ID: <3E38EBFD.2010003@wipro.com>

What about the ACPI tables. Whether the Linuxbios support ACPI?

Thanks,
Siva


Andrew Ip wrote:

>Sivakumar,
>
>  
>
>>When I was reading a document about the APM, it is mentioned that we
>>need to have BIOS support to have APM on the machine. Also it is
>>mentioned that if the BIOS is not properly supported it will lead the
>>APM to crash the system.
>>So I want to know about APM support in the case of LINUXBIOS.
>>Can any one help me out?
>>    
>>
>It is not supported.
>
>  
>
>>Also yesterday I have downloaded the latest code of the Linuxbios. Still
>>now I was working with old source base from sourceforge.net. After
>>compiling with the new code, I found some new file like c_start.s and
>>linuxbios_c.*.
>>what I have to do with these file?
>>    
>>
>I think your code is pretty old.  These files are required.  You also 
>probably need to regenerate your build directory to reflect the new
>change.
>
>-Andrew
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030130/a1a48d00/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030130/a1a48d00/attachment.txt>

From rminnich at lanl.gov  Thu Jan 30 10:24:01 2003
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu Jan 30 10:24:01 2003
Subject: APM /  ACPI support in linuxbios.
In-Reply-To: <3E38EBFD.2010003@wipro.com>
Message-ID: <Pine.LNX.4.44.0301300840160.3702-100000@carotid.ccs.lanl.gov>

On Thu, 30 Jan 2003, siva wrote:

> What about the ACPI tables. Whether the Linuxbios support ACPI?

no, and that's a good thing. The kernel can do the hard part of ACPI, so 
we just need ACPI tables but not ACPI support. 

ron



From alesan at manoweb.com  Thu Jan 30 14:44:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Thu Jan 30 14:44:00 2003
Subject: pc chips 810
Message-ID: <3E3984C5.4090002@manoweb.com>

Hi. Still waiting for our burocracy to buy cwlinux motherboards, we got 
a pcchips 810 lmr motherboard.

I've download the prepackaged image from cwlinux website and the cvs 
version of freebios. I flashed the file:

ftp.cwlinux.com/pub/downloads/linuxbios-sdk/images/romimages/m810-ide.rom


on the hard disk, connected as hda, I've made a partition hda1 of few MB 
and formatted as ext2. Here I've placed a kernel compiled from vanilla 
2.4.20 sources and processed with:

mkelfImage --kernel=/usr/src/linux-2.4.20/linux/arch/i386/boot/bzImage 
--command-line="console=ttyS0,115200 CONSOLE=ttyS0,115200 root=/dev/hda1 
video=sisfb:640x480-8 at 60,font:VGA8x16" --output=kernel.elf

I've renamed the kernel.elf image in "kernel" and I put it on hda1. hda2 
is my root fs.

When I turn the computer on, I can see (as soon as the monitor resumes 
from the silly dpms powerdown) a tux logo and a cursor flashing.

On a serial terminal I get the attached log.

At this point caps lock and no scroll leds are blinking.

Frame buffer seems to work well! Why isn't my system booting properly?


bye thank you
as



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bios-output.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030130/974e088d/attachment.txt>

From aip at cwlinux.com  Thu Jan 30 19:04:01 2003
From: aip at cwlinux.com (Andrew Ip)
Date: Thu Jan 30 19:04:01 2003
Subject: pc chips 810
In-Reply-To: <3E3984C5.4090002@manoweb.com>; from Alessio Sangalli on Thu, Jan 30, 2003 at 09:02:13PM +0100
References: <3E3984C5.4090002@manoweb.com>
Message-ID: <20030131082042.B3877@mail.cwlinux.com>

Can you send the kernel config also??

-Andrew
-- 
Andrew Ip
Email:  aip at cwlinux.com
Tel:    (852) 2542 2046
Fax:    (852) 2542 2036
Mobile: (852) 9201 9866

Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi Kok, Kowloon,
Hong Kong.

Tel: (852)2542 2046
Fax: (852)2542 2036

For public pgp key, please obtain it from http://www.keyserver.net/en.

On Thu, Jan 30, 2003 at 09:02:13PM +0100, Alessio Sangalli wrote:
> I've download the prepackaged image from cwlinux website and the cvs 
> version of freebios. I flashed the file:
> 
> ftp.cwlinux.com/pub/downloads/linuxbios-sdk/images/romimages/m810-ide.rom
> 
> 
> on the hard disk, connected as hda, I've made a partition hda1 of few MB 
> and formatted as ext2. Here I've placed a kernel compiled from vanilla 
> 2.4.20 sources and processed with:
> 
> mkelfImage --kernel=/usr/src/linux-2.4.20/linux/arch/i386/boot/bzImage 
> --command-line="console=ttyS0,115200 CONSOLE=ttyS0,115200 root=/dev/hda1 
> video=sisfb:640x480-8 at 60,font:VGA8x16" --output=kernel.elf
> 
> I've renamed the kernel.elf image in "kernel" and I put it on hda1. hda2 
> is my root fs.
> 
> When I turn the computer on, I can see (as soon as the monitor resumes 
> from the silly dpms powerdown) a tux logo and a cursor flashing.
> 
> On a serial terminal I get the attached log.
> 
> At this point caps lock and no scroll leds are blinking.
> 
> Frame buffer seems to work well! Why isn't my system booting properly?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030130/fb77057e/attachment.sig>

From alesan at manoweb.com  Fri Jan 31 03:02:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Fri Jan 31 03:02:00 2003
Subject: pc chips 810
In-Reply-To: <3E3984C5.4090002@manoweb.com>
References: <3E3984C5.4090002@manoweb.com> <20030131082042.B3877@mail.cwlinux.com>
Message-ID: <3E3A31A8.80304@manoweb.com>


Andrew Ip wrote:

> Can you send the kernel config also??


I'm not on that system now... I will try to get the kernel config asap. 
I wonder if I should apply some patch or configure some specific option. 
If yes, please do.

The kernel is not very thin because we need many drivers for video 
acquisition etc. I've setup the sis drivers for IDE, agp/dri, sound and 
framebuffer (a regular boot with normal BIOS and the append line in LILO 
shows the framebuffer without problems)

Should I use a kernel from your ftp?

thank you
as






From alesan at manoweb.com  Fri Jan 31 05:26:00 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Fri Jan 31 05:26:00 2003
Subject: pc chips 810
In-Reply-To: <3E3984C5.4090002@manoweb.com>
References: <3E3984C5.4090002@manoweb.com> <20030131082042.B3877@mail.cwlinux.com>
Message-ID: <3E3A537B.5010504@manoweb.com>



Andrew Ip wrote:

> Can you send the kernel config also??


I attache the kenrenl config I've used (for a VANILLA 2.4.20)

bye and thank you
as




-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pcchips810.config
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20030131/59d0f4d7/attachment.ksh>

From jallen at integraltech.com  Fri Jan 31 10:15:01 2003
From: jallen at integraltech.com (John Allen)
Date: Fri Jan 31 10:15:01 2003
Subject: giving the user a boot option
Message-ID: <3E3A96C9.1020300@integraltech.com>

Does anyone think it is possible the offer the user a choice of 
commandline parameters.  I would like to use the serial console, or 
something else convienient, to allow the user to choose commandline1 or 
commandline2.  One of them mounts root over nfs, the other from the hard 
drive.  I guess this would be a simplified boot loader such as lilo or 
grub.  Unfortunately this 'boot loader'  must reside in the flash chip, 
since my hard drive will initially be completely blank.

John



From adam at cfar.umd.edu  Fri Jan 31 11:12:00 2003
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri Jan 31 11:12:00 2003
Subject: giving the user a boot option
In-Reply-To: <3E3A96C9.1020300@integraltech.com>
Message-ID: <20030131114220.P64285-100000@www.missl.cs.umd.edu>

> Does anyone think it is possible the offer the user a choice of
> commandline parameters.  I would like to use the serial console, or
> something else convienient, to allow the user to choose commandline1 or
> commandline2.  One of them mounts root over nfs, the other from the hard
> drive.  I guess this would be a simplified boot loader such as lilo or
> grub.  Unfortunately this 'boot loader'  must reside in the flash chip,
> since my hard drive will initially be completely blank.

Well, u could put grub or lilo on flash, either of them works with
linuxbios. The space may be big tight though.

-- 
Adam Sulmicki
http://www.eax.com 	The Supreme Headquarters of the 32 bit registers



From steve at nexpath.com  Fri Jan 31 12:53:00 2003
From: steve at nexpath.com (Steve M. Gehlbach)
Date: Fri Jan 31 12:53:00 2003
Subject: giving the user a boot option
In-Reply-To: <20030131114220.P64285-100000@www.missl.cs.umd.edu>
Message-ID: <BPEDILBPDCBCGKGGANJLAEOPEDAA.steve@nexpath.com>

> Well, u could put grub or lilo on flash, either of them works with
> linuxbios. The space may be big tight though.


Maybe I'm missing something here, but I don't understand how you do this.
Grub and lilo require a legacy BIOS.


-Steve



From adam at cfar.umd.edu  Fri Jan 31 12:56:01 2003
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri Jan 31 12:56:01 2003
Subject: giving the user a boot option
In-Reply-To: <BPEDILBPDCBCGKGGANJLAEOPEDAA.steve@nexpath.com>
Message-ID: <20030131132537.B66184-100000@www.missl.cs.umd.edu>

> > Well, u could put grub or lilo on flash, either of them works with
> > linuxbios. The space may be big tight though.
>
> Maybe I'm missing something here, but I don't understand how you do this.
> Grub and lilo require a legacy BIOS.

LinuxBIOS + ADLO + BOCHS BIOS + ( LILO | GRUB )

Adam,
who's for time beeing been (stolen|borrowed|reassigned) to wireless group.

-- 
Adam Sulmicki
http://www.eax.com 	The Supreme Headquarters of the 32 bit registers



From john-at-thinman at nyc.rr.com  Fri Jan 31 14:19:01 2003
From: john-at-thinman at nyc.rr.com (John van Vlaaderen)
Date: Fri Jan 31 14:19:01 2003
Subject: Kernel Repository ??  Config Files ??
In-Reply-To: <BPEDILBPDCBCGKGGANJLAEOPEDAA.steve@nexpath.com>
Message-ID: <2734770D-3553-11D7-9A50-003065F15622@nyc.rr.com>

Hello --

I am getting ready to create a student Bochs development environment 
including the latest uClibc-only env and Busybox.

uClibc and Busybox are easy.. but where do I get kernels ??

Or more useful -- where do I get config files and LinuxBIOS compile 
instructions and standards ??

Thx, John



From alesan at manoweb.com  Fri Jan 31 15:52:01 2003
From: alesan at manoweb.com (Alessio Sangalli)
Date: Fri Jan 31 15:52:01 2003
Subject: sourceforge cvs and wrong web page
Message-ID: <3E3AE649.3080109@manoweb.com>

Hi. On http://www.linuxbios.org/developer/download/index.html you show 
the commands to checkout linuxbioss from sourceforge cvs:

cvs -d:pserver:anonymous at cvs.freebios.sourceforge.net:/cvsroot/freebios 
login

cvs-z3 
-d:pserver:anonymous at cvs.freebios.sourceforge.net:/cvsroot/freebios co 
freebios

this is wrong and "cvs.sourceforge.net" should be used (or you won't be 
able to download anything).

bye
as






From gonzapata at vtr.net  Fri Jan 31 18:27:01 2003
From: gonzapata at vtr.net (gonzapata at vtr.net)
Date: Fri Jan 31 18:27:01 2003
Subject: keyboard enable
Message-ID: <3E0445DC000291CA@hudson.vtr.net>

Hi, I wanna know if there is a parameter for the config file of linuxbios
to active the keyboard, everything works fine except that i don't have keyboard.

Thanx

Gonzalo Zapata