From bari at onelabs.com  Mon May  3 11:54:00 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon May  3 11:54:00 2004
Subject: LinuxBIOS Video?
In-Reply-To: <5.2.1.1.2.20040430113521.00bbca80@mail.sizzard.com>
References: <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> <5.2.1.1.2.20040430113521.00bbca80@mail.sizzard.com>
Message-ID: <40967D37.9040901@onelabs.com>

What's the possibility of getting either ATI family parts to work with 
non-x86 platforms, ARM in particular?

-Bari

aphthong at sizzard.com wrote:

> I would recommend the newer tree.  It's still pretty cryptic, but much 
> cleaner than the old tree.  It took me about three weeks to get a new 
> NB/SB up and running.  But I had to deal with hardware that was being 
> debugged at the same time.
> 
> I'll let you know when I get it up and running.
> 
> Jordan
> 
> At 09:03 AM 4/30/2004, Richard Smith wrote:
> 
>> aphthong at sizzard.com wrote:
>>
>>> Yeah, I am getting access to ATI info.  Because of the NDA I don't 
>>> know how much I can release through GPL.  My second problem there is 
>>> that the linuxbios2 tree has drifted enough that it may be too much 
>>> of a pain to
>>
>>
>> Ask and see.  I asked and got full permission to release any code I 
>> generate under GPL.
>>
>> I'm working with v1.  The 440bx tree hasn't been ported.  Well right 
>> now its not even linuxbios.  My board boots linux bios but I'm running 
>> user space app from a serial console.
>>
>> Perhaps we can compare notes once both of us get something working.
>>
>>
>> _______________________________________________
>> 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
> 
> 




From rminnich at lanl.gov  Mon May  3 12:06:43 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May  3 12:06:43 2004
Subject: LinuxBIOS Video?
In-Reply-To: <40967D37.9040901@onelabs.com>
Message-ID: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>

we are working on putting the emulator into linuxbios as an optional 
component. Once this is done, I think the prognosis is good. We've gotten 
distracted by fixing other things needed to support the emulator.

ron



From bari at onelabs.com  Mon May  3 13:27:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon May  3 13:27:01 2004
Subject: Non-x86 Video
In-Reply-To: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>
Message-ID: <4096930A.7060904@onelabs.com>

ron minnich wrote:

> we are working on putting the emulator into linuxbios as an optional 
> component. Once this is done, I think the prognosis is good. We've gotten 
> distracted by fixing other things needed to support the emulator.

What will be needed to run video on non-x86? The oem videoBIOS plus an 
8086 emulator for when videoBIOS calls are made?

Is this how the layers end up for video?

video application
-----------------
   GUI/OS Linux
-----------------
   8086 emulator
-----------------
    videoBIOS
-----------------
graphics hardware

-Bari




From stepan at openbios.org  Mon May  3 13:38:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May  3 13:38:00 2004
Subject: Non-x86 Video
In-Reply-To: <4096930A.7060904@onelabs.com>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov> <4096930A.7060904@onelabs.com>
Message-ID: <20040503185417.GA450@openbios.org>

* Bari Ari <bari at onelabs.com> [040503 20:44]:
> What will be needed to run video on non-x86? The oem videoBIOS plus an 
> 8086 emulator for when videoBIOS calls are made?
 
Once the operating system is running no video bios calls are needed.
It's all only about initializing the graphics hardware in first place.
Today's graphics cards need complex ram setup, mode initialization, etc.

> Is this how the layers end up for video?
> 
> video application
> -----------------
>   GUI/OS Linux
> -----------------
>   8086 emulator
> -----------------
>    videoBIOS
> -----------------
> graphics hardware

The x86 emulation would be running as part of LinuxBIOS, or as a user
space program. Once video is initialized, Linux can take over the
hardware and use it's own drivers (which are not capable to initialize
the hardware from power on)

    Stefan



From rminnich at lanl.gov  Mon May  3 13:44:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May  3 13:44:01 2004
Subject: Non-x86 Video
In-Reply-To: <4096930A.7060904@onelabs.com>
Message-ID: <Pine.LNX.4.44.0405031259290.13873-100000@maxroach.lanl.gov>

On Mon, 3 May 2004, Bari Ari wrote:

> What will be needed to run video on non-x86? The oem videoBIOS plus an 
> 8086 emulator for when videoBIOS calls are made?

we don't plan to support videoBIOS calls, just plan to support enabling 
the hardware. 

ron
> 
> video application
> -----------------
>    GUI/OS Linux
> -----------------

that's it.

ron



From rsmith at bitworks.com  Mon May  3 13:50:00 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Mon May  3 13:50:00 2004
Subject: LinuxBIOS Video?
In-Reply-To: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>
Message-ID: <40969808.8080206@bitworks.com>

ron minnich wrote:
> we are working on putting the emulator into linuxbios as an optional 
> component. Once this is done, I think the prognosis is good. We've gotten 
> distracted by fixing other things needed to support the emulator.
> 

My tests of the emulator so far with ATI bios have failed.



From rminnich at lanl.gov  Mon May  3 13:52:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May  3 13:52:01 2004
Subject: LinuxBIOS Video?
In-Reply-To: <40969808.8080206@bitworks.com>
Message-ID: <Pine.LNX.4.44.0405031307260.13873-100000@maxroach.lanl.gov>

On Mon, 3 May 2004, Richard Smith wrote:

> ron minnich wrote:
> > we are working on putting the emulator into linuxbios as an optional 
> > component. Once this is done, I think the prognosis is good. We've gotten 
> > distracted by fixing other things needed to support the emulator.
> > 
> 
> My tests of the emulator so far with ATI bios have failed.
> 


yes, this is the "INT 10" problem :-(

still working on ATI issues. nvidia is fine.

ron



From bari at onelabs.com  Mon May  3 14:59:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon May  3 14:59:01 2004
Subject: Non-x86 Video
In-Reply-To: <20040503185417.GA450@openbios.org>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov> <4096930A.7060904@onelabs.com> <20040503185417.GA450@openbios.org>
Message-ID: <4096A870.6030502@onelabs.com>

Stefan Reinauer wrote:

> * Bari Ari <bari at onelabs.com> [040503 20:44]:
> 
>>What will be needed to run video on non-x86? The oem videoBIOS plus an 
>>8086 emulator for when videoBIOS calls are made?
> 
>  
> Once the operating system is running no video bios calls are needed.
> It's all only about initializing the graphics hardware in first place.
> Today's graphics cards need complex ram setup, mode initialization, etc.
> 
> 
I've gotten various answers from graphics chip vendors over the years on 
all this.

You need the videoBIOS when you first init the device after reset unless 
you wish to come up with all your own (possibly several hundred) 
register values.

You may use the videoBIOS when you wish to change the video mode but you 
may also do it with your own set of register values on the fly.

XFree86 drivers sometimes rely on the videoBIOS, sometimes not.

>>Is this how the layers end up for video?
>>
>>video application
>>-----------------
>>  GUI/OS Linux
>>-----------------
>>  8086 emulator
>>-----------------
>>   videoBIOS
>>-----------------
>>graphics hardware
> 
> 
> The x86 emulation would be running as part of LinuxBIOS, or as a user
> space program. Once video is initialized, Linux can take over the
> hardware and use it's own drivers (which are not capable to initialize
> the hardware from power on)
> 
I know this is going beyond Ron's plan. Let's say there is source for an 
XFree86 driver for a graphics device with all the 3-D and Zoom port 
support. I haven't looked at the emulator yet. Using the 8086 emulator 
would this support fb driver only? or would you also be able to support 
XFree86 drivers compiled for ARM?

-Bari




From stepan at openbios.org  Mon May  3 15:09:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May  3 15:09:01 2004
Subject: Non-x86 Video
In-Reply-To: <4096A870.6030502@onelabs.com>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov> <4096930A.7060904@onelabs.com> <20040503185417.GA450@openbios.org> <4096A870.6030502@onelabs.com>
Message-ID: <20040503202527.GA1289@openbios.org>

* Bari Ari <bari at onelabs.com> [040503 22:15]:
> You need the videoBIOS when you first init the device after reset unless 
> you wish to come up with all your own (possibly several hundred) 
> register values.

Going the direct way by programming registers is a lost game for
every component that is not onboard (And it even does not make all that
much sense for all onboard hardware)

> You may use the videoBIOS when you wish to change the video mode but you 
> may also do it with your own set of register values on the fly.
 
LinuxBIOS+x86 emulation should set an initial mode that can be used
later on by the operating system (vesafb basically works like this, too)

> XFree86 drivers sometimes rely on the videoBIOS, sometimes not.
 
If they do, and you are on a non-x86 platform, they are basically using
the same x86 emulation core that LinuxBIOS uses: x86emu. 

> I know this is going beyond Ron's plan. Let's say there is source for an 
> XFree86 driver for a graphics device with all the 3-D and Zoom port 
> support. I haven't looked at the emulator yet. Using the 8086 emulator 
> would this support fb driver only? or would you also be able to support 
> XFree86 drivers compiled for ARM?

The video bios is needed in first place to get the hardware on the video
card activated. This task is very often not performed by X11. This is
why we need to initialize the card before X11 comes into play.

If there are open source drivers for X11, they should work by just
recompiling them for your target platform. Given that they are cleanly
written.

  Stefan




From rminnich at lanl.gov  Mon May  3 15:18:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May  3 15:18:00 2004
Subject: Non-x86 Video
In-Reply-To: <4096A870.6030502@onelabs.com>
Message-ID: <Pine.LNX.4.44.0405031433440.13873-100000@maxroach.lanl.gov>

On Mon, 3 May 2004, Bari Ari wrote:

> I know this is going beyond Ron's plan. Let's say there is source for an
> XFree86 driver for a graphics device with all the 3-D and Zoom port
> support. I haven't looked at the emulator yet. Using the 8086 emulator
> would this support fb driver only? or would you also be able to support
> XFree86 drivers compiled for ARM?

It seems to me if there is a chipset-specific driver that runs on ARM, you 
can use it. 

ron



From bgregor at buphy.bu.edu  Mon May  3 15:44:00 2004
From: bgregor at buphy.bu.edu (Brian Gregor)
Date: Mon May  3 15:44:00 2004
Subject: Diskless Windows??
Message-ID: <Pine.LNX.4.58.0405031659440.25039@buphy.bu.edu>

Is it possible to use LinuxBIOS to boot Windows 2000 diskless?

Thanks,

Brian


From dwh at lanl.gov  Mon May  3 15:49:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Mon May  3 15:49:01 2004
Subject: Diskless Windows??
In-Reply-To: <Pine.LNX.4.58.0405031659440.25039@buphy.bu.edu>
Message-ID: <Pine.LNX.4.44.0405031503470.10454-100000@ccs-mail.lanl.gov>

Adam Sulmicki would be the guy to ask about that... He did ADLO a while 
back to boot Win2K. It's quite a bit messier than booting Linux, I gather.

On Mon, 3 May 2004, Brian Gregor wrote:

> 
> Is it possible to use LinuxBIOS to boot Windows 2000 diskless?
> 
> Thanks,
> 
> Brian
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From adam at cfar.umd.edu  Mon May  3 15:55:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Mon May  3 15:55:00 2004
Subject: Diskless Windows??
In-Reply-To: <Pine.LNX.4.44.0405031503470.10454-100000@ccs-mail.lanl.gov>
Message-ID: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>

I don't feel that my work is that relevant here.

Yes it allows you to boot windows but there's a bit of way to go from
there to having netbooted windows. In theory you could add appropriate
software to have boot block send over network, it starts and then what?

In other words windows would have some suport for getting rest of itself
over network, just like Linux does.... which I do not believe windows can.

or you could try to use VMware from linux.

Having said this all I think someone else did some work in that area,
transparent forwarding of disk I/O or some such..either way it would be
proprietary binary only stuff..

Dunno if it helps.

On Mon, 3 May 2004, Hendricks David W. wrote:

> Adam Sulmicki would be the guy to ask about that... He did ADLO a while
> back to boot Win2K. It's quite a bit messier than booting Linux, I gather.
>
> On Mon, 3 May 2004, Brian Gregor wrote:
>
> >
> > Is it possible to use LinuxBIOS to boot Windows 2000 diskless?
> >
> > Thanks,
> >
> > Brian
> > _______________________________________________
> > 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
>



From bari at onelabs.com  Mon May  3 16:37:00 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon May  3 16:37:00 2004
Subject: Non-x86 Video
In-Reply-To: <Pine.LNX.4.44.0405031433440.13873-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405031433440.13873-100000@maxroach.lanl.gov>
Message-ID: <4096BF76.10704@onelabs.com>

ron minnich wrote:

> On Mon, 3 May 2004, Bari Ari wrote:
> 
> 
>>I know this is going beyond Ron's plan. Let's say there is source for an
>>XFree86 driver for a graphics device with all the 3-D and Zoom port
>>support. I haven't looked at the emulator yet. Using the 8086 emulator
>>would this support fb driver only? or would you also be able to support
>>XFree86 drivers compiled for ARM?
> 
> 
> It seems to me if there is a chipset-specific driver that runs on ARM, you 
> can use it. 

That's the thing.... there usually aren't any drivers for ARM, just 
drivers for x86.

-Bari




From stepan at openbios.org  Tue May  4 03:32:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue May  4 03:32:00 2004
Subject: Non-x86 Video
In-Reply-To: <4096BF76.10704@onelabs.com>
References: <Pine.LNX.4.44.0405031433440.13873-100000@maxroach.lanl.gov> <4096BF76.10704@onelabs.com>
Message-ID: <20040504084845.GA8760@openbios.org>

* Bari Ari <bari at onelabs.com> [040503 23:53]:
> ron minnich wrote:
> 
> >It seems to me if there is a chipset-specific driver that runs on ARM, you 
> >can use it. 
> 
> That's the thing.... there usually aren't any drivers for ARM, just 
> drivers for x86.

chipset specific drivers in this case means graphics chipset. So if your
ARM has a PCI/AGP slot, you will be able to use Matrox, ATI, ... but not
drivers like the binary only NVidia stuff.

Stefan




From dwh at lanl.gov  Tue May  4 15:15:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Tue May  4 15:15:01 2004
Subject: Which kernel for framebuffering?
Message-ID: <Pine.LNX.4.44.0405041427090.15543-100000@ccs-mail.lanl.gov>

We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
FILO came up on screen and the keyboard worked, but we've been unable to 
get Linux framebuffering to work using a 64-bit kernel. We were wondering 
if there's anything special you had to do to make it work, or any special 
kernel version or patches we need to use.



From YhLu at tyan.com  Tue May  4 15:27:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May  4 15:27:01 2004
Subject: Which kernel for framebuffering?
Message-ID: <3174569B9743D511922F00A0C943142304B86C0E@TYANWEB>

David,

Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS
...

Also please refer to the matix to see which kernel you want to use.

Please make sure enable ati xl framebuffer only in kernel config. ( don't
enable noinit)

Regards

YH

-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?4? 13:31
???: YhLu
??: linuxbios at clustermatic.org
??: Which kernel for framebuffering?

We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
FILO came up on screen and the keyboard worked, but we've been unable to 
get Linux framebuffering to work using a 64-bit kernel. We were wondering 
if there's anything special you had to do to make it work, or any special 
kernel version or patches we need to use.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.6.5-offcial-mach64.diff.gz
Type: application/octet-stream
Size: 47435 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040504/a4523d4a/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.4.22-offical-aty_nobiosinit.patch
Type: application/octet-stream
Size: 43979 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040504/a4523d4a/attachment-0001.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: support matrix.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040504/a4523d4a/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lyh_ati_xl_noinit_2.6.2.diff
Type: application/octet-stream
Size: 29508 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040504/a4523d4a/attachment-0002.obj>

From YhLu at tyan.com  Wed May  5 01:35:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 01:35:00 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
Message-ID: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>

Ron,

I'm going to add several lines in amd8111_enable of amd8111.c to disable
USB2 in amd8111. 

        /* disable usb2 in amd 8111 because it does not work awlays*/
        byte = pci_read_config8(lpc_dev, 0x47);
        byte |= (1<<7);
        pci_write_config8(lpc_dev, 0x47, byte);

Also will remove several lines in amd8111_ide.c

        /* The AMD768 has a bug where the BM DMA address must be
         * 256 byte aligned while it is only 16 bytes long.
         * Hard code this to a valid address below 0x1000
         * where automatic port address assignment starts.
         * FIXME: I assume the 8111 does the same thing. We should
         * clarify. stepan at suse.de
         */
        pci_write_config32(dev, 0x20, 0xf01);

        pci_write_config32(dev, 0x48, 0x205e5e5e);
        word = 0x06a;
        pci_write_config16(dev, 0x4c, word);

and add 

        byte = 0x20 ; // Latency: 64-->32
        pci_write_config8(dev, 0xd, byte);


regards

YH


From stepan at openbios.org  Wed May  5 01:36:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed May  5 01:36:00 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>
Message-ID: <20040505065308.GA9973@openbios.org>

* YhLu <YhLu at tyan.com> [040505 07:26]:
> Ron,
> 
> I'm going to add several lines in amd8111_enable of amd8111.c to disable
> USB2 in amd8111. 
 
  [..]

> Also will remove several lines in amd8111_ide.c
> 
>         /* The AMD768 has a bug where the BM DMA address must be
>          * 256 byte aligned while it is only 16 bytes long.
>          * Hard code this to a valid address below 0x1000
>          * where automatic port address assignment starts.
>          * FIXME: I assume the 8111 does the same thing. We should
>          * clarify. stepan at suse.de
>          */
>         pci_write_config32(dev, 0x20, 0xf01);
> 
>         pci_write_config32(dev, 0x48, 0x205e5e5e);
>         word = 0x06a;
>         pci_write_config16(dev, 0x4c, word);
 
Fine. This should definitely go away, it's a dinosaur. ;)

> and add 
> 
>         byte = 0x20 ; // Latency: 64-->32
>         pci_write_config8(dev, 0xd, byte);

Am I just the only guy picky about this? I do prefer C style comments a
lot over C++ style when it comes down to permanent commenent. // is
typed so quickly that it qualifies for debugging comments that are
probably going away later on. But this is only cosmetics and does not
really matter.

   Stefan


From rminnich at lanl.gov  Wed May  5 08:45:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 08:45:00 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405050759380.10020-100000@maxroach.lanl.gov>

On Tue, 4 May 2004, YhLu wrote:

> I'm going to add several lines in amd8111_enable of amd8111.c to disable
> USB2 in amd8111. 
> 
>         /* disable usb2 in amd 8111 because it does not work awlays*/
>         byte = pci_read_config8(lpc_dev, 0x47);
>         byte |= (1<<7);
>         pci_write_config8(lpc_dev, 0x47, byte);

this is the wrong way to do this, please don't do it just yet. 

The right way to do it is in the config file. 

I will look at your code and we'll send an example.

> 
> Also will remove several lines in amd8111_ide.c
> 
>         /* The AMD768 has a bug where the BM DMA address must be
>          * 256 byte aligned while it is only 16 bytes long.
>          * Hard code this to a valid address below 0x1000
>          * where automatic port address assignment starts.
>          * FIXME: I assume the 8111 does the same thing. We should
>          * clarify. stepan at suse.de
>          */
>         pci_write_config32(dev, 0x20, 0xf01);
> 
>         pci_write_config32(dev, 0x48, 0x205e5e5e);
>         word = 0x06a;
>         pci_write_config16(dev, 0x4c, word);

why?

> 
> and add 
> 
>         byte = 0x20 ; // Latency: 64-->32
>         pci_write_config8(dev, 0xd, byte);

which is needed because ...

Let's talk some more.

ron



From rminnich at lanl.gov  Wed May  5 08:51:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 08:51:01 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <Pine.LNX.4.44.0405050759380.10020-100000@maxroach.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405050805550.10020-100000@maxroach.lanl.gov>

On Wed, 5 May 2004, ron minnich wrote:

> On Tue, 4 May 2004, YhLu wrote:
> 
> > I'm going to add several lines in amd8111_enable of amd8111.c to disable
> > USB2 in amd8111. 
> > 
> >         /* disable usb2 in amd 8111 because it does not work awlays*/
> >         byte = pci_read_config8(lpc_dev, 0x47);
> >         byte |= (1<<7);
> >         pci_write_config8(lpc_dev, 0x47, byte);
> 
> this is the wrong way to do this, please don't do it just yet. 

ok, the other two changes look fine. 

This disabling is fine if the kernel can later re-enable, but I doubt the 
kernel will do that. We need a way to make this usb enable/disable visible 
at configuration time, so people can turn on/off as needed, unless usb2.0 
on the 8111 NEVER work. I am willing to guess it will work someday, and 
this built-in disable will come back to bite us.

ron



From ebiederman at lnxi.com  Wed May  5 09:18:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed May  5 09:18:01 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <Pine.LNX.4.44.0405050759380.10020-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405050759380.10020-100000@maxroach.lanl.gov>
Message-ID: <m3pt9jj5vd.fsf@maxwell.lnxi.com>

ron minnich <rminnich at lanl.gov> writes:

> On Tue, 4 May 2004, YhLu wrote:
> 
> > I'm going to add several lines in amd8111_enable of amd8111.c to disable
> > USB2 in amd8111. 
> > 
> >         /* disable usb2 in amd 8111 because it does not work awlays*/
> >         byte = pci_read_config8(lpc_dev, 0x47);
> >         byte |= (1<<7);
> >         pci_write_config8(lpc_dev, 0x47, byte);
> 
> this is the wrong way to do this, please don't do it just yet. 
> 
> The right way to do it is in the config file. 
> 
> I will look at your code and we'll send an example.

The code should already exist to do this.

> > Also will remove several lines in amd8111_ide.c
> > 
> >         /* The AMD768 has a bug where the BM DMA address must be
> >          * 256 byte aligned while it is only 16 bytes long.
> >          * Hard code this to a valid address below 0x1000
> >          * where automatic port address assignment starts.
> >          * FIXME: I assume the 8111 does the same thing. We should
> >          * clarify. stepan at suse.de
> >          */
> >         pci_write_config32(dev, 0x20, 0xf01);
> > 
> >         pci_write_config32(dev, 0x48, 0x205e5e5e);
> >         word = 0x06a;
> >         pci_write_config16(dev, 0x4c, word);
> 
> why?

We should provide the necessary information to the resource allocator to
do this.  The extra alignment probably isn't needed but it should not be hard
to implement.

> > 
> > and add 
> > 
> >         byte = 0x20 ; // Latency: 64-->32
> >         pci_write_config8(dev, 0xd, byte);
> 
> which is needed because ...
> 
> Let's talk some more.

Latency should certainly be a general PCI thing unless there is a good
alternative.

Eric


From ollie at lanl.gov  Wed May  5 10:29:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May  5 10:29:00 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050638BE@TYANWEB>
Message-ID: <1083771953.18413.1338.camel@exponential.lanl.gov>

On Tue, 2004-05-04 at 23:26, YhLu wrote:
> Ron,
> 
> I'm going to add several lines in amd8111_enable of amd8111.c to disable
> USB2 in amd8111. 
> 
>         /* disable usb2 in amd 8111 because it does not work awlays*/
>         byte = pci_read_config8(lpc_dev, 0x47);
>         byte |= (1<<7);
>         pci_write_config8(lpc_dev, 0x47, byte);
> 

isn't that what the on/off in the config file and this code in
amd8111.c doing ?

	reg = reg_old = pci_read_config16(lpc_dev, 0x48);
	reg &= ~(1 << index);
	if (dev->enabled) {
		reg |= (1 << index);
	}
	if (reg != reg_old) {
		pci_write_config16(lpc_dev, 0x48, reg);
	}

Ollie




From rminnich at lanl.gov  Wed May  5 10:52:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 10:52:00 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <1083771953.18413.1338.camel@exponential.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405051008130.10302-100000@maxroach.lanl.gov>

On Wed, 5 May 2004, Li-Ta Lo wrote:

> On Tue, 2004-05-04 at 23:26, YhLu wrote:
> > Ron,
> > 
> > I'm going to add several lines in amd8111_enable of amd8111.c to disable
> > USB2 in amd8111. 
> > 
> >         /* disable usb2 in amd 8111 because it does not work awlays*/
> >         byte = pci_read_config8(lpc_dev, 0x47);
> >         byte |= (1<<7);
> >         pci_write_config8(lpc_dev, 0x47, byte);
> > 
> 
> isn't that what the on/off in the config file and this code in
> amd8111.c doing ?
> 
> 	reg = reg_old = pci_read_config16(lpc_dev, 0x48);
> 	reg &= ~(1 << index);
> 	if (dev->enabled) {
> 		reg |= (1 << index);
> 	}
> 	if (reg != reg_old) {
> 		pci_write_config16(lpc_dev, 0x48, reg);
> 	}

yes. 

ron



From YhLu at tyan.com  Wed May  5 11:04:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 11:04:01 2004
Subject: =?GB2312?B?tPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgxMTEgYW5kIHJlbW92?=
	=?GB2312?B?ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050638C2@TYANWEB>

According to AMD, USB 2 in amd8111 will never work.

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?5? 7:07
???: YhLu
??: Stefan Reinauer; linuxbios at clustermatic.org
??: Re: Disable USB2 in AMD8111 and remove ide hardcode io addr

On Wed, 5 May 2004, ron minnich wrote:

> On Tue, 4 May 2004, YhLu wrote:
> 
> > I'm going to add several lines in amd8111_enable of amd8111.c to disable
> > USB2 in amd8111. 
> > 
> >         /* disable usb2 in amd 8111 because it does not work awlays*/
> >         byte = pci_read_config8(lpc_dev, 0x47);
> >         byte |= (1<<7);
> >         pci_write_config8(lpc_dev, 0x47, byte);
> 
> this is the wrong way to do this, please don't do it just yet. 

ok, the other two changes look fine. 

This disabling is fine if the kernel can later re-enable, but I doubt the 
kernel will do that. We need a way to make this usb enable/disable visible 
at configuration time, so people can turn on/off as needed, unless usb2.0 
on the 8111 NEVER work. I am willing to guess it will work someday, and 
this built-in disable will come back to bite us.

ron


From rminnich at lanl.gov  Wed May  5 11:09:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 11:09:01 2004
Subject: =?GB2312?B?tPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgxMTEgYW5kIHJlbW92?=
 =?GB2312?B?ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
In-Reply-To: <3174569B9743D511922F00A0C9431423050638C2@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405051024170.10302-100000@maxroach.lanl.gov>

On Wed, 5 May 2004, YhLu wrote:

> According to AMD, USB 2 in amd8111 will never work.

well, that's certainly interesting. 

If AMD is certain about that, and no one else objects, I remove any 
concerns I have about this code. But please put in a more informative 
comment such as "will never work"

thanks

ron



From YhLu at tyan.com  Wed May  5 11:11:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 11:11:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgxMTEgYW5k?=
	=?GB2312?B?IHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050638C4@TYANWEB>

I change my mind, disable that in Config.lb is better and less code.

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?5? 9:25
???: YhLu
??: Stefan Reinauer; linuxbios at clustermatic.org
??: Re: ??: Disable USB2 in AMD8111 and remove ide hardcode io addr

On Wed, 5 May 2004, YhLu wrote:

> According to AMD, USB 2 in amd8111 will never work.

well, that's certainly interesting. 

If AMD is certain about that, and no one else objects, I remove any 
concerns I have about this code. But please put in a more informative 
comment such as "will never work"

thanks

ron


From rminnich at lanl.gov  Wed May  5 11:12:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 11:12:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgxMTEgYW5k?=
 =?GB2312?B?IHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
In-Reply-To: <3174569B9743D511922F00A0C9431423050638C4@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405051027540.10302-100000@maxroach.lanl.gov>

On Wed, 5 May 2004, YhLu wrote:

> I change my mind, disable that in Config.lb is better and less code.

good!

ron



From YhLu at tyan.com  Wed May  5 11:24:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 11:24:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgx?=
	=?GB2312?B?MTEgYW5kIHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>

If I changed config.lb
PCI 1:0.2 on --> PCI 1:0.2 off 
The PCI 1:0.0 and PCI 1:0.1 will be disabled together.

According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device
in second bus by device num, and the three USB share one device number.

So I guess the code about 0x47 must be there.

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?5? 9:28
???: YhLu
??: Stefan Reinauer; linuxbios at clustermatic.org
??: Re: ??: ??: Disable USB2 in AMD8111 and remove ide hardcode io
addr

On Wed, 5 May 2004, YhLu wrote:

> I change my mind, disable that in Config.lb is better and less code.

good!

ron


From rminnich at lanl.gov  Wed May  5 12:07:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May  5 12:07:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGluIEFNRDgx?=
 =?GB2312?B?MTEgYW5kIHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
In-Reply-To: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405051123160.10302-100000@maxroach.lanl.gov>

On Wed, 5 May 2004, YhLu wrote:

> If I changed config.lb
> PCI 1:0.2 on --> PCI 1:0.2 off 
> The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> 
> According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device
> in second bus by device num, and the three USB share one device number.
> 
> So I guess the code about 0x47 must be there.

sounds ok.

ron



From ollie at lanl.gov  Wed May  5 12:12:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May  5 12:12:00 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?=
	=?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= =?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?=
	Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
Message-ID: <1083778106.18413.1343.camel@exponential.lanl.gov>

On Wed, 2004-05-05 at 10:51, YhLu wrote:
> If I changed config.lb
> PCI 1:0.2 on --> PCI 1:0.2 off 
> The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> 
> According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device
> in second bus by device num, and the three USB share one device number.
> 
> So I guess the code about 0x47 must be there.
> 

Ron and I just dicurssed about the enable/disable mechanism for
amd8111. We are going to implement a slightly better one soon.

Actually, the enable/disable for devices in amd8111 is multiplexed
in amd8111_enable and the device_operation::enable() is directed to
amd8111_enable. We are going to demultiplex this and each devices
has its own "real" enable method.

Ollie
  



From YhLu at tyan.com  Wed May  5 12:16:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 12:16:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGlu?=
	=?GB2312?B?IEFNRDgxMTEgYW5kIHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050638E3@TYANWEB>

I add some lines in amd8111, if USB2 is disabled, it will don't touch 0x48,
only touch 0x47.


        if ((dev->vendor == PCI_VENDOR_ID_AMD) &&
            (dev->device == PCI_DEVICE_ID_AMD_8111_USB2)) {
                if(!dev->enabled) {
                        byte = pci_read_config8(lpc_dev, 0x47);
                        byte |= (1<<7);
                        pci_write_config8(lpc_dev, 0x47, byte);
                        return;
                }

        }

        reg = reg_old = pci_read_config16(lpc_dev, 0x48);
        reg &= ~(1 << index);
        if (dev->enabled) {
                reg |= (1 << index);
        }
        if (reg != reg_old) {
                pci_write_config16(lpc_dev, 0x48, reg);
        }

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?5? 10:28
???: YhLu
??: ron minnich; Stefan Reinauer; LinuxBIOS
??: Re: ??: ??: ??: Disable USB2 in AMD8111 and remove ide hardcode
io addr

On Wed, 2004-05-05 at 10:51, YhLu wrote:
> If I changed config.lb
> PCI 1:0.2 on --> PCI 1:0.2 off 
> The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> 
> According to AMD 8111 data sheet, LPC 0x48, only can be disabled the
device
> in second bus by device num, and the three USB share one device number.
> 
> So I guess the code about 0x47 must be there.
> 

Ron and I just dicurssed about the enable/disable mechanism for
amd8111. We are going to implement a slightly better one soon.

Actually, the enable/disable for devices in amd8111 is multiplexed
in amd8111_enable and the device_operation::enable() is directed to
amd8111_enable. We are going to demultiplex this and each devices
has its own "real" enable method.

Ollie
  


From YhLu at tyan.com  Wed May  5 12:16:20 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 12:16:20 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogtPC4tDogRGlzYWJsZSBVU0IyIGlu?=
	=?GB2312?B?IEFNRDgxMTEgYW5kIHJlbW92ZSBpZGUgaGFyZGNvZGUgaW8gYWRkcg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050638E4@TYANWEB>

So everyone need to find lpc_dev at first???

YH

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?5? 10:28
???: YhLu
??: ron minnich; Stefan Reinauer; LinuxBIOS
??: Re: ??: ??: ??: Disable USB2 in AMD8111 and remove ide hardcode
io addr

On Wed, 2004-05-05 at 10:51, YhLu wrote:
> If I changed config.lb
> PCI 1:0.2 on --> PCI 1:0.2 off 
> The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> 
> According to AMD 8111 data sheet, LPC 0x48, only can be disabled the
device
> in second bus by device num, and the three USB share one device number.
> 
> So I guess the code about 0x47 must be there.
> 

Ron and I just dicurssed about the enable/disable mechanism for
amd8111. We are going to implement a slightly better one soon.

Actually, the enable/disable for devices in amd8111 is multiplexed
in amd8111_enable and the device_operation::enable() is directed to
amd8111_enable. We are going to demultiplex this and each devices
has its own "real" enable method.

Ollie
  


From ollie at lanl.gov  Wed May  5 12:24:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May  5 12:24:01 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?=
	=?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= =?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?=
	=?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= Disable USB2 in AMD8111 and remove ide
	hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638E4@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050638E4@TYANWEB>
Message-ID: <1083778823.18413.1345.camel@exponential.lanl.gov>

On Wed, 2004-05-05 at 11:42, YhLu wrote:
> So everyone need to find lpc_dev at first???
> 

yea, is there any problem with this ?

Ollie
 
> YH
> 
> -----????-----
> ???: Li-Ta Lo [mailto:ollie at lanl.gov] 
> ????: 2004?5?5? 10:28
> ???: YhLu
> ??: ron minnich; Stefan Reinauer; LinuxBIOS
> ??: Re: ??: ??: ??: Disable USB2 in AMD8111 and remove ide hardcode
> io addr
> 
> On Wed, 2004-05-05 at 10:51, YhLu wrote:
> > If I changed config.lb
> > PCI 1:0.2 on --> PCI 1:0.2 off 
> > The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> > 
> > According to AMD 8111 data sheet, LPC 0x48, only can be disabled the
> device
> > in second bus by device num, and the three USB share one device number.
> > 
> > So I guess the code about 0x47 must be there.
> > 
> 
> Ron and I just dicurssed about the enable/disable mechanism for
> amd8111. We are going to implement a slightly better one soon.
> 
> Actually, the enable/disable for devices in amd8111 is multiplexed
> in amd8111_enable and the device_operation::enable() is directed to
> amd8111_enable. We are going to demultiplex this and each devices
> has its own "real" enable method.
> 
> Ollie
>   
> 



From YhLu at tyan.com  Wed May  5 12:49:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 12:49:01 2004
Subject: Disable USB2 in AMD8111 and remove ide hardcode io addr
Message-ID: <3174569B9743D511922F00A0C9431423050638F1@TYANWEB>

Committed.

Disable AMD8111 USB2 and remove hard code addr in amd8111 IDE
CVS: ----------------------------------------------------------------------
CVS: Enter Log.  Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS:    src/mainboard/tyan/s2850/Config.lb
CVS:    src/mainboard/tyan/s2875/Config.lb
CVS:    src/mainboard/tyan/s2880/Config.lb
CVS:    src/mainboard/tyan/s2881/Config.lb
CVS:    src/mainboard/tyan/s2882/Config.lb
CVS:    src/mainboard/tyan/s2885/Config.lb
CVS:    src/mainboard/tyan/s4880/Config.lb
CVS:    src/mainboard/tyan/s4882/Config.lb
CVS:    src/southbridge/amd/amd8111/amd8111.c
CVS:    src/southbridge/amd/amd8111/amd8111_ide.c
CVS: ----------------------------------------------------------------------

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?5? 10:23
???: YhLu
??: Stefan Reinauer; linuxbios at clustermatic.org
??: Re: ??: ??: ??: Disable USB2 in AMD8111 and remove ide hardcode
io addr

On Wed, 5 May 2004, YhLu wrote:

> If I changed config.lb
> PCI 1:0.2 on --> PCI 1:0.2 off 
> The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> 
> According to AMD 8111 data sheet, LPC 0x48, only can be disabled the
device
> in second bus by device num, and the three USB share one device number.
> 
> So I guess the code about 0x47 must be there.

sounds ok.

ron


From dwh at lanl.gov  Wed May  5 14:09:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May  5 14:09:00 2004
Subject: Which kernel for framebuffering?
In-Reply-To: <3174569B9743D511922F00A0C943142304B86C0E@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405051323280.2933-100000@ccs-mail.lanl.gov>

Worked nicely :) The keyboard worked at FILO, but did not work after the 
kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I 
guess that's another matter. I'm just very, very happy to see Linux boot 
into a console I can see on a real monitor :) 

On Tue, 4 May 2004, YhLu wrote:

> David,
> 
> Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS
> ...
> 
> Also please refer to the matix to see which kernel you want to use.
> 
> Please make sure enable ati xl framebuffer only in kernel config. ( don't
> enable noinit)
> 
> Regards
> 
> YH
> 
> -----????????-----
> ??????: Hendricks David W. [mailto:dwh at lanl.gov] 
> ????????: 2004??5??4?? 13:31
> ??????: YhLu
> ????: linuxbios at clustermatic.org
> ????: Which kernel for framebuffering?
> 
> We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
> FILO came up on screen and the keyboard worked, but we've been unable to 
> get Linux framebuffering to work using a 64-bit kernel. We were wondering 
> if there's anything special you had to do to make it work, or any special 
> kernel version or patches we need to use.
> 
> 



From YhLu at tyan.com  Wed May  5 14:12:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 14:12:00 2004
Subject: =?utf-8?B?562U5aSNOiBXaGljaCBrZXJuZWwgZm9yIGZyYW1lYnVmZmVyaW5n?=
	=?utf-8?B?Pw==?=
Message-ID: <3174569B9743D511922F00A0C943142305063907@TYANWEB>

What is your kernel version? 2.6?

Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need keyboard
be reset. It assume BIOS has did that for him.

Regards

YH

-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?5? 12:25
???: YhLu
??: linuxbios at clustermatic.org
??: Re: Which kernel for framebuffering?

Worked nicely :) The keyboard worked at FILO, but did not work after the 
kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I 
guess that's another matter. I'm just very, very happy to see Linux boot 
into a console I can see on a real monitor :) 

On Tue, 4 May 2004, YhLu wrote:

> David,
> 
> Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS
> ...
> 
> Also please refer to the matix to see which kernel you want to use.
> 
> Please make sure enable ati xl framebuffer only in kernel config. ( don't
> enable noinit)
> 
> Regards
> 
> YH
> 
> -----????????-----
> ??????: Hendricks David W. [mailto:dwh at lanl.gov] 
> ????????: 2004??5??4?? 13:31
> ??????: YhLu
> ????: linuxbios at clustermatic.org
> ????: Which kernel for framebuffering?
> 
> We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
> FILO came up on screen and the keyboard worked, but we've been unable to 
> get Linux framebuffering to work using a 64-bit kernel. We were wondering 
> if there's anything special you had to do to make it work, or any special 
> kernel version or patches we need to use.
> 
> 


From ebiederman at lnxi.com  Wed May  5 16:52:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed May  5 16:52:00 2004
Subject: ç­å¤: ç­å¤: ç­å¤: Disable USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <1083778106.18413.1343.camel@exponential.lanl.gov>
References: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
	<1083778106.18413.1343.camel@exponential.lanl.gov>
Message-ID: <m37jvqseub.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> On Wed, 2004-05-05 at 10:51, YhLu wrote:
> > If I changed config.lb
> > PCI 1:0.2 on --> PCI 1:0.2 off 
> > The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> > 
> > According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device
> > in second bus by device num, and the three USB share one device number.
> > 
> > So I guess the code about 0x47 must be there.
> > 
> 
> Ron and I just dicurssed about the enable/disable mechanism for
> amd8111. We are going to implement a slightly better one soon.
> 
> Actually, the enable/disable for devices in amd8111 is multiplexed
> in amd8111_enable and the device_operation::enable() is directed to
> amd8111_enable. We are going to demultiplex this and each devices
> has its own "real" enable method.

No.  This must be per chip.

Because you cannot necessarily see these devices before you enable/disable
them.  And only one device on the 8111 actually does the enable/disable.

Eric


From ebiederman at lnxi.com  Wed May  5 16:59:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed May  5 16:59:01 2004
Subject: =?gb2312?b?tPC4tA==?=: Disable USB2 in AMD8111 and remove ide
  hardcode io addr
In-Reply-To: <3174569B9743D511922F00A0C9431423050638C2@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050638C2@TYANWEB>
Message-ID: <m33c6esep4.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> According to AMD, USB 2 in amd8111 will never work.

As I have read the documentation it says USB 2.0 devices will never
work.  

However what you are disabling is not support for USB 2.0 devices but
a newer USB controller.  Granted it is usually used for USB 2.0
traffic but that is an orthogonal issue.

Eric


From ebiederman at lnxi.com  Wed May  5 17:07:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed May  5 17:07:00 2004
Subject: Non-x86 Video
In-Reply-To: <4096930A.7060904@onelabs.com>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>
	<4096930A.7060904@onelabs.com>
Message-ID: <m3wu3qqzld.fsf@maxwell.lnxi.com>

Bari Ari <bari at onelabs.com> writes:

> ron minnich wrote:
> 
> > we are working on putting the emulator into linuxbios as an optional
> > component. Once this is done, I think the prognosis is good. We've gotten
> > distracted by fixing other things needed to support the emulator.
> 
> What will be needed to run video on non-x86? The oem videoBIOS plus an 8086
> emulator for when videoBIOS calls are made?

For hardware that is not on a plugin card it will likely be an ATI Rage XL
or a simlar low end chip and we can get the docs to initialize it.  YhLu
and Stefan have already accomplished that for the ATI Rage XL, and that linuxbios
driver should have no arch dependencies. 

For a plugin card we need to run the boot rom just to initialize the card.  After
that all of the standard Linux code should work.

Eric


From ebiederman at lnxi.com  Wed May  5 17:09:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Wed May  5 17:09:00 2004
Subject: Diskless Windows??
In-Reply-To: <Pine.LNX.4.58.0405031659440.25039@buphy.bu.edu>
References: <Pine.LNX.4.58.0405031659440.25039@buphy.bu.edu>
Message-ID: <m3u0yuqzh8.fsf@maxwell.lnxi.com>

Brian Gregor <bgregor at buphy.bu.edu> writes:

> Is it possible to use LinuxBIOS to boot Windows 2000 diskless?

Is it possible to boot Windows 2000 diskless?
If someone can document that it is likely possible.

There are also games that can be played with System Management
Mode that may allow you to emulate a hardware device and fool
windows it has a local disk, instead of a Ramdisk or something.

Basically on the LinuxBIOS side you have the source so you can
get it to do anything you can code :)

Eric


From ollie at lanl.gov  Wed May  5 17:30:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May  5 17:30:01 2004
Subject: =?ISO-8859-1?Q?=E7=AD=E5=A4=3A?=
	=?ISO-8859-1?Q?_=E7=AD=E5=A4=3A?= =?ISO-8859-1?Q?_=E7=AD=E5=A4=3A?= Disable
	USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <m37jvqseub.fsf@maxwell.lnxi.com>
References: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
	 <1083778106.18413.1343.camel@exponential.lanl.gov>
	 <m37jvqseub.fsf@maxwell.lnxi.com>
Message-ID: <1083797224.18413.1375.camel@exponential.lanl.gov>

On Wed, 2004-05-05 at 16:12, Eric W. Biederman wrote:
> Li-Ta Lo <ollie at lanl.gov> writes:
> 
> > On Wed, 2004-05-05 at 10:51, YhLu wrote:
> > > If I changed config.lb
> > > PCI 1:0.2 on --> PCI 1:0.2 off 
> > > The PCI 1:0.0 and PCI 1:0.1 will be disabled together.
> > > 
> > > According to AMD 8111 data sheet, LPC 0x48, only can be disabled the device
> > > in second bus by device num, and the three USB share one device number.
> > > 
> > > So I guess the code about 0x47 must be there.
> > > 
> > 
> > Ron and I just dicurssed about the enable/disable mechanism for
> > amd8111. We are going to implement a slightly better one soon.
> > 
> > Actually, the enable/disable for devices in amd8111 is multiplexed
> > in amd8111_enable and the device_operation::enable() is directed to
> > amd8111_enable. We are going to demultiplex this and each devices
> > has its own "real" enable method.
> 
> No.  This must be per chip.
> 
> Because you cannot necessarily see these devices before you enable/disable

What do you mean ? Do you mean when I try to enable/disable something on
8111 but the LPC bridge is not there yet ?

> them.  And only one device on the 8111 actually does the enable/disable.
> 

The function amd8111_enable() is used both as .enable and .enable_dev. 
Why are you doing this ? This make it very difficult know under which
contex the function is called and what it is supposed to do when it acts
as different method.

What I want to do is make amd8111_enable() a generic public function and
each device's .enable() calls amd8111_enable() to do the real thing.

Ollie




From ollie at lanl.gov  Wed May  5 17:35:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May  5 17:35:01 2004
Subject: =?ISO-8859-1?Q?=E7=AD=E5=A4=3A?=
	=?ISO-8859-1?Q?_=E7=AD=E5=A4=3A?= =?ISO-8859-1?Q?_=E7=AD=E5=A4=3A?= Disable
	USB2 in AMD8111 and remove ide hardcode io addr
In-Reply-To: <m37jvqseub.fsf@maxwell.lnxi.com>
References: <3174569B9743D511922F00A0C9431423050638C8@TYANWEB>
	 <1083778106.18413.1343.camel@exponential.lanl.gov>
	 <m37jvqseub.fsf@maxwell.lnxi.com>
Message-ID: <1083797522.18413.1379.camel@exponential.lanl.gov>

On Wed, 2004-05-05 at 16:12, Eric W. Biederman wrote:
> 
> No.  This must be per chip.
> 
> Because you cannot necessarily see these devices before you enable/disable
> them.  And only one device on the 8111 actually does the enable/disable.
> 

BTW, as shown in the log, the amd8111_enable is called as .enable and
.enable_dev multiple times for some specific device. Is that what we
want ? Why you want to enable/disable the same device so many times ?

Ollie



PCI: 01:01.0 [1022/7450] enabled next_unitid: 0003
amd8111_enable_dev: enabling PCI: 01:00.0 [1022/7460]
PCI: 01:03.0 [1022/7460] enabled next_unitid: 0007
HyperT reset not needed
PCI: pci_scan_bus for bus 1
POST: 0x24
PCI: 01:01.0 [1022/7450] bus ops
PCI: 01:01.0 [1022/7450] enabled
PCI: 01:01.1 [1022/7451] ops
PCI: 01:01.1 [1022/7451] enabled
PCI: 01:02.0 [1022/7450] bus ops
PCI: 01:02.0 [1022/7450] enabled
PCI: 01:02.1 [1022/7451] ops
PCI: 01:02.1 [1022/7451] enabled
amd8111_enable_dev: enabling PCI: 01:03.0 [1022/7460]
PCI: 01:03.0 [1022/7460] bus ops
amd8111_enable_dev: enabling PCI: 01:03.0 [1022/7460]
PCI: 01:03.0 [1022/7460] enabled
amd8111_enable_dev: enabling PCI: 01:04.0 [1022/7468]
PCI: 01:04.0 [1022/7468] bus ops
amd8111_enable: enabling PCI: 01:04.0 [1022/7468]
PCI: 01:04.0 [1022/7468] enabled
amd8111_enable_dev: enabling PCI: 01:04.1 [1022/7469]
PCI: 01:04.1 [1022/7469] ops
amd8111_enable_dev: enabling PCI: 01:04.1 [1022/7469]
PCI: 01:04.1 [1022/7469] enabled
amd8111_enable_dev: enabling PCI: 01:04.2 [1022/746a]
amd8111_enable_dev: enabling PCI: 01:04.2 [1022/746a]
PCI: 01:04.2 [1022/746a] enabled
amd8111_enable_dev: enabling PCI: 01:04.3 [1022/746b]
PCI: 01:04.3 [1022/746b] ops
amd8111_enable: enabling PCI: 01:04.3 [1022/746b]
PCI: 01:04.3 [1022/746b] enabled
amd8111_enable_dev: enabling PCI: 01:04.5 [1022/746d]
PCI: 01:04.5 [1022/746d] ops
amd8111_enable: disabling PCI: 01:04.5 [1022/746d]
PCI: 01:04.5 [1022/746d] disabled
amd8111_enable_dev: enabling PCI: 01:04.6 [1022/746e]
PCI: 01:04.6 [1022/746e] ops
amd8111_enable: disabling PCI: 01:04.6 [1022/746e]
PCI: 01:04.6 [1022/746e] disabled
POST: 0x25
PCI: pci_scan_bus for bus 2
POST: 0x24
PCI: 02:01.0 [14e4/1648] enabled
PCI: 02:01.1 [14e4/1648] enabled
PCI: 02:02.0 [1000/0030] enabled
POST: 0x25
PCI: pci_scan_bus returning with max=02
POST: 0x55
PCI: pci_scan_bus for bus 3
POST: 0x24
POST: 0x25
PCI: pci_scan_bus returning with max=03
POST: 0x55
PCI: pci_scan_bus for bus 4
POST: 0x24
amd8111_enable_dev: enabling PCI: 04:00.0 [1022/7464]
PCI: 04:00.0 [1022/7464] ops
amd8111_enable: enabling PCI: 04:00.0 [1022/7464]
PCI: 04:00.0 [1022/7464] enabled
amd8111_enable_dev: enabling PCI: 04:00.1 [1022/7464]
PCI: 04:00.1 [1022/7464] ops
amd8111_enable: enabling PCI: 04:00.1 [1022/7464]
PCI: 04:00.1 [1022/7464] enabled
amd8111_enable_dev: enabling PCI: 04:00.2 [1022/7463]
PCI: 04:00.2 [1022/7463] ops
amd8111_enable: enabling PCI: 04:00.2 [1022/7463]
PCI: 04:00.2 [1022/7463] enabled
amd8111_enable_dev: enabling PCI: 04:01.0 [1022/7462]
PCI: 04:01.0 [1022/7462] ops
amd8111_enable: disabling PCI: 04:01.0 [1022/7462]




From bari at onelabs.com  Wed May  5 18:39:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Wed May  5 18:39:01 2004
Subject: Non-x86 Video
In-Reply-To: <m3wu3qqzld.fsf@maxwell.lnxi.com>
References: <Pine.LNX.4.44.0405031116290.13873-100000@maxroach.lanl.gov>	<4096930A.7060904@onelabs.com> <m3wu3qqzld.fsf@maxwell.lnxi.com>
Message-ID: <40997F48.8060104@onelabs.com>

Eric W. Biederman wrote:

> Bari Ari <bari at onelabs.com> writes:
> 
> 
>>ron minnich wrote:
>>
>>
>>>we are working on putting the emulator into linuxbios as an optional
>>>component. Once this is done, I think the prognosis is good. We've gotten
>>>distracted by fixing other things needed to support the emulator.
>>
>>What will be needed to run video on non-x86? The oem videoBIOS plus an 8086
>>emulator for when videoBIOS calls are made?
> 
> 
> For hardware that is not on a plugin card it will likely be an ATI Rage XL
> or a simlar low end chip and we can get the docs to initialize it.  YhLu
> and Stefan have already accomplished that for the ATI Rage XL, and that linuxbios
> driver should have no arch dependencies. 
> 
> For a plugin card we need to run the boot rom just to initialize the card.  After
> that all of the standard Linux code should work.

We design all our own boards and have the access to the graphics 
processor data as well as the vendors videoBIOS.

For x86 it's easy for us. We get oem drivers and the tools to modify the 
oem videoBIOS.

For non-x86 such as ARM the GPU developers (who make the silicon) don't 
have answers since they only work in the x86 world or a very small 
fraction know PPC for Apple or IBM.

ATI and nVidia don't let source out for the most current parts. There is 
some xFree86 driver source for the 3-4 year old devices. For ATI there 
may be source for up the Radeon 9000. That source is what were looking 
at to get PC GPU's working on ARM with ARMLinux.

-Bari




From dwh at lanl.gov  Wed May  5 19:09:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May  5 19:09:00 2004
Subject: =?utf-8?B?562U5aSNOiBXaGljaCBrZXJuZWwgZm9yIGZyYW1lYnVmZmVyaW5n?=
 =?utf-8?B?Pw==?=
In-Reply-To: <3174569B9743D511922F00A0C943142305063907@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405051817170.5907-100000@ccs-mail.lanl.gov>

I am using kernel 2.6.5. I'm not sure that the pc_kbd_init function exists 
in kernel 2.6.5. But it does not look like atkbd_init() is called, in case 
that's what you meant to say. I'll check it out again tomorrow if I have 
some time.

When we cat /proc/interrupts, int 1 does not appear on the list:

k root # cat /proc/interrupts 
           CPU0       CPU1       
  0:   17164403          0    IO-APIC-edge  timer
  2:          0          0          XT-PIC  cascade
  4:          8          0    IO-APIC-edge  serial
  8:          0          0    IO-APIC-edge  rtc
 12:      41628          0    IO-APIC-edge  i8042
 14:      23228          0    IO-APIC-edge  ide0
 15:          2          0    IO-APIC-edge  ide1
 19:     270954          0   IO-APIC-level  eth0
NMI:        181         22 
LOC:   17161863   17161969 
ERR:          0
MIS:          0

However, this is in our dmesg:
k root # dmesg | grep -ie 'kbd'
serio: i8042 KBD port at 0x60,0x64 irq 1

Also, the mouse works in X windows.

On Wed, 5 May 2004, YhLu wrote:

> What is your kernel version? 2.6?
> 
> Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need keyboard
> be reset. It assume BIOS has did that for him.
> 
> Regards
> 
> YH
> 
> -----????????????-----
> ?????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> ????????????: 2004???5???5??? 12:25
> ?????????: YhLu
> ??????: linuxbios at clustermatic.org
> ??????: Re: Which kernel for framebuffering?
> 
> Worked nicely :) The keyboard worked at FILO, but did not work after the 
> kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I 
> guess that's another matter. I'm just very, very happy to see Linux boot 
> into a console I can see on a real monitor :) 
> 
> On Tue, 4 May 2004, YhLu wrote:
> 
> > David,
> > 
> > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS
> > ...
> > 
> > Also please refer to the matix to see which kernel you want to use.
> > 
> > Please make sure enable ati xl framebuffer only in kernel config. ( don't
> > enable noinit)
> > 
> > Regards
> > 
> > YH
> > 
> > -----????????????????-----
> > ????????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> > ????????????????: 2004????5????4???? 13:31
> > ????????????: YhLu
> > ????????: linuxbios at clustermatic.org
> > ????????: Which kernel for framebuffering?
> > 
> > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
> > FILO came up on screen and the keyboard worked, but we've been unable to 
> > get Linux framebuffering to work using a 64-bit kernel. We were wondering 
> > if there's anything special you had to do to make it work, or any special 
> > kernel version or patches we need to use.
> > 
> > 
> 






From YhLu at tyan.com  Wed May  5 19:13:00 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 19:13:00 2004
Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IFdoaWNoIGtlcm5lbCBmb3IgZnJhbWVi?=
	=?utf-8?B?dWZmZXJpbmc/?=
Message-ID: <3174569B9743D511922F00A0C94314230506395A@TYANWEB>

Mine's in s2885
~ # cat /proc/interrupts 
           CPU0       CPU1       
  0:    2419417          0    IO-APIC-edge  timer
  1:          9          0    IO-APIC-edge  i8042
  2:          0          0          XT-PIC  cascade
  4:        277          0    IO-APIC-edge  serial
  8:          0          0    IO-APIC-edge  rtc
 14:         12          0    IO-APIC-edge  ide0
 15:         29          0    IO-APIC-edge  ide1
 17:          2          0   IO-APIC-level  libata
 19:          3          0   IO-APIC-level  ohci1394
NMI:         28          2 
LOC:    2418600    2418591 
ERR:          0
MIS:          0
~ #

Also in boot message:

serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0



-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?5? 17:26
???: YhLu
??: linuxbios at clustermatic.org
??: Re: ????: Which kernel for framebuffering?

I am using kernel 2.6.5. I'm not sure that the pc_kbd_init function exists 
in kernel 2.6.5. But it does not look like atkbd_init() is called, in case 
that's what you meant to say. I'll check it out again tomorrow if I have 
some time.

When we cat /proc/interrupts, int 1 does not appear on the list:

k root # cat /proc/interrupts 
           CPU0       CPU1       
  0:   17164403          0    IO-APIC-edge  timer
  2:          0          0          XT-PIC  cascade
  4:          8          0    IO-APIC-edge  serial
  8:          0          0    IO-APIC-edge  rtc
 12:      41628          0    IO-APIC-edge  i8042
 14:      23228          0    IO-APIC-edge  ide0
 15:          2          0    IO-APIC-edge  ide1
 19:     270954          0   IO-APIC-level  eth0
NMI:        181         22 
LOC:   17161863   17161969 
ERR:          0
MIS:          0

However, this is in our dmesg:
k root # dmesg | grep -ie 'kbd'
serio: i8042 KBD port at 0x60,0x64 irq 1

Also, the mouse works in X windows.

On Wed, 5 May 2004, YhLu wrote:

> What is your kernel version? 2.6?
> 
> Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need
keyboard
> be reset. It assume BIOS has did that for him.
> 
> Regards
> 
> YH
> 
> -----????????????-----
> ?????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> ????????????: 2004???5???5??? 12:25
> ?????????: YhLu
> ??????: linuxbios at clustermatic.org
> ??????: Re: Which kernel for framebuffering?
> 
> Worked nicely :) The keyboard worked at FILO, but did not work after the 
> kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I

> guess that's another matter. I'm just very, very happy to see Linux boot 
> into a console I can see on a real monitor :) 
> 
> On Tue, 4 May 2004, YhLu wrote:
> 
> > David,
> > 
> > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in
CVS
> > ...
> > 
> > Also please refer to the matix to see which kernel you want to use.
> > 
> > Please make sure enable ati xl framebuffer only in kernel config. (
don't
> > enable noinit)
> > 
> > Regards
> > 
> > YH
> > 
> > -----????????????????-----
> > ????????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> > ????????????????: 2004????5????4???? 13:31
> > ????????????: YhLu
> > ????????: linuxbios at clustermatic.org
> > ????????: Which kernel for framebuffering?
> > 
> > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
> > FILO came up on screen and the keyboard worked, but we've been unable to

> > get Linux framebuffering to work using a 64-bit kernel. We were
wondering 
> > if there's anything special you had to do to make it work, or any
special 
> > kernel version or patches we need to use.
> > 
> > 
> 





From YhLu at tyan.com  Wed May  5 19:16:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 19:16:01 2004
Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IFdoaWNoIGtlcm5lbCBmb3IgZnJhbWVi?=
	=?utf-8?B?dWZmZXJpbmc/?=
Message-ID: <3174569B9743D511922F00A0C94314230506395C@TYANWEB>

Please check your pnp_device.c

Are there following lines

                if(info[i].ops == 0) {  // BY LYH
                  dev->ops = ops;
                } 
                else { 
                  dev->ops = info[i].ops;  // BY LYH
                }

Otherwise you need do one cvs update for that file.

YH

-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?5? 17:26
???: YhLu
??: linuxbios at clustermatic.org
??: Re: ????: Which kernel for framebuffering?

I am using kernel 2.6.5. I'm not sure that the pc_kbd_init function exists 
in kernel 2.6.5. But it does not look like atkbd_init() is called, in case 
that's what you meant to say. I'll check it out again tomorrow if I have 
some time.

When we cat /proc/interrupts, int 1 does not appear on the list:

k root # cat /proc/interrupts 
           CPU0       CPU1       
  0:   17164403          0    IO-APIC-edge  timer
  2:          0          0          XT-PIC  cascade
  4:          8          0    IO-APIC-edge  serial
  8:          0          0    IO-APIC-edge  rtc
 12:      41628          0    IO-APIC-edge  i8042
 14:      23228          0    IO-APIC-edge  ide0
 15:          2          0    IO-APIC-edge  ide1
 19:     270954          0   IO-APIC-level  eth0
NMI:        181         22 
LOC:   17161863   17161969 
ERR:          0
MIS:          0

However, this is in our dmesg:
k root # dmesg | grep -ie 'kbd'
serio: i8042 KBD port at 0x60,0x64 irq 1

Also, the mouse works in X windows.

On Wed, 5 May 2004, YhLu wrote:

> What is your kernel version? 2.6?
> 
> Please check if the pc_kbd_init is called, 2.6 for X86-64/i386 need
keyboard
> be reset. It assume BIOS has did that for him.
> 
> Regards
> 
> YH
> 
> -----????????????-----
> ?????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> ????????????: 2004???5???5??? 12:25
> ?????????: YhLu
> ??????: linuxbios at clustermatic.org
> ??????: Re: Which kernel for framebuffering?
> 
> Worked nicely :) The keyboard worked at FILO, but did not work after the 
> kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I

> guess that's another matter. I'm just very, very happy to see Linux boot 
> into a console I can see on a real monitor :) 
> 
> On Tue, 4 May 2004, YhLu wrote:
> 
> > David,
> > 
> > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in
CVS
> > ...
> > 
> > Also please refer to the matix to see which kernel you want to use.
> > 
> > Please make sure enable ati xl framebuffer only in kernel config. (
don't
> > enable noinit)
> > 
> > Regards
> > 
> > YH
> > 
> > -----????????????????-----
> > ????????????: Hendricks David W. [mailto:dwh at lanl.gov] 
> > ????????????????: 2004????5????4???? 13:31
> > ????????????: YhLu
> > ????????: linuxbios at clustermatic.org
> > ????????: Which kernel for framebuffering?
> > 
> > We were able to build and boot LinuxBIOS with VGA support for an HDAMA. 
> > FILO came up on screen and the keyboard worked, but we've been unable to

> > get Linux framebuffering to work using a 64-bit kernel. We were
wondering 
> > if there's anything special you had to do to make it work, or any
special 
> > kernel version or patches we need to use.
> > 
> > 
> 





From YhLu at tyan.com  Wed May  5 23:46:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May  5 23:46:01 2004
Subject: AMD8111 PCI bridge
Message-ID: <3174569B9743D511922F00A0C94314230506397A@TYANWEB>

Eric,

If the discard timer is enabled, when using Silicon Image 3114 serial SATA,
I can not fisk the disk and format it.

Disable it, all operations will be OK.
//      dword |= (1<<27); /* Discard timer */
        dword &= ~(1<<27); /* Discard timer */

Why did you enable it?

Regards

YH


From mdeschamps at mangrove-systems.com  Thu May  6 07:43:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Thu May  6 07:43:01 2004
Subject: Pleased experienced on EPIA : Linuxbios runs,but smbus errors, no
	normal rom starting, payload making difficulties
Message-ID: <1083848312.1279.148.camel@Calliphara>

hello to every linuxBios people,

First, I would like I got V2 started on EPIA C3 Ezra with a null 
payload for a start ...and that truely welcome and pleasant. 


I heared a while ago of a half baud rate problem, I 
have no worries on this side. I was trying to to collect
debug serial sent strings via minicom, but i would't advice 
this, it's a mess to configure (in fact for someone like I).
I've just make it with this script that I have joined in there
if it is of any use to somebody :

#!/bin/bash
# Hear !
#
#
( [ "x$1" = "x" ] && echo "Usage $0 log_file" && exit 0)|| $LOG="$1"
ter=`tty`
echo "****************************************************" >>$LOG 
echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> $LOG
echo "  tty in use : $ter  from ttyS0 " >>$LOG
echo "****************************************************" >>$LOG 
 
  cat -sbA </dev/ttyS0 | tee -a $LOG
  

It can be lauch that way :
[root at ge] sh hear.sh boot.log
[root at ge] cat boot.log | while read line; do if [ "x$line" != "x$" ];
then echo $line;fi;done

it outputs the bellow log with some non-fatal (?) error
on which, firstly I would like some explanation if you will

****************************************************
 Hear! Boot Log started on 04/05/04|17:27:54 
  tty in use : /dev/pts/0  from ttyS0 
****************************************************
1 jM-^^xM-C$
2 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$

Why the normal rom didn't start first, though I config 2 payloads
normal and fallback. I belived fallback were called in case of
fallback BTW of erroring normal rom ?! 

3 vt8601 init starting$
4 Slot 00 is SDRAM 04000000 bytes $
5 Slot 01 is SDRAM 04000000 bytes $


6 Slot 02smbus_error: 04$
7 Device Error$
8 is empty$
9 Slot 03smbus_error: 04$
10 Device Error$
11 is empty$

What are these error number refers to ? 
It work though, but these errors while init plus the fallback mode
right from the start, show nothing good for the future deployement
I presume ... anyway


12 vt8601 done$
13 POST: 0x39$
14 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$
15 POST: 0x40$
16 Finding PCI configuration type.$
17 POST: 0x5f$
18 Enumerating static devices...$
19 Enumerating buses...$
20 POST: 0x24$
21 POST: 0x25$
22 POST: 0x24$
23 POST: 0x25$
24 POST: 0x55$
25 POST: 0x55$
26 done$
27 POST: 0x66$
28 Allocating resources...done.$
29 POST: 0x88$
30 Enabling resourcess...$
31 done.$
32 Initializing devices...$
33 Devices initialized$
34 POST: 0x89$
35 vt8231_init: enabling compatibility IDE addresses$
36 Ethernet fixup$
37 pci_routing_fixup: dev is 00017fc0$
38 setting southbridge$
39 setting ethernet$
40 setting pci slot$
41 pci_routing_fixup: DONE$
42 POST: 0x70$
43 totalram: 128M$
44 Initializing CPU #0$
45 POST: 0x60$
46 Enabling cache...POST: 0x6a$
47 done.$
48 POST: 0x92$
49 POST: 0x93$
50 Disabling local apic...done.$
51 POST: 0x9b$
52 CPU #0 Initialized$
53 POST: 0x75$
54 POST: 0x9a$
55 Checking IRQ routing tables...$
56 done.$
57 Copying IRQ routing tables to 0xf0000...done.$
58 Verifing copy of IRQ routing tables at 0xf0000...done$
59 POST: 0x96$
60 Welcome to elfboot, the open sourced starter.$
61 January 2002, Eric Biederman.$
62 Version 1.3$
63 POST: 0xf8$
64 Cannot Load ELF Image$
65 POST: 0xff$

	So this is ok I have not linked any payload, but why does it 
	redo it once more :

66 jM-^^xM-C$
67 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$
68 vt8601 init starting$
69 Slot 00 is SDRAM 04000000 bytes $
70 Slot 01 is SDRAM 04000000 bytes $
71 Slot 02smbus_error: 04$
72 Device Error$
73 is empty$
74 Slot 03smbus_error: 04$
75 Device Error$
76 is empty$
77 vt8601 done$
78 POST: 0x39$
79 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$
80 POST: 0x40$
81 Finding PCI configuration type.$
82 POST: 0x5f$
83 Enumerating static devices...$
84 Enumerating buses...$
85 POST: 0x24$
86 POST: 0x25$
87 POST: 0x24$
88 POST: 0x25$
89 POST: 0x55$
90 POST: 0x55$
91 done$
92 POST: 0x66$
93 Allocating resources...done.$
94 POST: 0x88$
95 Enabling resourcess...$
96 done.$
97 Initializing devices...$
98 Devices initialized$
99 POST: 0x89$
100 vt8231_init: enabling compatibility IDE addresses$
101 Ethernet fixup$
102 pci_routing_fixup: dev is 00017fc0$
103 setting southbridge$
104 setting ethernet$
105 setting pci slot$
106 pci_routing_fixup: DONE$
107 POST: 0x70$
108 totalram: 128M$
109 Initializing CPU #0$
110 POST: 0x60$
111 Enabling cache...POST: 0x6a$
112 done.$
113 POST: 0x92$
114 POST: 0x93$
115 Disabling local apic...done.$
116 POST: 0x9b$
117 CPU #0 Initialized$
118 POST: 0x75$
119 POST: 0x9a$
120 Checking IRQ routing tables...$
121 done.$
122 Copying IRQ routing tables to 0xf0000...done.$
123 Verifing copy of IRQ routing tables at 0xf0000...done$
124 POST: 0x96$
125 Welcome to elfboot, the open sourced starter.$
126 January 2002, Eric Biederman.$
127 Version 1.3$
128 POST: 0xf8$
129 Cannot Load ELF Image$
130 POST: 0xff$

Secondly, I intended to make a IDE elfImagepayload to boot a kernel
on a hard disk, I've read that LinuxBios alone could do that quite
well.
So got mkelfImage 1.16 (i know it's quite old
but i can't find a link to a recent one- BTW please a link to a more
recent one would be appreciated). 

I had a error on the build that's seems not to be relevant since 
ending ok ( that's i like to say to myself in these cases ) 

[root at ge] make;echo "Build : $?";
find :./kunzip_src: No such file
...
Build : 0

So I made  : mkelfImage -kernel=/boot/vmlinuz 
vmlinuz is a kenel bzImage.
It made elfImage, that is wierd :

ls says :
-rwxr-xr-x    1 root     root       901816 mai  5 10:08 elfImage

file says:
elfImage: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linkedfile: corrupted section header size.

It's corrupted, could it be the build "warn"-error message ?

 
I've done a readelf -x on it too :

En-t?te ELF:
  Magique:   7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 
  Classe:                            ELF32
  Donn?es:                          compl?ment ? 2, syst?me ? octets de
poids faible d'abord (little endian)
  Version:                           1 (current)
  OS/ABI:                            UNIX - System V
  Version ABI:                       0
  Type:                              EXEC (fichier ex?cutable)
  Machine:                           Intel 80386
  Version:                           0x1
  Adresse du point d'entr?e:         0x101c0
  D?but des en-t?tes de programme:   52 (octets dans le fichier)
  D?but des en-t?tes de section:          0 (octets dans le fichier)
  Fanions:                           0x0
  Taille de cet en-t?te:             52 (bytes)
  Taille de l'en-t?te du programme:  32 (bytes)
  Nombre d'en-t?te du programme:     5
  Taille des en-t?tes de section:    0 (bytes)
  Nombre d'en-t?tes de section:      0
  Table d'indexes des cha?nes d'en-t?te de section: 0

Il n'y a pas de section dans ce fichier.

En-t?tes de programme:
  Type           D?calage Adr. vir.  Adr.phys.  T.Fich. T.M?m.  Fan
Alignement
  NOTE           0x0000d4 0x00010000 0x00010000 0x001c0 0x001c0 RWE 0
  LOAD           0x0000d4 0x00010000 0x00010000 0x0562c 0x058b8 RWE 0
  LOAD           0x0058b8 0x00091000 0x00091000 0x00000 0x00028 RWE 0
  LOAD           0x0058b8 0x00100000 0x00100000 0xd6a00 0x700000 RWE 0
  LOAD           0x0dc2b8 0x00800000 0x00800000 0x00000 0x00000 RWE 0

Il n'y a pas de segement dynamique dans ce fichier.

Il n'y a pas de relocalisation dans ce fichier.

Il n'y a pas de section unwind dans ce fichier.

Aucune information de version rep?r?e dans ce fichier.






From pub at goldshmidt.org  Thu May  6 09:53:00 2004
From: pub at goldshmidt.org (Oleg Goldshmidt)
Date: Thu May  6 09:53:00 2004
Subject: Diskless Windows??
In-Reply-To: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>
References: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>
Message-ID: <m3r7txo27y.fsf@zaphod.goldshmidt.org>

Adam Sulmicki <adam at cfar.umd.edu> writes:

> Having said this all I think someone else did some work in that area,
> transparent forwarding of disk I/O or some such..either way it would be
> proprietary binary only stuff..

I am not sure what the OP meant by "diskless". If the question is
about booting Windows from a networked disk on a computer without a
local disk, then it is possible booting off an iSCSI disk. Check

http://www.haifa.il.ibm.com/projects/storage/iboot/

Disclosure: I work at IBM's Haifa Labs - iBOOT is rather routine for us. 

LinuxBIOS is not a part of this, though. Pity.

To be quite fair, Cisco are also working hard:

http://www.internetnews.com/infra/article.php/1490471

-- 
Oleg Goldshmidt | pub at NOSPAM.goldshmidt.org


From rminnich at lanl.gov  Thu May  6 09:59:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May  6 09:59:01 2004
Subject: Diskless Windows??
In-Reply-To: <m3r7txo27y.fsf@zaphod.goldshmidt.org>
Message-ID: <Pine.LNX.4.44.0405060915210.19864-100000@maxroach.lanl.gov>

the way I would want to do diskless windows is under vmware, I would never 
trust it otherwise.

ron



From ebiederman at lnxi.com  Thu May  6 11:49:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May  6 11:49:01 2004
Subject: Diskless Windows??
In-Reply-To: <m3r7txo27y.fsf@zaphod.goldshmidt.org>
References: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>
	<m3r7txo27y.fsf@zaphod.goldshmidt.org>
Message-ID: <m3ekpx32j8.fsf@maxwell.lnxi.com>

Oleg Goldshmidt <pub at goldshmidt.org> writes:

> Adam Sulmicki <adam at cfar.umd.edu> writes:
> 
> > Having said this all I think someone else did some work in that area,
> > transparent forwarding of disk I/O or some such..either way it would be
> > proprietary binary only stuff..
> 
> I am not sure what the OP meant by "diskless". If the question is
> about booting Windows from a networked disk on a computer without a
> local disk, then it is possible booting off an iSCSI disk. Check
> 
> http://www.haifa.il.ibm.com/projects/storage/iboot/
> 
> Disclosure: I work at IBM's Haifa Labs - iBOOT is rather routine for us. 

My general impression with this is that you still need iscsi drivers
on the OS side to make this work.  And that you have to be quite careful
at the transition point on the OS side.  Not knowing how windows works
this is where I get leery of these kinds of things.

It sounds like from the description there is no way to do windows diskless
without emulating a disk.

I have serious issues with iSCSI because the only implementation I have
seen was tremendously complex and nasty looking.  Which is a real downside
when compared to something simple like nbd.

How well does iBOOT work on the linux side.  I guess if you can get a kernel
and ramdisk into memory with lilo or something like that using the legacy
BIOS calls it should work ok.  If you have an iSCSI driver for Linux.

Eric


From adam at cfar.umd.edu  Thu May  6 11:55:04 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Thu May  6 11:55:04 2004
Subject: Diskless Windows??
In-Reply-To: <m3r7txo27y.fsf@zaphod.goldshmidt.org>
Message-ID: <20040506131213.S29924-100000@www.missl.cs.umd.edu>

On 6 May 2004, Oleg Goldshmidt wrote:

> I am not sure what the OP meant by "diskless". If the question is
> about booting Windows from a networked disk on a computer without a
> local disk, then it is possible booting off an iSCSI disk. Check
>
> http://www.haifa.il.ibm.com/projects/storage/iboot/

seems to me like this solution basically redirect BIOS I/O interrupts.

What happens once Windows boots up and attempt to access hardware directly
without BIOS calls in between? Is Windows smart enough to work by default
with hdd (for example : what about swap?)





From ollie at lanl.gov  Thu May  6 16:29:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May  6 16:29:00 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Which kernel for
	framebuffering?
In-Reply-To: <3174569B9743D511922F00A0C943142305063907@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063907@TYANWEB>
Message-ID: <1083879950.2459.103.camel@exponential.lanl.gov>

On Wed, 2004-05-05 at 13:39, YhLu wrote:

did you do anything with the LDT/Resource for VGA Card ? We have problem
on the IBM/e325 which has different HT topology with hdama.

Ollie

> 
> Worked nicely :) The keyboard worked at FILO, but did not work after the 
> kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I 
> guess that's another matter. I'm just very, very happy to see Linux boot 
> into a console I can see on a real monitor :) 
> 
> On Tue, 4 May 2004, YhLu wrote:
> 
> > David,
> > 
> > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in CVS
> > ...
> > 
> > Also please refer to the matix to see which kernel you want to use.
> > 
> > Please make sure enable ati xl framebuffer only in kernel config. ( don't
> > enable noinit)
> > 
> > Regards
> > 
> > YH
> > 




From YhLu at tyan.com  Thu May  6 16:33:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May  6 16:33:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogV2hpY2gga2VybmVsIGZvciBmcmFtZWJ1ZmZl?=
	=?GB2312?B?cmluZz8=?=
Message-ID: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB>

So the IBM MB does't work again? 
Can not get output in CRT or sth?

YH

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?6? 14:46
???: YhLu
??: Hendricks David W.; LinuxBIOS
??: Re: ??: Which kernel for framebuffering?

On Wed, 2004-05-05 at 13:39, YhLu wrote:

did you do anything with the LDT/Resource for VGA Card ? We have problem
on the IBM/e325 which has different HT topology with hdama.

Ollie

> 
> Worked nicely :) The keyboard worked at FILO, but did not work after the 
> kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I

> guess that's another matter. I'm just very, very happy to see Linux boot 
> into a console I can see on a real monitor :) 
> 
> On Tue, 4 May 2004, YhLu wrote:
> 
> > David,
> > 
> > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in
CVS
> > ...
> > 
> > Also please refer to the matix to see which kernel you want to use.
> > 
> > Please make sure enable ati xl framebuffer only in kernel config. (
don't
> > enable noinit)
> > 
> > Regards
> > 
> > YH
> > 



From ollie at lanl.gov  Thu May  6 16:36:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May  6 16:36:01 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?=
	=?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= Which kernel for framebuffering?
In-Reply-To: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB>
Message-ID: <1083880346.2459.105.camel@exponential.lanl.gov>

On Thu, 2004-05-06 at 15:59, YhLu wrote:
> So the IBM MB does't work again? 
> Can not get output in CRT or sth?
> 

When I checked with David yesterday, it didn't.
There is nothing on the screen even for FILO.
I think it is due to different HT topology.

Ollie

> YH
> 
> -----????-----
> ???: Li-Ta Lo [mailto:ollie at lanl.gov] 
> ????: 2004?5?6? 14:46
> ???: YhLu
> ??: Hendricks David W.; LinuxBIOS
> ??: Re: ??: Which kernel for framebuffering?
> 
> On Wed, 2004-05-05 at 13:39, YhLu wrote:
> 
> did you do anything with the LDT/Resource for VGA Card ? We have problem
> on the IBM/e325 which has different HT topology with hdama.
> 
> Ollie
> 
> > 
> > Worked nicely :) The keyboard worked at FILO, but did not work after the 
> > kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but I
> 
> > guess that's another matter. I'm just very, very happy to see Linux boot 
> > into a console I can see on a real monitor :) 
> > 
> > On Tue, 4 May 2004, YhLu wrote:
> > 
> > > David,
> > > 
> > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in
> CVS
> > > ...
> > > 
> > > Also please refer to the matix to see which kernel you want to use.
> > > 
> > > Please make sure enable ati xl framebuffer only in kernel config. (
> don't
> > > enable noinit)
> > > 
> > > Regards
> > > 
> > > YH
> > > 
> 
> 



From ollie at lanl.gov  Thu May  6 16:36:59 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May  6 16:36:59 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?=
	=?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= Which kernel for framebuffering?
In-Reply-To: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB>
Message-ID: <1083880424.2459.107.camel@exponential.lanl.gov>

On Thu, 2004-05-06 at 15:59, YhLu wrote:
> So the IBM MB does't work again? 
> Can not get output in CRT or sth?
> 


BTW, does the BTEXT use the graphics card in legacy mode
or in framebuffer mode ?

Ollie




From YhLu at tyan.com  Thu May  6 16:38:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May  6 16:38:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogV2hpY2gga2VybmVsIGZvciBmcmFt?=
	=?GB2312?B?ZWJ1ZmZlcmluZz8=?=
Message-ID: <3174569B9743D511922F00A0C943142305063A0E@TYANWEB>

Framebuffer mode

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?6? 14:54
???: YhLu
??: Hendricks David W.; LinuxBIOS
??: Re: ??: ??: Which kernel for framebuffering?

On Thu, 2004-05-06 at 15:59, YhLu wrote:
> So the IBM MB does't work again? 
> Can not get output in CRT or sth?
> 


BTW, does the BTEXT use the graphics card in legacy mode
or in framebuffer mode ?

Ollie



From YhLu at tyan.com  Thu May  6 16:38:16 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May  6 16:38:16 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogV2hpY2gga2VybmVsIGZvciBmcmFt?=
	=?GB2312?B?ZWJ1ZmZlcmluZz8=?=
Message-ID: <3174569B9743D511922F00A0C943142305063A0F@TYANWEB>

Are your changes in CVS server?

You need to enable CONFIG_BTEXT_CONSOLE

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?6? 14:52
???: YhLu
??: Hendricks David W.; LinuxBIOS
??: Re: ??: ??: Which kernel for framebuffering?

On Thu, 2004-05-06 at 15:59, YhLu wrote:
> So the IBM MB does't work again? 
> Can not get output in CRT or sth?
> 

When I checked with David yesterday, it didn't.
There is nothing on the screen even for FILO.
I think it is due to different HT topology.

Ollie

> YH
> 
> -----????-----
> ???: Li-Ta Lo [mailto:ollie at lanl.gov] 
> ????: 2004?5?6? 14:46
> ???: YhLu
> ??: Hendricks David W.; LinuxBIOS
> ??: Re: ??: Which kernel for framebuffering?
> 
> On Wed, 2004-05-05 at 13:39, YhLu wrote:
> 
> did you do anything with the LDT/Resource for VGA Card ? We have problem
> on the IBM/e325 which has different HT topology with hdama.
> 
> Ollie
> 
> > 
> > Worked nicely :) The keyboard worked at FILO, but did not work after the

> > kernel booted. It didn't even show IRQ 1 in /proc/interrupts. Weird, but
I
> 
> > guess that's another matter. I'm just very, very happy to see Linux boot

> > into a console I can see on a real monitor :) 
> > 
> > On Tue, 4 May 2004, YhLu wrote:
> > 
> > > David,
> > > 
> > > Please refer to the patch for 2.4.22 and 2.6.5, or you can put that in
> CVS
> > > ...
> > > 
> > > Also please refer to the matix to see which kernel you want to use.
> > > 
> > > Please make sure enable ati xl framebuffer only in kernel config. (
> don't
> > > enable noinit)
> > > 
> > > Regards
> > > 
> > > YH
> > > 
> 
> 


From firstone5 at hotmail.com  Thu May  6 16:42:00 2004
From: firstone5 at hotmail.com (M. Renee Hopkins)
Date: Thu May  6 16:42:00 2004
Subject: EPIA-M startup times
Message-ID: <BAY10-F119gIjOiwsN300005a20@hotmail.com>

OK, I finally timed my ME-6000.  It takes about 20 seconds to get to the 
init scripts.  Even though I have the framebuffer support compiled into 
2.6.4, the kernel doesn't ever see the vesafb device.  Although the same 
kernel sees it from award bios boot.

I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.

Is it possible something isn't set right in filo or LB?  I have

option HAVE_FRAMEBUFFER=1 in linuxbios config.

Any help is appreciated.  Thanks to all who contributed.

M.R.

>From: "Dmitry Borisov" <jbors at mail.ru>
>To: <Linuxbios at clustermatic.org>
>Subject: EPIA-M startup times
>Date: Mon, 26 Apr 2004 19:34:00 -0700
>
>Guys,
>Just wanted to have your estimate about startup times for EPIA-M mobo.
>ATM it takes about 9 secs to go to payload. 7 secs to go to splash. Which 
>seems to be really high values.
>Does anyone can say what it would be if everything is "perfect" ?
>How much time at minimum the BIOS can take assuming RAM, VGA and PCI 
>initialized properly ?
>
>If the answer would be 4 secs in ideal case, I'll invest some time to 
>tighten it up... If 9 secs is a minimum, then...
>
>Any suggestions ?
>Dmitry/

_________________________________________________________________
Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com



From stepan at openbios.org  Thu May  6 17:48:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May  6 17:48:01 2004
Subject: ??????: ??????: Which kernel for framebuffering?
In-Reply-To: <1083880424.2459.107.camel@exponential.lanl.gov>
References: <3174569B9743D511922F00A0C943142305063A0D@TYANWEB> <1083880424.2459.107.camel@exponential.lanl.gov>
Message-ID: <20040506230535.GA4105@openbios.org>

* Li-Ta Lo <ollie at lanl.gov> [040506 23:53]:
> 
> BTW, does the BTEXT use the graphics card in legacy mode
> or in framebuffer mode ?

Framebuffer.

    Stefan
 


From YhLu at tyan.com  Thu May  6 18:28:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May  6 18:28:01 2004
Subject: FILO boot from SATA disk on SI 3114.
Message-ID: <3174569B9743D511922F00A0C943142305063A35@TYANWEB>

With some changes to filo, the sata can be used as normal IDE device in
filo.

Last problem in filo is only can boot from port 0 and port 1, and can not
boot from port 2 and port 3. That is SI 3114 limitation.

After install SUSE 9 Pro for AMD64, use following can boot into disk.
hde2:/boot/vmlinuz initrd=/boot/initrd ro root=/dev/sda2 console=tty0
console=ttyS0,115200

Please note "root=/dev/sda2", because kernel in Suse think it is SCSI just
as new 2.6 kernel.

regards

YH


-----????-----
???: YhLu 
????: 2004?4?28? 21:12
???: ron minnich; Langlois Evan
??: Hendricks David W.; linuxbios at clustermatic.org
??: Re: LinuxBIOS Video?

1. S2875 support is in the CVS tree already.
2. ATI randon --- At this time, you may not get the output from very
beginning.
3. boot sata --- good question, I will try that. Maybe need to add some code
in filo. 

Regards

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


From rsmith at bitworks.com  Thu May  6 19:49:01 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Thu May  6 19:49:01 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <m3r7txo27y.fsf@zaphod.goldshmidt.org>
References: <20040503171410.Q51417-100000@www.missl.cs.umd.edu> <m3r7txo27y.fsf@zaphod.goldshmidt.org>
Message-ID: <409AE0C1.6090504@bitworks.com>

How do I specify 2 superios in V1 that are the same chip only different 
pnp bases using nsuperio?




From rminnich at lanl.gov  Thu May  6 19:59:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May  6 19:59:00 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <409AE0C1.6090504@bitworks.com>
Message-ID: <Pine.LNX.4.44.0405061914580.23852-100000@maxroach.lanl.gov>

On Thu, 6 May 2004, Richard Smith wrote:

> How do I specify 2 superios in V1 that are the same chip only different 
> pnp bases using nsuperio?

here's how it should work (example, two same part at 0x370 and 0x3f0):

nsuperio SMC/fdc37b72x com1={1} port=0x370
nsuperio SMC/fdc37b72x com1={1} port=0x3f0




From rsmith at bitworks.com  Thu May  6 20:09:01 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Thu May  6 20:09:01 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <Pine.LNX.4.44.0405061914580.23852-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405061914580.23852-100000@maxroach.lanl.gov>
Message-ID: <409AE579.7090906@bitworks.com>

ron minnich wrote:

> On Thu, 6 May 2004, Richard Smith wrote:
> 
> 
>>How do I specify 2 superios in V1 that are the same chip only different 
>>pnp bases using nsuperio?
> 
> 
> here's how it should work (example, two same part at 0x370 and 0x3f0):
> 
> nsuperio SMC/fdc37b72x com1={1} port=0x370
> nsuperio SMC/fdc37b72x com1={1} port=0x3f0


Thats kinda what I though but here's the nsuperio.c that gets built

#include <pci.h>
extern struct superio_control superio_NSC_pc87351_control;
struct superio superio_NSC_pc87351= { &superio_NSC_pc87351_control, 
.keyboard=1, .com1={1}, .com2={1}, .floppy=0, .lpt=0, .mouse=1,
.port=0x2f};
extern struct superio_control superio_NSC_pc87351_control;
struct superio superio_NSC_pc87351= { &superio_NSC_pc87351_control, 
.keyboard=1, .com1={1}, .com2={1}, .floppy=0, .lpt=0, .mouse=1, .port=0x2f};
struct superio *all_superio[] = {&superio_NSC_pc87351,
&superio_NSC_pc87351,
};
unsigned long nsuperio = 2;

As you can see you end up with 2 structs that are the same name which 
won't build.




From rminnich at lanl.gov  Thu May  6 20:16:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May  6 20:16:00 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <409AE579.7090906@bitworks.com>
Message-ID: <Pine.LNX.4.44.0405061932090.23852-100000@maxroach.lanl.gov>

bug. I screwed up. 

I'll try to see how to fix this. It will take me a bit but I think it is 
easy, I did handle this in V2.

ron



From pub at goldshmidt.org  Fri May  7 00:42:01 2004
From: pub at goldshmidt.org (Oleg Goldshmidt)
Date: Fri May  7 00:42:01 2004
Subject: Diskless Windows??
In-Reply-To: <m3ekpx32j8.fsf@maxwell.lnxi.com>
References: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>
	<m3r7txo27y.fsf@zaphod.goldshmidt.org>
	<m3ekpx32j8.fsf@maxwell.lnxi.com>
Message-ID: <m3n04kobml.fsf@zaphod.goldshmidt.org>

ebiederman at lnxi.com (Eric W. Biederman) writes:

> It sounds like from the description there is no way to do windows diskless
> without emulating a disk.

I am not sure I understand what you mean. Isn't that what iSCSI is
about: everything above that thinks there is a local SCSI disk...

> I have serious issues with iSCSI because the only implementation I have
> seen was tremendously complex and nasty looking.  Which is a real downside
> when compared to something simple like nbd.

Well, I don't know what implementations you have seen. There are
undoubtedly some ugly ones. That's an implementation issue, though:
the basic idea looks quite clean to me. Not that there are no issues...

> How well does iBOOT work on the linux side.  

Better ;-)

> If you have an iSCSI driver for Linux.

We do.

-- 
Oleg Goldshmidt | pub at NOSPAM.goldshmidt.org


From pub at goldshmidt.org  Fri May  7 00:46:00 2004
From: pub at goldshmidt.org (Oleg Goldshmidt)
Date: Fri May  7 00:46:00 2004
Subject: Diskless Windows??
In-Reply-To: <20040506131213.S29924-100000@www.missl.cs.umd.edu>
References: <20040506131213.S29924-100000@www.missl.cs.umd.edu>
Message-ID: <m3isf8obhc.fsf@zaphod.goldshmidt.org>

Adam Sulmicki <adam at cfar.umd.edu> writes:

> seems to me like this solution basically redirect BIOS I/O interrupts.
> 
> What happens once Windows boots up and attempt to access hardware directly
> without BIOS calls in between? Is Windows smart enough to work by default
> with hdd (for example : what about swap?)

You have to solve the problem at BIOS time and at OS time,
obviously. Google for "Windows iSCSI" to get an idea of iSCSI support
in Windows. Booting is more complicated for a variety of reasons.

-- 
Oleg Goldshmidt | pub at NOSPAM.goldshmidt.org


From stepan at openbios.org  Fri May  7 02:38:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Fri May  7 02:38:01 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <Pine.LNX.4.44.0405061932090.23852-100000@maxroach.lanl.gov>
References: <409AE579.7090906@bitworks.com> <Pine.LNX.4.44.0405061932090.23852-100000@maxroach.lanl.gov>
Message-ID: <20040507075605.GA8453@openbios.org>

* ron minnich <rminnich at lanl.gov> [040507 03:32]:
> bug. I screwed up. 
> 
> I'll try to see how to fix this. It will take me a bit but I think it is 
> easy, I did handle this in V2.

Before getting into backporting a lot, Richard, can your motherboard be
ported to V2?

  Stefan



From ebiederman at lnxi.com  Fri May  7 05:05:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May  7 05:05:01 2004
Subject: Diskless Windows??
In-Reply-To: <m3isf8obhc.fsf@zaphod.goldshmidt.org>
References: <20040506131213.S29924-100000@www.missl.cs.umd.edu>
	<m3isf8obhc.fsf@zaphod.goldshmidt.org>
Message-ID: <m33c6c8rdr.fsf@maxwell.lnxi.com>

Oleg Goldshmidt <pub at goldshmidt.org> writes:

> Adam Sulmicki <adam at cfar.umd.edu> writes:
> 
> > seems to me like this solution basically redirect BIOS I/O interrupts.
> > 
> > What happens once Windows boots up and attempt to access hardware directly
> > without BIOS calls in between? Is Windows smart enough to work by default
> > with hdd (for example : what about swap?)
> 
> You have to solve the problem at BIOS time and at OS time,
> obviously. Google for "Windows iSCSI" to get an idea of iSCSI support
> in Windows. Booting is more complicated for a variety of reasons.

OK.  With iSCSI you really are doing a disked based boot, and
have the same issues you have booting from fiber channel or any
other disk that does not have an OS based driver.  The rough edges
are different but the basic problems are the same.  

That make sense.

Eric


From ebiederman at lnxi.com  Fri May  7 05:16:02 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May  7 05:16:02 2004
Subject: Diskless Windows??
In-Reply-To: <m3n04kobml.fsf@zaphod.goldshmidt.org>
References: <20040503171410.Q51417-100000@www.missl.cs.umd.edu>
	<m3r7txo27y.fsf@zaphod.goldshmidt.org>
	<m3ekpx32j8.fsf@maxwell.lnxi.com>
	<m3n04kobml.fsf@zaphod.goldshmidt.org>
Message-ID: <m3y8o47clk.fsf@maxwell.lnxi.com>

Oleg Goldshmidt <pub at goldshmidt.org> writes:

> ebiederman at lnxi.com (Eric W. Biederman) writes:
> 
> > It sounds like from the description there is no way to do windows diskless
> > without emulating a disk.
> 
> I am not sure I understand what you mean. Isn't that what iSCSI is
> about: everything above that thinks there is a local SCSI disk...

There are some efficiencies to be gained by not having a remote disk,
and instead having a remote filesystem.  From everything I have
heard that does not sound like it has been implemented for windows
with NT kernels.
 
> > I have serious issues with iSCSI because the only implementation I have
> > seen was tremendously complex and nasty looking.  Which is a real downside
> > when compared to something simple like nbd.
> 
> Well, I don't know what implementations you have seen. There are
> undoubtedly some ugly ones. That's an implementation issue, though:
> the basic idea looks quite clean to me. Not that there are no issues...

nbd is 600 likes of obviously correct code, which can put full disk
speed onto the wire.  Nor have I seen any issues with it.  That
makes tough competition for iSCSI in modest deployment locations.

I still need to read the spec to see how sane iSCSI looks on the wire.
 
> > How well does iBOOT work on the linux side.  
> 
> Better ;-)
> 
> > If you have an iSCSI driver for Linux.
> 
> We do.

Cool.  If iSCSI looks sane I will suggest to the etherboot guys that
we implementing booting over it :)

Eric


From rsmith at bitworks.com  Fri May  7 09:11:01 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Fri May  7 09:11:01 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <20040507075605.GA8453@openbios.org>
References: <409AE579.7090906@bitworks.com> <Pine.LNX.4.44.0405061932090.23852-100000@maxroach.lanl.gov> <20040507075605.GA8453@openbios.org>
Message-ID: <409B9CC8.5070504@bitworks.com>

Stefan Reinauer wrote:

> * ron minnich <rminnich at lanl.gov> [040507 03:32]:
> 
>>bug. I screwed up. 
>>
>>I'll try to see how to fix this. It will take me a bit but I think it is 
>>easy, I did handle this in V2.
> 
> Before getting into backporting a lot, Richard, can your motherboard be
> ported to V2?

Not without a lot of work.  I'm one of the few 440bx users and no mem 
init code for this chipset has been written in V2 yet.  I need spd 
detection.  I keep waiting for the epia to get this all working and then 
I might look at porting forward.

I also currently use ADLO and LILO.  Eventually I'll move to FILO but 
right now I have my hands, feet and head buried under tyring to get an 
ATI M1 chip up without a bios.

ADLO is not strictly necessary.  I used it to run my Assiliaint 69000 
video bios.  Dosen't work with ATI so once I have an ATI solution I 
won't need ADLO.




From rminnich at lanl.gov  Fri May  7 11:49:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May  7 11:49:00 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <409B9CC8.5070504@bitworks.com>
Message-ID: <Pine.LNX.4.44.0405071105270.30154-100000@maxroach.lanl.gov>

I will try to fix v1 config tool today.

ron



From adam at cfar.umd.edu  Fri May  7 11:58:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May  7 11:58:00 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <409B9CC8.5070504@bitworks.com>
Message-ID: <20040507132112.E59570-100000@www.missl.cs.umd.edu>

> I also currently use ADLO and LILO.

I'm curious, how many people actually use ADLO?  I had been recently
speaking with Kevin Lawton (of BOCHS fame) and he was curious about it. He
also mentioned that BOCHS runs Windows XP (well) those days and was
curious if this success has been transposed into ADLO as well.




From rsmith at bitworks.com  Fri May  7 13:32:00 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Fri May  7 13:32:00 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <20040507132112.E59570-100000@www.missl.cs.umd.edu>
References: <20040507132112.E59570-100000@www.missl.cs.umd.edu>
Message-ID: <409BD9E4.5050103@bitworks.com>

Adam Sulmicki wrote:

>>I also currently use ADLO and LILO.
> 
> I'm curious, how many people actually use ADLO?  I had been recently
> speaking with Kevin Lawton (of BOCHS fame) and he was curious about it. He
> also mentioned that BOCHS runs Windows XP (well) those days and was
> curious if this success has been transposed into ADLO as well.

Does the BIOS of later versions of BOCHS handle video int10 replacement 
correctly?  That would make my life a whole lot easier right now.




From adam at cfar.umd.edu  Fri May  7 13:39:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May  7 13:39:01 2004
Subject: V1 2 superio chips of the same type
In-Reply-To: <409BD9E4.5050103@bitworks.com>
Message-ID: <20040507150355.I59570-100000@www.missl.cs.umd.edu>

> >>I also currently use ADLO and LILO.
> >
> > I'm curious, how many people actually use ADLO?  I had been recently
> > speaking with Kevin Lawton (of BOCHS fame) and he was curious about it. He
> > also mentioned that BOCHS runs Windows XP (well) those days and was
> > curious if this success has been transposed into ADLO as well.
>
> Does the BIOS of later versions of BOCHS handle video int10 replacement
> correctly?  That would make my life a whole lot easier right now.

uh, I don't remember it being problem i the first place.



From flavio_grupos at yahoo.com.br  Fri May  7 14:39:00 2004
From: flavio_grupos at yahoo.com.br (=?iso-8859-1?q?Flavio=20Tobias?=)
Date: Fri May  7 14:39:00 2004
Subject: Is possible Linux on flash memory?
Message-ID: <20040507195618.16465.qmail@web90001.mail.scd.yahoo.com>

How can I boot and run Linux from a PenDrive or CompactFlash or other kind of flash memory device?
How can I do that?
There is some documentation about this?
There is motherboards that suport this? Wich ones?
 
Thanks
Flavio
 



---------------------------------
Yahoo! Messenger - Fale com seus amigos online. Instale agora!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040507/affc5972/attachment.html>

From rminnich at lanl.gov  Fri May  7 14:52:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May  7 14:52:00 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <20040507195618.16465.qmail@web90001.mail.scd.yahoo.com>
Message-ID: <Pine.LNX.4.44.0405071408040.30154-100000@maxroach.lanl.gov>

On Fri, 7 May 2004, Flavio Tobias wrote:

> How can I boot and run Linux from a PenDrive or CompactFlash or other kind of flash memory device?

sure. 

> How can I do that?

you'll have to hope somebody here can show you. 

> There is some documentation about this?

our docs are terrible.

> There is motherboards that suport this? Wich ones?

anything with IDE->CF or CF slots


ron



From YhLu at tyan.com  Fri May  7 15:26:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May  7 15:26:01 2004
Subject: =?GB2312?B?tPC4tDogVjEgMiBzdXBlcmlvIGNoaXBzIG9mIHRoZSBzYW1lIHR5?=
	=?GB2312?B?cGU=?=
Message-ID: <3174569B9743D511922F00A0C943142305063AD1@TYANWEB>

Where can I find the latest ADLO and BOCHS?

I want to boot windows 2000 with it?

YH

-----????-----
???: Adam Sulmicki [mailto:adam at cfar.umd.edu] 
????: 2004?5?7? 12:04
???: Richard Smith
??: stepan at openbios.org; ron minnich; linuxbios at clustermatic.org
??: Re: V1 2 superio chips of the same type

> >>I also currently use ADLO and LILO.
> >
> > I'm curious, how many people actually use ADLO?  I had been recently
> > speaking with Kevin Lawton (of BOCHS fame) and he was curious about it.
He
> > also mentioned that BOCHS runs Windows XP (well) those days and was
> > curious if this success has been transposed into ADLO as well.
>
> Does the BIOS of later versions of BOCHS handle video int10 replacement
> correctly?  That would make my life a whole lot easier right now.

uh, I don't remember it being problem i the first place.

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


From adam at cfar.umd.edu  Fri May  7 15:33:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May  7 15:33:00 2004
Subject: =?GB2312?B?tPC4tDogVjEgMiBzdXBlcmlvIGNoaXBzIG9mIHRoZSBzYW1lIHR5?=
 =?GB2312?B?cGU=?=
In-Reply-To: <3174569B9743D511922F00A0C943142305063AD1@TYANWEB>
Message-ID: <20040507165430.D59570-100000@www.missl.cs.umd.edu>

On Fri, 7 May 2004, YhLu wrote:

> Where can I find the latest ADLO and BOCHS?

latest ADLO should be in CVS tree for LinuxBIOS v1.

as for latest BOCHS BIOS looks CVS for BOCHS program. it is reasonable
they made number of improvements to it in the last year (and possibly
number of time-dependent bugs). So it is a trade off which BOCHS BIOS you
want to use.

> I want to boot windows 2000 with it?

yes, we could boot Win2K and unmodified linux with it.

the main problem here was that mainteance of the 16 bit bochs BIOS was
nightmare. number of static entry points, etc. it is what put off most
people (including me).

it is basically two conflicting goals here. one is legacy code which
allows you to boot windows, and then there's legayc-free bios in form of
LinuxBIOS. it just donesn't get along too well.



From ollie at lanl.gov  Fri May  7 15:47:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Fri May  7 15:47:01 2004
Subject: Enable or Disable ?
Message-ID: <1083963834.2459.120.camel@exponential.lanl.gov>

Eric,

I still don't understand why we have to enable some device
even the config file says the device is disabled. The code
in pci_device.c:pci_scan_bus()

		if (dev->chip && dev->chip->control &&
		    dev->chip->control->enable_dev) {
			int enabled  = dev->enabled;
			dev->enabled = 1;
			dev->chip->control->enable_dev(dev);
			dev->enabled = enabled;
		}

tries to ignore the dev->enabled flag and enable the device.
Later the enable_dev() or enable() is called again.

Ollie




From ebiederman at lnxi.com  Fri May  7 16:58:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May  7 16:58:00 2004
Subject: Enable or Disable ?
In-Reply-To: <1083963834.2459.120.camel@exponential.lanl.gov>
References: <1083963834.2459.120.camel@exponential.lanl.gov>
Message-ID: <m3hduryj69.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> Eric,
> 
> I still don't understand why we have to enable some device
> even the config file says the device is disabled. The code
> in pci_device.c:pci_scan_bus()
> 
> 		if (dev->chip && dev->chip->control &&
> 		    dev->chip->control->enable_dev) {
> 			int enabled  = dev->enabled;
> 			dev->enabled = 1;
> 			dev->chip->control->enable_dev(dev);
> 			dev->enabled = enabled;
> 		}
> 
> tries to ignore the dev->enabled flag and enable the device.
> Later the enable_dev() or enable() is called again.

Because we don't know what kind of devices it is, just that it exists.
We temporarily enable the device's config space so we can look up the
type of device (vendor/device id) and get more specific methods.  In
the case of the 8111 it does not matter.  For some chips we may need
to do more to disable an device than just disable it's pci
configuration space. 

The other half of the picture is that doing it that way more reliably
tests the code paths of a device.  So we catch it if someone forgets
to implement the code needed if the device is enabled.

Probably that piece of code deserves a comment.

Eric


From ebiederman at lnxi.com  Fri May  7 21:05:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May  7 21:05:00 2004
Subject: Pleased experienced on EPIA : Linuxbios runs,but smbus errors, no normal rom starting, payload making difficulties
In-Reply-To: <1083852388.1279.151.camel@Calliphara>
References: <1083852388.1279.151.camel@Calliphara>
Message-ID: <m3oeozslg9.fsf@maxwell.lnxi.com>

Mathieu Deschamps <mdeschamps at mangrove-systems.com> writes:

> Hello,
> [...]
> 
> 
> I intended to make a IDE elfImagepayload to boot a kernel
> on a hard disk, I've read that LinuxBios alone could do that quite
> well.
> So got mkelfImage 1.16 (i know it's quite old
> but i can't find a link to a recent one- BTW please a link to a more
> recent one would be appreciated). 

ftp://ftp.lnxi.com/pub/mkelfImage
2.5 should work better.

Also the LinuxBIOS list is a good place to ask questions like this
in case I get distracted.


Eric


From kfuchs at winternet.com  Fri May  7 21:13:00 2004
From: kfuchs at winternet.com (Ken Fuchs)
Date: Fri May  7 21:13:00 2004
Subject: Is possible Linux on flash memory?
Message-ID: <200405080230.i482UAk32169@ecstasy1.winternet.com>

LinuxBIOS doesn't support USB pen drives or USB compact flash.  It does
support ATA (IDE) flash devices.

On a normal (proprietary) BIOS:

Booting from USB is supported on many newer motherboards with a BIOS
that supports this.  I use Flonix to boot from a 64MB USB pen drive:

http://mir2.ovh.net/flonix/

The Flonix forums are at:

http://www.flonix.com/support/viewforum.php?f=11

I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
2-16-2004, I was able to install it's syslinux 2.04 bootloader:

# syslinux /dev/sda1

To make Flonix bootable, you can also use the above command from
the Knoppix live CD.

(The first USB flash is /dev/sda, if there are _no_ SCSI drives.
Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with two
SCSI hard drives with special files /dev/sda and /dev/sdb.)

There are other Linux distributions built to be installed on a USB pen
drive or flash.

Check out http://www.linux-usb.org/ for general Linux USB information.

BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br and it
bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
Sorry.

Sincerely,

Ken Fuchs <kfuchs at winternet.com>


From pyro at linuxlabs.com  Fri May  7 22:03:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Fri May  7 22:03:01 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <200405080230.i482UAk32169@ecstasy1.winternet.com>
References: <200405080230.i482UAk32169@ecstasy1.winternet.com>
Message-ID: <Pine.LNX.4.58.0405080316550.6056@ucontrol.mobiledns.com>

Greetings,

I've checked in the start of USB booting in util/baremetal/usb.
It will actually load an ELF image written to the raw device. I haven't
been able to find enough time yet to integrate it into FILO, but it should
probably go there.

G'day,
sjames


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


On Fri, 7 May 2004, Ken Fuchs wrote:

> LinuxBIOS doesn't support USB pen drives or USB compact flash.  It does
> support ATA (IDE) flash devices.
>
> On a normal (proprietary) BIOS:
>
> Booting from USB is supported on many newer motherboards with a BIOS
> that supports this.  I use Flonix to boot from a 64MB USB pen drive:
>
> http://mir2.ovh.net/flonix/
>
> The Flonix forums are at:
>
> http://www.flonix.com/support/viewforum.php?f=11
>
> I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
>
> # syslinux /dev/sda1
>
> To make Flonix bootable, you can also use the above command from
> the Knoppix live CD.
>
> (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with two
> SCSI hard drives with special files /dev/sda and /dev/sdb.)
>
> There are other Linux distributions built to be installed on a USB pen
> drive or flash.
>
> Check out http://www.linux-usb.org/ for general Linux USB information.
>
> BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br and it
> bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> Sorry.
>
> Sincerely,
>
> Ken Fuchs <kfuchs at winternet.com>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From YhLu at tyan.com  Fri May  7 22:31:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May  7 22:31:01 2004
Subject: =?GB2312?B?tPC4tDogSXMgcG9zc2libGUgTGludXggb24gZmxhc2ggbWVtb3J5?=
	=?GB2312?B?Pw==?=
Message-ID: <3174569B9743D511922F00A0C943142305063B2D@TYANWEB>

Does it work now?

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?7? 20:20
???: Ken Fuchs
??: linuxbios at clustermatic.org
??: Re: Is possible Linux on flash memory?

Greetings,

I've checked in the start of USB booting in util/baremetal/usb.
It will actually load an ELF image written to the raw device. I haven't
been able to find enough time yet to integrate it into FILO, but it should
probably go there.

G'day,
sjames


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


On Fri, 7 May 2004, Ken Fuchs wrote:

> LinuxBIOS doesn't support USB pen drives or USB compact flash.  It does
> support ATA (IDE) flash devices.
>
> On a normal (proprietary) BIOS:
>
> Booting from USB is supported on many newer motherboards with a BIOS
> that supports this.  I use Flonix to boot from a 64MB USB pen drive:
>
> http://mir2.ovh.net/flonix/
>
> The Flonix forums are at:
>
> http://www.flonix.com/support/viewforum.php?f=11
>
> I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
>
> # syslinux /dev/sda1
>
> To make Flonix bootable, you can also use the above command from
> the Knoppix live CD.
>
> (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with two
> SCSI hard drives with special files /dev/sda and /dev/sdb.)
>
> There are other Linux distributions built to be installed on a USB pen
> drive or flash.
>
> Check out http://www.linux-usb.org/ for general Linux USB information.
>
> BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br and it
> bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> Sorry.
>
> Sincerely,
>
> Ken Fuchs <kfuchs at winternet.com>
> _______________________________________________
> 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


From hansolofalcon at worldnet.att.net  Sat May  8 00:14:01 2004
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Sat May  8 00:14:01 2004
Subject: CVS server naming reset---webpages need to be reset
Message-ID: <000001c434bd$bfcd90c0$6401a8c0@who5>

Hello from Gregg C Levine
Apologies in advance for the wordiness of the message, but I wanted to
present everything that led up to the title of the mail message.

Everyone, who in this group manages the website's pages on the subject
of CVS? The Source Forge pages will need to be reset, as will be the
one on www.linuxbios.org .

Reason being that our good friends at Source Forge, made a few changes
in their BIND software, and well they said it best:
( 2004-05-03 05:41:25 - Project CVS Service ) As of 2004-04-28 the CVS
services will no longer function with the hostname of
cvs.PROJECTNAME.sourceforge.net. You should change your CVS commands
to use the host cvs.sourceforge.net (the fix for this under all
platforms is to perform a checkout into a new directory using the new
hostname) and that should resolve any outstanding issues that you may
have (this includes issues relating to the SSH host key change
warning, among others). This issue came about as a result of upgrading
from BIND 8 to BIND 9 which doesn't allow for a wildcard in the middle
of a hostname.

Obviously they should have e-mailed that blurb to all project leaders,
for all of the hosted projects, but, ah, they probably expected them
to read the status report page, as I did.

I discovered that, early on when I had problems downloading source
code for a totally different project. I gave up on it, when I realized
I didn't need them.

However regarding the recent discussion on USB flash drives, it
revived an interest of mine regarding same, I refreshed my memory
going over the relevant e-mail messages from the archive. I did have
to update my local storage, and that's why this whole business
surfaced. Anyway on that theme, and subject, more later when I try out
one of my ideas.

Anyway I did notice the rearrangement of the stored files, and such
like, and I appreciate the neat layout of same. 
-------------------
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




From hansolofalcon at worldnet.att.net  Sat May  8 00:21:01 2004
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Sat May  8 00:21:01 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <Pine.LNX.4.58.0405080316550.6056@ucontrol.mobiledns.com>
Message-ID: <000101c434be$b7a9b6c0$6401a8c0@who5>

Hello from Gregg C Levine
It happens I just finished examining the code for the contents of that
directory. But I've got just one question pending at the moment, how
do you mean, "It will actually load an ELF image written to the raw
device.". Explain that line of reasoning. Do you mean a kernel that's
been pushed through the creation tool that Eric has created? And "raw
device", now I'm lost, how about clarifying your position?
-------------------
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

> -----Original Message-----
> From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> admin at clustermatic.org] On Behalf Of Steven James
> Sent: Friday, May 07, 2004 11:20 PM
> To: Ken Fuchs
> Cc: linuxbios at clustermatic.org
> Subject: Re: Is possible Linux on flash memory?
> 
> Greetings,
> 
> I've checked in the start of USB booting in util/baremetal/usb.
> It will actually load an ELF image written to the raw device. I
haven't
> been able to find enough time yet to integrate it into FILO, but it
should
> probably go there.
> 
> G'day,
> sjames
> 
> 
> -------------------------steven james, director of research, linux
labs
> ... ........ ..... ....                    230 peachtree st nw ste
2701
> the original linux labs                             atlanta.ga.us
30303
>       -since 1995
http://www.linuxlabs.com
>                                               office & fax
866.545.6306
>
----------------------------------------------------------------------
-
> 
> 
> On Fri, 7 May 2004, Ken Fuchs wrote:
> 
> > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
does
> > support ATA (IDE) flash devices.
> >
> > On a normal (proprietary) BIOS:
> >
> > Booting from USB is supported on many newer motherboards with a
BIOS
> > that supports this.  I use Flonix to boot from a 64MB USB pen
drive:
> >
> > http://mir2.ovh.net/flonix/
> >
> > The Flonix forums are at:
> >
> > http://www.flonix.com/support/viewforum.php?f=11
> >
> > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> >
> > # syslinux /dev/sda1
> >
> > To make Flonix bootable, you can also use the above command from
> > the Knoppix live CD.
> >
> > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
two
> > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> >
> > There are other Linux distributions built to be installed on a USB
pen
> > drive or flash.
> >
> > Check out http://www.linux-usb.org/ for general Linux USB
information.
> >
> > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
and it
> > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > Sorry.
> >
> > Sincerely,
> >
> > Ken Fuchs <kfuchs at winternet.com>
> > _______________________________________________
> > 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



From pyro at linuxlabs.com  Sat May  8 07:00:00 2004
From: pyro at linuxlabs.com (Steven James)
Date: Sat May  8 07:00:00 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <000101c434be$b7a9b6c0$6401a8c0@who5>
References: <000101c434be$b7a9b6c0$6401a8c0@who5>
Message-ID: <Pine.LNX.4.58.0405081214340.6056@ucontrol.mobiledns.com>

Greetings,

Yes, a kernel processed with Eric's mkelfImage.

I don't have any filesystem code in the loader, so rather than mounting a
filesystem on the USB storage device, you need to partition it and then dd
the kernel image to the first partition.

e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1

G'day,
sjames


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


On Sat, 8 May 2004, Gregg C Levine wrote:

> Hello from Gregg C Levine
> It happens I just finished examining the code for the contents of that
> directory. But I've got just one question pending at the moment, how
> do you mean, "It will actually load an ELF image written to the raw
> device.". Explain that line of reasoning. Do you mean a kernel that's
> been pushed through the creation tool that Eric has created? And "raw
> device", now I'm lost, how about clarifying your position?
> -------------------
> 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
>
> > -----Original Message-----
> > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > admin at clustermatic.org] On Behalf Of Steven James
> > Sent: Friday, May 07, 2004 11:20 PM
> > To: Ken Fuchs
> > Cc: linuxbios at clustermatic.org
> > Subject: Re: Is possible Linux on flash memory?
> >
> > Greetings,
> >
> > I've checked in the start of USB booting in util/baremetal/usb.
> > It will actually load an ELF image written to the raw device. I
> haven't
> > been able to find enough time yet to integrate it into FILO, but it
> should
> > probably go there.
> >
> > G'day,
> > sjames
> >
> >
> > -------------------------steven james, director of research, linux
> labs
> > ... ........ ..... ....                    230 peachtree st nw ste
> 2701
> > the original linux labs                             atlanta.ga.us
> 30303
> >       -since 1995
> http://www.linuxlabs.com
> >                                               office & fax
> 866.545.6306
> >
> ----------------------------------------------------------------------
> -
> >
> >
> > On Fri, 7 May 2004, Ken Fuchs wrote:
> >
> > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> does
> > > support ATA (IDE) flash devices.
> > >
> > > On a normal (proprietary) BIOS:
> > >
> > > Booting from USB is supported on many newer motherboards with a
> BIOS
> > > that supports this.  I use Flonix to boot from a 64MB USB pen
> drive:
> > >
> > > http://mir2.ovh.net/flonix/
> > >
> > > The Flonix forums are at:
> > >
> > > http://www.flonix.com/support/viewforum.php?f=11
> > >
> > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > >
> > > # syslinux /dev/sda1
> > >
> > > To make Flonix bootable, you can also use the above command from
> > > the Knoppix live CD.
> > >
> > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> two
> > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > >
> > > There are other Linux distributions built to be installed on a USB
> pen
> > > drive or flash.
> > >
> > > Check out http://www.linux-usb.org/ for general Linux USB
> information.
> > >
> > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> and it
> > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > Sorry.
> > >
> > > Sincerely,
> > >
> > > Ken Fuchs <kfuchs at winternet.com>
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From yhlu at tyan.com  Sat May  8 11:31:01 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sat May  8 11:31:01 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <Pine.LNX.4.58.0405081214340.6056@ucontrol.mobiledns.com>
Message-ID: <200405081530.i48FUXK16370@nwn.definitive.org>

Does it work now?

If it works with raw device, after merge it into filo, it should use file system FAT etc.

Regards

YH

-----????-----
???: linuxbios-admin at clustermatic.org [mailto:linuxbios-admin at clustermatic.org] ?? Steven James
????: 2004?5?8? 5:18
???: Gregg C Levine
??: linuxbios at clustermatic.org
??: RE: Is possible Linux on flash memory?

Greetings,

Yes, a kernel processed with Eric's mkelfImage.

I don't have any filesystem code in the loader, so rather than mounting a
filesystem on the USB storage device, you need to partition it and then dd
the kernel image to the first partition.

e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1

G'day,
sjames


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


On Sat, 8 May 2004, Gregg C Levine wrote:

> Hello from Gregg C Levine
> It happens I just finished examining the code for the contents of that
> directory. But I've got just one question pending at the moment, how
> do you mean, "It will actually load an ELF image written to the raw
> device.". Explain that line of reasoning. Do you mean a kernel that's
> been pushed through the creation tool that Eric has created? And "raw
> device", now I'm lost, how about clarifying your position?
> -------------------
> 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
>
> > -----Original Message-----
> > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > admin at clustermatic.org] On Behalf Of Steven James
> > Sent: Friday, May 07, 2004 11:20 PM
> > To: Ken Fuchs
> > Cc: linuxbios at clustermatic.org
> > Subject: Re: Is possible Linux on flash memory?
> >
> > Greetings,
> >
> > I've checked in the start of USB booting in util/baremetal/usb.
> > It will actually load an ELF image written to the raw device. I
> haven't
> > been able to find enough time yet to integrate it into FILO, but it
> should
> > probably go there.
> >
> > G'day,
> > sjames
> >
> >
> > -------------------------steven james, director of research, linux
> labs
> > ... ........ ..... ....                    230 peachtree st nw ste
> 2701
> > the original linux labs                             atlanta.ga.us
> 30303
> >       -since 1995
> http://www.linuxlabs.com
> >                                               office & fax
> 866.545.6306
> >
> ----------------------------------------------------------------------
> -
> >
> >
> > On Fri, 7 May 2004, Ken Fuchs wrote:
> >
> > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> does
> > > support ATA (IDE) flash devices.
> > >
> > > On a normal (proprietary) BIOS:
> > >
> > > Booting from USB is supported on many newer motherboards with a
> BIOS
> > > that supports this.  I use Flonix to boot from a 64MB USB pen
> drive:
> > >
> > > http://mir2.ovh.net/flonix/
> > >
> > > The Flonix forums are at:
> > >
> > > http://www.flonix.com/support/viewforum.php?f=11
> > >
> > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > >
> > > # syslinux /dev/sda1
> > >
> > > To make Flonix bootable, you can also use the above command from
> > > the Knoppix live CD.
> > >
> > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> two
> > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > >
> > > There are other Linux distributions built to be installed on a USB
> pen
> > > drive or flash.
> > >
> > > Check out http://www.linux-usb.org/ for general Linux USB
> information.
> > >
> > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> and it
> > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > Sorry.
> > >
> > > Sincerely,
> > >
> > > Ken Fuchs <kfuchs at winternet.com>
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> 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



From pyro at linuxlabs.com  Sat May  8 11:56:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Sat May  8 11:56:01 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <200405081530.i48FUXK16370@nwn.definitive.org>
References: <200405081530.i48FUXK16370@nwn.definitive.org>
Message-ID: <Pine.LNX.4.58.0405081711250.6056@ucontrol.mobiledns.com>

Greetings,

It works on USB drives that do SCSI over bulk transport. For other drives,
more work will be needed, but I don't have one of those. It can also
enumerate hubs like the iMac keyboard.

G'day,
sjames


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


On Sat, 8 May 2004, Yinghai Lu wrote:

> Does it work now?
>
> If it works with raw device, after merge it into filo, it should use file system FAT etc.
>
> Regards
>
> YH
>
> -----????-----
> ???: linuxbios-admin at clustermatic.org [mailto:linuxbios-admin at clustermatic.org] ?? Steven James
> ????: 2004?5?8? 5:18
> ???: Gregg C Levine
> ??: linuxbios at clustermatic.org
> ??: RE: Is possible Linux on flash memory?
>
> Greetings,
>
> Yes, a kernel processed with Eric's mkelfImage.
>
> I don't have any filesystem code in the loader, so rather than mounting a
> filesystem on the USB storage device, you need to partition it and then dd
> the kernel image to the first partition.
>
> e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Sat, 8 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > It happens I just finished examining the code for the contents of that
> > directory. But I've got just one question pending at the moment, how
> > do you mean, "It will actually load an ELF image written to the raw
> > device.". Explain that line of reasoning. Do you mean a kernel that's
> > been pushed through the creation tool that Eric has created? And "raw
> > device", now I'm lost, how about clarifying your position?
> > -------------------
> > 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
> >
> > > -----Original Message-----
> > > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > > admin at clustermatic.org] On Behalf Of Steven James
> > > Sent: Friday, May 07, 2004 11:20 PM
> > > To: Ken Fuchs
> > > Cc: linuxbios at clustermatic.org
> > > Subject: Re: Is possible Linux on flash memory?
> > >
> > > Greetings,
> > >
> > > I've checked in the start of USB booting in util/baremetal/usb.
> > > It will actually load an ELF image written to the raw device. I
> > haven't
> > > been able to find enough time yet to integrate it into FILO, but it
> > should
> > > probably go there.
> > >
> > > G'day,
> > > sjames
> > >
> > >
> > > -------------------------steven james, director of research, linux
> > labs
> > > ... ........ ..... ....                    230 peachtree st nw ste
> > 2701
> > > the original linux labs                             atlanta.ga.us
> > 30303
> > >       -since 1995
> > http://www.linuxlabs.com
> > >                                               office & fax
> > 866.545.6306
> > >
> > ----------------------------------------------------------------------
> > -
> > >
> > >
> > > On Fri, 7 May 2004, Ken Fuchs wrote:
> > >
> > > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> > does
> > > > support ATA (IDE) flash devices.
> > > >
> > > > On a normal (proprietary) BIOS:
> > > >
> > > > Booting from USB is supported on many newer motherboards with a
> > BIOS
> > > > that supports this.  I use Flonix to boot from a 64MB USB pen
> > drive:
> > > >
> > > > http://mir2.ovh.net/flonix/
> > > >
> > > > The Flonix forums are at:
> > > >
> > > > http://www.flonix.com/support/viewforum.php?f=11
> > > >
> > > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > > >
> > > > # syslinux /dev/sda1
> > > >
> > > > To make Flonix bootable, you can also use the above command from
> > > > the Knoppix live CD.
> > > >
> > > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> > two
> > > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > > >
> > > > There are other Linux distributions built to be installed on a USB
> > pen
> > > > drive or flash.
> > > >
> > > > Check out http://www.linux-usb.org/ for general Linux USB
> > information.
> > > >
> > > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> > and it
> > > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > > Sorry.
> > > >
> > > > Sincerely,
> > > >
> > > > Ken Fuchs <kfuchs at winternet.com>
> > > > _______________________________________________
> > > > 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
> >
> > _______________________________________________
> > 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
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From hansolofalcon at worldnet.att.net  Sat May  8 15:35:01 2004
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Sat May  8 15:35:01 2004
Subject: Is possible Linux on flash memory?
Message-ID: <000e01c4353e$85be4420$6401a8c0@who5>

Hello from Gregg C Levine
It should work indeed. However, I've got a strange series of problems that might be related to my distribution's choice of versions, and I'll post the script output here in this message. However, it will be a long one.  I think some of these problems might be related to the distribution you chose, Steven, whose is it, and what's the version on it? Mine is Slackware 9.1, which came with those versions of tools.
(Script output follows.) 
That's the versions of my GCC, and binary tools.:

Script started on Sat May  8 12:59:30 2004
root at who5:/# gcc --version
gcc (GCC) 3.2.3
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

root at who5:/# ld --version
GNU ld version 2.14.90.0.6 20030820
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.
root at who5:/# exit
Script done on Sat May  8 12:59:46 2004 

This one is from the library for the bare metal project:
Script started on Sat May  8 12:47:01 2004
root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/printk.c
gcc -I ../include -I ../include/i386 -O2    -c -o serial_subr.o serial_subr.c
gcc -I ../include -I ../include/i386 -O2    -c -o subr.o subr.c
In file included from subr.c:16:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/vsprintf.c
In file included from ../../../src/lib/vsprintf.c:18:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/memcpy.c
In file included from ../../../src/lib/memcpy.c:1:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/malloc.c
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/memset.c
In file included from ../../../src/lib/memset.c:1:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/compute_ip_checksum.c
gcc -I ../include -I ../include/i386 -O2    -c -o elfboot.o elfboot.c
In file included from elfboot.c:8:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2    -c -o boot.o boot.c
In file included from boot.c:4:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2  -c ../../../src/pc80/ide/ide.c
In file included from ../../../src/pc80/ide/ide.c:26:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
../../../src/pc80/ide/ide.c:27:19: delay.h: No such file or directory
../../../src/pc80/ide/ide.c:28:17: pci.h: No such file or directory
../../../src/pc80/ide/ide.c:33: conflicting types for `harddisk_info'
../include/pc80/ide.h:54: previous declaration of `harddisk_info'
../../../src/pc80/ide/ide.c: In function `not_bsy':
../../../src/pc80/ide/ide.c:59: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:59: warning: passing arg 1 of `inb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:59: `IDE_STATUS_BSY' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:59: (Each undeclared identifier is reported only once
../../../src/pc80/ide/ide.c:59: for each function it appears in.)
../../../src/pc80/ide/ide.c: In function `ide_software_reset':
../../../src/pc80/ide/ide.c:83: `IDE_CTRL_HD15' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:83: `IDE_CTRL_SRST' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:83: `IDE_CTRL_NIEN' undeclared (first use in this function)
../../../src/pc80/ide/ide.c: At top level:
../../../src/pc80/ide/ide.c:95: warning: `struct ide_pio_command' declared inside parameter list
../../../src/pc80/ide/ide.c:95: warning: its scope is only this definition or declaration, which is probably not what you want
../../../src/pc80/ide/ide.c: In function `pio_set_registers':
../../../src/pc80/ide/ide.c:97: `uint8_t' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:97: syntax error before "device"
../../../src/pc80/ide/ide.c:99: `IDE_CTRL_HD15' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:99: `IDE_CTRL_NIEN' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:102: `device' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:103: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:104: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:111: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:112: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:112: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:112: warning: passing arg 2 of `outb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:113: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:113: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:113: warning: passing arg 2 of `outb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:114: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:115: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:116: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:117: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:118: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:119: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:120: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:120: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:120: warning: passing arg 2 of `outb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c: At top level:
../../../src/pc80/ide/ide.c:124: warning: `struct ide_pio_command' declared inside parameter list
../../../src/pc80/ide/ide.c: In function `pio_non_data':
../../../src/pc80/ide/ide.c:131: warning: passing arg 2 of `pio_set_registers' from incompatible pointer type
../../../src/pc80/ide/ide.c: At top level:
../../../src/pc80/ide/ide.c:140: warning: `struct ide_pio_command' declared inside parameter list
../../../src/pc80/ide/ide.c: In function `pio_data_in':
../../../src/pc80/ide/ide.c:151: warning: passing arg 2 of `pio_set_registers' from incompatible pointer type
../../../src/pc80/ide/ide.c:155: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:155: warning: passing arg 1 of `inb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:156: `IDE_STATUS_DRQ' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:159: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:159: warning: passing arg 1 of `insw' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:160: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:160: warning: passing arg 1 of `inb' makes integer from pointer without a cast
../../../src/pc80/ide/ide.c:161: `IDE_STATUS_ERR' undeclared (first use in this function)
../../../src/pc80/ide/ide.c: In function `ide_read_sector_chs':
../../../src/pc80/ide/ide.c:170: storage size of `cmd' isn't known
../../../src/pc80/ide/ide.c:178: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:180: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:181: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:186: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:187: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:189: `IDE_CMD_READ_SECTORS' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:190: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c: In function `ide_read_sector_lba':
../../../src/pc80/ide/ide.c:196: storage size of `cmd' isn't known
../../../src/pc80/ide/ide.c:205: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:207: `IDE_CMD_READ_SECTORS' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:208: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c: At top level:
../../../src/pc80/ide/ide.c:212: syntax error before "sector_t"
../../../src/pc80/ide/ide.c: In function `ide_read_sector_lba48':
../../../src/pc80/ide/ide.c:214: storage size of `cmd' isn't known
../../../src/pc80/ide/ide.c:218: `sector' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:224: `info' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:225: `IDE_CMD_READ_SECTORS_EXT' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:226: `buffer' undeclared (first use in this function)
../../../src/pc80/ide/ide.c: In function `ide_read_sector':
../../../src/pc80/ide/ide.c:232: invalid use of undefined type `struct harddisk_info'
../../../src/pc80/ide/ide.c:236: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:239: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:239: `ADDRESS_MODE_CHS' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:242: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:242: `ADDRESS_MODE_LBA' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:245: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:245: `ADDRESS_MODE_LBA48' undeclared (first use in this function)
../../../src/pc80/ide/ide.c: In function `init_drive':
../../../src/pc80/ide/ide.c:256: `uint16_t' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:256: `drive_info' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:257: storage size of `cmd' isn't known
../../../src/pc80/ide/ide.c:258: `DISK_BUFFER_SIZE' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:261: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:262: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:263: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:264: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:265: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:266: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:267: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:268: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:269: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:270: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:272: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:275: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:283: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:286: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:291: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:294: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:299: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:302: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:303: `IDE_CMD_IDENTIFY_DEVICE' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:313: syntax error before ')' token
../../../src/pc80/ide/ide.c:318: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:319: `IDE_FEATURE_STANDBY_SPINUP_DRIVE' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:330: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:346: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:347: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:349: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:350: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:354: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:354: `ADDRESS_MODE_LBA' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:355: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:360: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:360: `ADDRESS_MODE_LBA48' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:361: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:362: `sector_t' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:362: syntax error before "drive_info"
../../../src/pc80/ide/ide.c:363: syntax error before "drive_info"
../../../src/pc80/ide/ide.c:364: syntax error before "drive_info"
../../../src/pc80/ide/ide.c:365: syntax error before "drive_info"
../../../src/pc80/ide/ide.c:368: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:368: `ADDRESS_MODE_CHS' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:369: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:370: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:371: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:372: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:373: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:374: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:375: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:383: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:384: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:390: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:391: `IDE_FEATURE_CFA_ENABLE_POWER_MODE1' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:403: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c:403: dereferencing pointer to incomplete type
../../../src/pc80/ide/ide.c: In function `init_controller':
../../../src/pc80/ide/ide.c:457: invalid use of undefined type `struct harddisk_info'
../../../src/pc80/ide/ide.c: In function `ide_init':
../../../src/pc80/ide/ide.c:478: sizeof applied to an incomplete type
../../../src/pc80/ide/ide.c:498: `uint16_t' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:498: syntax error before "base"
../../../src/pc80/ide/ide.c:499: `base' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:499: `IDE_BASE0' undeclared (first use in this function)
../../../src/pc80/ide/ide.c:500: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:501: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:503: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c:503: invalid use of undefined type `struct controller'
../../../src/pc80/ide/ide.c: At top level:
../../../src/pc80/ide/ide.c:33: storage size of `harddisk_info' isn't known
../../../src/pc80/ide/ide.c:32: storage size of `controller' isn't known
make: *** [ide.o] Error 1
root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
Script done on Sat May  8 12:47:09 2004

And this one is from the USB directory:
Script started on Sat May  8 12:44:02 2004
root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
uhci.c:332:1: warning: "USBCMD" redefined
In file included from uhci.c:39:
uhci.h:290:1: warning: this is the location of the previous definition
uhci.c:333:1: warning: "USBSTS" redefined
uhci.h:291:1: warning: this is the location of the previous definition
uhci.c:334:1: warning: "USBINTR" redefined
uhci.h:292:1: warning: this is the location of the previous definition
uhci.c:335:1: warning: "FRNUM" redefined
uhci.h:293:1: warning: this is the location of the previous definition
uhci.c:336:1: warning: "FLBASE" redefined
uhci.h:294:1: warning: this is the location of the previous definition
uhci.c:337:1: warning: "SOFMOD" redefined
uhci.h:295:1: warning: this is the location of the previous definition
uhci.c:338:1: warning: "PORTSC1" redefined
uhci.h:296:1: warning: this is the location of the previous definition
uhci.c:339:1: warning: "PORTSC2" redefined
uhci.h:297:1: warning: this is the location of the previous definition
uhci.c: In function `ctrl_msg':
uhci.c:776: warning: assignment makes pointer from integer without a cast
uhci.c: In function `hub_port_reset':
uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible pointer type
uhci.c: In function `usb_hub_init':
uhci.c:1272: warning: assignment makes pointer from integer without a cast
uhci.c: In function `configure_device':
uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from incompatible pointer type
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
In file included from debug.c:31:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
scsi_cmds.c: In function `ll_read_block':
scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `ll_write_block':
scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `ll_read_long':
scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `get_capacity':
scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `query':
scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `ReportLUNS':
scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `ReportOpCodes':
scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `CheckVolumes':
scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `CheckPartitions':
scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from incompatible pointer type
scsi_cmds.c: In function `UnitReady':
scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from incompatible pointer type
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o block_fill_inbuf.c
In file included from block_fill_inbuf.c:8:
../include/string.h:9: warning: conflicting types for built-in function `strcpy'
gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o main.o main.c
main.c: In function `main':
main.c:41: warning: assignment makes pointer from integer without a cast
ld -defsym HEAPSIZE=0x8000 -T elfImage.lds main.o uhci.o usb_scsi_low.o debug.o scsi_cmds.o pci_util.o block_fill_inbuf.o ../lib/baremetal.a  -o usbboot.elf
uhci.o(.text+0x5e): In function `wait_head':
: undefined reference to `udelay'
uhci.o(.text+0x70a): In function `port_resume':
: undefined reference to `udelay'
uhci.o(.text+0x7c2): In function `port_reset':
: undefined reference to `udelay'
uhci.o(.text+0x819): In function `port_reset_long':
: undefined reference to `udelay'
uhci.o(.text+0x875): In function `hc_reset':
: undefined reference to `udelay'
uhci.o(.text+0xcdf): more undefined references to `udelay' follow
make: *** [usbboot.elf] Error 1
root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
Script done on Sat May  8 12:44:16 2004

--------------------
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

> -----Original Message-----
> From: Yinghai Lu [mailto:yhlu at tyan.com]
> Sent: Saturday, May 08, 2004 12:48 PM
> To: 'Steven James'; 'Gregg C Levine'
> Cc: linuxbios at clustermatic.org
> Subject: re: Is possible Linux on flash memory?
> 
> Does it work now?
> 
> If it works with raw device, after merge it into filo, it should use file system FAT
> etc.
> 
> Regards
> 
> YH
> 
> -----????????????-----
> ?????????: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> admin at clustermatic.org] ?????? Steven James
> ????????????: 2004???5???8??? 5:18
> ?????????: Gregg C Levine
> ??????: linuxbios at clustermatic.org
> ??????: RE: Is possible Linux on flash memory?
> 
> Greetings,
> 
> Yes, a kernel processed with Eric's mkelfImage.
> 
> I don't have any filesystem code in the loader, so rather than mounting a
> filesystem on the USB storage device, you need to partition it and then dd
> the kernel image to the first partition.
> 
> e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1
> 
> G'day,
> sjames
> 
> 
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
> 
> 
> On Sat, 8 May 2004, Gregg C Levine wrote:
> 
> > Hello from Gregg C Levine
> > It happens I just finished examining the code for the contents of that
> > directory. But I've got just one question pending at the moment, how
> > do you mean, "It will actually load an ELF image written to the raw
> > device.". Explain that line of reasoning. Do you mean a kernel that's
> > been pushed through the creation tool that Eric has created? And "raw
> > device", now I'm lost, how about clarifying your position?
> > -------------------
> > 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
> >
> > > -----Original Message-----
> > > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > > admin at clustermatic.org] On Behalf Of Steven James
> > > Sent: Friday, May 07, 2004 11:20 PM
> > > To: Ken Fuchs
> > > Cc: linuxbios at clustermatic.org
> > > Subject: Re: Is possible Linux on flash memory?
> > >
> > > Greetings,
> > >
> > > I've checked in the start of USB booting in util/baremetal/usb.
> > > It will actually load an ELF image written to the raw device. I
> > haven't
> > > been able to find enough time yet to integrate it into FILO, but it
> > should
> > > probably go there.
> > >
> > > G'day,
> > > sjames
> > >
> > >
> > > -------------------------steven james, director of research, linux
> > labs
> > > ... ........ ..... ....                    230 peachtree st nw ste
> > 2701
> > > the original linux labs                             atlanta.ga.us
> > 30303
> > >       -since 1995
> > http://www.linuxlabs.com
> > >                                               office & fax
> > 866.545.6306
> > >
> > ----------------------------------------------------------------------
> > -
> > >
> > >
> > > On Fri, 7 May 2004, Ken Fuchs wrote:
> > >
> > > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> > does
> > > > support ATA (IDE) flash devices.
> > > >
> > > > On a normal (proprietary) BIOS:
> > > >
> > > > Booting from USB is supported on many newer motherboards with a
> > BIOS
> > > > that supports this.  I use Flonix to boot from a 64MB USB pen
> > drive:
> > > >
> > > > http://mir2.ovh.net/flonix/
> > > >
> > > > The Flonix forums are at:
> > > >
> > > > http://www.flonix.com/support/viewforum.php?f=11
> > > >
> > > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > > >
> > > > # syslinux /dev/sda1
> > > >
> > > > To make Flonix bootable, you can also use the above command from
> > > > the Knoppix live CD.
> > > >
> > > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> > two
> > > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > > >
> > > > There are other Linux distributions built to be installed on a USB
> > pen
> > > > drive or flash.
> > > >
> > > > Check out http://www.linux-usb.org/ for general Linux USB
> > information.
> > > >
> > > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> > and it
> > > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > > Sorry.
> > > >
> > > > Sincerely,
> > > >
> > > > Ken Fuchs <kfuchs at winternet.com>



From pyro at linuxlabs.com  Sat May  8 17:33:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Sat May  8 17:33:01 2004
Subject: Is possible Linux on flash memory?
In-Reply-To: <000e01c4353e$85be4420$6401a8c0@who5>
References: <000e01c4353e$85be4420$6401a8c0@who5>
Message-ID: <Pine.LNX.4.58.0405082244490.6056@ucontrol.mobiledns.com>

Greetings,

It looks like the IDE stuff is the result of things changing in the
linuxbios source since baremetal was checked in.

I'll have to look at the usb problems. My setup was with gcc 2.95. I'll
try it on my newer gcc 3.2.2 (RH 9 ish) and see what's up.

G'day,
sjames



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


On Sat, 8 May 2004, Gregg C Levine wrote:

> Hello from Gregg C Levine
> It should work indeed. However, I've got a strange series of problems that might be related to my distribution's choice of versions, and I'll post the script output here in this message. However, it will be a long one.  I think some of these problems might be related to the distribution you chose, Steven, whose is it, and what's the version on it? Mine is Slackware 9.1, which came with those versions of tools.
> (Script output follows.)
> That's the versions of my GCC, and binary tools.:
>
> Script started on Sat May  8 12:59:30 2004
> root at who5:/# gcc --version
> gcc (GCC) 3.2.3
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> root at who5:/# ld --version
> GNU ld version 2.14.90.0.6 20030820
> 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.
> root at who5:/# exit
> Script done on Sat May  8 12:59:46 2004
>
> This one is from the library for the bare metal project:
> Script started on Sat May  8 12:47:01 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/printk.c
> gcc -I ../include -I ../include/i386 -O2    -c -o serial_subr.o serial_subr.c
> gcc -I ../include -I ../include/i386 -O2    -c -o subr.o subr.c
> In file included from subr.c:16:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/vsprintf.c
> In file included from ../../../src/lib/vsprintf.c:18:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/memcpy.c
> In file included from ../../../src/lib/memcpy.c:1:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/malloc.c
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/memset.c
> In file included from ../../../src/lib/memset.c:1:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/lib/compute_ip_checksum.c
> gcc -I ../include -I ../include/i386 -O2    -c -o elfboot.o elfboot.c
> In file included from elfboot.c:8:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2    -c -o boot.o boot.c
> In file included from boot.c:4:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2  -c ../../../src/pc80/ide/ide.c
> In file included from ../../../src/pc80/ide/ide.c:26:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> ../../../src/pc80/ide/ide.c:27:19: delay.h: No such file or directory
> ../../../src/pc80/ide/ide.c:28:17: pci.h: No such file or directory
> ../../../src/pc80/ide/ide.c:33: conflicting types for `harddisk_info'
> ../include/pc80/ide.h:54: previous declaration of `harddisk_info'
> ../../../src/pc80/ide/ide.c: In function `not_bsy':
> ../../../src/pc80/ide/ide.c:59: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:59: warning: passing arg 1 of `inb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:59: `IDE_STATUS_BSY' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:59: (Each undeclared identifier is reported only once
> ../../../src/pc80/ide/ide.c:59: for each function it appears in.)
> ../../../src/pc80/ide/ide.c: In function `ide_software_reset':
> ../../../src/pc80/ide/ide.c:83: `IDE_CTRL_HD15' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:83: `IDE_CTRL_SRST' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:83: `IDE_CTRL_NIEN' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c: At top level:
> ../../../src/pc80/ide/ide.c:95: warning: `struct ide_pio_command' declared inside parameter list
> ../../../src/pc80/ide/ide.c:95: warning: its scope is only this definition or declaration, which is probably not what you want
> ../../../src/pc80/ide/ide.c: In function `pio_set_registers':
> ../../../src/pc80/ide/ide.c:97: `uint8_t' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:97: syntax error before "device"
> ../../../src/pc80/ide/ide.c:99: `IDE_CTRL_HD15' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:99: `IDE_CTRL_NIEN' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:102: `device' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:103: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:104: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:111: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:112: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:112: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:112: warning: passing arg 2 of `outb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:113: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:113: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:113: warning: passing arg 2 of `outb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:114: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:115: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:116: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:117: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:118: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:119: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:120: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:120: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:120: warning: passing arg 2 of `outb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c: At top level:
> ../../../src/pc80/ide/ide.c:124: warning: `struct ide_pio_command' declared inside parameter list
> ../../../src/pc80/ide/ide.c: In function `pio_non_data':
> ../../../src/pc80/ide/ide.c:131: warning: passing arg 2 of `pio_set_registers' from incompatible pointer type
> ../../../src/pc80/ide/ide.c: At top level:
> ../../../src/pc80/ide/ide.c:140: warning: `struct ide_pio_command' declared inside parameter list
> ../../../src/pc80/ide/ide.c: In function `pio_data_in':
> ../../../src/pc80/ide/ide.c:151: warning: passing arg 2 of `pio_set_registers' from incompatible pointer type
> ../../../src/pc80/ide/ide.c:155: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:155: warning: passing arg 1 of `inb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:156: `IDE_STATUS_DRQ' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:159: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:159: warning: passing arg 1 of `insw' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:160: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:160: warning: passing arg 1 of `inb' makes integer from pointer without a cast
> ../../../src/pc80/ide/ide.c:161: `IDE_STATUS_ERR' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c: In function `ide_read_sector_chs':
> ../../../src/pc80/ide/ide.c:170: storage size of `cmd' isn't known
> ../../../src/pc80/ide/ide.c:178: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:180: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:181: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:186: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:187: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:189: `IDE_CMD_READ_SECTORS' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:190: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c: In function `ide_read_sector_lba':
> ../../../src/pc80/ide/ide.c:196: storage size of `cmd' isn't known
> ../../../src/pc80/ide/ide.c:205: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:207: `IDE_CMD_READ_SECTORS' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:208: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c: At top level:
> ../../../src/pc80/ide/ide.c:212: syntax error before "sector_t"
> ../../../src/pc80/ide/ide.c: In function `ide_read_sector_lba48':
> ../../../src/pc80/ide/ide.c:214: storage size of `cmd' isn't known
> ../../../src/pc80/ide/ide.c:218: `sector' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:224: `info' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:225: `IDE_CMD_READ_SECTORS_EXT' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:226: `buffer' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c: In function `ide_read_sector':
> ../../../src/pc80/ide/ide.c:232: invalid use of undefined type `struct harddisk_info'
> ../../../src/pc80/ide/ide.c:236: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:239: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:239: `ADDRESS_MODE_CHS' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:242: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:242: `ADDRESS_MODE_LBA' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:245: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:245: `ADDRESS_MODE_LBA48' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c: In function `init_drive':
> ../../../src/pc80/ide/ide.c:256: `uint16_t' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:256: `drive_info' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:257: storage size of `cmd' isn't known
> ../../../src/pc80/ide/ide.c:258: `DISK_BUFFER_SIZE' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:261: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:262: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:263: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:264: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:265: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:266: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:267: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:268: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:269: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:270: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:272: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:275: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:283: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:286: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:291: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:294: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:299: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:302: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:303: `IDE_CMD_IDENTIFY_DEVICE' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:313: syntax error before ')' token
> ../../../src/pc80/ide/ide.c:318: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:319: `IDE_FEATURE_STANDBY_SPINUP_DRIVE' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:330: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:346: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:347: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:349: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:350: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:354: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:354: `ADDRESS_MODE_LBA' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:355: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:360: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:360: `ADDRESS_MODE_LBA48' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:361: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:362: `sector_t' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:362: syntax error before "drive_info"
> ../../../src/pc80/ide/ide.c:363: syntax error before "drive_info"
> ../../../src/pc80/ide/ide.c:364: syntax error before "drive_info"
> ../../../src/pc80/ide/ide.c:365: syntax error before "drive_info"
> ../../../src/pc80/ide/ide.c:368: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:368: `ADDRESS_MODE_CHS' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:369: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:370: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:371: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:372: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:373: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:374: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:375: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:380: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:383: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:384: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:390: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:391: `IDE_FEATURE_CFA_ENABLE_POWER_MODE1' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:403: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c:403: dereferencing pointer to incomplete type
> ../../../src/pc80/ide/ide.c: In function `init_controller':
> ../../../src/pc80/ide/ide.c:457: invalid use of undefined type `struct harddisk_info'
> ../../../src/pc80/ide/ide.c: In function `ide_init':
> ../../../src/pc80/ide/ide.c:478: sizeof applied to an incomplete type
> ../../../src/pc80/ide/ide.c:498: `uint16_t' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:498: syntax error before "base"
> ../../../src/pc80/ide/ide.c:499: `base' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:499: `IDE_BASE0' undeclared (first use in this function)
> ../../../src/pc80/ide/ide.c:500: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:501: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:503: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c:503: invalid use of undefined type `struct controller'
> ../../../src/pc80/ide/ide.c: At top level:
> ../../../src/pc80/ide/ide.c:33: storage size of `harddisk_info' isn't known
> ../../../src/pc80/ide/ide.c:32: storage size of `controller' isn't known
> make: *** [ide.o] Error 1
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> Script done on Sat May  8 12:47:09 2004
>
> And this one is from the USB directory:
> Script started on Sat May  8 12:44:02 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> uhci.c:332:1: warning: "USBCMD" redefined
> In file included from uhci.c:39:
> uhci.h:290:1: warning: this is the location of the previous definition
> uhci.c:333:1: warning: "USBSTS" redefined
> uhci.h:291:1: warning: this is the location of the previous definition
> uhci.c:334:1: warning: "USBINTR" redefined
> uhci.h:292:1: warning: this is the location of the previous definition
> uhci.c:335:1: warning: "FRNUM" redefined
> uhci.h:293:1: warning: this is the location of the previous definition
> uhci.c:336:1: warning: "FLBASE" redefined
> uhci.h:294:1: warning: this is the location of the previous definition
> uhci.c:337:1: warning: "SOFMOD" redefined
> uhci.h:295:1: warning: this is the location of the previous definition
> uhci.c:338:1: warning: "PORTSC1" redefined
> uhci.h:296:1: warning: this is the location of the previous definition
> uhci.c:339:1: warning: "PORTSC2" redefined
> uhci.h:297:1: warning: this is the location of the previous definition
> uhci.c: In function `ctrl_msg':
> uhci.c:776: warning: assignment makes pointer from integer without a cast
> uhci.c: In function `hub_port_reset':
> uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible pointer type
> uhci.c: In function `usb_hub_init':
> uhci.c:1272: warning: assignment makes pointer from integer without a cast
> uhci.c: In function `configure_device':
> uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from incompatible pointer type
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> In file included from debug.c:31:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> scsi_cmds.c: In function `ll_read_block':
> scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `ll_write_block':
> scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `ll_read_long':
> scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `get_capacity':
> scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `query':
> scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `ReportLUNS':
> scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `ReportOpCodes':
> scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `CheckVolumes':
> scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `CheckPartitions':
> scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> scsi_cmds.c: In function `UnitReady':
> scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from incompatible pointer type
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o block_fill_inbuf.c
> In file included from block_fill_inbuf.c:8:
> ../include/string.h:9: warning: conflicting types for built-in function `strcpy'
> gcc -I ../include -I ../include/i386 -O2 -DDEBUG -DZKERNEL_START=0xfff00000   -c -o main.o main.c
> main.c: In function `main':
> main.c:41: warning: assignment makes pointer from integer without a cast
> ld -defsym HEAPSIZE=0x8000 -T elfImage.lds main.o uhci.o usb_scsi_low.o debug.o scsi_cmds.o pci_util.o block_fill_inbuf.o ../lib/baremetal.a  -o usbboot.elf
> uhci.o(.text+0x5e): In function `wait_head':
> : undefined reference to `udelay'
> uhci.o(.text+0x70a): In function `port_resume':
> : undefined reference to `udelay'
> uhci.o(.text+0x7c2): In function `port_reset':
> : undefined reference to `udelay'
> uhci.o(.text+0x819): In function `port_reset_long':
> : undefined reference to `udelay'
> uhci.o(.text+0x875): In function `hc_reset':
> : undefined reference to `udelay'
> uhci.o(.text+0xcdf): more undefined references to `udelay' follow
> make: *** [usbboot.elf] Error 1
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> Script done on Sat May  8 12:44:16 2004
>
> --------------------
> 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
>
> > -----Original Message-----
> > From: Yinghai Lu [mailto:yhlu at tyan.com]
> > Sent: Saturday, May 08, 2004 12:48 PM
> > To: 'Steven James'; 'Gregg C Levine'
> > Cc: linuxbios at clustermatic.org
> > Subject: re: Is possible Linux on flash memory?
> >
> > Does it work now?
> >
> > If it works with raw device, after merge it into filo, it should use file system FAT
> > etc.
> >
> > Regards
> >
> > YH
> >
> > -----????????????-----
> > ?????????: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > admin at clustermatic.org] ?????? Steven James
> > ????????????: 2004???5???8??? 5:18
> > ?????????: Gregg C Levine
> > ??????: linuxbios at clustermatic.org
> > ??????: RE: Is possible Linux on flash memory?
> >
> > Greetings,
> >
> > Yes, a kernel processed with Eric's mkelfImage.
> >
> > I don't have any filesystem code in the loader, so rather than mounting a
> > filesystem on the USB storage device, you need to partition it and then dd
> > the kernel image to the first partition.
> >
> > e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1
> >
> > G'day,
> > sjames
> >
> >
> > -------------------------steven james, director of research, linux labs
> > ... ........ ..... ....                    230 peachtree st nw ste 2701
> > the original linux labs                             atlanta.ga.us 30303
> >       -since 1995                              http://www.linuxlabs.com
> >                                               office & fax 866.545.6306
> > -----------------------------------------------------------------------
> >
> >
> > On Sat, 8 May 2004, Gregg C Levine wrote:
> >
> > > Hello from Gregg C Levine
> > > It happens I just finished examining the code for the contents of that
> > > directory. But I've got just one question pending at the moment, how
> > > do you mean, "It will actually load an ELF image written to the raw
> > > device.". Explain that line of reasoning. Do you mean a kernel that's
> > > been pushed through the creation tool that Eric has created? And "raw
> > > device", now I'm lost, how about clarifying your position?
> > > -------------------
> > > 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
> > >
> > > > -----Original Message-----
> > > > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > > > admin at clustermatic.org] On Behalf Of Steven James
> > > > Sent: Friday, May 07, 2004 11:20 PM
> > > > To: Ken Fuchs
> > > > Cc: linuxbios at clustermatic.org
> > > > Subject: Re: Is possible Linux on flash memory?
> > > >
> > > > Greetings,
> > > >
> > > > I've checked in the start of USB booting in util/baremetal/usb.
> > > > It will actually load an ELF image written to the raw device. I
> > > haven't
> > > > been able to find enough time yet to integrate it into FILO, but it
> > > should
> > > > probably go there.
> > > >
> > > > G'day,
> > > > sjames
> > > >
> > > >
> > > > -------------------------steven james, director of research, linux
> > > labs
> > > > ... ........ ..... ....                    230 peachtree st nw ste
> > > 2701
> > > > the original linux labs                             atlanta.ga.us
> > > 30303
> > > >       -since 1995
> > > http://www.linuxlabs.com
> > > >                                               office & fax
> > > 866.545.6306
> > > >
> > > ----------------------------------------------------------------------
> > > -
> > > >
> > > >
> > > > On Fri, 7 May 2004, Ken Fuchs wrote:
> > > >
> > > > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> > > does
> > > > > support ATA (IDE) flash devices.
> > > > >
> > > > > On a normal (proprietary) BIOS:
> > > > >
> > > > > Booting from USB is supported on many newer motherboards with a
> > > BIOS
> > > > > that supports this.  I use Flonix to boot from a 64MB USB pen
> > > drive:
> > > > >
> > > > > http://mir2.ovh.net/flonix/
> > > > >
> > > > > The Flonix forums are at:
> > > > >
> > > > > http://www.flonix.com/support/viewforum.php?f=11
> > > > >
> > > > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > > > >
> > > > > # syslinux /dev/sda1
> > > > >
> > > > > To make Flonix bootable, you can also use the above command from
> > > > > the Knoppix live CD.
> > > > >
> > > > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> > > two
> > > > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > > > >
> > > > > There are other Linux distributions built to be installed on a USB
> > > pen
> > > > > drive or flash.
> > > > >
> > > > > Check out http://www.linux-usb.org/ for general Linux USB
> > > information.
> > > > >
> > > > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> > > and it
> > > > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > > > Sorry.
> > > > >
> > > > > Sincerely,
> > > > >
> > > > > Ken Fuchs <kfuchs at winternet.com>
>
>


From yhlu at tyan.com  Sun May  9 12:03:00 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun May  9 12:03:00 2004
Subject: =?gb2312?B?tPC4tDogSXMgcG9zc2libGUgTGludXggb24gZmxhc2ggbWVtb3J5Pw==?=
In-Reply-To: <Pine.LNX.4.58.0405081711250.6056@ucontrol.mobiledns.com>
Message-ID: <200405091602.i49G2XK25983@nwn.definitive.org>

Great, I will move that to filo in etherboot to have a test next week.

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?8? 10:14
???: Yinghai Lu
??: 'Gregg C Levine'; linuxbios at clustermatic.org
??: re: Is possible Linux on flash memory?

Greetings,

It works on USB drives that do SCSI over bulk transport. For other drives,
more work will be needed, but I don't have one of those. It can also
enumerate hubs like the iMac keyboard.

G'day,
sjames


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


On Sat, 8 May 2004, Yinghai Lu wrote:

> Does it work now?
>
> If it works with raw device, after merge it into filo, it should use file
system FAT etc.
>
> Regards
>
> YH
>
> -----????-----
> ???: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] ?? Steven James
> ????: 2004?5?8? 5:18
> ???: Gregg C Levine
> ??: linuxbios at clustermatic.org
> ??: RE: Is possible Linux on flash memory?
>
> Greetings,
>
> Yes, a kernel processed with Eric's mkelfImage.
>
> I don't have any filesystem code in the loader, so rather than mounting a
> filesystem on the USB storage device, you need to partition it and then dd
> the kernel image to the first partition.
>
> e.g. if your USB device shows up as sdb, dd if=kernel.elf of=/dev/sdb1
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Sat, 8 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > It happens I just finished examining the code for the contents of that
> > directory. But I've got just one question pending at the moment, how
> > do you mean, "It will actually load an ELF image written to the raw
> > device.". Explain that line of reasoning. Do you mean a kernel that's
> > been pushed through the creation tool that Eric has created? And "raw
> > device", now I'm lost, how about clarifying your position?
> > -------------------
> > 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
> >
> > > -----Original Message-----
> > > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > > admin at clustermatic.org] On Behalf Of Steven James
> > > Sent: Friday, May 07, 2004 11:20 PM
> > > To: Ken Fuchs
> > > Cc: linuxbios at clustermatic.org
> > > Subject: Re: Is possible Linux on flash memory?
> > >
> > > Greetings,
> > >
> > > I've checked in the start of USB booting in util/baremetal/usb.
> > > It will actually load an ELF image written to the raw device. I
> > haven't
> > > been able to find enough time yet to integrate it into FILO, but it
> > should
> > > probably go there.
> > >
> > > G'day,
> > > sjames
> > >
> > >
> > > -------------------------steven james, director of research, linux
> > labs
> > > ... ........ ..... ....                    230 peachtree st nw ste
> > 2701
> > > the original linux labs                             atlanta.ga.us
> > 30303
> > >       -since 1995
> > http://www.linuxlabs.com
> > >                                               office & fax
> > 866.545.6306
> > >
> > ----------------------------------------------------------------------
> > -
> > >
> > >
> > > On Fri, 7 May 2004, Ken Fuchs wrote:
> > >
> > > > LinuxBIOS doesn't support USB pen drives or USB compact flash.  It
> > does
> > > > support ATA (IDE) flash devices.
> > > >
> > > > On a normal (proprietary) BIOS:
> > > >
> > > > Booting from USB is supported on many newer motherboards with a
> > BIOS
> > > > that supports this.  I use Flonix to boot from a 64MB USB pen
> > drive:
> > > >
> > > > http://mir2.ovh.net/flonix/
> > > >
> > > > The Flonix forums are at:
> > > >
> > > > http://www.flonix.com/support/viewforum.php?f=11
> > > >
> > > > I also tried Puppy Linux (http.goosee.com/puppy/), but the USB
> > > > bootloader (syslinux 2.08) didn't work for me.  Using Knoppix 3.3
> > > > 2-16-2004, I was able to install it's syslinux 2.04 bootloader:
> > > >
> > > > # syslinux /dev/sda1
> > > >
> > > > To make Flonix bootable, you can also use the above command from
> > > > the Knoppix live CD.
> > > >
> > > > (The first USB flash is /dev/sda, if there are _no_ SCSI drives.
> > > > Otherwise, USB flash is the last "SCSI" device, i.e. /dev/sdc with
> > two
> > > > SCSI hard drives with special files /dev/sda and /dev/sdb.)
> > > >
> > > > There are other Linux distributions built to be installed on a USB
> > pen
> > > > drive or flash.
> > > >
> > > > Check out http://www.linux-usb.org/ for general Linux USB
> > information.
> > > >
> > > > BTW, I sent Flavio a private e-mail to flavio_groups at yahoo.com.br
> > and it
> > > > bounced.  So, I'm forced to answer via the LinuxBIOS mailing list.
> > > > Sorry.
> > > >
> > > > Sincerely,
> > > >
> > > > Ken Fuchs <kfuchs at winternet.com>
> > > > _______________________________________________
> > > > 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
> >
> > _______________________________________________
> > 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
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>



From cforney at opus.com  Mon May 10 01:07:00 2004
From: cforney at opus.com (Craig C Forney)
Date: Mon May 10 01:07:00 2004
Subject: LinuxBIOS for HDAMA not building
Message-ID: <000001c43657$73ab5740$6400a8c0@opusone>

The current LinuxBIOS tree from sourceforge doesn't seem to build
properly for the last few days.  I noticed that arima/hdama,
amd/quartet, and tyan/s2850 all get the same error (compilation of
src/southbridge/amd/amd8111/amd8111_lpc.c fails).

I assume it's related to the current discussion around the 8111 stuff.

Is the current source tree in an unstable state?  Or is my build
environment screwed up?

Craig Forney
Opus Innovations LLC





From mdeschamps at mangrove-systems.com  Mon May 10 04:06:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Mon May 10 04:06:01 2004
Subject: Pleased experienced on EPIA : Linuxbios runs,but smbus errors,
	no normal rom starting, payload making difficulties
In-Reply-To: <m3oeozslg9.fsf@maxwell.lnxi.com>
References: <1083852388.1279.151.camel@Calliphara>
	 <m3oeozslg9.fsf@maxwell.lnxi.com>
Message-ID: <1084180835.13653.113.camel@Calliphara>

Thanks a lot, i was losing faith finding it :)

Please, can some experienced users or develloppers 
enlighten me on my problem  risen to into my previous mail
this one
:http://www.clustermatic.org/pipermail/linuxbios/2004-May/007766.html

Thanks in advance.
mathieu
 

Le sam 08/05/2004 ? 04:26, Eric W. Biederman a ?crit :
> Mathieu Deschamps <mdeschamps at mangrove-systems.com> writes:
> 
> > Hello,
> > [...]
> > 
> > 
> > I intended to make a IDE elfImagepayload to boot a kernel
> > on a hard disk, I've read that LinuxBios alone could do that quite
> > well.
> > So got mkelfImage 1.16 (i know it's quite old
> > but i can't find a link to a recent one- BTW please a link to a more
> > recent one would be appreciated). 
> 
> ftp://ftp.lnxi.com/pub/mkelfImage
> 2.5 should work better.
> 
> Also the LinuxBIOS list is a good place to ask questions like this
> in case I get distracted.
> 
> 
> Eric
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


From jmiller at actuality-systems.com  Mon May 10 08:42:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Mon May 10 08:42:00 2004
Subject: Where to find freebios2 info?
Message-ID: <E8F8DBCB0468204E856114A2CD20741F28BC@mail.local.ActualitySystems.com>

Hello All,

 

We just started a project that we hope to use LinuxBIOS on.

 

We're using Athlon64, with AMD 8111, 8131, and a dual broadcom gige
chipset.

 

Looking around it appears that freebios2 supports this hardware.  Where
do I go to find information about freebios2 development?

 

Specifically I'm looking for, where the kernel patches are (do you still
do that in 2.0)?  What kernels do you support?

 

Thanks,

 

Jay Miller

Actuality Systems, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040510/b84d5234/attachment.html>

From rminnich at lanl.gov  Mon May 10 09:45:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 09:45:01 2004
Subject: LinuxBIOS for HDAMA not building
In-Reply-To: <000001c43657$73ab5740$6400a8c0@opusone>
Message-ID: <Pine.LNX.4.44.0405100901300.27333-100000@maxroach.lanl.gov>

On Sun, 9 May 2004, Craig C Forney wrote:

> Is the current source tree in an unstable state?  Or is my build
> environment screwed up?

I guess somebody busted something, let me try it ...

well, can't get to it just now. Hold on and let me get back to you. 

ron



From rminnich at lanl.gov  Mon May 10 09:49:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 09:49:01 2004
Subject: Pleased experienced on EPIA : Linuxbios runs,but smbus errors,
 no normal rom starting, payload making difficulties
In-Reply-To: <1084180835.13653.113.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405100906430.27333-100000@maxroach.lanl.gov>

you're still not setting up your elfimage correctly somehow, but I can't 
tell how. 

ron



From rminnich at lanl.gov  Mon May 10 09:53:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 09:53:01 2004
Subject: Where to find freebios2 info?
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F28BC@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405100909420.27333-100000@maxroach.lanl.gov>

no real kernel patches needed any more. We use FILO and it brings up the 
IDE just fine, etherboot works well too. 

Go to freebios.sourceforge.net to find the source tree. 

To check it out:

cvs -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios login 
cvs -z3 -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios co 
freebios2





From rminnich at lanl.gov  Mon May 10 10:04:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 10:04:01 2004
Subject: OOPS ... 
Message-ID: <Pine.LNX.4.44.0405100920330.27333-100000@maxroach.lanl.gov>

Ollie, you busted the tree, I think.

can you fix?

/rminnich/src/bios/freebios2/src/mainboard/arima/hdama' 
-DMAINBOARD_PART_NUMBER='HDAMA' -DMAINBOARD_VENDOR='ARIMA' 
-DCONFIG_SMP='1' -DCONFIG_MAX_CPUS='2' -DCONFIG_MAX_PHYSICAL_CPUS='2' 
-DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' 
-DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' 
-DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' 
-DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 
console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='0' -DIDE_BOOT_DRIVE='0' 
-DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='4' 
-DHARD_RESET_FUNCTION='0' -DMAX_REBOOT_CNT='3' -DFAKE_SPDROM='0' 
-DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' 
-DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' 
-Dk7='1' -Dk8='1' -DROM_SIZE='0x80000' -DFALLBACK_SIZE='0x20000' 
-DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' 
-DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='9' 
-DHAVE_MP_TABLE='1' -DCONFIG_IOAPIC='1' -DROM_SECTION_SIZE='0x20000' 
-DROM_SECTION_OFFSET='0x60000' -DXIP_ROM_SIZE='0x10000' 
-DXIP_ROM_BASE='0xffff0000' -Os -nostdinc -nostdlib -fno-builtin  -Wall -o 
amd8111_lpc.o 
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: 
In function `lpc_init':
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:153: 
warning: implicit declaration of function `isa_dma_init'
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: 
At top level:
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
`walk_static_devices' undeclared here (not in a function)
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
initializer element is not constant
/home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
(near initialization for `lpc_ops.scan_bus')
make[1]: *** [amd8111_lpc.o] Error 1
make[1]: Leaving directory 
`/home/rminnich/src/bios/freebios2/targets/arima/hdama/hdama/fallback'
make: *** [fallback-rom] Error 1

To those who are waiting: we'll get this sometime this morning. Sorry for 
any inconvenience.

ron



From jmiller at actuality-systems.com  Mon May 10 10:10:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Mon May 10 10:10:00 2004
Subject: Where to find freebios2 info?
Message-ID: <E8F8DBCB0468204E856114A2CD20741F28C8@mail.local.ActualitySystems.com>

Thanks for the quick response!

I suspected that you'd moved away from patching the kernel due to the
lack of a patch directory under the freebios2 tree.

I have a TYAN S2885 system on my desk running SUSE 9.0 for x86-64.  So
the tools are pretty much latest-n-greatest.  But after checking out the
latest sources I am getting the following error message(s):

/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: In
function `lpc_init':
/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:153:
warning: implicit declaration of function `isa_dma_init'
/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: At
top level:
/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
error: `walk_static_devices' undeclared here (not in a function)
/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
error: initializer element is not constant
/home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
error: (near initialization for `lpc_ops.scan_bus')
make[1]: *** [amd8111_lpc.o] Error 1
make[1]: Leaving directory
`/home/jmiller/freebios2/targets/tyan/s2885/s2885/fallback'
make: *** [fallback-rom] Error 1

It looks like I picked up unfinished changes.  Is there a list of tags
that can be used to check out a stable set of sources?  I want to try
and familiarize myself with LinuxBIOS on the TYAN board before jumping
headlong into our project.

-J


-----Original Message-----
From: ron minnich [mailto:rminnich at lanl.gov] 
Sent: Monday, May 10, 2004 11:11 AM
To: Jay Miller
Cc: linuxbios at clustermatic.org
Subject: Re: Where to find freebios2 info?

no real kernel patches needed any more. We use FILO and it brings up the

IDE just fine, etherboot works well too. 

Go to freebios.sourceforge.net to find the source tree. 

To check it out:

cvs -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios login 
cvs -z3 -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios co 
freebios2







From stepan at openbios.org  Mon May 10 10:18:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May 10 10:18:00 2004
Subject: Where to find freebios2 info?
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F28C8@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F28C8@mail.local.ActualitySystems.com>
Message-ID: <20040510153534.GA4947@openbios.org>

* Jay Miller <jmiller at actuality-systems.com> [040510 17:26]:
> It looks like I picked up unfinished changes.  Is there a list of tags
> that can be used to check out a stable set of sources?  I want to try
> and familiarize myself with LinuxBIOS on the TYAN board before jumping
> headlong into our project.

Unfortunately no. But we will fix this asap.

    Stefan



From rminnich at lanl.gov  Mon May 10 10:18:10 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 10:18:10 2004
Subject: Where to find freebios2 info?
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F28C8@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405100935280.27333-100000@maxroach.lanl.gov>

On Mon, 10 May 2004, Jay Miller wrote:

> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: In
> function `lpc_init':
> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:153:
> warning: implicit declaration of function `isa_dma_init'
> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: At
> top level:
> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
> error: `walk_static_devices' undeclared here (not in a function)
> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
> error: initializer element is not constant
> /home/jmiller/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196:
> error: (near initialization for `lpc_ops.scan_bus')
> make[1]: *** [amd8111_lpc.o] Error 1
> make[1]: Leaving directory
> `/home/jmiller/freebios2/targets/tyan/s2885/s2885/fallback'
> make: *** [fallback-rom] Error 1

no, someobdy here busted the tree. SOrry, this will be fixed soon. 

This happens from time to time ... 

ron



From rminnich at lanl.gov  Mon May 10 10:37:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 10:37:01 2004
Subject: people at amcc.com
Message-ID: <Pine.LNX.4.44.0405100953570.27333-100000@maxroach.lanl.gov>


your spam filter needs fixin'. it will reject any email on subject such as 
freebios, freebsd, etc. 

see below. It figures it's a symantec filter.

ron
---------- Forwarded message ----------
Date: Mon, 10 May 2004 10:27:49 -0400
From: Symantec_AntiVirus_for_SMTP_Gateways at amcc.com
To: linuxbios-admin at clustermatic.org
Subject: Content violation

Content violation found in email message.

From: linuxbios-admin at clustermatic.org
To: tdeclerck at 3ware.com

Subject: RE: Where to find freebios2 info?

Matching Subject: *free*








From ollie at lanl.gov  Mon May 10 10:53:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Mon May 10 10:53:00 2004
Subject: OOPS ...
In-Reply-To: <Pine.LNX.4.44.0405100920330.27333-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405100920330.27333-100000@maxroach.lanl.gov>
Message-ID: <1084205420.2459.129.camel@exponential.lanl.gov>

On Mon, 2004-05-10 at 09:21, ron minnich wrote:
> Ollie, you busted the tree, I think.
> 
> can you fix?
> 
> /rminnich/src/bios/freebios2/src/mainboard/arima/hdama' 
> -DMAINBOARD_PART_NUMBER='HDAMA' -DMAINBOARD_VENDOR='ARIMA' 
> -DCONFIG_SMP='1' -DCONFIG_MAX_CPUS='2' -DCONFIG_MAX_PHYSICAL_CPUS='2' 
> -DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' 
> -DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' 
> -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' 
> -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 
> console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='0' -DIDE_BOOT_DRIVE='0' 
> -DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='4' 
> -DHARD_RESET_FUNCTION='0' -DMAX_REBOOT_CNT='3' -DFAKE_SPDROM='0' 
> -DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' 
> -DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' 
> -Dk7='1' -Dk8='1' -DROM_SIZE='0x80000' -DFALLBACK_SIZE='0x20000' 
> -DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' 
> -DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='9' 
> -DHAVE_MP_TABLE='1' -DCONFIG_IOAPIC='1' -DROM_SECTION_SIZE='0x20000' 
> -DROM_SECTION_OFFSET='0x60000' -DXIP_ROM_SIZE='0x10000' 
> -DXIP_ROM_BASE='0xffff0000' -Os -nostdinc -nostdlib -fno-builtin  -Wall -o 
> amd8111_lpc.o 
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: 
> In function `lpc_init':
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:153: 
> warning: implicit declaration of function `isa_dma_init'
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c: 
> At top level:
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
> `walk_static_devices' undeclared here (not in a function)
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
> initializer element is not constant
> /home/rminnich/src/bios/freebios2/src/southbridge/amd/amd8111/amd8111_lpc.c:196: 
> (near initialization for `lpc_ops.scan_bus')
> make[1]: *** [amd8111_lpc.o] Error 1
> make[1]: Leaving directory 
> `/home/rminnich/src/bios/freebios2/targets/arima/hdama/hdama/fallback'
> make: *** [fallback-rom] Error 1
> 
> To those who are waiting: we'll get this sometime this morning. Sorry for 
> any inconvenience.
> 

It is my falut. I left some files uncommitted. It should be o.k. now.

Ollie
> ron
> 



From lists at braindonors.net  Mon May 10 11:58:00 2004
From: lists at braindonors.net (Jacob Alifrangis (LISTS))
Date: Mon May 10 11:58:00 2004
Subject: TS-5300 Support
Message-ID: <200405101557.i4AFvcK31239@nwn.definitive.org>

Is there any support in the tree for a Technologic Systems TS-5x00 board.

 

We are developing an embedded project and would like to use linuxbios to
start the boards up.

 

If anybody wants to develop for the board, and can promise us a timeline, we
will ship you a unit asap.

 

 

The boards are available at http://www.embeddedx86.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040510/afa918d4/attachment.html>

From lists at braindonors.net  Mon May 10 12:12:01 2004
From: lists at braindonors.net (Jacob Alifrangis (LISTS))
Date: Mon May 10 12:12:01 2004
Subject: Hardware compatibility lists
Message-ID: <200405101611.i4AGB0K31385@nwn.definitive.org>

I would like to help cleanup the 'supported systems' list on the website and
update it.

 

I would like to make it database driven, and turn it into a more dynamic
page, as hardware support is added or broken it could be updated.

 

 

Something else we want to add, Hardware support for some desktop
motherboards.

 

ELEMENTS P4 Motherboard (P4MDPT) - www.elements-pc.com

ELEMENTS AMD Motherboard (N2PAP) - www.elements-pc.com

 

I am willing to contribute hardware and the documentation from these
manufacturers. 

 

 

The people at embeddedx86 are extremely helpful, and I have a good working
relationship with them.

 

I'm willing to foot the bill for some expenses for this project.

 

Thanks -J

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040510/feed282d/attachment.html>

From Antony at Soft-Solutions.co.uk  Mon May 10 12:19:00 2004
From: Antony at Soft-Solutions.co.uk (Antony Stone)
Date: Mon May 10 12:19:00 2004
Subject: TS-5300 Support
In-Reply-To: <200405101557.i4AFvcK31239@nwn.definitive.org>
References: <200405101557.i4AFvcK31239@nwn.definitive.org>
Message-ID: <200405101835.26599.Antony@Soft-Solutions.co.uk>

On Monday 10 May 2004 6:17 pm, Jacob Alifrangis (LISTS) wrote:

> Is there any support in the tree for a Technologic Systems TS-5x00 board.

What do "lspci" and "lspci -v" generate for this board?

Regards,

Antony.

-- 
"Note: Windows 98, Windows 98SE and Windows 95 are not affected by [MS
Blaster].   However, these products are no longer supported.   Users of these
products are strongly encouraged to upgrade to later versions."

(which *are* affected by MS Blaster...)

http://www.microsoft.com/security/security_bulletins/ms03-026.asp

                                                     Please reply to the list;
                                                           please don't CC me.



From bari at onelabs.com  Mon May 10 12:24:01 2004
From: bari at onelabs.com (Bari Ari)
Date: Mon May 10 12:24:01 2004
Subject: TS-5300 Support
In-Reply-To: <200405101557.i4AFvcK31239@nwn.definitive.org>
References: <200405101557.i4AFvcK31239@nwn.definitive.org>
Message-ID: <409FBF3E.1080301@onelabs.com>

Jacob Alifrangis (LISTS) wrote:
> Is there any support in the tree for a Technologic Systems TS-5x00 board.
> 
They all look like AMD Elan based boards. I don't think anyone ever 
tried to get them up, but all the specs to do so are at:

http://www.amd.com/epd/processors/4.32bitcont/14.lan5xxfam/24.lansc520/

-Bari




From rminnich at lanl.gov  Mon May 10 13:06:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 13:06:01 2004
Subject: TS-5300 Support
In-Reply-To: <200405101557.i4AFvcK31239@nwn.definitive.org>
Message-ID: <Pine.LNX.4.44.0405101221310.27333-100000@maxroach.lanl.gov>

On Mon, 10 May 2004, Jacob Alifrangis (LISTS) wrote:

> Is there any support in the tree for a Technologic Systems TS-5x00 board.

This looks like an SC 520 board?. Is it? If so I'm VERY interested, but 
only if flash is removable. Can you find out?

Which one of these are you using. If it does have removable flash I'd like 
to look at them for building new low-power clusters. We need to know more 
about it though. Do you have an lspci? 

thanks

ron



From rminnich at lanl.gov  Mon May 10 13:16:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 13:16:01 2004
Subject: Hardware compatibility lists
In-Reply-To: <200405101611.i4AGB0K31385@nwn.definitive.org>
Message-ID: <Pine.LNX.4.44.0405101231180.27333-100000@maxroach.lanl.gov>

On Mon, 10 May 2004, Jacob Alifrangis (LISTS) wrote:

> I would like to help cleanup the 'supported systems' list on the website and
> update it.

that's actually not the problem. The problem is automating unit testing. 
The supported systems is driven by a script already. People don't always 
update the STATUS entires. I'm going to yank that page as it has not 
worked out.

> I would like to make it database driven, and turn it into a more dynamic
> page, as hardware support is added or broken it could be updated.

You have to recall: 'added' or 'broken' requires a test. How do we do 
these tests? That's the hard problem. 

> Something else we want to add, Hardware support for some desktop
> motherboards.

yee ha!

> I am willing to contribute hardware and the documentation from these
> manufacturers. 

we'll take it :-)

I think this is a GREAT idea. Thanks for your offer of support.

> I'm willing to foot the bill for some expenses for this project.

we need to work out how to do this type of thing, but for now: what kind 
of hardware makes a good desktop? I'd really like to see some K8 desktops 
with linuxbios.

Thanks for your offer of support!

ron



From rminnich at lanl.gov  Mon May 10 13:18:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 13:18:00 2004
Subject: TS-5300 Support
In-Reply-To: <409FBF3E.1080301@onelabs.com>
Message-ID: <Pine.LNX.4.44.0405101234550.27333-100000@maxroach.lanl.gov>

On Mon, 10 May 2004, Bari Ari wrote:

> They all look like AMD Elan based boards. I don't think anyone ever 
> tried to get them up, but all the specs to do so are at:
> 
> http://www.amd.com/epd/processors/4.32bitcont/14.lan5xxfam/24.lansc520/

I have an sc520 board, but the flash part is soldered-on, and I've been 
too chicken to flash it. I need a board with removable flash. The port 
looks easy given the high quality of AMD support for this part -- they 
give sample code!!!

ron



From lists at braindonors.net  Mon May 10 13:41:01 2004
From: lists at braindonors.net (Jacob Alifrangis (LISTS))
Date: Mon May 10 13:41:01 2004
Subject: TS-5300 Support
In-Reply-To: <Pine.LNX.4.44.0405101234550.27333-100000@maxroach.lanl.gov>
Message-ID: <200405101740.i4AHeaK31896@nwn.definitive.org>

The uboot project has amd elan support already.

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of ron minnich
Sent: Monday, May 10, 2004 11:36 AM
To: Bari Ari
Cc: Jacob Alifrangis (LISTS); linuxbios at clustermatic.org
Subject: Re: TS-5300 Support

On Mon, 10 May 2004, Bari Ari wrote:

> They all look like AMD Elan based boards. I don't think anyone ever 
> tried to get them up, but all the specs to do so are at:
> 
> http://www.amd.com/epd/processors/4.32bitcont/14.lan5xxfam/24.lansc520/

I have an sc520 board, but the flash part is soldered-on, and I've been 
too chicken to flash it. I need a board with removable flash. The port 
looks easy given the high quality of AMD support for this part -- they 
give sample code!!!

ron

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



From rminnich at lanl.gov  Mon May 10 13:42:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 10 13:42:00 2004
Subject: TS-5300 Support
In-Reply-To: <200405101858.i4AIwj2Z026170@mailproxy2.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405101259101.27333-100000@maxroach.lanl.gov>

On Mon, 10 May 2004, Jacob Alifrangis (LISTS) wrote:

> The uboot project has amd elan support already.

yep. We can use some of that code too.

ron



From hansolofalcon at worldnet.att.net  Mon May 10 14:17:00 2004
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Mon May 10 14:17:00 2004
Subject: New problems with building Baremetal
Message-ID: <000b01c436c6$065e89e0$6401a8c0@who5>

Hello from Gregg C Levine
Now something else has happened. I've managed to build a copy of GCC
version 2.9.5.3 and have it installed in the /opt directory.  But
there are unusual problems in the building of the bare metal library,
here's a script output regarding the errors:
Script started on Mon May 10 14:47:28 2004
root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/printk.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
serial_subr.o serial_subr.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
subr.o subr.c
In file included from subr.c:16:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/vsprintf.c
In file included from ../../../src/lib/vsprintf.c:18:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/memcpy.c
In file included from ../../../src/lib/memcpy.c:1:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/malloc.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/memset.c
In file included from ../../../src/lib/memset.c:1:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/lib/compute_ip_checksum.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
elfboot.o elfboot.c
In file included from elfboot.c:8:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
boot.o boot.c
In file included from boot.c:4:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
../../../src/pc80/ide/ide.c
../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
make: *** [ide.o] Error 1
root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
Script done on Mon May 10 14:47:36 2004

Obviously some of those errors can be corrected by reminding the make
file to find the include files that GCC 2.95.3 prefers. But the ones
that concern me, are the "missing files" for the IDE issues.

And here's the latest problem with the USB attachment to bare metal:
Script started on Mon May 10 14:49:02 2004
root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
uhci.c:332: warning: `USBCMD' redefined
uhci.h:290: warning: this is the location of the previous definition
uhci.c:333: warning: `USBSTS' redefined
uhci.h:291: warning: this is the location of the previous definition
uhci.c:334: warning: `USBINTR' redefined
uhci.h:292: warning: this is the location of the previous definition
uhci.c:335: warning: `FRNUM' redefined
uhci.h:293: warning: this is the location of the previous definition
uhci.c:336: warning: `FLBASE' redefined
uhci.h:294: warning: this is the location of the previous definition
uhci.c:337: warning: `SOFMOD' redefined
uhci.h:295: warning: this is the location of the previous definition
uhci.c:338: warning: `PORTSC1' redefined
uhci.h:296: warning: this is the location of the previous definition
uhci.c:339: warning: `PORTSC2' redefined
uhci.h:297: warning: this is the location of the previous definition
uhci.c: In function `ctrl_msg':
uhci.c:776: warning: assignment makes pointer from integer without a
cast
uhci.c: In function `hub_port_reset':
uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
pointer type
uhci.c: In function `usb_hub_init':
uhci.c:1272: warning: assignment makes pointer from integer without a
cast
uhci.c: In function `configure_device':
uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
incompatible pointer type
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
In file included from debug.c:31:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
In file included from scsi_cmds.c:26:
/usr/include/sys/types.h:152: warning: redefinition of `ushort'
uhci.h:13: warning: `ushort' previously declared here
scsi_cmds.c: In function `ll_read_block':
scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `ll_write_block':
scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `ll_read_long':
scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `get_capacity':
scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `query':
scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `ReportLUNS':
scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `ReportOpCodes':
scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `CheckVolumes':
scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `CheckPartitions':
scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
scsi_cmds.c: In function `UnitReady':
scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
incompatible pointer type
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
/opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
-DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
block_fill_inbuf.c
In file included from block_fill_inbuf.c:8:
../include/string.h:9: warning: conflicting types for built-in
function `strcpy'
make: *** No rule to make target `../lib/baremetal.a', needed by
`usbboot.elf'.  Stop.
root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
Script done on Mon May 10 14:49:10 2004

Again I expect that by instructing the make file to use the include
files supplied by GCC 2.95.3, that most of the errors will be gone,
but I'm listing those for reference. 
-------------------
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




From pyro at linuxlabs.com  Mon May 10 14:37:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Mon May 10 14:37:01 2004
Subject: New problems with building Baremetal
In-Reply-To: <000b01c436c6$065e89e0$6401a8c0@who5>
References: <000b01c436c6$065e89e0$6401a8c0@who5>
Message-ID: <Pine.LNX.4.58.0405101952240.6056@ucontrol.mobiledns.com>

Greetings,

In the lib directory, try removing ide.o from DEPS for now. That should
get the library to compile.

The rest is all warnings except at the end where it can't link against
libbaremetal.a

G'day,
sjames


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


On Mon, 10 May 2004, Gregg C Levine wrote:

> Hello from Gregg C Levine
> Now something else has happened. I've managed to build a copy of GCC
> version 2.9.5.3 and have it installed in the /opt directory.  But
> there are unusual problems in the building of the bare metal library,
> here's a script output regarding the errors:
> Script started on Mon May 10 14:47:28 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/printk.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> serial_subr.o serial_subr.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> subr.o subr.c
> In file included from subr.c:16:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/vsprintf.c
> In file included from ../../../src/lib/vsprintf.c:18:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/memcpy.c
> In file included from ../../../src/lib/memcpy.c:1:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/malloc.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/memset.c
> In file included from ../../../src/lib/memset.c:1:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/compute_ip_checksum.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> elfboot.o elfboot.c
> In file included from elfboot.c:8:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> boot.o boot.c
> In file included from boot.c:4:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/pc80/ide/ide.c
> ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> make: *** [ide.o] Error 1
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> Script done on Mon May 10 14:47:36 2004
>
> Obviously some of those errors can be corrected by reminding the make
> file to find the include files that GCC 2.95.3 prefers. But the ones
> that concern me, are the "missing files" for the IDE issues.
>
> And here's the latest problem with the USB attachment to bare metal:
> Script started on Mon May 10 14:49:02 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> uhci.c:332: warning: `USBCMD' redefined
> uhci.h:290: warning: this is the location of the previous definition
> uhci.c:333: warning: `USBSTS' redefined
> uhci.h:291: warning: this is the location of the previous definition
> uhci.c:334: warning: `USBINTR' redefined
> uhci.h:292: warning: this is the location of the previous definition
> uhci.c:335: warning: `FRNUM' redefined
> uhci.h:293: warning: this is the location of the previous definition
> uhci.c:336: warning: `FLBASE' redefined
> uhci.h:294: warning: this is the location of the previous definition
> uhci.c:337: warning: `SOFMOD' redefined
> uhci.h:295: warning: this is the location of the previous definition
> uhci.c:338: warning: `PORTSC1' redefined
> uhci.h:296: warning: this is the location of the previous definition
> uhci.c:339: warning: `PORTSC2' redefined
> uhci.h:297: warning: this is the location of the previous definition
> uhci.c: In function `ctrl_msg':
> uhci.c:776: warning: assignment makes pointer from integer without a
> cast
> uhci.c: In function `hub_port_reset':
> uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> pointer type
> uhci.c: In function `usb_hub_init':
> uhci.c:1272: warning: assignment makes pointer from integer without a
> cast
> uhci.c: In function `configure_device':
> uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> incompatible pointer type
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> In file included from debug.c:31:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> In file included from scsi_cmds.c:26:
> /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> uhci.h:13: warning: `ushort' previously declared here
> scsi_cmds.c: In function `ll_read_block':
> scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ll_write_block':
> scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ll_read_long':
> scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `get_capacity':
> scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `query':
> scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ReportLUNS':
> scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ReportOpCodes':
> scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `CheckVolumes':
> scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `CheckPartitions':
> scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `UnitReady':
> scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> block_fill_inbuf.c
> In file included from block_fill_inbuf.c:8:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> make: *** No rule to make target `../lib/baremetal.a', needed by
> `usbboot.elf'.  Stop.
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> Script done on Mon May 10 14:49:10 2004
>
> Again I expect that by instructing the make file to use the include
> files supplied by GCC 2.95.3, that most of the errors will be gone,
> but I'm listing those for reference.
> -------------------
> 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
>
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From hansolofalcon at worldnet.att.net  Mon May 10 16:08:00 2004
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Mon May 10 16:08:00 2004
Subject: New problems with building Baremetal
In-Reply-To: <Pine.LNX.4.58.0405101952240.6056@ucontrol.mobiledns.com>
Message-ID: <000601c436d5$85369fa0$6401a8c0@who5>

Hello from Gregg C Levine
Well Steven, that worked. Both Baremetal, and USB compiled with out
any complaints, the library contents also built correctly. Now the
obvious question. I selected a ROM image sent to me, by an earlier
correspondent, and then got it to work inside Bochs. The original
reasoning is that the board that he was building came close the one
being emulated. Here's the boot log from it:
LinuxBIOS-1.0.0 Wed Nov 13 22:27:29 EST 2002 starting...
Ram1
After 0x0000000 nop...
Before 0x4000000 nop...
After 0x4000000 nop...
After 0x54...
After 0x00...
Before 0x4000000 nop...
After 0x4000000 nop...
After 0x4000000 nop...
Before 0x4000000 nop...
After 0x4000000 nop...
After 0x0000000 nop...
Before 0x4000000 nop...
After 0x4000000 nop...
After 0x54...
After 0x00...
Before 0x4000000 nop...
After 0x4000000 nop...
After 0x4000000 nop...
First DRAM setup done
Ram2
Ram3
Ram Enable 1
Ram Enable 2
Ram Enable 3
Ram Enable 4
Ram Enable 5
Ram4
Ram5
Ram6
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.0.0 Wed Nov 13 22:27:29 EST 2002 booting...
Finding PCI configuration type.
PCI: Using configuration type 1
Scanning PCI bus...PCI: pci_scan_bus for bus 0
PCI: 00:00.0 [8086/1237]
PCI: 00:01.0 [8086/7000]
PCI: 00:02.0 [1234/1111]
PCI: pci_scan_bus returning with max=00
done
Allocating PCI resources...
ASSIGN RESOURCES, bus 0
PCI: 00:00.0 10 <- [0x00001000 - 0x00001003] io
PCI: 00:00.0 14 <- [0x00001010 - 0x00001013] io
PCI: 00:00.0 18 <- [0x00001020 - 0x00001023] io
PCI: 00:00.0 1c <- [0x00001030 - 0x00001033] io
PCI: 00:00.0 20 <- [0x00001040 - 0x00001043] io
PCI: 00:00.0 24 <- [0x00001050 - 0x00001053] io
PCI: 00:01.0 10 <- [0x00001060 - 0x00001063] io
PCI: 00:01.0 14 <- [0x00001070 - 0x00001073] io
PCI: 00:01.0 18 <- [0x00001080 - 0x00001083] io
PCI: 00:01.0 1c <- [0x00001090 - 0x00001093] io
PCI: 00:01.0 20 <- [0x000010a0 - 0x000010a3] io
PCI: 00:01.0 24 <- [0x000010b0 - 0x000010b3] io
PCI: 00:02.0 10 <- [0x000010c0 - 0x000010c3] io
PCI: 00:02.0 14 <- [0x000010d0 - 0x000010d3] io
PCI: 00:02.0 18 <- [0x000010e0 - 0x000010e3] io
PCI: 00:02.0 1c <- [0x000010f0 - 0x000010f3] io
PCI: 00:02.0 20 <- [0x00001100 - 0x00001103] io
PCI: 00:02.0 24 <- [0x00001400 - 0x00001403] io
ASSIGNED RESOURCES, bus 0
Allocating VGA resource
done.
Enabling PCI resourcess...PCI: 00:00.0 cmd <- 07
PCI: 00:01.0 cmd <- 07
PCI: 00:02.0 cmd <- 03
done.
Initializing PCI devices...
PCI devices initialized
totalram: 128M
Initializing CPU #0
Enabling cache...done.

Max cpuid index    : 1
Vendor ID          : GenuineIntel
Processor Type     : 0x00
Processor Family   : 0x05
Processor Model    : 0x01
Processor Mask     : 0x00
Processor Stepping : 0x03
Feature flags      : 0x00800131

done.
CPU #0 Initialized
intel_mainboard_fixup()
Testing SMI
SMI disabled
Enabling extended BIOS access...done.
Checking IRQ routing
tables.../home/andrew/linuxbios/freebios/src/arch/i386/lib/pirq_routin
g.c:    24:check_pirq_routing_table() - irq_routing_table located at:
0x00009740
/home/andrew/linuxbios/freebios/src/arch/i386/lib/pirq_routing.c:
31:check_pirq_routing_table() - checksum is: 0x63 but should be: 0xa6
/home/andrew/linuxbios/freebios/src/arch/i386/lib/pirq_routing.c:
49:check_pirq_routing_table() - checksum error in irq routing table
done.
Copying IRQ routing tables to 0xf0000...done.
Wrote linuxbios table at: 00000500 - 00000660  checksum 48b3

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

    37:init_bytes() - zkernel_start:0xfffc0000
zkernel_mask:0x0000007f
Cannot Load ELF Image

By the way, that happened while testing the arrangement both before I
had gotten Baremetal to compile, and afterwards. I stuck the ELF file,
as an Option ROM file, however, apparently the Linux BIOS ROM image
doesn't find it. 

If need be, I'll probably need to build my own image, and see what
happens 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

> -----Original Message-----
> From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> admin at clustermatic.org] On Behalf Of Steven James
> Sent: Monday, May 10, 2004 3:55 PM
> To: Gregg C Levine
> Cc: Linuxbios
> Subject: Re: New problems with building Baremetal
> 
> Greetings,
> 
> In the lib directory, try removing ide.o from DEPS for now. That
should
> get the library to compile.
> 
> The rest is all warnings except at the end where it can't link
against
> libbaremetal.a
> 
> G'day,
> sjames
> 
> 
> -------------------------steven james, director of research, linux
labs
> ... ........ ..... ....                    230 peachtree st nw ste
2701
> the original linux labs                             atlanta.ga.us
30303
>       -since 1995
http://www.linuxlabs.com
>                                               office & fax
866.545.6306
>
----------------------------------------------------------------------
-
> 
> 
> On Mon, 10 May 2004, Gregg C Levine wrote:
> 
> > Hello from Gregg C Levine
> > Now something else has happened. I've managed to build a copy of
GCC
> > version 2.9.5.3 and have it installed in the /opt directory.  But
> > there are unusual problems in the building of the bare metal
library,
> > here's a script output regarding the errors:
> > Script started on Mon May 10 14:47:28 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/printk.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c
-o
> > serial_subr.o serial_subr.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c
-o
> > subr.o subr.c
> > In file included from subr.c:16:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/vsprintf.c
> > In file included from ../../../src/lib/vsprintf.c:18:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memcpy.c
> > In file included from ../../../src/lib/memcpy.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/malloc.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memset.c
> > In file included from ../../../src/lib/memset.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/compute_ip_checksum.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c
-o
> > elfboot.o elfboot.c
> > In file included from elfboot.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c
-o
> > boot.o boot.c
> > In file included from boot.c:4:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/pc80/ide/ide.c
> > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> > make: *** [ide.o] Error 1
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> > Script done on Mon May 10 14:47:36 2004
> >
> > Obviously some of those errors can be corrected by reminding the
make
> > file to find the include files that GCC 2.95.3 prefers. But the
ones
> > that concern me, are the "missing files" for the IDE issues.
> >
> > And here's the latest problem with the USB attachment to bare
metal:
> > Script started on Mon May 10 14:49:02 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> > uhci.c:332: warning: `USBCMD' redefined
> > uhci.h:290: warning: this is the location of the previous
definition
> > uhci.c:333: warning: `USBSTS' redefined
> > uhci.h:291: warning: this is the location of the previous
definition
> > uhci.c:334: warning: `USBINTR' redefined
> > uhci.h:292: warning: this is the location of the previous
definition
> > uhci.c:335: warning: `FRNUM' redefined
> > uhci.h:293: warning: this is the location of the previous
definition
> > uhci.c:336: warning: `FLBASE' redefined
> > uhci.h:294: warning: this is the location of the previous
definition
> > uhci.c:337: warning: `SOFMOD' redefined
> > uhci.h:295: warning: this is the location of the previous
definition
> > uhci.c:338: warning: `PORTSC1' redefined
> > uhci.h:296: warning: this is the location of the previous
definition
> > uhci.c:339: warning: `PORTSC2' redefined
> > uhci.h:297: warning: this is the location of the previous
definition
> > uhci.c: In function `ctrl_msg':
> > uhci.c:776: warning: assignment makes pointer from integer without
a
> > cast
> > uhci.c: In function `hub_port_reset':
> > uhci.c:1193: warning: passing arg 1 of `dump_hex' from
incompatible
> > pointer type
> > uhci.c: In function `usb_hub_init':
> > uhci.c:1272: warning: assignment makes pointer from integer
without a
> > cast
> > uhci.c: In function `configure_device':
> > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor'
from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> > In file included from debug.c:31:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> > In file included from scsi_cmds.c:26:
> > /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> > uhci.h:13: warning: `ushort' previously declared here
> > scsi_cmds.c: In function `ll_read_block':
> > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_write_block':
> > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_read_long':
> > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `get_capacity':
> > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `query':
> > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportLUNS':
> > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportOpCodes':
> > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckVolumes':
> > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckPartitions':
> > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `UnitReady':
> > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2
-DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> > block_fill_inbuf.c
> > In file included from block_fill_inbuf.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > make: *** No rule to make target `../lib/baremetal.a', needed by
> > `usbboot.elf'.  Stop.
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> > Script done on Mon May 10 14:49:10 2004
> >
> > Again I expect that by instructing the make file to use the
include
> > files supplied by GCC 2.95.3, that most of the errors will be
gone,
> > but I'm listing those for reference.
> > -------------------
> > 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
> >
> >
> > _______________________________________________
> > 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



From YhLu at tyan.com  Mon May 10 16:39:00 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 10 16:39:00 2004
Subject: =?utf-8?B?562U5aSNOiBOZXcgcHJvYmxlbXMgd2l0aCBidWlsZGluZyBCYXJl?=
	=?utf-8?B?bWV0YWw=?=
Message-ID: <3174569B9743D511922F00A0C943142305063B93@TYANWEB>

Steven,

The uhci.c is from 2.4.22 or 2.6.5?

I merged your code into FILO in Etherboot, but at last I found that the USB
in AMD8111 is ohci. And I can not debug uhci now.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?10? 12:55
???: Gregg C Levine
??: Linuxbios
??: Re: New problems with building Baremetal

Greetings,

In the lib directory, try removing ide.o from DEPS for now. That should
get the library to compile.

The rest is all warnings except at the end where it can't link against
libbaremetal.a

G'day,
sjames


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


On Mon, 10 May 2004, Gregg C Levine wrote:

> Hello from Gregg C Levine
> Now something else has happened. I've managed to build a copy of GCC
> version 2.9.5.3 and have it installed in the /opt directory.  But
> there are unusual problems in the building of the bare metal library,
> here's a script output regarding the errors:
> Script started on Mon May 10 14:47:28 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/printk.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> serial_subr.o serial_subr.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> subr.o subr.c
> In file included from subr.c:16:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/vsprintf.c
> In file included from ../../../src/lib/vsprintf.c:18:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/memcpy.c
> In file included from ../../../src/lib/memcpy.c:1:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/malloc.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/memset.c
> In file included from ../../../src/lib/memset.c:1:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/lib/compute_ip_checksum.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> elfboot.o elfboot.c
> In file included from elfboot.c:8:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> boot.o boot.c
> In file included from boot.c:4:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> ../../../src/pc80/ide/ide.c
> ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> make: *** [ide.o] Error 1
> root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> Script done on Mon May 10 14:47:36 2004
>
> Obviously some of those errors can be corrected by reminding the make
> file to find the include files that GCC 2.95.3 prefers. But the ones
> that concern me, are the "missing files" for the IDE issues.
>
> And here's the latest problem with the USB attachment to bare metal:
> Script started on Mon May 10 14:49:02 2004
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> uhci.c:332: warning: `USBCMD' redefined
> uhci.h:290: warning: this is the location of the previous definition
> uhci.c:333: warning: `USBSTS' redefined
> uhci.h:291: warning: this is the location of the previous definition
> uhci.c:334: warning: `USBINTR' redefined
> uhci.h:292: warning: this is the location of the previous definition
> uhci.c:335: warning: `FRNUM' redefined
> uhci.h:293: warning: this is the location of the previous definition
> uhci.c:336: warning: `FLBASE' redefined
> uhci.h:294: warning: this is the location of the previous definition
> uhci.c:337: warning: `SOFMOD' redefined
> uhci.h:295: warning: this is the location of the previous definition
> uhci.c:338: warning: `PORTSC1' redefined
> uhci.h:296: warning: this is the location of the previous definition
> uhci.c:339: warning: `PORTSC2' redefined
> uhci.h:297: warning: this is the location of the previous definition
> uhci.c: In function `ctrl_msg':
> uhci.c:776: warning: assignment makes pointer from integer without a
> cast
> uhci.c: In function `hub_port_reset':
> uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> pointer type
> uhci.c: In function `usb_hub_init':
> uhci.c:1272: warning: assignment makes pointer from integer without a
> cast
> uhci.c: In function `configure_device':
> uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> incompatible pointer type
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> In file included from debug.c:31:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> In file included from scsi_cmds.c:26:
> /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> uhci.h:13: warning: `ushort' previously declared here
> scsi_cmds.c: In function `ll_read_block':
> scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ll_write_block':
> scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ll_read_long':
> scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `get_capacity':
> scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `query':
> scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ReportLUNS':
> scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `ReportOpCodes':
> scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `CheckVolumes':
> scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `CheckPartitions':
> scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> scsi_cmds.c: In function `UnitReady':
> scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> incompatible pointer type
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> block_fill_inbuf.c
> In file included from block_fill_inbuf.c:8:
> ../include/string.h:9: warning: conflicting types for built-in
> function `strcpy'
> make: *** No rule to make target `../lib/baremetal.a', needed by
> `usbboot.elf'.  Stop.
> root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> Script done on Mon May 10 14:49:10 2004
>
> Again I expect that by instructing the make file to use the include
> files supplied by GCC 2.95.3, that most of the errors will be gone,
> but I'm listing those for reference.
> -------------------
> 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
>
>
> _______________________________________________
> 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


From pyro at linuxlabs.com  Mon May 10 17:39:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Mon May 10 17:39:01 2004
Subject: =?utf-8?B?562U5aSNOiBOZXcgcHJvYmxlbXMgd2l0aCBidWlsZGluZyBCYXJl?=
 =?utf-8?B?bWV0YWw=?=
In-Reply-To: <3174569B9743D511922F00A0C943142305063B93@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063B93@TYANWEB>
Message-ID: <Pine.LNX.4.58.0405102252390.6056@ucontrol.mobiledns.com>

Greetings,

Actually, it is my own implementation, though I did use the 2.4.x kernel's
uhci.c as a guide. I couldn't use that as is since it had a good many
kernel dependencies and was interrupt driven.

I did have it loading as a module at one point to test things.

If you want, I can get a machine here set up and test/debug your merge.

G'day,
sjames



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


On Mon, 10 May 2004, YhLu wrote:

> Steven,
>
> The uhci.c is from 2.4.22 or 2.6.5?
>
> I merged your code into FILO in Etherboot, but at last I found that the USB
> in AMD8111 is ohci. And I can not debug uhci now.
>
> Regards
>
> YH
>
> -----????-----
> ???: Steven James [mailto:pyro at linuxlabs.com]
> ????: 2004?5?10? 12:55
> ???: Gregg C Levine
> ??: Linuxbios
> ??: Re: New problems with building Baremetal
>
> Greetings,
>
> In the lib directory, try removing ide.o from DEPS for now. That should
> get the library to compile.
>
> The rest is all warnings except at the end where it can't link against
> libbaremetal.a
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Mon, 10 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > Now something else has happened. I've managed to build a copy of GCC
> > version 2.9.5.3 and have it installed in the /opt directory.  But
> > there are unusual problems in the building of the bare metal library,
> > here's a script output regarding the errors:
> > Script started on Mon May 10 14:47:28 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/printk.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > serial_subr.o serial_subr.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > subr.o subr.c
> > In file included from subr.c:16:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/vsprintf.c
> > In file included from ../../../src/lib/vsprintf.c:18:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memcpy.c
> > In file included from ../../../src/lib/memcpy.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/malloc.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memset.c
> > In file included from ../../../src/lib/memset.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/compute_ip_checksum.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > elfboot.o elfboot.c
> > In file included from elfboot.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > boot.o boot.c
> > In file included from boot.c:4:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/pc80/ide/ide.c
> > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> > make: *** [ide.o] Error 1
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> > Script done on Mon May 10 14:47:36 2004
> >
> > Obviously some of those errors can be corrected by reminding the make
> > file to find the include files that GCC 2.95.3 prefers. But the ones
> > that concern me, are the "missing files" for the IDE issues.
> >
> > And here's the latest problem with the USB attachment to bare metal:
> > Script started on Mon May 10 14:49:02 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> > uhci.c:332: warning: `USBCMD' redefined
> > uhci.h:290: warning: this is the location of the previous definition
> > uhci.c:333: warning: `USBSTS' redefined
> > uhci.h:291: warning: this is the location of the previous definition
> > uhci.c:334: warning: `USBINTR' redefined
> > uhci.h:292: warning: this is the location of the previous definition
> > uhci.c:335: warning: `FRNUM' redefined
> > uhci.h:293: warning: this is the location of the previous definition
> > uhci.c:336: warning: `FLBASE' redefined
> > uhci.h:294: warning: this is the location of the previous definition
> > uhci.c:337: warning: `SOFMOD' redefined
> > uhci.h:295: warning: this is the location of the previous definition
> > uhci.c:338: warning: `PORTSC1' redefined
> > uhci.h:296: warning: this is the location of the previous definition
> > uhci.c:339: warning: `PORTSC2' redefined
> > uhci.h:297: warning: this is the location of the previous definition
> > uhci.c: In function `ctrl_msg':
> > uhci.c:776: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `hub_port_reset':
> > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> > pointer type
> > uhci.c: In function `usb_hub_init':
> > uhci.c:1272: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `configure_device':
> > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> > In file included from debug.c:31:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> > In file included from scsi_cmds.c:26:
> > /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> > uhci.h:13: warning: `ushort' previously declared here
> > scsi_cmds.c: In function `ll_read_block':
> > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_write_block':
> > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_read_long':
> > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `get_capacity':
> > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `query':
> > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportLUNS':
> > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportOpCodes':
> > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckVolumes':
> > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckPartitions':
> > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `UnitReady':
> > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> > block_fill_inbuf.c
> > In file included from block_fill_inbuf.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > make: *** No rule to make target `../lib/baremetal.a', needed by
> > `usbboot.elf'.  Stop.
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> > Script done on Mon May 10 14:49:10 2004
> >
> > Again I expect that by instructing the make file to use the include
> > files supplied by GCC 2.95.3, that most of the errors will be gone,
> > but I'm listing those for reference.
> > -------------------
> > 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
> >
> >
> > _______________________________________________
> > 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
>


From YhLu at tyan.com  Mon May 10 17:42:01 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 10 17:42:01 2004
Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IE5ldyBwcm9ibGVtcyB3aXRoIGJ1aWxk?=
	=?utf-8?B?aW5nIEJhcmVtZXRhbA==?=
Message-ID: <3174569B9743D511922F00A0C943142305063BA6@TYANWEB>

Good,

I will pack the code into tar and send to you.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?10? 15:57
???: YhLu
??: Gregg C Levine; Linuxbios
??: Re: ??: New problems with building Baremetal

Greetings,

Actually, it is my own implementation, though I did use the 2.4.x kernel's
uhci.c as a guide. I couldn't use that as is since it had a good many
kernel dependencies and was interrupt driven.

I did have it loading as a module at one point to test things.

If you want, I can get a machine here set up and test/debug your merge.

G'day,
sjames



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


On Mon, 10 May 2004, YhLu wrote:

> Steven,
>
> The uhci.c is from 2.4.22 or 2.6.5?
>
> I merged your code into FILO in Etherboot, but at last I found that the
USB
> in AMD8111 is ohci. And I can not debug uhci now.
>
> Regards
>
> YH
>
> -----????-----
> ???: Steven James [mailto:pyro at linuxlabs.com]
> ????: 2004?5?10? 12:55
> ???: Gregg C Levine
> ??: Linuxbios
> ??: Re: New problems with building Baremetal
>
> Greetings,
>
> In the lib directory, try removing ide.o from DEPS for now. That should
> get the library to compile.
>
> The rest is all warnings except at the end where it can't link against
> libbaremetal.a
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Mon, 10 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > Now something else has happened. I've managed to build a copy of GCC
> > version 2.9.5.3 and have it installed in the /opt directory.  But
> > there are unusual problems in the building of the bare metal library,
> > here's a script output regarding the errors:
> > Script started on Mon May 10 14:47:28 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/printk.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > serial_subr.o serial_subr.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > subr.o subr.c
> > In file included from subr.c:16:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/vsprintf.c
> > In file included from ../../../src/lib/vsprintf.c:18:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memcpy.c
> > In file included from ../../../src/lib/memcpy.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/malloc.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memset.c
> > In file included from ../../../src/lib/memset.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/compute_ip_checksum.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > elfboot.o elfboot.c
> > In file included from elfboot.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > boot.o boot.c
> > In file included from boot.c:4:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/pc80/ide/ide.c
> > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> > make: *** [ide.o] Error 1
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> > Script done on Mon May 10 14:47:36 2004
> >
> > Obviously some of those errors can be corrected by reminding the make
> > file to find the include files that GCC 2.95.3 prefers. But the ones
> > that concern me, are the "missing files" for the IDE issues.
> >
> > And here's the latest problem with the USB attachment to bare metal:
> > Script started on Mon May 10 14:49:02 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> > uhci.c:332: warning: `USBCMD' redefined
> > uhci.h:290: warning: this is the location of the previous definition
> > uhci.c:333: warning: `USBSTS' redefined
> > uhci.h:291: warning: this is the location of the previous definition
> > uhci.c:334: warning: `USBINTR' redefined
> > uhci.h:292: warning: this is the location of the previous definition
> > uhci.c:335: warning: `FRNUM' redefined
> > uhci.h:293: warning: this is the location of the previous definition
> > uhci.c:336: warning: `FLBASE' redefined
> > uhci.h:294: warning: this is the location of the previous definition
> > uhci.c:337: warning: `SOFMOD' redefined
> > uhci.h:295: warning: this is the location of the previous definition
> > uhci.c:338: warning: `PORTSC1' redefined
> > uhci.h:296: warning: this is the location of the previous definition
> > uhci.c:339: warning: `PORTSC2' redefined
> > uhci.h:297: warning: this is the location of the previous definition
> > uhci.c: In function `ctrl_msg':
> > uhci.c:776: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `hub_port_reset':
> > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> > pointer type
> > uhci.c: In function `usb_hub_init':
> > uhci.c:1272: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `configure_device':
> > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> > In file included from debug.c:31:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> > In file included from scsi_cmds.c:26:
> > /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> > uhci.h:13: warning: `ushort' previously declared here
> > scsi_cmds.c: In function `ll_read_block':
> > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_write_block':
> > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_read_long':
> > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `get_capacity':
> > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `query':
> > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportLUNS':
> > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportOpCodes':
> > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckVolumes':
> > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckPartitions':
> > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `UnitReady':
> > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> > block_fill_inbuf.c
> > In file included from block_fill_inbuf.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > make: *** No rule to make target `../lib/baremetal.a', needed by
> > `usbboot.elf'.  Stop.
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> > Script done on Mon May 10 14:49:10 2004
> >
> > Again I expect that by instructing the make file to use the include
> > files supplied by GCC 2.95.3, that most of the errors will be gone,
> > but I'm listing those for reference.
> > -------------------
> > 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
> >
> >
> > _______________________________________________
> > 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
>


From mdeschamps at mangrove-systems.com  Tue May 11 03:47:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 11 03:47:01 2004
Subject: Com. script for /dev/ttyS0
Message-ID: <1084262767.8658.22.camel@Calliphara>

Hello,

As i've seen there are no tool to handle ttyS0 communication, I've
done some tiny scripts to handle this in bash so it relies on linux.
It logs and calculate the elapse time of hearing, that could be 
interrupt. That's very minimal, I find it useful and the command line
of hear isn't that simple.

 To use them, you just have to check out your com driver with your
actual LB Baud rate :

[root at ge] cat /proc/tty/driver/serial 

serinfo:1.0 driver:5.05c revision:2001-07-08
0: uart:16550A port:3F8 irq:4 baud:9600 tx:967431 rx:955468 fe:2155
brk:2 
1: uart:16550A port:2F8 irq:3 baud:9600 tx:3 rx:0

Then copy these file hear.sh and digest.sh  (note:render 'em executable)
-------------------------------------------------------------------
#!/bin/sh
#
# Hear! script  listen & log from ttyS0 (serial port a.k.a COM1)
#  Mathieu Deschamps for mangove-systems
#
VERSION="07/05/04|16:24:03 MD"
i="Bienvenu(e) dans Hear! v. $VERSION j'ecoute sur ttyS0 ..."
ter=`tty`
if [ "x$1" = "x" ]; then
  echo "Usage $0 log_to_file"
  exit 0
 else
  LOG="$1"
fi
echo $i
echo  "Logging in $LOG"
echo "****************************************************" >>"$LOG" 
echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> "$LOG"
echo "  tty in use : $ter  from ttyS0 " >>"$LOG"
echo "****************************************************" >>"$LOG"

  /usr/bin/time -pao "$LOG" -- cat -sbA </dev/ttyS0 | tee -a "$LOG" 
  
  ./digest.sh $LOG -s

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

#!/bin/bash
#
# Script to digest hard-human readable hear! logs
#  Mathieu Deschamps for mangrove-systems
#
VERSION="11/05/04|09:40:28 MD"
SUPP=0
DAT="`date +%d\-%m\-%y\ %T`"
if  [ "x$1" = "x"  ]; then
        echo "usage: $0 hear!_log_file [--suppress-log,-s] " 
        echo "v. $VERSION"
        exit 0
  else
        FIL="$1"
fi

[ "x$2" = "x-s" ] || [ "x$2" = "x--suppress-log" ]  && SUPP=1

if [ -f "$FIL.adv" ]; then
  mv "$FIL.adv"  "$FIL.adv.$DAT"
fi

cat $FIL | while read line; 
        do 
                [ "x$line" != "x$" ] && echo "$line"
        done >  "$FIL.adv"

( [ $? -eq 0 ];  echo "$FIL digested into $FIL.adv" ) || echo "Digestion
gets harden ...blurp (error) "

[ $SUPP -eq 1 ] && rm -f $FIL 2>&1 >/dev/null
------------------------------------------------------------------------


Of course, first, you should test hear.sh  in typing  : echo "test"
>/dev/ttyS0 on you build station and see what you'll get, to end and
close dialog you can send a /dev/null or CTRL Interrup the listener.

It has helped me keeping trails, so if could for you.
mathieu


From jmiller at actuality-systems.com  Tue May 11 06:39:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Tue May 11 06:39:00 2004
Subject: Using DATA I/O to burn flash
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com>

We've got a Data I/O machine and I would like to use it to burn my
linuxbios.rom image to flash.

What format is this image?  If I'm not mistaken it's ELF, but the DATA
I/O doesn't have a listing for ELF files.  Has anyone used this type of
burner to flash their BIOS chips?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From stepan at openbios.org  Tue May 11 06:53:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue May 11 06:53:01 2004
Subject: Using DATA I/O to burn flash
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com>
Message-ID: <20040511121056.GA19163@openbios.org>

* Jay Miller <jmiller at actuality-systems.com> [040511 13:55]:
> We've got a Data I/O machine and I would like to use it to burn my
> linuxbios.rom image to flash.
> 
> What format is this image?  If I'm not mistaken it's ELF, but the DATA
> I/O doesn't have a listing for ELF files.  Has anyone used this type of
> burner to flash their BIOS chips?

Only the payload is ELF. That is the code that is executed after
hardware setup is done. This allows easy development of applications on
top of LinuxBIOS. 

The LinuxBIOS image itself is just a raw 1:1 image of what needs to be
burned to the flash chip. No headers, no bells, no whistles.

Stefan



From stuge-linuxbios at cdy.org  Tue May 11 06:59:00 2004
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Tue May 11 06:59:00 2004
Subject: Using DATA I/O to burn flash
In-Reply-To: <20040511121056.GA19163@openbios.org>
References: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com> <20040511121056.GA19163@openbios.org>
Message-ID: <20040511121714.GB9575@foo.birdnet.se>

On Tue, May 11, 2004 at 02:10:56PM +0200, Stefan Reinauer wrote:
> > What format is this image?
> 
> The LinuxBIOS image itself is just a raw 1:1 image of what needs
> to be burned to the flash chip. No headers, no bells, no whistles.

Often called "binary" in the programming software I've seen.


//Peter


From pyro at linuxlabs.com  Tue May 11 09:13:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Tue May 11 09:13:01 2004
Subject: Using DATA I/O to burn flash
In-Reply-To: <20040511121056.GA19163@openbios.org>
References: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com>
 <20040511121056.GA19163@openbios.org>
Message-ID: <Pine.LNX.4.58.0405111429300.6056@ucontrol.mobiledns.com>

Greetings,

Since the ELF header is interpreted by LinuxBIOS, it should be flashed as
binary so it is retained.

G'day,
sjames


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


On Tue, 11 May 2004, Stefan Reinauer wrote:

> * Jay Miller <jmiller at actuality-systems.com> [040511 13:55]:
> > We've got a Data I/O machine and I would like to use it to burn my
> > linuxbios.rom image to flash.
> >
> > What format is this image?  If I'm not mistaken it's ELF, but the DATA
> > I/O doesn't have a listing for ELF files.  Has anyone used this type of
> > burner to flash their BIOS chips?
>
> Only the payload is ELF. That is the code that is executed after
> hardware setup is done. This allows easy development of applications on
> top of LinuxBIOS.
>
> The LinuxBIOS image itself is just a raw 1:1 image of what needs to be
> burned to the flash chip. No headers, no bells, no whistles.
>
> Stefan
>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From rminnich at lanl.gov  Tue May 11 09:36:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Tue May 11 09:36:01 2004
Subject: Using DATA I/O to burn flash
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1162FF@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405110853250.5635-100000@maxroach.lanl.gov>

On Tue, 11 May 2004, Jay Miller wrote:

> What format is this image?  

it's a raw set of bytes. It's an image. 

> Has anyone used this type of burner to flash their BIOS chips?

yes, it works fine. I used to do it all the time.

ron



From ollie at lanl.gov  Tue May 11 11:07:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Tue May 11 11:07:00 2004
Subject: Is pc80/vgabios.c still used in LB2 ?
Message-ID: <1084292711.2459.160.camel@exponential.lanl.gov>

Hello,

I am trying to build rom iamge for EPIA and finding
a good way to do vga in LinuxBIOS. I found that the
pc80/vgabios.c is not used for EPIA and the 
southbridge_via_vt8231_control is redefinde in 
southbridge/via/vt8231/vt8231.c and used. There
is nothing about vga in that file. How does EPIA
enable its VGA chip ?

Ollie




From YhLu at tyan.com  Tue May 11 11:12:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 11:12:01 2004
Subject: =?gb2312?B?tPC4tDogVXNpbmcgREFUQSBJL08gdG8gYnVybiBmbGFzaA==?=
Message-ID: <3174569B9743D511922F00A0C943142305063BE9@TYANWEB>

I tried to send you one prebuilt image, but I can not reach you.

-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?11? 4:56
???: linuxbios at clustermatic.org
??: Using DATA I/O to burn flash

We've got a Data I/O machine and I would like to use it to burn my
linuxbios.rom image to flash.

What format is this image?  If I'm not mistaken it's ELF, but the DATA
I/O doesn't have a listing for ELF files.  Has anyone used this type of
burner to flash their BIOS chips?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



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


From YhLu at tyan.com  Tue May 11 12:19:00 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 12:19:00 2004
Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IE5ldyBwcm9ibGVtcyB3aXRoIGJ1aWxk?=
	=?utf-8?B?aW5nIEJhcmVtZXRhbA==?=
Message-ID: <3174569B9743D511922F00A0C943142305063C0C@TYANWEB>

Steven,

I just sent you the tar ball include OHCI support, Please let know if you
got it.
It can not reset the OHCI yet.

Regards

YH

-----????-----
???: YhLu 
????: 2004?5?10? 16:11
???: Steven James
??: Gregg C Levine; Linuxbios
??: ??: ??: New problems with building Baremetal

Good,

I will pack the code into tar and send to you.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?10? 15:57
???: YhLu
??: Gregg C Levine; Linuxbios
??: Re: ??: New problems with building Baremetal

Greetings,

Actually, it is my own implementation, though I did use the 2.4.x kernel's
uhci.c as a guide. I couldn't use that as is since it had a good many
kernel dependencies and was interrupt driven.

I did have it loading as a module at one point to test things.

If you want, I can get a machine here set up and test/debug your merge.

G'day,
sjames



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


On Mon, 10 May 2004, YhLu wrote:

> Steven,
>
> The uhci.c is from 2.4.22 or 2.6.5?
>
> I merged your code into FILO in Etherboot, but at last I found that the
USB
> in AMD8111 is ohci. And I can not debug uhci now.
>
> Regards
>
> YH
>
> -----????-----
> ???: Steven James [mailto:pyro at linuxlabs.com]
> ????: 2004?5?10? 12:55
> ???: Gregg C Levine
> ??: Linuxbios
> ??: Re: New problems with building Baremetal
>
> Greetings,
>
> In the lib directory, try removing ide.o from DEPS for now. That should
> get the library to compile.
>
> The rest is all warnings except at the end where it can't link against
> libbaremetal.a
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Mon, 10 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > Now something else has happened. I've managed to build a copy of GCC
> > version 2.9.5.3 and have it installed in the /opt directory.  But
> > there are unusual problems in the building of the bare metal library,
> > here's a script output regarding the errors:
> > Script started on Mon May 10 14:47:28 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/printk.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > serial_subr.o serial_subr.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > subr.o subr.c
> > In file included from subr.c:16:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/vsprintf.c
> > In file included from ../../../src/lib/vsprintf.c:18:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memcpy.c
> > In file included from ../../../src/lib/memcpy.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/malloc.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memset.c
> > In file included from ../../../src/lib/memset.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/compute_ip_checksum.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > elfboot.o elfboot.c
> > In file included from elfboot.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > boot.o boot.c
> > In file included from boot.c:4:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/pc80/ide/ide.c
> > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> > make: *** [ide.o] Error 1
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> > Script done on Mon May 10 14:47:36 2004
> >
> > Obviously some of those errors can be corrected by reminding the make
> > file to find the include files that GCC 2.95.3 prefers. But the ones
> > that concern me, are the "missing files" for the IDE issues.
> >
> > And here's the latest problem with the USB attachment to bare metal:
> > Script started on Mon May 10 14:49:02 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> > uhci.c:332: warning: `USBCMD' redefined
> > uhci.h:290: warning: this is the location of the previous definition
> > uhci.c:333: warning: `USBSTS' redefined
> > uhci.h:291: warning: this is the location of the previous definition
> > uhci.c:334: warning: `USBINTR' redefined
> > uhci.h:292: warning: this is the location of the previous definition
> > uhci.c:335: warning: `FRNUM' redefined
> > uhci.h:293: warning: this is the location of the previous definition
> > uhci.c:336: warning: `FLBASE' redefined
> > uhci.h:294: warning: this is the location of the previous definition
> > uhci.c:337: warning: `SOFMOD' redefined
> > uhci.h:295: warning: this is the location of the previous definition
> > uhci.c:338: warning: `PORTSC1' redefined
> > uhci.h:296: warning: this is the location of the previous definition
> > uhci.c:339: warning: `PORTSC2' redefined
> > uhci.h:297: warning: this is the location of the previous definition
> > uhci.c: In function `ctrl_msg':
> > uhci.c:776: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `hub_port_reset':
> > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> > pointer type
> > uhci.c: In function `usb_hub_init':
> > uhci.c:1272: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `configure_device':
> > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> > In file included from debug.c:31:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> > In file included from scsi_cmds.c:26:
> > /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> > uhci.h:13: warning: `ushort' previously declared here
> > scsi_cmds.c: In function `ll_read_block':
> > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_write_block':
> > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_read_long':
> > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `get_capacity':
> > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `query':
> > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportLUNS':
> > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportOpCodes':
> > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckVolumes':
> > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckPartitions':
> > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `UnitReady':
> > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> > block_fill_inbuf.c
> > In file included from block_fill_inbuf.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > make: *** No rule to make target `../lib/baremetal.a', needed by
> > `usbboot.elf'.  Stop.
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> > Script done on Mon May 10 14:49:10 2004
> >
> > Again I expect that by instructing the make file to use the include
> > files supplied by GCC 2.95.3, that most of the errors will be gone,
> > but I'm listing those for reference.
> > -------------------
> > 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
> >
> >
> > _______________________________________________
> > 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
>
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From YhLu at tyan.com  Tue May 11 12:24:00 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 12:24:00 2004
Subject: New problems with building Baremetal
Message-ID: <3174569B9743D511922F00A0C943142305063C0F@TYANWEB>

when prompt boot:
input
uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf

YH

-----????-----
???: YhLu 
????: 2004?5?11? 10:37
???: Steven James
??: Gregg C Levine; Linuxbios
??: ??: ??: New problems with building Baremetal

Steven,

I just sent you the tar ball include OHCI support, Please let know if you
got it.
It can not reset the OHCI yet.

Regards

YH

-----????-----
???: YhLu 
????: 2004?5?10? 16:11
???: Steven James
??: Gregg C Levine; Linuxbios
??: ??: ??: New problems with building Baremetal

Good,

I will pack the code into tar and send to you.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?10? 15:57
???: YhLu
??: Gregg C Levine; Linuxbios
??: Re: ??: New problems with building Baremetal

Greetings,

Actually, it is my own implementation, though I did use the 2.4.x kernel's
uhci.c as a guide. I couldn't use that as is since it had a good many
kernel dependencies and was interrupt driven.

I did have it loading as a module at one point to test things.

If you want, I can get a machine here set up and test/debug your merge.

G'day,
sjames



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


On Mon, 10 May 2004, YhLu wrote:

> Steven,
>
> The uhci.c is from 2.4.22 or 2.6.5?
>
> I merged your code into FILO in Etherboot, but at last I found that the
USB
> in AMD8111 is ohci. And I can not debug uhci now.
>
> Regards
>
> YH
>
> -----????-----
> ???: Steven James [mailto:pyro at linuxlabs.com]
> ????: 2004?5?10? 12:55
> ???: Gregg C Levine
> ??: Linuxbios
> ??: Re: New problems with building Baremetal
>
> Greetings,
>
> In the lib directory, try removing ide.o from DEPS for now. That should
> get the library to compile.
>
> The rest is all warnings except at the end where it can't link against
> libbaremetal.a
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Mon, 10 May 2004, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > Now something else has happened. I've managed to build a copy of GCC
> > version 2.9.5.3 and have it installed in the /opt directory.  But
> > there are unusual problems in the building of the bare metal library,
> > here's a script output regarding the errors:
> > Script started on Mon May 10 14:47:28 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/printk.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > serial_subr.o serial_subr.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > subr.o subr.c
> > In file included from subr.c:16:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/vsprintf.c
> > In file included from ../../../src/lib/vsprintf.c:18:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memcpy.c
> > In file included from ../../../src/lib/memcpy.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/malloc.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/memset.c
> > In file included from ../../../src/lib/memset.c:1:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/lib/compute_ip_checksum.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > elfboot.o elfboot.c
> > In file included from elfboot.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2    -c -o
> > boot.o boot.c
> > In file included from boot.c:4:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2  -c
> > ../../../src/pc80/ide/ide.c
> > ../../../src/pc80/ide/ide.c:27: delay.h: No such file or directory
> > ../../../src/pc80/ide/ide.c:28: pci.h: No such file or directory
> > make: *** [ide.o] Error 1
> > root at who5:/usr/src/lobos/freebios/util/baremetal/lib# exit
> > Script done on Mon May 10 14:47:36 2004
> >
> > Obviously some of those errors can be corrected by reminding the make
> > file to find the include files that GCC 2.95.3 prefers. But the ones
> > that concern me, are the "missing files" for the IDE issues.
> >
> > And here's the latest problem with the USB attachment to bare metal:
> > Script started on Mon May 10 14:49:02 2004
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# make
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o uhci.o uhci.c
> > uhci.c:332: warning: `USBCMD' redefined
> > uhci.h:290: warning: this is the location of the previous definition
> > uhci.c:333: warning: `USBSTS' redefined
> > uhci.h:291: warning: this is the location of the previous definition
> > uhci.c:334: warning: `USBINTR' redefined
> > uhci.h:292: warning: this is the location of the previous definition
> > uhci.c:335: warning: `FRNUM' redefined
> > uhci.h:293: warning: this is the location of the previous definition
> > uhci.c:336: warning: `FLBASE' redefined
> > uhci.h:294: warning: this is the location of the previous definition
> > uhci.c:337: warning: `SOFMOD' redefined
> > uhci.h:295: warning: this is the location of the previous definition
> > uhci.c:338: warning: `PORTSC1' redefined
> > uhci.h:296: warning: this is the location of the previous definition
> > uhci.c:339: warning: `PORTSC2' redefined
> > uhci.h:297: warning: this is the location of the previous definition
> > uhci.c: In function `ctrl_msg':
> > uhci.c:776: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `hub_port_reset':
> > uhci.c:1193: warning: passing arg 1 of `dump_hex' from incompatible
> > pointer type
> > uhci.c: In function `usb_hub_init':
> > uhci.c:1272: warning: assignment makes pointer from integer without a
> > cast
> > uhci.c: In function `configure_device':
> > uhci.c:1383: warning: passing arg 1 of `dump_config_descriptor' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o usb_scsi_low.o usb_scsi_low.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o debug.o debug.c
> > In file included from debug.c:31:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o scsi_cmds.o scsi_cmds.c
> > In file included from scsi_cmds.c:26:
> > /usr/include/sys/types.h:152: warning: redefinition of `ushort'
> > uhci.h:13: warning: `ushort' previously declared here
> > scsi_cmds.c: In function `ll_read_block':
> > scsi_cmds.c:258: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_write_block':
> > scsi_cmds.c:280: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ll_read_long':
> > scsi_cmds.c:311: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `get_capacity':
> > scsi_cmds.c:328: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `query':
> > scsi_cmds.c:349: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportLUNS':
> > scsi_cmds.c:372: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `ReportOpCodes':
> > scsi_cmds.c:423: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c:423: warning: passing arg 5 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckVolumes':
> > scsi_cmds.c:469: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `CheckPartitions':
> > scsi_cmds.c:494: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > scsi_cmds.c: In function `UnitReady':
> > scsi_cmds.c:514: warning: passing arg 2 of `scsi_command' from
> > incompatible pointer type
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o pci_util.o pci_util.c
> > /opt/gcc-2.95.3/bin/gcc -I ../include -I ../include/i386 -O2 -DDEBUG
> > -DZKERNEL_START=0xfff00000   -c -o block_fill_inbuf.o
> > block_fill_inbuf.c
> > In file included from block_fill_inbuf.c:8:
> > ../include/string.h:9: warning: conflicting types for built-in
> > function `strcpy'
> > make: *** No rule to make target `../lib/baremetal.a', needed by
> > `usbboot.elf'.  Stop.
> > root at who5:/usr/src/lobos/freebios/util/baremetal/usb# exit
> > Script done on Mon May 10 14:49:10 2004
> >
> > Again I expect that by instructing the make file to use the include
> > files supplied by GCC 2.95.3, that most of the errors will be gone,
> > but I'm listing those for reference.
> > -------------------
> > 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
> >
> >
> > _______________________________________________
> > 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
>
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


From adam at cfar.umd.edu  Tue May 11 13:43:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Tue May 11 13:43:01 2004
Subject: Is pc80/vgabios.c still used in LB2 ?
In-Reply-To: <1084292711.2459.160.camel@exponential.lanl.gov>
Message-ID: <20040511150632.G76033-100000@www.missl.cs.umd.edu>

Could it be that they used ADLO? I seem to vaguely recall some work being
done in that direction. Dunno if that helps.

from archives:
	Subject: Re: ADLO for EPIA
	Subject: linuxbios with ADLO [EPIA]
	Subject: ADLO + EPIA-M + No hard disk, just etherboot/tftp?

On Tue, 11 May 2004, Li-Ta Lo wrote:

> Hello,
>
> I am trying to build rom iamge for EPIA and finding
> a good way to do vga in LinuxBIOS. I found that the
> pc80/vgabios.c is not used for EPIA and the
> southbridge_via_vt8231_control is redefinde in
> southbridge/via/vt8231/vt8231.c and used. There
> is nothing about vga in that file. How does EPIA
> enable its VGA chip ?



From YhLu at tyan.com  Tue May 11 22:45:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 22:45:01 2004
Subject: New problems with building Baremetal
Message-ID: <3174569B9743D511922F00A0C943142305063C81@TYANWEB>

Steven,

I made some progress, and it met failed transaction.

Regards

YH

[FILO]FILO version 0.4.1 (root at tst2723-rh9) Tue May 11 20:39:11 PDT 2004
Press <Enter> for default boot, or <Esc> for boot prompt... timed out
boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
LinuxLabs USB bootloader
raw frame_list is at 000795c0
frame_list is at 0007a000
frame_list_link: addr: 000785d0
frame_list_link:  raw addr: efef5f40
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 00070560
raw frame_list is at 0007b5c0
frame_list is at 0007c000
frame_list_link: addr: 000785f0
frame_list_link:  raw addr: efef5f60
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 000705a0
raw frame_list is at 0007d5c0
frame_list is at 0007e000
frame_list_link: addr: 00078610
frame_list_link:  raw addr: efef5f80
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 000705e0
raw frame_list is at 0007f5c0
frame_list is at 00080000
frame_list_link: addr: 00078630
frame_list_link:  raw addr: efef5fa0
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 00070620
Found OHCI at 0d1a2690
Resetting OHCI
USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef7970
Starting OHCI
Found OHCI at 0d1a3690
Resetting OHCI
USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef9970
Starting OHCI
poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00010101     poll_o_root_hub2 v=00010101poll_o_root_hub21
v=00010101    Connection on port 0d1a36e8
poll_o_root_hub211 v=00000101   poll_o_root_hub212 v=00000101
poll_o_root_hub213 v=00000101   poll_o_root_hub214 v=00000101  New USB
device, setting address 00000003
UHCI at 0d1a3690
failed_transaction: TD(00070660):
failed_transaction: type: SETUP
failed_transaction: retries: 00000003
failed_transaction: IOC
failed_transaction: active: 00000001
failed_transaction: device_addr: 00000000
failed_transaction: endpoint: 00000000
failed_transaction: data_toggle: 00000000
failed_transaction: max_transfer: 00000007
failed_transaction: actual: 00000000
failed_transaction: link:
        failed_transaction: addr: 00070680
        failed_transaction:  raw addr: efeedff0
        failed_transaction: terminate: 00000000
        failed_transaction: queue: 00000000
        failed_transaction: depth: 00000000
failed_transaction: TD(00070680):
failed_transaction: type: IN
failed_transaction: retries: 00000000
failed_transaction: active: 00000001
failed_transaction: device_addr: 00000000
failed_transaction: endpoint: 00000000
failed_transaction: data_toggle: 00000001
failed_transaction: max_transfer: 000007ff
failed_transaction: actual: 00000000
failed_transaction: link:
        failed_transaction:ddr: 10182690
        failed_transaction:aw addr: 00000000
        failed_transaction:erminate: 00000001
        failed_transaction:ueue: 00000000
        failed_transaction:epth: 00000000
configure_device: set_address failed!
configure_device: can't set address! bailing!



-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb.tar.bz2
Type: application/octet-stream
Size: 20322 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040511/0e51f132/attachment.obj>

From ts1 at tsn.or.jp  Tue May 11 23:10:00 2004
From: ts1 at tsn.or.jp (Takeshi Sone)
Date: Tue May 11 23:10:00 2004
Subject: New problems with building Baremetal
In-Reply-To: <3174569B9743D511922F00A0C943142305063C81@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063C81@TYANWEB>
Message-ID: <59441.202.32.178.36.1084336051.squirrel@202.32.178.36>

YH,
I have tried porting Steven's USB driver into FILO some months ago
(without success, though).
FILO is running on virtual address, but hardware that does DMA
needs to know physical address, so some translation is needed when
you pass some memory address to hardware registers.
I believe this situation is same in Etherboot.
(In fact, I stealed the idea of relocation/virtual addressing from
Etherboot.)

> Steven,
>
> I made some progress, and it met failed transaction.
>
> Regards
>
> YH
>
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Tue May 11 20:39:11 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt... timed out
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 000795c0
> frame_list is at 0007a000
> frame_list_link: addr: 000785d0
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070560
> raw frame_list is at 0007b5c0
> frame_list is at 0007c000
> frame_list_link: addr: 000785f0
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705a0
> raw frame_list is at 0007d5c0
> frame_list is at 0007e000
> frame_list_link: addr: 00078610
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705e0
> raw frame_list is at 0007f5c0
> frame_list is at 00080000
> frame_list_link: addr: 00078630
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070620
> Found OHCI at 0d1a2690
> Resetting OHCI
> USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef7970
> Starting OHCI
> Found OHCI at 0d1a3690
> Resetting OHCI
> USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef9970
> Starting OHCI
> poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1
> v=00000100
> poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00010101     poll_o_root_hub2
> v=00010101poll_o_root_hub21
> v=00010101    Connection on port 0d1a36e8
> poll_o_root_hub211 v=00000101   poll_o_root_hub212 v=00000101
> poll_o_root_hub213 v=00000101   poll_o_root_hub214 v=00000101  New USB
> device, setting address 00000003
> UHCI at 0d1a3690
> failed_transaction: TD(00070660):
> failed_transaction: type: SETUP
> failed_transaction: retries: 00000003
> failed_transaction: IOC
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000000
> failed_transaction: max_transfer: 00000007
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction: addr: 00070680
>         failed_transaction:  raw addr: efeedff0
>         failed_transaction: terminate: 00000000
>         failed_transaction: queue: 00000000
>         failed_transaction: depth: 00000000
> failed_transaction: TD(00070680):
> failed_transaction: type: IN
> failed_transaction: retries: 00000000
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000001
> failed_transaction: max_transfer: 000007ff
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction:ddr: 10182690
>         failed_transaction:aw addr: 00000000
>         failed_transaction:erminate: 00000001
>         failed_transaction:ueue: 00000000
>         failed_transaction:epth: 00000000
> configure_device: set_address failed!
> configure_device: can't set address! bailing!
>
>
>
>

--
Takeshi


From YhLu at tyan.com  Tue May 11 23:23:01 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 23:23:01 2004
Subject: =?gb2312?B?tPC4tDogTmV3IHByb2JsZW1zIHdpdGggYnVpbGRpbmcgQmFyZW1l?=
	=?gb2312?B?dGFs?=
Message-ID: <3174569B9743D511922F00A0C943142305063C85@TYANWEB>

YES, I have modified that with phy_to_virt for mem range for OHCI.
I can not debug UHCI, because I can not find such adapter. Amd 8111 is OHCI.

Please let me know if you can debug the code.

Regards

YH

-----????-----
???: Takeshi Sone [mailto:ts1 at tsn.or.jp] 
????: 2004?5?11? 21:28
???: YhLu
??: Steven James; Linuxbios
??: Re: New problems with building Baremetal

YH,
I have tried porting Steven's USB driver into FILO some months ago
(without success, though).
FILO is running on virtual address, but hardware that does DMA
needs to know physical address, so some translation is needed when
you pass some memory address to hardware registers.
I believe this situation is same in Etherboot.
(In fact, I stealed the idea of relocation/virtual addressing from
Etherboot.)

> Steven,
>
> I made some progress, and it met failed transaction.
>
> Regards
>
> YH
>
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Tue May 11 20:39:11 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt... timed out
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 000795c0
> frame_list is at 0007a000
> frame_list_link: addr: 000785d0
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070560
> raw frame_list is at 0007b5c0
> frame_list is at 0007c000
> frame_list_link: addr: 000785f0
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705a0
> raw frame_list is at 0007d5c0
> frame_list is at 0007e000
> frame_list_link: addr: 00078610
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705e0
> raw frame_list is at 0007f5c0
> frame_list is at 00080000
> frame_list_link: addr: 00078630
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070620
> Found OHCI at 0d1a2690
> Resetting OHCI
> USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef7970
> Starting OHCI
> Found OHCI at 0d1a3690
> Resetting OHCI
> USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef9970
> Starting OHCI
> poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1
> v=00000100
> poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00010101     poll_o_root_hub2
> v=00010101poll_o_root_hub21
> v=00010101    Connection on port 0d1a36e8
> poll_o_root_hub211 v=00000101   poll_o_root_hub212 v=00000101
> poll_o_root_hub213 v=00000101   poll_o_root_hub214 v=00000101  New USB
> device, setting address 00000003
> UHCI at 0d1a3690
> failed_transaction: TD(00070660):
> failed_transaction: type: SETUP
> failed_transaction: retries: 00000003
> failed_transaction: IOC
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000000
> failed_transaction: max_transfer: 00000007
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction: addr: 00070680
>         failed_transaction:  raw addr: efeedff0
>         failed_transaction: terminate: 00000000
>         failed_transaction: queue: 00000000
>         failed_transaction: depth: 00000000
> failed_transaction: TD(00070680):
> failed_transaction: type: IN
> failed_transaction: retries: 00000000
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000001
> failed_transaction: max_transfer: 000007ff
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction:ddr: 10182690
>         failed_transaction:aw addr: 00000000
>         failed_transaction:erminate: 00000001
>         failed_transaction:ueue: 00000000
>         failed_transaction:epth: 00000000
> configure_device: set_address failed!
> configure_device: can't set address! bailing!
>
>
>
>

--
Takeshi


From YhLu at tyan.com  Tue May 11 23:37:00 2004
From: YhLu at tyan.com (YhLu)
Date: Tue May 11 23:37:00 2004
Subject: =?gb2312?B?tPC4tDogTmV3IHByb2JsZW1zIHdpdGggYnVpbGRpbmcgQmFyZW1l?=
	=?gb2312?B?dGFs?=
Message-ID: <3174569B9743D511922F00A0C943142305063C86@TYANWEB>

You mean the frame_list[]....?

YH

-----????-----
???: YhLu 
????: 2004?5?11? 21:53
???: Takeshi Sone
??: Steven James; Linuxbios
??: ??: New problems with building Baremetal

YES, I have modified that with phy_to_virt for mem range for OHCI.
I can not debug UHCI, because I can not find such adapter. Amd 8111 is OHCI.

Please let me know if you can debug the code.

Regards

YH

-----????-----
???: Takeshi Sone [mailto:ts1 at tsn.or.jp] 
????: 2004?5?11? 21:28
???: YhLu
??: Steven James; Linuxbios
??: Re: New problems with building Baremetal

YH,
I have tried porting Steven's USB driver into FILO some months ago
(without success, though).
FILO is running on virtual address, but hardware that does DMA
needs to know physical address, so some translation is needed when
you pass some memory address to hardware registers.
I believe this situation is same in Etherboot.
(In fact, I stealed the idea of relocation/virtual addressing from
Etherboot.)

> Steven,
>
> I made some progress, and it met failed transaction.
>
> Regards
>
> YH
>
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Tue May 11 20:39:11 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt... timed out
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 000795c0
> frame_list is at 0007a000
> frame_list_link: addr: 000785d0
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070560
> raw frame_list is at 0007b5c0
> frame_list is at 0007c000
> frame_list_link: addr: 000785f0
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705a0
> raw frame_list is at 0007d5c0
> frame_list is at 0007e000
> frame_list_link: addr: 00078610
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705e0
> raw frame_list is at 0007f5c0
> frame_list is at 00080000
> frame_list_link: addr: 00078630
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070620
> Found OHCI at 0d1a2690
> Resetting OHCI
> USB HC reset_hc usb-0d1a2690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef7970
> Starting OHCI
> Found OHCI at 0d1a3690
> Resetting OHCI
> USB HC reset_hc usb-0d1a3690: ctrl = 0x00000600 ;ohc_init setting
> framelist
> to: efef9970
> Starting OHCI
> poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1
> v=00000100
> poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00010101     poll_o_root_hub2
> v=00010101poll_o_root_hub21
> v=00010101    Connection on port 0d1a36e8
> poll_o_root_hub211 v=00000101   poll_o_root_hub212 v=00000101
> poll_o_root_hub213 v=00000101   poll_o_root_hub214 v=00000101  New USB
> device, setting address 00000003
> UHCI at 0d1a3690
> failed_transaction: TD(00070660):
> failed_transaction: type: SETUP
> failed_transaction: retries: 00000003
> failed_transaction: IOC
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000000
> failed_transaction: max_transfer: 00000007
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction: addr: 00070680
>         failed_transaction:  raw addr: efeedff0
>         failed_transaction: terminate: 00000000
>         failed_transaction: queue: 00000000
>         failed_transaction: depth: 00000000
> failed_transaction: TD(00070680):
> failed_transaction: type: IN
> failed_transaction: retries: 00000000
> failed_transaction: active: 00000001
> failed_transaction: device_addr: 00000000
> failed_transaction: endpoint: 00000000
> failed_transaction: data_toggle: 00000001
> failed_transaction: max_transfer: 000007ff
> failed_transaction: actual: 00000000
> failed_transaction: link:
>         failed_transaction:ddr: 10182690
>         failed_transaction:aw addr: 00000000
>         failed_transaction:erminate: 00000001
>         failed_transaction:ueue: 00000000
>         failed_transaction:epth: 00000000
> configure_device: set_address failed!
> configure_device: can't set address! bailing!
>
>
>
>

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


From ollie at lanl.gov  Wed May 12 11:22:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Wed May 12 11:22:00 2004
Subject: Dealing with Bus Master Enable
Message-ID: <1084380006.26760.3.camel@exponential.lanl.gov>

YHLu,

I have a new idea about the bus master enable and
subsystem ids. We should do it with config tool.
We can add new config keywords like busmaster and
subsystem and use some generic code to enable the
bit and program the subsystems ids. Thus we can
remove a lot of codes in src/driver and mainboard/tyan.
How do you think ?

Ollie




From jmiller at actuality-systems.com  Wed May 12 11:26:01 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Wed May 12 11:26:01 2004
Subject: Lessons learned and more ???
Message-ID: <E8F8DBCB0468204E856114A2CD20741F116375@mail.local.ActualitySystems.com>

Thanks everyone for your help!

It took me some time to realize the reason that I wasn't seeing any data
on the VGA console is because it doesn't work on the S2885.  But I have
my null modem connected and am seeing lots of interesting stuff now.

YH sent me a pre-built S2885 image and the FIRST time it executed I got
this:


LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting...

setting up resource map....done.                                
coherent_ht_finalize                    
done    
Ram1.00       
Ram1.01       
Ram2.00       
Ram2.01       
No memory for this cpu                      
Ram3    
Initializing memory:  done                          
Initializing memory:
...........................................................

........................................................................

........................................................................
........

........................................................................
. failed


Clearing LinuxBIOS memory:  done                                
Ram4    
Copying LinuxBIOS to ram.                         
Jumping to LinuxBIOS.                     
LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting...

Finding PCI configuration type.                               
PCI: Using configuration type 1                               
Enumerating static devices...                             
Enumerating: AMD K8 Northbridge                               
Enumerating: AMD K8 Northbridge                               
Enumerating: AMD K8 CPU                       
Enumerating: AMD K8                   
Enumerating: AMD 8111 Southbridge                                 
Enumerating: Winbond w83627hf                             
Enumerating buses...                    
amdk8_scan_root_bus                   
amdk8_scan_root_bus: start scaning pci bus

PCI: pci_scan_bus for bus 0                           
PCI: 00:18.0 [1022/1100] enabled                                
PCI: 00:18.1 [1022/1101] enabled                                
PCI: 00:18.2 [1022/1102] enabled                                
PCI: 00:18.3 [1022/1103] ops                            
PCI: 00:18.3 [1022/1103] enabled                                
PCI: 00:19.0 [ffff/ffff] enabled                                
PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring.

PCI: 00:19.1 No device operations                                 
PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h

PCI: 00:19.2 No device operations                                 
PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring.

PCI: 00:19.3 No device operations                                 
amdk8_scan_chains max: 0 starting...                                    
Hyper transport scan link: 0 max: 1                                   
PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004

HyperT reset not needed                       
PCI: pci_scan_bus for bus 1                           
PCI: 01:01.0 [1022/7454] ops                            
PCI: 01:01.0 [1022/7454] enabled                                
PCI: 01:02.0 [1022/7455] bus ops                                
PCI: 01:02.0 [1022/7455] enabled                                
PCI: pci_scan_bus for bus 2                           
PCI: 02:00.0 [10de/0333] enabled                                
PCI: pci_scan_bus returning with max=02

PCI: pci_scan_bus returning with max=02

Hyper transport scan link: 0 new max: 2

Hypertransport scan link done                             
Hyper transport scan link: 2 max: 3                                   
PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003

amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460]

PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007

HyperT reset not needed                       
PCI: pci_scan_bus for bus 3                           
PCI: 03:01.0 [1022/7450] bus ops                                
PCI: 03:01.0 [1022/7450] enabled                                
PCI: 03:01.1 [1022/7451] ops                            
PCI: 03:01.1 [1022/7451] enabl                            
PCI: 03:02.0 [1022/7450] bus ops                                
PCI: 03:02.0 [1022/7450] enabled                                
PCI: 03:02.1 [1022/7451] ops                            
PCI: 03:02.1 [1022/7451] enabled                                
amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]

PCI: 03:03.0 [1022/7460] bus ops                                
amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]

PCI: 03:03.0 [1022/7460] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468]

PCI: 03:04.0 [1022/7468] bus ops                                
amd8111_enable: enabling PCI: 03:04.0 [1022/7468]

PCI: 03:04.0 [1022/7468] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.1 [102

PCI: 03:04.1 [1022/7469] ops                            
amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469]

PCI: 03:04.1 [1022/7469] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]

amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]

PCI: 03:04.2 [1022/746a] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b]

PCI: 03:04.3 [1022/746b] ops                            
amd8111_enable: enabling PCI: 03:04.3 [1022/746b]

PCI: 03:04.3 [1022/746b] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d]

PCI: 03:04.5 [1022/746d] ops                            
amd8111_enable: enabling PCI: 03:04.5 [1022/746d]

PCI: 03:04.5 [1022/746d] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e]

PCI: 03:04.6 [1022/746e] ops                            
amd8111_enable: disabling PCI: 03:04.6 [1022/746e]

PCI: 03:04.6 [1022/746e] disabled                                 
PCI: pci_scan_bus for bus 4                           
PCI: 04:09.0 [14e4/16a7] enabled                                
PCI: pci_scan_bus returning with max=04

PCI: pci_scan_bus for bus 5                           
PCI: pci_scan_bus returning with max=05

PCI: pci_scan_bus for bus 6                           
amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464]

PCI: 06:00.0 [102               
amd8111_enable: enabling PCI: 06:00.0 [1022/7464]

PCI: 06:00.0 [1022/7464] enabled                                
amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464]

PCI: 06:00.1 [1022/7464] ops                            
amd8111_enable: enabling PCI: 06:00.1 [1022/7464]

PCI: 06:00.1 [1022/7464] enabled                                
amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463]

PCI: 06:00.2 [1022/7463] ops                            
amd8111_enable: disabling PCI: 06:00.2 [1022/7463]

PCI: 06:00.2 [1022/7463] disabled                                 
amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462]

PCI: 06:01.0 [1022/7462] ops                            
PCI: 06:01.0 [1022                 
PCI: 06:01.0 [1022/7462] disabled                                 
PCI: 06:0b.0 [1095/3114] enabled                                
PCI: 06:0c.0 [104c/8023] ops                            
PCI: 06:0c.0 [104c/8023] enabled                                
PCI: pci_scan_bus returning with max=06

scan_static_bus for PCI: 03:04.0                                
PNP: 002e.0 enabled                   
PNP: 002e.1 disabled                    
PNP: 002e.2 enabled                   
PNP: 002e.3 disabled                    
PNP: 002e.5 enabled                   
PNP: 002e.6 disabled                    
PNP: 002e.7 disabled                    
PNP: 002e.8 disabled                    
PNP: 002e.9 disabled                    
PNP: 002e.a disabled                    
PNP: 002e.b enabled                   
scan_static_bus done                    
PCI: pci_scan_bus returning with max=06

Hyper transport scan link: 2 new                              
Hypertransport scan link done                             
amdk8_scan_chains max: 6 done                             
amdk8_scan_chains max: 6 starting...                           



This looked pretty good, but I didn't know what it was trying to start.
Unfortunately the next time the same image executed (reset via power
cycle) I got this:


LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...

setting up resource map....done.                                
No connection to Node 1.                        
ht reset -


LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...
setting up resource map....done.
No connection to Node 1.
Ram1.00
Ram1.01
Ram2.00
Ram2.01
No memory for this cpu
Ram3
Initializing memory:  done
Initializing memory:
...........................................................
........................................................................
........
........................................................................
........
........................................................................
. failed

Clearing LinuxBIOS memory:  done
Ram4
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting...



Has anyone seen this issue?  Is something not getting reset?  BTW, my
own image does the same thing.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com




From YhLu at tyan.com  Wed May 12 11:57:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 12 11:57:01 2004
Subject: Dealing with Bus Master Enable
Message-ID: <3174569B9743D511922F00A0C943142305063CA0@TYANWEB>

OK for me.

YH

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?12? 9:40
???: LinuxBIOS; YhLu
??: Dealing with Bus Master Enable

YHLu,

I have a new idea about the bus master enable and
subsystem ids. We should do it with config tool.
We can add new config keywords like busmaster and
subsystem and use some generic code to enable the
bit and program the subsystems ids. Thus we can
remove a lot of codes in src/driver and mainboard/tyan.
How do you think ?

Ollie



From YhLu at tyan.com  Wed May 12 11:59:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 12 11:59:01 2004
Subject: =?gb2312?B?tPC4tDogTGVzc29ucyBsZWFybmVkIGFuZCBtb3JlID8/Pw==?=
Message-ID: <3174569B9743D511922F00A0C943142305063CA1@TYANWEB>

How about the mem install configuration?

Regards

YH

-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?12? 9:43
???: linuxbios at clustermatic.org
??: Lessons learned and more ???

Thanks everyone for your help!

It took me some time to realize the reason that I wasn't seeing any data
on the VGA console is because it doesn't work on the S2885.  But I have
my null modem connected and am seeing lots of interesting stuff now.

YH sent me a pre-built S2885 image and the FIRST time it executed I got
this:


LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting...

setting up resource map....done.                                
coherent_ht_finalize                    
done    
Ram1.00       
Ram1.01       
Ram2.00       
Ram2.01       
No memory for this cpu                      
Ram3    
Initializing memory:  done                          
Initializing memory:
...........................................................

........................................................................

........................................................................
........

........................................................................
. failed


Clearing LinuxBIOS memory:  done                                
Ram4    
Copying LinuxBIOS to ram.                         
Jumping to LinuxBIOS.                     
LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting...

Finding PCI configuration type.                               
PCI: Using configuration type 1                               
Enumerating static devices...                             
Enumerating: AMD K8 Northbridge                               
Enumerating: AMD K8 Northbridge                               
Enumerating: AMD K8 CPU                       
Enumerating: AMD K8                   
Enumerating: AMD 8111 Southbridge                                 
Enumerating: Winbond w83627hf                             
Enumerating buses...                    
amdk8_scan_root_bus                   
amdk8_scan_root_bus: start scaning pci bus

PCI: pci_scan_bus for bus 0                           
PCI: 00:18.0 [1022/1100] enabled                                
PCI: 00:18.1 [1022/1101] enabled                                
PCI: 00:18.2 [1022/1102] enabled                                
PCI: 00:18.3 [1022/1103] ops                            
PCI: 00:18.3 [1022/1103] enabled                                
PCI: 00:19.0 [ffff/ffff] enabled                                
PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring.

PCI: 00:19.1 No device operations                                 
PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h

PCI: 00:19.2 No device operations                                 
PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring.

PCI: 00:19.3 No device operations                                 
amdk8_scan_chains max: 0 starting...                                    
Hyper transport scan link: 0 max: 1                                   
PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004

HyperT reset not needed                       
PCI: pci_scan_bus for bus 1                           
PCI: 01:01.0 [1022/7454] ops                            
PCI: 01:01.0 [1022/7454] enabled                                
PCI: 01:02.0 [1022/7455] bus ops                                
PCI: 01:02.0 [1022/7455] enabled                                
PCI: pci_scan_bus for bus 2                           
PCI: 02:00.0 [10de/0333] enabled                                
PCI: pci_scan_bus returning with max=02

PCI: pci_scan_bus returning with max=02

Hyper transport scan link: 0 new max: 2

Hypertransport scan link done                             
Hyper transport scan link: 2 max: 3                                   
PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003

amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460]

PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007

HyperT reset not needed                       
PCI: pci_scan_bus for bus 3                           
PCI: 03:01.0 [1022/7450] bus ops                                
PCI: 03:01.0 [1022/7450] enabled                                
PCI: 03:01.1 [1022/7451] ops                            
PCI: 03:01.1 [1022/7451] enabl                            
PCI: 03:02.0 [1022/7450] bus ops                                
PCI: 03:02.0 [1022/7450] enabled                                
PCI: 03:02.1 [1022/7451] ops                            
PCI: 03:02.1 [1022/7451] enabled                                
amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]

PCI: 03:03.0 [1022/7460] bus ops                                
amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]

PCI: 03:03.0 [1022/7460] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468]

PCI: 03:04.0 [1022/7468] bus ops                                
amd8111_enable: enabling PCI: 03:04.0 [1022/7468]

PCI: 03:04.0 [1022/7468] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.1 [102

PCI: 03:04.1 [1022/7469] ops                            
amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469]

PCI: 03:04.1 [1022/7469] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]

amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]

PCI: 03:04.2 [1022/746a] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b]

PCI: 03:04.3 [1022/746b] ops                            
amd8111_enable: enabling PCI: 03:04.3 [1022/746b]

PCI: 03:04.3 [1022/746b] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d]

PCI: 03:04.5 [1022/746d] ops                            
amd8111_enable: enabling PCI: 03:04.5 [1022/746d]

PCI: 03:04.5 [1022/746d] enabled                                
amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e]

PCI: 03:04.6 [1022/746e] ops                            
amd8111_enable: disabling PCI: 03:04.6 [1022/746e]

PCI: 03:04.6 [1022/746e] disabled                                 
PCI: pci_scan_bus for bus 4                           
PCI: 04:09.0 [14e4/16a7] enabled                                
PCI: pci_scan_bus returning with max=04

PCI: pci_scan_bus for bus 5                           
PCI: pci_scan_bus returning with max=05

PCI: pci_scan_bus for bus 6                           
amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464]

PCI: 06:00.0 [102               
amd8111_enable: enabling PCI: 06:00.0 [1022/7464]

PCI: 06:00.0 [1022/7464] enabled                                
amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464]

PCI: 06:00.1 [1022/7464] ops                            
amd8111_enable: enabling PCI: 06:00.1 [1022/7464]

PCI: 06:00.1 [1022/7464] enabled                                
amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463]

PCI: 06:00.2 [1022/7463] ops                            
amd8111_enable: disabling PCI: 06:00.2 [1022/7463]

PCI: 06:00.2 [1022/7463] disabled                                 
amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462]

PCI: 06:01.0 [1022/7462] ops                            
PCI: 06:01.0 [1022                 
PCI: 06:01.0 [1022/7462] disabled                                 
PCI: 06:0b.0 [1095/3114] enabled                                
PCI: 06:0c.0 [104c/8023] ops                            
PCI: 06:0c.0 [104c/8023] enabled                                
PCI: pci_scan_bus returning with max=06

scan_static_bus for PCI: 03:04.0                                
PNP: 002e.0 enabled                   
PNP: 002e.1 disabled                    
PNP: 002e.2 enabled                   
PNP: 002e.3 disabled                    
PNP: 002e.5 enabled                   
PNP: 002e.6 disabled                    
PNP: 002e.7 disabled                    
PNP: 002e.8 disabled                    
PNP: 002e.9 disabled                    
PNP: 002e.a disabled                    
PNP: 002e.b enabled                   
scan_static_bus done                    
PCI: pci_scan_bus returning with max=06

Hyper transport scan link: 2 new                              
Hypertransport scan link done                             
amdk8_scan_chains max: 6 done                             
amdk8_scan_chains max: 6 starting...                           



This looked pretty good, but I didn't know what it was trying to start.
Unfortunately the next time the same image executed (reset via power
cycle) I got this:


LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...

setting up resource map....done.                                
No connection to Node 1.                        
ht reset -


LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...
setting up resource map....done.
No connection to Node 1.
Ram1.00
Ram1.01
Ram2.00
Ram2.01
No memory for this cpu
Ram3
Initializing memory:  done
Initializing memory:
...........................................................
........................................................................
........
........................................................................
........
........................................................................
. failed

Clearing LinuxBIOS memory:  done
Ram4
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting...



Has anyone seen this issue?  Is something not getting reset?  BTW, my
own image does the same thing.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com


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


From YhLu at tyan.com  Wed May 12 13:17:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 12 13:17:01 2004
Subject: flash_rom with exclude range
Message-ID: <3174569B9743D511922F00A0C943142305063CCD@TYANWEB>

Ollie,

I add exclude range feature to the Pm49FL004, and it should apply to other
chip.

But can not make getopt work with input parameter. Please check it.
I hardcode exclude_start_position to 0x60000, and exclude_end_postion to
0x8000.

Regards

YH

-------------- next part --------------
A non-text attachment was scrubbed...
Name: flash_rom.tar.bz2
Type: application/octet-stream
Size: 13588 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040512/c4c041ec/attachment.obj>

From cforney at opus.com  Wed May 12 14:34:00 2004
From: cforney at opus.com (Craig C Forney)
Date: Wed May 12 14:34:00 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <20040512155901.9543.30219.Mailman@nwn.definitive.org>
Message-ID: <009b01c43859$23235760$6400a8c0@opusone>

First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier
this week.

I've been using LinuxBIOS successfully for some custom dense board
designs being used for hardware verification, primarily running
memtest86.  I only have a serial port available.  I'm using an Arima
HDAMA board as a known working testbed for trying software before
running it on our own boards.

At this point, I'd like to attempt to boot up Linux.  The first step is
getting it to work properly on the Arima HDAMA board.  I have booted and
loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as
the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on
the Arima HDAMA board.

Using LinuxBIOS plus FILO, I'm not having much luck.  I've checked
through the archives, but I'm not finding the right combination of steps
that works.

 -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk
gets up to the point where yast has determined the proper partition
sizes during it's initial config screens, but then hangs.  It's in the
middle of the yast formatted screens, so I don't know a good way to copy
this to an email.

 -- Booting an already loaded 9.0 system panics the kernel:

		POSIX conformance testing by UNIFIX
		mtrr: v2.02 (20020716))
		CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K
(64 bytes/line/2 way)
		CPU: L2 Cache: 1024K (64 bytes/line/8 way)
		CPU0:  stepping 01
		per-CPU timeslice cutoff: 5119.55 usecs.
		task migration cache decay timeout: 10 msecs.
		Booting processor 1/1 rip 6000 page 000001000261a000
		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
eip ffffffff80204027, registers:
		CPU 0 
		Pid: 0, comm: swapper Not tainted
		RIP: 0010:[<ffffffff80204027>]{serial_in+71}
		RSP: 0018:ffffffff804dfda8  EFLAGS: 00000202
		RAX: 0000000000000000 RBX: 00000000000f4238 RCX:
0000000000008000
		RDX: 00000000000003fd RSI: 0000000000000005 RDI:
ffffffff804837a0
		RBP: ffffffff804837a0 R08: 000000000000006e R09:
00000000409fa439
		R10: 0000000000000000 R11: 0000000000000000 R12:
ffffffff80413bf4
		R13: 000000000000000d R14: 0000000000000010 R15:
0000000000000000
		FS:  0000000000000000(0000) GS:ffffffff804cb3c0(0000)
knlGS:0000000000000000
		CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
		CR2: 0000000000000000 CR3: 0000000000101000 CR4:
00000000000006e0
		Process swapper (pid: 0, stackpage=ffffffff804df000)
		Stack: ffffffff804dfda8 0000000000000018
0000000000040000 0000000000000000 
		       0000000000000000 0000000000000000
0000000000000000 0000000000000000 
  		     0000000000000000 0000000000000000 0000000000000000
0000000000000000 
		Call Trace:  <EOE>
[<ffffffff80209ff0>]{serial_console_write+96} 
 		      [<ffffffff80124fcc>]{__call_console_drivers+76}
[<ffffffff80125127>]{call_console_drivers+231} 
 		      [<ffffffff801254b2>]{release_console_sem+82}
[<ffffffff80125355>]{vprintk+357} 
 		      [<ffffffff801253fd>]{printk+141}
[<ffffffff802d164c>]{__delay+12} 
       

		Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89
d0 83 f8 
		console shuts up ...

 -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD
to the root file system on an already installed Suse 9.0 system)

		boot: hda3:/livecd/vmlinuz root=/dev/hda3
initrd=hda3:/livecd/initrd.gz console=ttyS0,115200
		Found Linux version 2.6.4-52-default (geeko at buildhost)
#1 Wed Apr 7 02:08:30 UTC 2004 bzImage.
		Loading kernel... ok
		Loading initrd... ok
		Jumping to entry point...
		Linux version 2.6.4-52-default (geeko at buildhost) (gcc
version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004
		BIOS-provided physical RAM map:
		 BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable)
		 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
		128MB vmalloc/ioremap area available.
		128MB HIGHMEM available.
		896MB LOWMEM available.
		On node 0 totalpages: 262144
		  DMA zone: 4096 pages, LIFO batch:1
		  Normal zone: 225280 pages, LIFO batch:16
		  HighMem zone: 32768 pages, LIFO batch:8
		DMI not present.
		ACPI: Unable to locate RSDP
		Built 1 zonelists
		Kernel command line: root=/dev/hda3 console=ttyS0,115200
		Initializing CPU#0
		PID hash table entries: 4096 (order 12: 32768 bytes)
		CKRM Initialized
		Detected 1403.889 MHz processor.
		Using tsc for high-res timesource
		Console: colour VGA+ 80x25
		Memory: 1009620k/1048576k available (1969k kernel code,
37972k reserved, 677k data, 212k init, 131072k highmem)
		Checking if this processor honours the WP bit even in
supervisor mode... Ok.
		Calibrating delay loop... 2760.70 BogoMIPS
		Security Scaffold v1.0.0 initialized
		SELinux:  Initializing.
		SELinux:  Starting in permissive mode
		There is already a security framework initialized,
register_security failed.
		Failure registering capabilities with the kernel
		selinux_register_security:  Registering secondary module
capability
		Capability LSM initialized
		Dentry cache hash table entries: 131072 (order: 7,
524288 bytes)
		Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
		Mount-cache hash table entries: 512 (order: 0, 4096
bytes)
		checking if image is initramfs... it is
		Freeing initrd memory: 26442k freed
		CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
		CPU: L2 Cache: 1024K (64 bytes/line)
		Intel machine check architecture supported.
		Intel machine check reporting enabled on CPU#0.
		CPU: AMD 02/05 stepping 01
		Enabling fast FPU save and restore... done.
		Enabling unmasked SIMD FPU exception support... done.
		Checking 'hlt' instruction... OK.
		POSIX conformance testing by UNIFIX
		do_initcalls
		init_elf_binfmt
		NET: Registered protocol family 16
		PCI: Using configuration type 1
		mtrr: v2.0 (20020519)
		ACPI: Subsystem revision 20040326
		ACPI: Interpreter disabled.
		Linux Plug and Play Support v0.97 (c) Adam Belay
		ACPI: ACPI tables contain no PCI IRQ routing entries
		PCI: Invalid ACPI-PCI IRQ routing table
		PCI: Probing PCI hardware
		PCI: Probing PCI hardware (bus 00)
		 ... the first call_usermodehelper: pci_bus
		CPU 0: Machine Check Exception: 0000000000000004
		Bank 4: b200000000070f0f
		Kernel panic: CPU context corrupt

So, it's pretty clear I am missing a crucial step (or two or three) to
booting Linux successfully with LinuxBIOS+FILO.  I'd appreciate some
help in identifying the basic steps.

Thanks,

Craig Forney
Opus Innovations LLC




From YhLu at tyan.com  Wed May 12 14:54:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 12 14:54:01 2004
Subject: =?gb2312?B?tPC4tDogSERBTUErRklMTyBib290aW5nIFNVU0UgTGludXg=?=
Message-ID: <3174569B9743D511922F00A0C943142305063CDC@TYANWEB>

Try add 

acpi=off

YH
-----????-----
???: Craig C Forney [mailto:cforney at opus.com] 
????: 2004?5?12? 12:42
???: linuxbios at clustermatic.org
??: HDAMA+FILO booting SUSE Linux


First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier
this week.

I've been using LinuxBIOS successfully for some custom dense board
designs being used for hardware verification, primarily running
memtest86.  I only have a serial port available.  I'm using an Arima
HDAMA board as a known working testbed for trying software before
running it on our own boards.

At this point, I'd like to attempt to boot up Linux.  The first step is
getting it to work properly on the Arima HDAMA board.  I have booted and
loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as
the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on
the Arima HDAMA board.

Using LinuxBIOS plus FILO, I'm not having much luck.  I've checked
through the archives, but I'm not finding the right combination of steps
that works.

 -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk
gets up to the point where yast has determined the proper partition
sizes during it's initial config screens, but then hangs.  It's in the
middle of the yast formatted screens, so I don't know a good way to copy
this to an email.

 -- Booting an already loaded 9.0 system panics the kernel:

		POSIX conformance testing by UNIFIX
		mtrr: v2.02 (20020716))
		CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K
(64 bytes/line/2 way)
		CPU: L2 Cache: 1024K (64 bytes/line/8 way)
		CPU0:  stepping 01
		per-CPU timeslice cutoff: 5119.55 usecs.
		task migration cache decay timeout: 10 msecs.
		Booting processor 1/1 rip 6000 page 000001000261a000
		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
eip ffffffff80204027, registers:
		CPU 0 
		Pid: 0, comm: swapper Not tainted
		RIP: 0010:[<ffffffff80204027>]{serial_in+71}
		RSP: 0018:ffffffff804dfda8  EFLAGS: 00000202
		RAX: 0000000000000000 RBX: 00000000000f4238 RCX:
0000000000008000
		RDX: 00000000000003fd RSI: 0000000000000005 RDI:
ffffffff804837a0
		RBP: ffffffff804837a0 R08: 000000000000006e R09:
00000000409fa439
		R10: 0000000000000000 R11: 0000000000000000 R12:
ffffffff80413bf4
		R13: 000000000000000d R14: 0000000000000010 R15:
0000000000000000
		FS:  0000000000000000(0000) GS:ffffffff804cb3c0(0000)
knlGS:0000000000000000
		CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
		CR2: 0000000000000000 CR3: 0000000000101000 CR4:
00000000000006e0
		Process swapper (pid: 0, stackpage=ffffffff804df000)
		Stack: ffffffff804dfda8 0000000000000018
0000000000040000 0000000000000000 
		       0000000000000000 0000000000000000
0000000000000000 0000000000000000 
  		     0000000000000000 0000000000000000 0000000000000000
0000000000000000 
		Call Trace:  <EOE>
[<ffffffff80209ff0>]{serial_console_write+96} 
 		      [<ffffffff80124fcc>]{__call_console_drivers+76}
[<ffffffff80125127>]{call_console_drivers+231} 
 		      [<ffffffff801254b2>]{release_console_sem+82}
[<ffffffff80125355>]{vprintk+357} 
 		      [<ffffffff801253fd>]{printk+141}
[<ffffffff802d164c>]{__delay+12} 
       

		Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89
d0 83 f8 
		console shuts up ...

 -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD
to the root file system on an already installed Suse 9.0 system)

		boot: hda3:/livecd/vmlinuz root=/dev/hda3
initrd=hda3:/livecd/initrd.gz console=ttyS0,115200
		Found Linux version 2.6.4-52-default (geeko at buildhost)
#1 Wed Apr 7 02:08:30 UTC 2004 bzImage.
		Loading kernel... ok
		Loading initrd... ok
		Jumping to entry point...
		Linux version 2.6.4-52-default (geeko at buildhost) (gcc
version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004
		BIOS-provided physical RAM map:
		 BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable)
		 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
		128MB vmalloc/ioremap area available.
		128MB HIGHMEM available.
		896MB LOWMEM available.
		On node 0 totalpages: 262144
		  DMA zone: 4096 pages, LIFO batch:1
		  Normal zone: 225280 pages, LIFO batch:16
		  HighMem zone: 32768 pages, LIFO batch:8
		DMI not present.
		ACPI: Unable to locate RSDP
		Built 1 zonelists
		Kernel command line: root=/dev/hda3 console=ttyS0,115200
		Initializing CPU#0
		PID hash table entries: 4096 (order 12: 32768 bytes)
		CKRM Initialized
		Detected 1403.889 MHz processor.
		Using tsc for high-res timesource
		Console: colour VGA+ 80x25
		Memory: 1009620k/1048576k available (1969k kernel code,
37972k reserved, 677k data, 212k init, 131072k highmem)
		Checking if this processor honours the WP bit even in
supervisor mode... Ok.
		Calibrating delay loop... 2760.70 BogoMIPS
		Security Scaffold v1.0.0 initialized
		SELinux:  Initializing.
		SELinux:  Starting in permissive mode
		There is already a security framework initialized,
register_security failed.
		Failure registering capabilities with the kernel
		selinux_register_security:  Registering secondary module
capability
		Capability LSM initialized
		Dentry cache hash table entries: 131072 (order: 7,
524288 bytes)
		Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
		Mount-cache hash table entries: 512 (order: 0, 4096
bytes)
		checking if image is initramfs... it is
		Freeing initrd memory: 26442k freed
		CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
		CPU: L2 Cache: 1024K (64 bytes/line)
		Intel machine check architecture supported.
		Intel machine check reporting enabled on CPU#0.
		CPU: AMD 02/05 stepping 01
		Enabling fast FPU save and restore... done.
		Enabling unmasked SIMD FPU exception support... done.
		Checking 'hlt' instruction... OK.
		POSIX conformance testing by UNIFIX
		do_initcalls
		init_elf_binfmt
		NET: Registered protocol family 16
		PCI: Using configuration type 1
		mtrr: v2.0 (20020519)
		ACPI: Subsystem revision 20040326
		ACPI: Interpreter disabled.
		Linux Plug and Play Support v0.97 (c) Adam Belay
		ACPI: ACPI tables contain no PCI IRQ routing entries
		PCI: Invalid ACPI-PCI IRQ routing table
		PCI: Probing PCI hardware
		PCI: Probing PCI hardware (bus 00)
		 ... the first call_usermodehelper: pci_bus
		CPU 0: Machine Check Exception: 0000000000000004
		Bank 4: b200000000070f0f
		Kernel panic: CPU context corrupt

So, it's pretty clear I am missing a crucial step (or two or three) to
booting Linux successfully with LinuxBIOS+FILO.  I'd appreciate some
help in identifying the basic steps.

Thanks,

Craig Forney
Opus Innovations LLC


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


From jmiller at actuality-systems.com  Wed May 12 15:03:01 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Wed May 12 15:03:01 2004
Subject: S2885 Uni-processor image
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1163A0@mail.local.ActualitySystems.com>

My S2885 board is only uni-processor, so I modified the follow options:

option CONFIG_MAX_CPUS=1
option CONFIG_LOGICAL_CPUS=0
option CONFIG_MAX_PHYSICAL_CPUS=1

But the static.c that is generated still enumerates two CPUs.  What else
do I need to do to force uni-processor?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From rminnich at lanl.gov  Wed May 12 15:13:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May 12 15:13:01 2004
Subject: S2885 Uni-processor image
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1163A0@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405121430410.8407-100000@maxroach.lanl.gov>

On Wed, 12 May 2004, Jay Miller wrote:

> My S2885 board is only uni-processor, so I modified the follow options:
> 
> option CONFIG_MAX_CPUS=1
> option CONFIG_LOGICAL_CPUS=0
> option CONFIG_MAX_PHYSICAL_CPUS=1
> 
> But the static.c that is generated still enumerates two CPUs.  What else
> do I need to do to force uni-processor?
> 

It should not matter. I would be happier if you left it at 2 and we 
made it work with 1.

ron



From YhLu at tyan.com  Wed May 12 15:21:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 12 15:21:01 2004
Subject: =?gb2312?B?tPC4tDogUzI4ODUgVW5pLXByb2Nlc3NvciBpbWFnZQ==?=
Message-ID: <3174569B9743D511922F00A0C943142305063CE0@TYANWEB>

auto.c

and 

mainboard.c


-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?12? 13:19
???: linuxbios at clustermatic.org
??: S2885 Uni-processor image

My S2885 board is only uni-processor, so I modified the follow options:

option CONFIG_MAX_CPUS=1
option CONFIG_LOGICAL_CPUS=0
option CONFIG_MAX_PHYSICAL_CPUS=1

But the static.c that is generated still enumerates two CPUs.  What else
do I need to do to force uni-processor?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



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


From dwh at lanl.gov  Wed May 12 15:54:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May 12 15:54:01 2004
Subject: Lessons learned and more ???
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F116375@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405121508120.26068-100000@ccs-mail.lanl.gov>

On a side note, what's going on with your memory? It should not fail to 
initialize. Maybe try removing each DIMM to see if one is bad?

On Wed, 12 May 2004, Jay Miller wrote:

> Thanks everyone for your help!
> 
> It took me some time to realize the reason that I wasn't seeing any data
> on the VGA console is because it doesn't work on the S2885.  But I have
> my null modem connected and am seeing lots of interesting stuff now.
> 
> YH sent me a pre-built S2885 image and the FIRST time it executed I got
> this:
> 
> 
> LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting...
> 
> setting up resource map....done.                                
> coherent_ht_finalize                    
> done    
> Ram1.00       
> Ram1.01       
> Ram2.00       
> Ram2.01       
> No memory for this cpu                      
> Ram3    
> Initializing memory:  done                          
> Initializing memory:
> ...........................................................
> 
> ........................................................................
> 
> ........................................................................
> ........
> 
> ........................................................................
> . failed
> 
> 
> Clearing LinuxBIOS memory:  done                                
> Ram4    
> Copying LinuxBIOS to ram.                         
> Jumping to LinuxBIOS.                     
> LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting...
> 
> Finding PCI configuration type.                               
> PCI: Using configuration type 1                               
> Enumerating static devices...                             
> Enumerating: AMD K8 Northbridge                               
> Enumerating: AMD K8 Northbridge                               
> Enumerating: AMD K8 CPU                       
> Enumerating: AMD K8                   
> Enumerating: AMD 8111 Southbridge                                 
> Enumerating: Winbond w83627hf                             
> Enumerating buses...                    
> amdk8_scan_root_bus                   
> amdk8_scan_root_bus: start scaning pci bus
> 
> PCI: pci_scan_bus for bus 0                           
> PCI: 00:18.0 [1022/1100] enabled                                
> PCI: 00:18.1 [1022/1101] enabled                                
> PCI: 00:18.2 [1022/1102] enabled                                
> PCI: 00:18.3 [1022/1103] ops                            
> PCI: 00:18.3 [1022/1103] enabled                                
> PCI: 00:19.0 [ffff/ffff] enabled                                
> PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring.
> 
> PCI: 00:19.1 No device operations                                 
> PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h
> 
> PCI: 00:19.2 No device operations                                 
> PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring.
> 
> PCI: 00:19.3 No device operations                                 
> amdk8_scan_chains max: 0 starting...                                    
> Hyper transport scan link: 0 max: 1                                   
> PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004
> 
> HyperT reset not needed                       
> PCI: pci_scan_bus for bus 1                           
> PCI: 01:01.0 [1022/7454] ops                            
> PCI: 01:01.0 [1022/7454] enabled                                
> PCI: 01:02.0 [1022/7455] bus ops                                
> PCI: 01:02.0 [1022/7455] enabled                                
> PCI: pci_scan_bus for bus 2                           
> PCI: 02:00.0 [10de/0333] enabled                                
> PCI: pci_scan_bus returning with max=02
> 
> PCI: pci_scan_bus returning with max=02
> 
> Hyper transport scan link: 0 new max: 2
> 
> Hypertransport scan link done                             
> Hyper transport scan link: 2 max: 3                                   
> PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003
> 
> amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460]
> 
> PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007
> 
> HyperT reset not needed                       
> PCI: pci_scan_bus for bus 3                           
> PCI: 03:01.0 [1022/7450] bus ops                                
> PCI: 03:01.0 [1022/7450] enabled                                
> PCI: 03:01.1 [1022/7451] ops                            
> PCI: 03:01.1 [1022/7451] enabl                            
> PCI: 03:02.0 [1022/7450] bus ops                                
> PCI: 03:02.0 [1022/7450] enabled                                
> PCI: 03:02.1 [1022/7451] ops                            
> PCI: 03:02.1 [1022/7451] enabled                                
> amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]
> 
> PCI: 03:03.0 [1022/7460] bus ops                                
> amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460]
> 
> PCI: 03:03.0 [1022/7460] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468]
> 
> PCI: 03:04.0 [1022/7468] bus ops                                
> amd8111_enable: enabling PCI: 03:04.0 [1022/7468]
> 
> PCI: 03:04.0 [1022/7468] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.1 [102
> 
> PCI: 03:04.1 [1022/7469] ops                            
> amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469]
> 
> PCI: 03:04.1 [1022/7469] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]
> 
> amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a]
> 
> PCI: 03:04.2 [1022/746a] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b]
> 
> PCI: 03:04.3 [1022/746b] ops                            
> amd8111_enable: enabling PCI: 03:04.3 [1022/746b]
> 
> PCI: 03:04.3 [1022/746b] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d]
> 
> PCI: 03:04.5 [1022/746d] ops                            
> amd8111_enable: enabling PCI: 03:04.5 [1022/746d]
> 
> PCI: 03:04.5 [1022/746d] enabled                                
> amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e]
> 
> PCI: 03:04.6 [1022/746e] ops                            
> amd8111_enable: disabling PCI: 03:04.6 [1022/746e]
> 
> PCI: 03:04.6 [1022/746e] disabled                                 
> PCI: pci_scan_bus for bus 4                           
> PCI: 04:09.0 [14e4/16a7] enabled                                
> PCI: pci_scan_bus returning with max=04
> 
> PCI: pci_scan_bus for bus 5                           
> PCI: pci_scan_bus returning with max=05
> 
> PCI: pci_scan_bus for bus 6                           
> amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464]
> 
> PCI: 06:00.0 [102               
> amd8111_enable: enabling PCI: 06:00.0 [1022/7464]
> 
> PCI: 06:00.0 [1022/7464] enabled                                
> amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464]
> 
> PCI: 06:00.1 [1022/7464] ops                            
> amd8111_enable: enabling PCI: 06:00.1 [1022/7464]
> 
> PCI: 06:00.1 [1022/7464] enabled                                
> amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463]
> 
> PCI: 06:00.2 [1022/7463] ops                            
> amd8111_enable: disabling PCI: 06:00.2 [1022/7463]
> 
> PCI: 06:00.2 [1022/7463] disabled                                 
> amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462]
> 
> PCI: 06:01.0 [1022/7462] ops                            
> PCI: 06:01.0 [1022                 
> PCI: 06:01.0 [1022/7462] disabled                                 
> PCI: 06:0b.0 [1095/3114] enabled                                
> PCI: 06:0c.0 [104c/8023] ops                            
> PCI: 06:0c.0 [104c/8023] enabled                                
> PCI: pci_scan_bus returning with max=06
> 
> scan_static_bus for PCI: 03:04.0                                
> PNP: 002e.0 enabled                   
> PNP: 002e.1 disabled                    
> PNP: 002e.2 enabled                   
> PNP: 002e.3 disabled                    
> PNP: 002e.5 enabled                   
> PNP: 002e.6 disabled                    
> PNP: 002e.7 disabled                    
> PNP: 002e.8 disabled                    
> PNP: 002e.9 disabled                    
> PNP: 002e.a disabled                    
> PNP: 002e.b enabled                   
> scan_static_bus done                    
> PCI: pci_scan_bus returning with max=06
> 
> Hyper transport scan link: 2 new                              
> Hypertransport scan link done                             
> amdk8_scan_chains max: 6 done                             
> amdk8_scan_chains max: 6 starting...                           
> 
> 
> 
> This looked pretty good, but I didn't know what it was trying to start.
> Unfortunately the next time the same image executed (reset via power
> cycle) I got this:
> 
> 
> LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...
> 
> setting up resource map....done.                                
> No connection to Node 1.                        
> ht reset -
> 
> 
> LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting...
> setting up resource map....done.
> No connection to Node 1.
> Ram1.00
> Ram1.01
> Ram2.00
> Ram2.01
> No memory for this cpu
> Ram3
> Initializing memory:  done
> Initializing memory:
> ...........................................................
> ........................................................................
> ........
> ........................................................................
> ........
> ........................................................................
> . failed
> 
> Clearing LinuxBIOS memory:  done
> Ram4
> Copying LinuxBIOS to ram.
> Jumping to LinuxBIOS.
> LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting...
> 
> 
> 
> Has anyone seen this issue?  Is something not getting reset?  BTW, my
> own image does the same thing.
> 
> Thanks,
> 
> Jay Miller
> Actuality Systems, Inc.
> jmiller at acutality-systems.com
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From jbors at mail.ru  Wed May 12 17:11:01 2004
From: jbors at mail.ru (=?koi8-r?Q?=22?=Dmitry Borisov=?koi8-r?Q?=22=20?=)
Date: Wed May 12 17:11:01 2004
Subject: Epia-M + Linuxbios
In-Reply-To: <Pine.SUN.4.58.0405121446381.18577@eskimo.com>
Message-ID: <E1BO2DU-000LwY-00.jbors-mail-ru@f21.mail.ru>


-----Original Message-----
From: Jerome Ibanes <jibanes at eskimo.com>
> 
> Hi, I'd like to get LinuxBios on some Epia boards, and I have a couple of
> questions about that:

Dear Jerome,
Please use this link to find your answers:

http://www.google.com/search?as_q=+Linuxbios&num=10&hl=en&btnG=Google+Search&as_epq=Epia+M+&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_nlo=&as_nhi=&as_occt=any&as_dt=i&as_sitesearch=www.clustermatic.org&safe=images

Dmitry/


From cforney at opus.com  Thu May 13 02:37:00 2004
From: cforney at opus.com (Craig C Forney)
Date: Thu May 13 02:37:00 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <3174569B9743D511922F00A0C943142305063CDC@TYANWEB>
Message-ID: <000801c438bf$98411e90$6400a8c0@opusone>

YH,

Thanks for the tip, but I had already tried all the failsafe options,
and I was still having trouble booting.

I stumbled upon a solution, and can now boot Suse Linux 9.0 from
HDAMA+LINUXBIOS+FILO only using a serial connection.  Using
LINUXBIOS+FILO, I booted the 9.0 Suse CD and ran the repair function on
the 9.0 system on the hard drive (which has always booted just fine
under the HDAMA Phoenix BIOS).  Somehow, I assume the reconfiguring must
have changed some dependencies on the Pheonix BIOS, thus allowing
LinuxBIOS to boot properly.  I had to make a few changes to the /etc/rc
files (remove the keyboard startup), and I was able to get it to boot up
completely into init state 3.

So, I'm still struggling with trying to load off of the Suse 9.0
Distribution DVD.  I'd really like to be able to load a complete system
from scratch using the serial port.  It seems awfully close (the repair
worked fine ... even the update sems to work).

If anyone out there has been successful loading a disk using a standard
distribution (I'm not that particular about which distribution), I'd
like to hear about it.  Alternatively, if there is a reasonable way to
make a custom distribution that would work, I'd appreciate any advice.

Thanks,

Craig Forney
Opus Innovations LLC




> -----Original Message-----
> From: YhLu [mailto:YhLu at tyan.com] 
> Sent: Wednesday, May 12, 2004 1:23 PM
> To: cforney at opus.com; linuxbios at clustermatic.org
> Subject: ??: HDAMA+FILO booting SUSE Linux
> 
> 
> Try add 
> 
> acpi=off
> 
> YH
> -----????-----
> ???: Craig C Forney [mailto:cforney at opus.com] 
> ????: 2004?5?12? 12:42
> ???: linuxbios at clustermatic.org
> ??: HDAMA+FILO booting SUSE Linux
> 
> 
> First, thanks for fixing the broken sourceforge LinuxBIOS 
> tree earlier this week.
> 
> I've been using LinuxBIOS successfully for some custom dense 
> board designs being used for hardware verification, primarily 
> running memtest86.  I only have a serial port available.  I'm 
> using an Arima HDAMA board as a known working testbed for 
> trying software before running it on our own boards.
> 
> At this point, I'd like to attempt to boot up Linux.  The 
> first step is getting it to work properly on the Arima HDAMA 
> board.  I have booted and loaded Suse 9.0 Professional (I'm 
> awaiting delivery of 9.1), as well as the Suse 9.1 Live CD, 
> without problems with the standard Phoenix BIOS on the Arima 
> HDAMA board.
> 
> Using LinuxBIOS plus FILO, I'm not having much luck.  I've 
> checked through the archives, but I'm not finding the right 
> combination of steps that works.
> 
>  -- Booting of the Suse 9.0 DVD in an attempt to install 
> Linux on disk gets up to the point where yast has determined 
> the proper partition sizes during it's initial config 
> screens, but then hangs.  It's in the middle of the yast 
> formatted screens, so I don't know a good way to copy this to 
> an email.
> 
>  -- Booting an already loaded 9.0 system panics the kernel:
> 
> 		POSIX conformance testing by UNIFIX
> 		mtrr: v2.02 (20020716))
> 		CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K
> (64 bytes/line/2 way)
> 		CPU: L2 Cache: 1024K (64 bytes/line/8 way)
> 		CPU0:  stepping 01
> 		per-CPU timeslice cutoff: 5119.55 usecs.
> 		task migration cache decay timeout: 10 msecs.
> 		Booting processor 1/1 rip 6000 page 000001000261a000
> 		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
> eip ffffffff80204027, registers:
> 		CPU 0 
> 		Pid: 0, comm: swapper Not tainted
> 		RIP: 0010:[<ffffffff80204027>]{serial_in+71}
> 		RSP: 0018:ffffffff804dfda8  EFLAGS: 00000202
> 		RAX: 0000000000000000 RBX: 00000000000f4238 
> RCX: 0000000000008000
> 		RDX: 00000000000003fd RSI: 0000000000000005 
> RDI: ffffffff804837a0
> 		RBP: ffffffff804837a0 R08: 000000000000006e 
> R09: 00000000409fa439
> 		R10: 0000000000000000 R11: 0000000000000000 
> R12: ffffffff80413bf4
> 		R13: 000000000000000d R14: 0000000000000010 
> R15: 0000000000000000
> 		FS:  0000000000000000(0000) 
> GS:ffffffff804cb3c0(0000) knlGS:0000000000000000
> 		CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> 		CR2: 0000000000000000 CR3: 0000000000101000 
> CR4: 00000000000006e0
> 		Process swapper (pid: 0, stackpage=ffffffff804df000)
> 		Stack: ffffffff804dfda8 0000000000000018
> 0000000000040000 0000000000000000 
> 		       0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 
>   		     0000000000000000 0000000000000000 
> 0000000000000000 0000000000000000 
> 		Call Trace:  <EOE> 
> [<ffffffff80209ff0>]{serial_console_write+96} 
>  		      [<ffffffff80124fcc>]{__call_console_drivers+76}
> [<ffffffff80125127>]{call_console_drivers+231} 
>  		      [<ffffffff801254b2>]{release_console_sem+82}
> [<ffffffff80125355>]{vprintk+357} 
>  		      [<ffffffff801253fd>]{printk+141} 
> [<ffffffff802d164c>]{__delay+12} 
>        
> 
> 		Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89
> d0 83 f8 
> 		console shuts up ...
> 
>  -- Booting the Suse 9.1 Live CD (I copied all the files on 
> the Live CD to the root file system on an already installed 
> Suse 9.0 system)
> 
> 		boot: hda3:/livecd/vmlinuz root=/dev/hda3 
> initrd=hda3:/livecd/initrd.gz console=ttyS0,115200
> 		Found Linux version 2.6.4-52-default (geeko at buildhost)
> #1 Wed Apr 7 02:08:30 UTC 2004 bzImage.
> 		Loading kernel... ok
> 		Loading initrd... ok
> 		Jumping to entry point...
> 		Linux version 2.6.4-52-default (geeko at buildhost) (gcc
> version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004
> 		BIOS-provided physical RAM map:
> 		 BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable)
> 		 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
> 		128MB vmalloc/ioremap area available.
> 		128MB HIGHMEM available.
> 		896MB LOWMEM available.
> 		On node 0 totalpages: 262144
> 		  DMA zone: 4096 pages, LIFO batch:1
> 		  Normal zone: 225280 pages, LIFO batch:16
> 		  HighMem zone: 32768 pages, LIFO batch:8
> 		DMI not present.
> 		ACPI: Unable to locate RSDP
> 		Built 1 zonelists
> 		Kernel command line: root=/dev/hda3 console=ttyS0,115200
> 		Initializing CPU#0
> 		PID hash table entries: 4096 (order 12: 32768 bytes)
> 		CKRM Initialized
> 		Detected 1403.889 MHz processor.
> 		Using tsc for high-res timesource
> 		Console: colour VGA+ 80x25
> 		Memory: 1009620k/1048576k available (1969k 
> kernel code, 37972k reserved, 677k data, 212k init, 131072k highmem)
> 		Checking if this processor honours the WP bit 
> even in supervisor mode... Ok.
> 		Calibrating delay loop... 2760.70 BogoMIPS
> 		Security Scaffold v1.0.0 initialized
> 		SELinux:  Initializing.
> 		SELinux:  Starting in permissive mode
> 		There is already a security framework 
> initialized, register_security failed.
> 		Failure registering capabilities with the kernel
> 		selinux_register_security:  Registering 
> secondary module capability
> 		Capability LSM initialized
> 		Dentry cache hash table entries: 131072 (order: 7,
> 524288 bytes)
> 		Inode-cache hash table entries: 65536 (order: 6, 262144
> bytes)
> 		Mount-cache hash table entries: 512 (order: 0, 4096
> bytes)
> 		checking if image is initramfs... it is
> 		Freeing initrd memory: 26442k freed
> 		CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
> bytes/line)
> 		CPU: L2 Cache: 1024K (64 bytes/line)
> 		Intel machine check architecture supported.
> 		Intel machine check reporting enabled on CPU#0.
> 		CPU: AMD 02/05 stepping 01
> 		Enabling fast FPU save and restore... done.
> 		Enabling unmasked SIMD FPU exception support... done.
> 		Checking 'hlt' instruction... OK.
> 		POSIX conformance testing by UNIFIX
> 		do_initcalls
> 		init_elf_binfmt
> 		NET: Registered protocol family 16
> 		PCI: Using configuration type 1
> 		mtrr: v2.0 (20020519)
> 		ACPI: Subsystem revision 20040326
> 		ACPI: Interpreter disabled.
> 		Linux Plug and Play Support v0.97 (c) Adam Belay
> 		ACPI: ACPI tables contain no PCI IRQ routing entries
> 		PCI: Invalid ACPI-PCI IRQ routing table
> 		PCI: Probing PCI hardware
> 		PCI: Probing PCI hardware (bus 00)
> 		 ... the first call_usermodehelper: pci_bus
> 		CPU 0: Machine Check Exception: 0000000000000004
> 		Bank 4: b200000000070f0f
> 		Kernel panic: CPU context corrupt
> 
> So, it's pretty clear I am missing a crucial step (or two or 
> three) to booting Linux successfully with LinuxBIOS+FILO.  
> I'd appreciate some help in identifying the basic steps.
> 
> Thanks,
> 
> Craig Forney
> Opus Innovations LLC
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org 
> http://www.clustermatic.org/mailman/listinfo/l> inuxbios
> 
> 




From stepan at openbios.org  Thu May 13 03:23:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May 13 03:23:01 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <000801c438bf$98411e90$6400a8c0@opusone>
References: <3174569B9743D511922F00A0C943142305063CDC@TYANWEB> <000801c438bf$98411e90$6400a8c0@opusone>
Message-ID: <20040513084234.GA20217@openbios.org>

* Craig C Forney <cforney at opus.com> [040513 09:54]:
> LinuxBIOS to boot properly.  I had to make a few changes to the /etc/rc
> files (remove the keyboard startup), and I was able to get it to boot up
> completely into init state 3.
 
This stuff should probably be fixed in LinuxBIOS. 

> So, I'm still struggling with trying to load off of the Suse 9.0
> Distribution DVD.  I'd really like to be able to load a complete system
> from scratch using the serial port.  It seems awfully close (the repair
> worked fine ... even the update sems to work).

Hm. I was successful installing SUSE 9 on an AMD64 system (Solo) using
filo and I described some stuff here:
   http://www.openbios.org/linuxbioswiki/Filo_2bAMD64

One thing that might be worth trying is to disable the nmi watchdog and
machine check exceptions via linux kernel boot parameters, ie with
     nmi_watchdog=0 nomce 
and probably 
     acpi=off

> > 		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
[..]
> > 		CPU 0: Machine Check Exception: 0000000000000004
> > 		Bank 4: b200000000070f0f
> > 		Kernel panic: CPU context corrupt

   Stefan




From mdeschamps at mangrove-systems.com  Thu May 13 05:18:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Thu May 13 05:18:00 2004
Subject: About EPIA-M Frambuffer + VGA on V2 status
Message-ID: <1084444413.9074.55.camel@Calliphara>

Hi,

Acutally , I've LinuxBios IDE_BOOT onto hard drive. All this is
fascinating. I'am so excited :)
Ok , ok i've got a "unknown file system"  : i've got ext3 root partition
on it, couldn't Linuxbios boot ext3 part just by now ? If true want
option should I add ?

I've seen this about framebuffer and VGA on epia-M:
http://www.clustermatic.org/pipermail/linuxbios/2004-March/006817.html
http://www.clustermatic.org/pipermail/linuxbios/2004-April/007494.html
humm i'd love to see tux sitting on the corner of my screen...

Dmitry or Ron may I ask you if you could send me the HOWTO that you were
talking about ?

Is it already operationnal ? What type of option does/will it requiere
to get set in Config ?
I need also these info this because I'am coding a sort linuxbios command
center script.
It lets user choose between IDE HARD BOOT or CF BOOT or ETHER BOOT and
so on, and automatically add options, configure stuffs and lauches makes
logs strings, and point errors or dangereous warnings at the user. It
also  gather video.bios and flashes the whole into a specified target
(for now ROM chip). What do you think of this ?

Thanks. 
mathieu




From rminnich at lanl.gov  Thu May 13 08:41:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 08:41:01 2004
Subject: About EPIA-M Frambuffer + VGA on V2 status
In-Reply-To: <1084444413.9074.55.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405130758500.17352-100000@maxroach.lanl.gov>

I'm not going to get too look at -M for another 10 days.

But we'd like to get that up under V2 with graphics. Also I have no docs 
from VIA yet.

ron



From kfuchs at winternet.com  Thu May 13 08:48:01 2004
From: kfuchs at winternet.com (Ken Fuchs)
Date: Thu May 13 08:48:01 2004
Subject: Anyone using LinuxBIOS for hardware verification?
Message-ID: <200405131406.i4DE6f1t024236@tundra.winternet.com>

LinuxBIOS would seem to be an excellent tool for hardware
verification, since it gets extremely close to the hardware and it is
GPL licensed ...

Please respond with your comments concerning hardware verification
whether LinuxBIOS related or not.

There are several places where hardware verification could be executed:

1) The verification code could be an optional part of LinuxBIOS itself
   to test hardware immediately after (or during) hardware
   initialization.

2) It could also be a LinuxBIOS payload (a stand-alone hardware
   verification program).

3) It could be integrated into the Linux kernel (loaded by LinuxBIOS)
   that finishes hardware initialization.

4) It could be a suite of user programs that are started by the
   initial (and only) Linux kernel via /sbin/init or user initiated.

5) It could be 3 above, except relative to a second Linux kernel
   (loaded via the initial Linux kernel).

6) It could be 4 above, except relative to a second Linux kernel
   (loaded via the initial Linux kernel).

Points 5 and 6 are not directly LinuxBIOS related, but are probably
the most common types of open source hardware verification code that
is available.

Any information regarding open (even closed) source hardware
verification programs or code is welcome.  Please respond via the list 
(or private e-mail if you prefer -  I will summarize all private
responses via the list, unless requested otherwise).

Sincerely,

Ken Fuchs <kfuchs at winternet.com>


From dwh at lanl.gov  Thu May 13 09:54:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 13 09:54:00 2004
Subject: Pm49FL004 on Tyan Tiger AMD 76x chipset (fwd)
Message-ID: <Pine.LNX.4.44.0405130909320.26068-100000@ccs-mail.lanl.gov>

Has anyone flash a ROM on a Tyan Tiger mainboard?

---------- Forwarded message ----------
Date: Thu, 13 May 2004 10:05:51 -0500
From: Donald Zoch <donald.zoch at amd.com>
To: Hendricks David W. <dwh at lanl.gov>
Cc: Donald Zoch <donald.zoch at amd.com>, rminnich at lanl.gov, ollie at lanl.gov
Subject: Re: Pm49FL004 on Tyan Tiger AMD 76x chipset

Ok.  Much appreciated.       

On Thu, May 13, 2004 at 09:03:45AM -0600, Hendricks David W. wrote:
> We do not have any Tyan Tiger boards on our workbench. However if you'd 
> like I can forward your request to the LinuxBIOS mailing list. We have a 
> friend working at Tyan who I am very confident will be able to respond to 
> this issue.
> 
> On Thu, 13 May 2004, Donald Zoch wrote:
> 
> > Could any of you pass on any hints about how to get a Pm49FL004
> > detected in an AMD Athlon based Tyan Tiger board?   The same chip
> > flashes with flash_rom flawlessly in the K8W.  
> 
Donald
----
Donald Zoch                    
Phone: (512) 602-7945
Pager: (512) 604-5401
donald.zoch at amd.com                 



From jmiller at actuality-systems.com  Thu May 13 10:19:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Thu May 13 10:19:00 2004
Subject: Making payloads
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1163DA@mail.local.ActualitySystems.com>

The reason why my S2885 image wasn't working is because my system only
has 1 CPU populated.  A little tweaking to remove the second processor
and I can get FILO to come up. Unfortunately FILO does not detect the
IDE disk.

I noticed in the payloads section of Config.lb there are some multi-part
payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.

How do I create the multi-part payloads?  Ideally I would be interested
in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
payload that will load my kernel over the network.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From mdeschamps at mangrove-systems.com  Thu May 13 10:26:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Thu May 13 10:26:00 2004
Subject: About EPIA-M Frambuffer + VGA on V2 status
In-Reply-To: <Pine.LNX.4.44.0405130758500.17352-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405130758500.17352-100000@maxroach.lanl.gov>
Message-ID: <1084462900.9074.78.camel@Calliphara>

Le jeu 13/05/2004 ? 15:59, ron minnich a ?crit :
> I'm not going to get too look at -M for another 10 days.
> 
> But we'd like to get that up under V2 with graphics. Also I have no docs 
> from VIA yet.
> 
> ron
> 
> 
hum i see ... but didn't we got native LinuxBIOS VGA up on EPIA-M  ? As
I read along mailist , I have believed it has been done, both vga bios
and VGA LB native , so what kind of info should we need more ? Indeed we
do need some more otherwise I wouldn't ask for a little:)

I should drawback to do it vga bios way ... need to push 1x0000 LB base
start so i can put 64k video bios from 0xc000 to 1xc000. Is that right ?
Do it need to use ALDO or/and BOCH ?  Sorry for the mess i feel i do but
i'am getting lost. As said in mails, i thought there were a guide on
this subject or at least some few docs written by goodwill LB people 
..snif.. i'll keep trying. 

any clarification are welcome .
 
mathieu.


From rminnich at lanl.gov  Thu May 13 10:31:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 10:31:01 2004
Subject: About EPIA-M Frambuffer + VGA on V2 status
In-Reply-To: <1084462900.9074.78.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405130946460.17756-100000@maxroach.lanl.gov>

On 13 May 2004, Mathieu Deschamps wrote:

> hum i see ... but didn't we got native LinuxBIOS VGA up on EPIA-M  ? 

on V1 not V2. It works fine on V1. But ram detection on V1 is not working. 
You only get one size ram.

> I should drawback to do it vga bios way ... need to push 1x0000 LB base
> start so i can put 64k video bios from 0xc000 to 1xc000. Is that right ?
> Do it need to use ALDO or/and BOCH ?  Sorry for the mess i feel i do but
> i'am getting lost. As said in mails, i thought there were a guide on
> this subject or at least some few docs written by goodwill LB people
> ..snif.. i'll keep trying.

you need to get a vga bios image. Once you have that I can send you the 
V1 config we used for -M

ron



From dwh at lanl.gov  Thu May 13 11:03:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 13 11:03:01 2004
Subject: Making payloads
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1163DA@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405130959030.26068-100000@ccs-mail.lanl.gov>

Oops, I forgot to mention Stefan's patch for FILO to make IDE work on the 
S2885. I think this is the one: 
http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html

On Thu, 13 May 2004, Jay Miller wrote:

> The reason why my S2885 image wasn't working is because my system only
> has 1 CPU populated.  A little tweaking to remove the second processor
> and I can get FILO to come up. Unfortunately FILO does not detect the
> IDE disk.
> 
> I noticed in the payloads section of Config.lb there are some multi-part
> payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.
> 
> How do I create the multi-part payloads?  Ideally I would be interested
> in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
> payload that will load my kernel over the network.
> 
> Thanks,
> 
> Jay Miller
> Actuality Systems, Inc.
> jmiller at acutality-systems.com
> 
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From rminnich at lanl.gov  Thu May 13 11:10:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 11:10:01 2004
Subject: Making payloads
In-Reply-To: <Pine.LNX.4.44.0405130959030.26068-100000@ccs-mail.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405131028020.17756-100000@maxroach.lanl.gov>

On Thu, 13 May 2004, Hendricks David W. wrote:

> Oops, I forgot to mention Stefan's patch for FILO to make IDE work on the 
> S2885. I think this is the one: 
> http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html

can we get this put back into filo?

ron



From dwh at lanl.gov  Thu May 13 11:18:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 13 11:18:00 2004
Subject: Making payloads
In-Reply-To: <Pine.LNX.4.44.0405131028020.17756-100000@maxroach.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405131035250.26068-100000@ccs-mail.lanl.gov>

I think Sone had mentioned it, but was too busy at the time.

On Thu, 13 May 2004, ron minnich wrote:

> On Thu, 13 May 2004, Hendricks David W. wrote:
> 
> > Oops, I forgot to mention Stefan's patch for FILO to make IDE work on the 
> > S2885. I think this is the one: 
> > http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html
> 
> can we get this put back into filo?
> 
> ron
> 



From YhLu at tyan.com  Thu May 13 11:25:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 11:25:01 2004
Subject: =?gb2312?B?tPC4tDogUG00OUZMMDA0IG9uIFR5YW4gVGlnZXIgQU1EIDc2eCBj?=
	=?gb2312?B?aGlwc2V0IChmd2Qp?=
Message-ID: <3174569B9743D511922F00A0C943142305063D64@TYANWEB>

I guess that amd 756 is needed to be enabled to access bios area.

Please try to add ids for it to the same as amd8111.
{0x1022, PCI_DEVICE_ID_AMD_VIPER_7410, "AMD766", enable_flash_amd8111}
{0x1022, PCI_DEVICE_ID_AMD_VIPER_7440, "AMD766", enable_flash_amd8111}
{0x1022, 0x7468, "AMD8111", enable_flash_amd8111},



Regards

YH
-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?13? 8:12
???: linuxbios at clustermatic.org
??: donald.zoch at amd.com
??: Re: Pm49FL004 on Tyan Tiger AMD 76x chipset (fwd)

Has anyone flash a ROM on a Tyan Tiger mainboard?

---------- Forwarded message ----------
Date: Thu, 13 May 2004 10:05:51 -0500
From: Donald Zoch <donald.zoch at amd.com>
To: Hendricks David W. <dwh at lanl.gov>
Cc: Donald Zoch <donald.zoch at amd.com>, rminnich at lanl.gov, ollie at lanl.gov
Subject: Re: Pm49FL004 on Tyan Tiger AMD 76x chipset

Ok.  Much appreciated.       

On Thu, May 13, 2004 at 09:03:45AM -0600, Hendricks David W. wrote:
> We do not have any Tyan Tiger boards on our workbench. However if you'd 
> like I can forward your request to the LinuxBIOS mailing list. We have a 
> friend working at Tyan who I am very confident will be able to respond to 
> this issue.
> 
> On Thu, 13 May 2004, Donald Zoch wrote:
> 
> > Could any of you pass on any hints about how to get a Pm49FL004
> > detected in an AMD Athlon based Tyan Tiger board?   The same chip
> > flashes with flash_rom flawlessly in the K8W.  
> 
Donald
----
Donald Zoch                    
Phone: (512) 602-7945
Pager: (512) 604-5401
donald.zoch at amd.com                 

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


From YhLu at tyan.com  Thu May 13 11:36:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 11:36:00 2004
Subject: =?gb2312?B?tPC4tDogTWFraW5nIHBheWxvYWRz?=
Message-ID: <3174569B9743D511922F00A0C943142305063D71@TYANWEB>

Jay,

I have merged into FILO into Etherboot. You can get that patch from
Etherboot group.  So you can build tg3--filo.zelf. About the PCI scan in
Etherboot has no problem to find IDE other than bus 0.

Current it already supports serial IDE and normal IDE.

I'm working on add usb boot into FILO in Etherboot. The AMD8111 is using
OHCI, and I'm trying to make use steven code for USB boot, but it is only
support UHCI.
OHCI has hardware support for ED (QH) instead of SW QH.

Maybe I need to get UHCI addon card at first.

Please let me know if you has problem to get filo patch. And I would send
you my tar ball about filo in Etherboot.

Regards

YH


-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?13? 8:36
???: linuxbios at clustermatic.org
??: Making payloads

The reason why my S2885 image wasn't working is because my system only
has 1 CPU populated.  A little tweaking to remove the second processor
and I can get FILO to come up. Unfortunately FILO does not detect the
IDE disk.

I noticed in the payloads section of Config.lb there are some multi-part
payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.

How do I create the multi-part payloads?  Ideally I would be interested
in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
payload that will load my kernel over the network.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



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


From YhLu at tyan.com  Thu May 13 11:38:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 11:38:00 2004
Subject: =?gb2312?B?tPC4tDogTWFraW5nIHBheWxvYWRz?=
Message-ID: <3174569B9743D511922F00A0C943142305063D75@TYANWEB>

The problem is in FILO it only scan bus 0.

For s2885, need force it scan bus 3. for the amd8111 ide is in 3:4.1

Other Opteron MB, need to scan bus 1, for the amd8111 ide is in 1:4.1

Regards

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?13? 9:28
???: Hendricks David W.
??: Jay Miller; linuxbios at clustermatic.org
??: Re: Making payloads

On Thu, 13 May 2004, Hendricks David W. wrote:

> Oops, I forgot to mention Stefan's patch for FILO to make IDE work on the 
> S2885. I think this is the one: 
> http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html

can we get this put back into filo?

ron

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


From YhLu at tyan.com  Thu May 13 11:46:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 11:46:00 2004
Subject: About EPIA-M Frambuffer + VGA on V2 status
Message-ID: <3174569B9743D511922F00A0C943142305063D7B@TYANWEB>

>It lets user choose between IDE HARD BOOT or CF BOOT or ETHER BOOT and
>so on, and automatically add options, configure stuffs and lauches makes
>logs strings, and point errors or dangereous warnings at the user. It
>also  gather video.bios and flashes the whole into a specified target
>(for now ROM chip). What do you think of this ?

Use FILO in Etherboot, and you
1. Control Boot sequence by CMOS setting.
2. input option after "boot:"

Regards

YH


From rminnich at lanl.gov  Thu May 13 11:47:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 11:47:00 2004
Subject: Fix for multiple superios of same type
Message-ID: <Pine.LNX.4.44.0405131104410.17756-100000@maxroach.lanl.gov>

I just committed the fix Richard Smith needed.

ron



From YhLu at tyan.com  Thu May 13 11:53:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 11:53:00 2004
Subject: =?gb2312?B?tPC4tDogTWFraW5nIHBheWxvYWRz?=
Message-ID: <3174569B9743D511922F00A0C943142305063D7D@TYANWEB>

http://sourceforge.net/tracker/index.php?func=detail&aid=943300&group_id=423
3&atid=304233

-----????-----
???: YhLu 
????: 2004?5?13? 10:05
???: Jay Miller; linuxbios at clustermatic.org
??: ??: Making payloads

Jay,

I have merged into FILO into Etherboot. You can get that patch from
Etherboot group.  So you can build tg3--filo.zelf. About the PCI scan in
Etherboot has no problem to find IDE other than bus 0.

Current it already supports serial IDE and normal IDE.

I'm working on add usb boot into FILO in Etherboot. The AMD8111 is using
OHCI, and I'm trying to make use steven code for USB boot, but it is only
support UHCI.
OHCI has hardware support for ED (QH) instead of SW QH.

Maybe I need to get UHCI addon card at first.

Please let me know if you has problem to get filo patch. And I would send
you my tar ball about filo in Etherboot.

Regards

YH


-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?13? 8:36
???: linuxbios at clustermatic.org
??: Making payloads

The reason why my S2885 image wasn't working is because my system only
has 1 CPU populated.  A little tweaking to remove the second processor
and I can get FILO to come up. Unfortunately FILO does not detect the
IDE disk.

I noticed in the payloads section of Config.lb there are some multi-part
payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.

How do I create the multi-part payloads?  Ideally I would be interested
in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
payload that will load my kernel over the network.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



_______________________________________________
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


From YhLu at tyan.com  Thu May 13 12:05:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 12:05:00 2004
Subject: =?gb2312?B?tPC4tDogSERBTUErRklMTyBib290aW5nIFNVU0UgTGludXg=?=
Message-ID: <3174569B9743D511922F00A0C943142305063D81@TYANWEB>

Are you using Suse 9 pro for AMD64 or for i386?

I guess you are using for i386. 

YH

-----????-----
???: Stefan Reinauer [mailto:stepan at openbios.org] 
????: 2004?5?13? 1:43
???: Craig C Forney
??: YhLu; linuxbios at clustermatic.org
??: Re: HDAMA+FILO booting SUSE Linux

* Craig C Forney <cforney at opus.com> [040513 09:54]:
> LinuxBIOS to boot properly.  I had to make a few changes to the /etc/rc
> files (remove the keyboard startup), and I was able to get it to boot up
> completely into init state 3.
 
This stuff should probably be fixed in LinuxBIOS. 

> So, I'm still struggling with trying to load off of the Suse 9.0
> Distribution DVD.  I'd really like to be able to load a complete system
> from scratch using the serial port.  It seems awfully close (the repair
> worked fine ... even the update sems to work).

Hm. I was successful installing SUSE 9 on an AMD64 system (Solo) using
filo and I described some stuff here:
   http://www.openbios.org/linuxbioswiki/Filo_2bAMD64

One thing that might be worth trying is to disable the nmi watchdog and
machine check exceptions via linux kernel boot parameters, ie with
     nmi_watchdog=0 nomce 
and probably 
     acpi=off

> > 		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
[..]
> > 		CPU 0: Machine Check Exception: 0000000000000004
> > 		Bank 4: b200000000070f0f
> > 		Kernel panic: CPU context corrupt

   Stefan



From jmiller at actuality-systems.com  Thu May 13 12:08:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Thu May 13 12:08:00 2004
Subject: S2885 Uni-processor image
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1163EA@mail.local.ActualitySystems.com>

The changes I'm making are just part of my learning process, and I don't
intend to submit them for inclusion.

I'm waiting on a custom embedded board that has a lot of the same pieces
as the Tyan board (that's why I got one to play with).  Are there any
embedded systems in the tree?

Also, once I get fully up to speed let me know if I can help in anyway.
I believe in giving back, so if I can write a newbie HOWTO or something,
let me know.

Jay

-----Original Message-----
From: ron minnich [mailto:rminnich at lanl.gov] 
Sent: Wednesday, May 12, 2004 4:31 PM
To: Jay Miller
Cc: linuxbios at clustermatic.org
Subject: Re: S2885 Uni-processor image

On Wed, 12 May 2004, Jay Miller wrote:

> My S2885 board is only uni-processor, so I modified the follow
options:
> 
> option CONFIG_MAX_CPUS=1
> option CONFIG_LOGICAL_CPUS=0
> option CONFIG_MAX_PHYSICAL_CPUS=1
> 
> But the static.c that is generated still enumerates two CPUs.  What
else
> do I need to do to force uni-processor?
> 

It should not matter. I would be happier if you left it at 2 and we 
made it work with 1.

ron





From rminnich at lanl.gov  Thu May 13 12:12:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 12:12:01 2004
Subject: S2885 Uni-processor image
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1163EA@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405131129320.17756-100000@maxroach.lanl.gov>

On Thu, 13 May 2004, Jay Miller wrote:

> Also, once I get fully up to speed let me know if I can help in anyway.
> I believe in giving back, so if I can write a newbie HOWTO or something,
> let me know.

we always love these ... :-)

ron



From YhLu at tyan.com  Thu May 13 12:23:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 12:23:01 2004
Subject: flash_rom with exclude range
Message-ID: <3174569B9743D511922F00A0C943142305063D86@TYANWEB>

David,

Can you check the code?

Ollie is on vocation?

Regards

YH

-----????-----
???: YhLu 
????: 2004?5?12? 11:46
???: Li-Ta Lo; LinuxBIOS
??: flash_rom with exclude range

Ollie,

I add exclude range feature to the Pm49FL004, and it should apply to other
chip.

But can not make getopt work with input parameter. Please check it.
I hardcode exclude_start_position to 0x60000, and exclude_end_postion to
0x8000.

Regards

YH


-------------- next part --------------
A non-text attachment was scrubbed...
Name: flash_rom.tar.bz2
Type: application/octet-stream
Size: 13588 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040513/94dbe6e1/attachment.obj>

From ollie at lanl.gov  Thu May 13 13:13:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 13 13:13:01 2004
Subject: flash_rom with exclude range
In-Reply-To: <3174569B9743D511922F00A0C943142305063D86@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063D86@TYANWEB>
Message-ID: <1084473082.26760.5.camel@exponential.lanl.gov>

On Thu, 2004-05-13 at 11:51, YhLu wrote:
> David,
> 
> Can you check the code?
> 
> Ollie is on vocation?
> 


I am busy doing the VGA/AGP stuff and we are going to LCI conference
next week. I don't have time to reveiw the patch yet.

Ollie




From dwh at lanl.gov  Thu May 13 13:25:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 13 13:25:00 2004
Subject: flash_rom with exclude range
In-Reply-To: <3174569B9743D511922F00A0C943142305063D86@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405131236100.26068-100000@ccs-mail.lanl.gov>

The attachment didn't go through. I'm recieving errors when 
decompressing it. Is 5c9827677b8ae1b8d5098d073a6d6758 the correct md5sum? 
I'd be happy to look at it, though I'm just a lowly student.  

PS. Don't forget that you can commit on Sourceforge now :)

On Thu, 13 May 2004, YhLu wrote:

> David,
> 
> Can you check the code?
> 
> Ollie is on vocation?
> 
> Regards
> 
> YH
> 
> -----????????-----
> ??????: YhLu 
> ????????: 2004??5??12?? 11:46
> ??????: Li-Ta Lo; LinuxBIOS
> ????: flash_rom with exclude range
> 
> Ollie,
> 
> I add exclude range feature to the Pm49FL004, and it should apply to other
> chip.
> 
> But can not make getopt work with input parameter. Please check it.
> I hardcode exclude_start_position to 0x60000, and exclude_end_postion to
> 0x8000.
> 
> Regards
> 
> YH
> 
> 
> 



From johnl at blurbco.com  Thu May 13 13:31:01 2004
From: johnl at blurbco.com (John Laur)
Date: Thu May 13 13:31:01 2004
Subject: EPIA-M startup times
In-Reply-To: <BAY10-F119gIjOiwsN300005a20@hotmail.com>
Message-ID: <003e01c4391a$896e80f0$8000a8c0@debbie>

If you have VGA correctly working with LinuxBIOS (Ie you see the
linuxbios logo on startup), then you have VGA working as best it does
with LinuxBIOS.

Then you can worry about the kernel. VESA Framebuffer does not work with
EPIA-M as the VGA bios doesn't initialize the video card up to where
vesafb can take over. You have to use viafb (part of the -epia patchset)
to get video on the console. Make sure you have it compiled into the
kernel and not as a module. Make sure vesafb is NOT compiled in either,
otherwise you'll need some commandline trickery to make it work. Also,
viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
are using that. I have not tested with kernel 2.6.

John

> -----Original Message-----
> From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> admin at clustermatic.org] On Behalf Of M. Renee Hopkins
> Sent: Thursday, May 06, 2004 4:58 PM
> To: jbors at mail.ru; Linuxbios at clustermatic.org
> Subject: RE: EPIA-M startup times
> 
> OK, I finally timed my ME-6000.  It takes about 20 seconds to get to
the
> init scripts.  Even though I have the framebuffer support compiled
into
> 2.6.4, the kernel doesn't ever see the vesafb device.  Although the
same
> kernel sees it from award bios boot.
> 
> I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.
> 
> Is it possible something isn't set right in filo or LB?  I have
> 
> option HAVE_FRAMEBUFFER=1 in linuxbios config.
> 
> Any help is appreciated.  Thanks to all who contributed.
> 
> M.R.
> 
> >From: "Dmitry Borisov" <jbors at mail.ru>
> >To: <Linuxbios at clustermatic.org>
> >Subject: EPIA-M startup times
> >Date: Mon, 26 Apr 2004 19:34:00 -0700
> >
> >Guys,
> >Just wanted to have your estimate about startup times for EPIA-M
mobo.
> >ATM it takes about 9 secs to go to payload. 7 secs to go to splash.
Which
> >seems to be really high values.
> >Does anyone can say what it would be if everything is "perfect" ?
> >How much time at minimum the BIOS can take assuming RAM, VGA and PCI
> >initialized properly ?
> >
> >If the answer would be 4 secs in ideal case, I'll invest some time to
> >tighten it up... If 9 secs is a minimum, then...
> >
> >Any suggestions ?
> >Dmitry/
> 
> _________________________________________________________________
> Check out the coupons and bargains on MSN Offers!
> http://youroffers.msn.com
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios



From YhLu at tyan.com  Thu May 13 13:56:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 13:56:01 2004
Subject: =?utf-8?B?562U5aSNOiBmbGFzaF9yb20gd2l0aCBleGNsdWRlIHJhbmdl?=
Message-ID: <3174569B9743D511922F00A0C943142305063DAA@TYANWEB>

Try this one.

There still is parameter input problem, I don't want to check it in. 

Regards

YH

-----????-----
???: Hendricks David W. [mailto:dwh at lanl.gov] 
????: 2004?5?13? 11:43
???: YhLu
??: Li-Ta Lo; LinuxBIOS
??: Re: flash_rom with exclude range

The attachment didn't go through. I'm recieving errors when 
decompressing it. Is 5c9827677b8ae1b8d5098d073a6d6758 the correct md5sum? 
I'd be happy to look at it, though I'm just a lowly student.  

PS. Don't forget that you can commit on Sourceforge now :)

On Thu, 13 May 2004, YhLu wrote:

> David,
> 
> Can you check the code?
> 
> Ollie is on vocation?
> 
> Regards
> 
> YH
> 
> -----????????-----
> ??????: YhLu 
> ????????: 2004??5??12?? 11:46
> ??????: Li-Ta Lo; LinuxBIOS
> ????: flash_rom with exclude range
> 
> Ollie,
> 
> I add exclude range feature to the Pm49FL004, and it should apply to other
> chip.
> 
> But can not make getopt work with input parameter. Please check it.
> I hardcode exclude_start_position to 0x60000, and exclude_end_postion to
> 0x8000.
> 
> Regards
> 
> YH
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: flash_rom.src.tar.bz2
Type: application/octet-stream
Size: 13650 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040513/671cbd07/attachment.obj>

From jmiller at actuality-systems.com  Thu May 13 14:32:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Thu May 13 14:32:00 2004
Subject: Making payloads
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1163FD@mail.local.ActualitySystems.com>

I built tg3--filo.zelf with the latest patch from the link in your message.

Getting the follow error message when loading:

Loading Etherboot version: 5.2.4
Dropping non PT_LOAD segment
New segment addr 0x20000 size 0x4aef5 offset 0xb0 filesize 0xa4b7
(cleaned up) New segment addr 0x20000 size 0x4aef5 offset 0xb0 filesize 0xa4b7
Loading Segment: addr: 0x000000001ffadfe8 memsz: 0x000000000001b00c filesz: 0x00
0000000000a4b7
Clearing Segment: addr: 0x000000001ffb849f memsz: 0x0000000000010b55
Loading Segment: addr: 0x000000000003b00c memsz: 0x000000000002fee9 filesz: 0x00
00000000000000
    39:stream_skip() - overflowed source buffer
ERROR: Skip of 68437 bytes skiped 23193 bytes
Cannot Load ELF Image

What am I doing wrong?

-J

-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, May 13, 2004 1:22 PM
To: Jay Miller; linuxbios at clustermatic.org
Subject: ??: Making payloads

http://sourceforge.net/tracker/index.php?func=detail&aid=943300&group_id=423
3&atid=304233

-----????-----
???: YhLu 
????: 2004?5?13? 10:05
???: Jay Miller; linuxbios at clustermatic.org
??: ??: Making payloads

Jay,

I have merged into FILO into Etherboot. You can get that patch from
Etherboot group.  So you can build tg3--filo.zelf. About the PCI scan in
Etherboot has no problem to find IDE other than bus 0.

Current it already supports serial IDE and normal IDE.

I'm working on add usb boot into FILO in Etherboot. The AMD8111 is using
OHCI, and I'm trying to make use steven code for USB boot, but it is only
support UHCI.
OHCI has hardware support for ED (QH) instead of SW QH.

Maybe I need to get UHCI addon card at first.

Please let me know if you has problem to get filo patch. And I would send
you my tar ball about filo in Etherboot.

Regards

YH


-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?13? 8:36
???: linuxbios at clustermatic.org
??: Making payloads

The reason why my S2885 image wasn't working is because my system only
has 1 CPU populated.  A little tweaking to remove the second processor
and I can get FILO to come up. Unfortunately FILO does not detect the
IDE disk.

I noticed in the payloads section of Config.lb there are some multi-part
payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.

How do I create the multi-part payloads?  Ideally I would be interested
in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
payload that will load my kernel over the network.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



_______________________________________________
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




From YhLu at tyan.com  Thu May 13 14:42:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 14:42:00 2004
Subject: =?gb2312?B?tPC4tDogTWFraW5nIHBheWxvYWRz?=
Message-ID: <3174569B9743D511922F00A0C943142305063DAC@TYANWEB>

Increase HEAP SIZE.

YH

-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?13? 12:49
???: YhLu; linuxbios at clustermatic.org
??: RE: Making payloads

I built tg3--filo.zelf with the latest patch from the link in your message.

Getting the follow error message when loading:

Loading Etherboot version: 5.2.4
Dropping non PT_LOAD segment
New segment addr 0x20000 size 0x4aef5 offset 0xb0 filesize 0xa4b7
(cleaned up) New segment addr 0x20000 size 0x4aef5 offset 0xb0 filesize
0xa4b7
Loading Segment: addr: 0x000000001ffadfe8 memsz: 0x000000000001b00c filesz:
0x00
0000000000a4b7
Clearing Segment: addr: 0x000000001ffb849f memsz: 0x0000000000010b55
Loading Segment: addr: 0x000000000003b00c memsz: 0x000000000002fee9 filesz:
0x00
00000000000000
    39:stream_skip() - overflowed source buffer
ERROR: Skip of 68437 bytes skiped 23193 bytes
Cannot Load ELF Image

What am I doing wrong?

-J

-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, May 13, 2004 1:22 PM
To: Jay Miller; linuxbios at clustermatic.org
Subject: ??: Making payloads

http://sourceforge.net/tracker/index.php?func=detail&aid=943300&group_id=423
3&atid=304233

-----????-----
???: YhLu 
????: 2004?5?13? 10:05
???: Jay Miller; linuxbios at clustermatic.org
??: ??: Making payloads

Jay,

I have merged into FILO into Etherboot. You can get that patch from
Etherboot group.  So you can build tg3--filo.zelf. About the PCI scan in
Etherboot has no problem to find IDE other than bus 0.

Current it already supports serial IDE and normal IDE.

I'm working on add usb boot into FILO in Etherboot. The AMD8111 is using
OHCI, and I'm trying to make use steven code for USB boot, but it is only
support UHCI.
OHCI has hardware support for ED (QH) instead of SW QH.

Maybe I need to get UHCI addon card at first.

Please let me know if you has problem to get filo patch. And I would send
you my tar ball about filo in Etherboot.

Regards

YH


-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?13? 8:36
???: linuxbios at clustermatic.org
??: Making payloads

The reason why my S2885 image wasn't working is because my system only
has 1 CPU populated.  A little tweaking to remove the second processor
and I can get FILO to come up. Unfortunately FILO does not detect the
IDE disk.

I noticed in the payloads section of Config.lb there are some multi-part
payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf.

How do I create the multi-part payloads?  Ideally I would be interested
in a FILO that recognizes IDE.  Alternatively I am also pursuing a tg3
payload that will load my kernel over the network.

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com



_______________________________________________
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




From rminnich at lanl.gov  Thu May 13 14:45:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 14:45:00 2004
Subject: flash_rom with exclude range
In-Reply-To: <Pine.LNX.4.44.0405131236100.26068-100000@ccs-mail.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405131402540.17756-100000@maxroach.lanl.gov>

On Thu, 13 May 2004, Hendricks David W. wrote:

> PS. Don't forget that you can commit on Sourceforge now :)

yeah but we should have a few more eyes on it BEFORE commit. 

thanks


ron



From nacho at estudio-verona.com  Thu May 13 15:10:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Thu May 13 15:10:01 2004
Subject: EPIA-M startup times
In-Reply-To: <003e01c4391a$896e80f0$8000a8c0@debbie>
References: <003e01c4391a$896e80f0$8000a8c0@debbie>
Message-ID: <200405132228.21514.nacho@estudio-verona.com>

20 sec to init scripts?? Isn't it very high times? I though using linuxbios I 
could get faster boot times...

El Jueves, 13 de Mayo de 2004 18:46, John Laur escribi?:
> If you have VGA correctly working with LinuxBIOS (Ie you see the
> linuxbios logo on startup), then you have VGA working as best it does
> with LinuxBIOS.
>
> Then you can worry about the kernel. VESA Framebuffer does not work with
> EPIA-M as the VGA bios doesn't initialize the video card up to where
> vesafb can take over. You have to use viafb (part of the -epia patchset)
> to get video on the console. Make sure you have it compiled into the
> kernel and not as a module. Make sure vesafb is NOT compiled in either,
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.
>
> John
>
> > -----Original Message-----
> > From: linuxbios-admin at clustermatic.org [mailto:linuxbios-
> > admin at clustermatic.org] On Behalf Of M. Renee Hopkins
> > Sent: Thursday, May 06, 2004 4:58 PM
> > To: jbors at mail.ru; Linuxbios at clustermatic.org
> > Subject: RE: EPIA-M startup times
> >
> > OK, I finally timed my ME-6000.  It takes about 20 seconds to get to
>
> the
>
> > init scripts.  Even though I have the framebuffer support compiled
>
> into
>
> > 2.6.4, the kernel doesn't ever see the vesafb device.  Although the
>
> same
>
> > kernel sees it from award bios boot.
> >
> > I'm using Linuxbios V1, cvs 050504, filo 4.1, 2.6.4 with patches.
> >
> > Is it possible something isn't set right in filo or LB?  I have
> >
> > option HAVE_FRAMEBUFFER=1 in linuxbios config.
> >
> > Any help is appreciated.  Thanks to all who contributed.
> >
> > M.R.
> >
> > >From: "Dmitry Borisov" <jbors at mail.ru>
> > >To: <Linuxbios at clustermatic.org>
> > >Subject: EPIA-M startup times
> > >Date: Mon, 26 Apr 2004 19:34:00 -0700
> > >
> > >Guys,
> > >Just wanted to have your estimate about startup times for EPIA-M
>
> mobo.
>
> > >ATM it takes about 9 secs to go to payload. 7 secs to go to splash.
>
> Which
>
> > >seems to be really high values.
> > >Does anyone can say what it would be if everything is "perfect" ?
> > >How much time at minimum the BIOS can take assuming RAM, VGA and PCI
> > >initialized properly ?
> > >
> > >If the answer would be 4 secs in ideal case, I'll invest some time to
> > >tighten it up... If 9 secs is a minimum, then...
> > >
> > >Any suggestions ?
> > >Dmitry/
> >
> > _________________________________________________________________
> > Check out the coupons and bargains on MSN Offers!
> > http://youroffers.msn.com
> >
> > _______________________________________________
> > 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


From rminnich at lanl.gov  Thu May 13 15:56:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 13 15:56:00 2004
Subject: EPIA-M startup times
In-Reply-To: <200405132228.21514.nacho@estudio-verona.com>
Message-ID: <Pine.LNX.4.44.0405131514220.17756-100000@maxroach.lanl.gov>

On Thu, 13 May 2004, Ignacio Verona wrote:

> 20 sec to init scripts?? Isn't it very high times? I though using linuxbios I 
> could get faster boot times...

It is higher than I would like. I wonder what the delay is.

ron



From backblue at netcabo.pt  Thu May 13 16:14:01 2004
From: backblue at netcabo.pt (backblue)
Date: Thu May 13 16:14:01 2004
Subject: Develop && WinXP
Message-ID: <20040512223539.34a89574@fork.ketic.com>

I would like to use linuxbios but it's not able to any of my (about) 15 motherboards i have at home :(((, what does i need to get suport to them, and where did i start reading? :)

Does LinuxBios boots windowsXP?

Tks


From YhLu at tyan.com  Thu May 13 17:58:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 17:58:01 2004
Subject: USB boot
Message-ID: <3174569B9743D511922F00A0C943142305063DD7@TYANWEB>

Steven,

I switch to S4882, because it has via USB chip. And it is UHCI. 

Also I got some output. It shows 
Product: USB Flash Drive
Serial: 070B01001340CA0

Can you send me some debug output message to let me figure out which is
right or not?

Regards

YH


LinuxBIOS-1.1.62.0_Fallback Thu May 13 15:11:33 PDT 2004 starting...
LinuxBIOS-1.1.62.0_Fallback Thu May 13 15:47:33 PDT 2004 booting...
Finding PCI configuration type.
Enumerating static devices...
Enumerating buses...
done
Allocating resources...ERROR: PNP: 002e.b 70 not allocated
done.
Enabling resourcess...
done.
Initializing devices...
set power on after power fail
Devices initialized
totalram: 16128M
Initializing CPU #0
Enabling cache...done.
Setting up local apic...done.
CPU #0 Initialized
Initializing CPU #1
Enabling cache...done.
Initializing CPU #2
Enabling cache...done.
Initializing CPU #3
Waiting for 4 CPUS to stop
Enabling cache...done.
Setting up local apic...done.
CPU #1 Initialized
Waiting for 3 CPUS to stop
Setting up local apic...done.
CPU #2 Initialized
Waiting for 2 CPUS to stop
Setting up local apic...done.
CPU #3 Initialized
Checking IRQ routing tables...
/home/yhlu/xx/xx/freebios2/src/arch/i386/boot/pirq_routing.c:
41:check_pirq_routing_table() - checksum is: 0x9a but should be: 0x5b
done.
Copying IRQ routing tables to 0xf0000...done.
Verifing copy of IRQ routing tables at 0xf0000...done

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

Loading Etherboot version: 5.2.4
ROM segment 0x0000 length 0x0000 reloc 0x00020000
CPU 2285 Mhz
Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO]
Relocating _text from: [0002d2a0,0008e8d0) to [efe9e9d0,eff00000)
Probing pci nic...
[tg3-5704]Ethernet addr: 00:E0:81:61:8C:27
Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit)
<abort>
Probing pci nic...
[tg3-5704]Ethernet addr: 00:E0:81:61:8C:28
Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
<abort>
Probing pci nic...
Probing pci disk...
[FILO]FILO version 0.4.1 (root at tst2723-rh9) Thu May 13 15:47:25 PDT 2004
Press <Enter> for default boot, or <Esc> for boot prompt... timed out
boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
LinuxLabs USB bootloader
raw frame_list is at 00078560
frame_list is at 00078630
frame_list_link: addr: 00077570
frame_list_link:  raw addr: efef5f40
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 0006f500
raw frame_list is at 0007a560
frame_list is at 0007a630
frame_list_link: addr: 00077590
frame_list_link:  raw addr: efef5f60
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 0006f540
raw frame_list is at 0007c560
frame_list is at 0007c630
frame_list_link: addr: 000775b0
frame_list_link:  raw addr: efef5f80
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 0006f580
raw frame_list is at 0007e560
frame_list is at 0007e630
frame_list_link: addr: 000775d0
frame_list_link:  raw addr: efef5fa0
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 0006f5c0
Found OHCI at 0d181630
Resetting OHCI
USB HC reset_hc usb-0d181630: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef7000
Starting OHCI
Found OHCI at 0d182630
Resetting OHCI
USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef9000
Starting OHCI
Found UHCI at 00002400
Resetting UHCI
uhc_init setting framelist to: efefb000
Starting UHCI
HCI at 00002400
Found UHCI at 00002420
Resetting UHCI
uhc_init setting framelist to: efefd000
Starting UHCI
HCI at 00002420
poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100poll_usb1 i=2
poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00001493
poll_u_root_hub2 v=00001493poll_u_root_hub21 v=00001493    Connection on
port 00002412
New USB device, setting address 00000003
Fetching device descriptor length
Fetching device descriptor
Fetching config descriptor length
Fetching config descriptor
device:
bLength: 00000012
type: 00000001
bcdVersion: 0000000200000000
Class: 00000000
SubClass: 00000000
protocol: 00000000
max_packet: 00000040
idVendor: 00001005
idProduct: 0000b113
bcdDeviceVersion: 0000000100000000
iManufacturor: 00000000
iProduct: 00000001
iSerial: 00000002
bNumConfig: 00000001
config:
bLength: 00000009
type: 00000002
wTotalLength: 00000020
bNumInterfaces: 00000001
bConfigurationValue: 00000001
iConfiguration: 00000000
bmAttributes: 00000080
bMaxPower: 000000fa

Interface(00081057):
        bLength: 00000009
        type: 00000004
        bInterfaceNumber: 00000000
        bAlternateSetting: 00000000
        bNumEndpoints: 00000002
        bInterfaceClass: 00000008
        bInterfaceSubClass: 00000006
        bInterfaceProtocol: 00000050
        iInterface: 00000000

        Endpoint (00081060):
                bLength: 00000007
                type: 00000005
                bEndpointAddress: 00000081
                bmAttributes: 00000002
                wMaxPacketSize: 00000040
                bInterval: 00000000

        Endpoint (00081067):
                bLength: 00000007
                type: 00000005
                bEndpointAddress: 00000002
                bmAttributes: 00000002
                wMaxPacketSize: 00000040
                bInterval: 00000000
Selecting Configuration number 00000001:
clear stall on ep=00000081
clear stall on ep=00000002
00000008:00000006:00000050
Manufacturor: unknown
Product: USB Flash Drive
Serial: 070B01001340CA0
Mass storage, bulk only SCSI transparent
Requesting initial sense data
sense data
:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
000000:00000000:00000000:00000000:00000000:00000000:00000000

code = 00000000 key = 00000000

Info: 00000000
536870913 536870912 byte blocks
ll_read_block returns 512
0: boot=00000000, start=00000000 length=00000000
1: boot=00000000, start=00000000 length=00000000
2: boot=00000000, start=00000000 length=00000000
3: boot=00000000, start=00000000 length=00000000
DEVICE CONFIGURED
poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
poll_usb1 i=0   poll_o_root_hub1 v=00000100    poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00000100     poll_usb1 i=1   poll_o_root_hub1 v=00000100
poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100     poll_usb1
i=2   poll_u_root_hub1 v=00000480    poll_u_root_hub1 v=00000495
poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
Found USB block device 3
bulk_transfer( dev= 00000003, ep = 00000081, len = 0b8a0000, buffer =
000810ac) = 2048:short transaction:
short_transaction:TD(0006f600):
short_transaction:type: IN
short_transaction:retries: 00000000
short_transaction:active: 00000000
short_transaction:device_addr: 00000003
short_transaction:endpoint: 00000001
short_transaction:data_toggle: 00000001
short_transaction:max_transfer: 0000003f
short_transaction:actual: 000007ff
short_transaction:link:
short_transaction:STALL
        short_transaction:addr: 0006f620
        short_transaction: raw addr: efeedff0
        short_transaction:terminate: 00000000
        short_transaction:queue: 00000000
        short_transaction:depth: 00000001


From pyro at linuxlabs.com  Thu May 13 21:31:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Thu May 13 21:31:01 2004
Subject: USB boot
In-Reply-To: <3174569B9743D511922F00A0C943142305063DD7@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063DD7@TYANWEB>
Message-ID: <Pine.LNX.4.58.0405140241090.26413@ucontrol.mobiledns.com>

Greetings,

I'll see if I can dig up the old debugging captures, I may still have
them.

The enumeration of the USB bus looks good. The problems seem to start
with:
536870913 536870912 byte blocks
ll_read_block returns 512
0: boot=00000000, start=00000000 length=00000000
1: boot=00000000, start=00000000 length=00000000
2: boot=00000000, start=00000000 length=00000000
3: boot=00000000, start=00000000 length=00000000

GEt capacity returned a VERY unreasonable result :-)

The read of the partition block seems to have actually read the block.
Does the drive have a partition table on it?

If not, try putting one on it and trying the boot so we can see if it
actually read the block correctly or if the data went to the wrong place.

G'day,
sjames



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


On Thu, 13 May 2004, YhLu wrote:

> Steven,
>
> I switch to S4882, because it has via USB chip. And it is UHCI.
>
> Also I got some output. It shows
> Product: USB Flash Drive
> Serial: 070B01001340CA0
>
> Can you send me some debug output message to let me figure out which is
> right or not?
>
> Regards
>
> YH
>
>
> LinuxBIOS-1.1.62.0_Fallback Thu May 13 15:11:33 PDT 2004 starting...
> LinuxBIOS-1.1.62.0_Fallback Thu May 13 15:47:33 PDT 2004 booting...
> Finding PCI configuration type.
> Enumerating static devices...
> Enumerating buses...
> done
> Allocating resources...ERROR: PNP: 002e.b 70 not allocated
> done.
> Enabling resourcess...
> done.
> Initializing devices...
> set power on after power fail
> Devices initialized
> totalram: 16128M
> Initializing CPU #0
> Enabling cache...done.
> Setting up local apic...done.
> CPU #0 Initialized
> Initializing CPU #1
> Enabling cache...done.
> Initializing CPU #2
> Enabling cache...done.
> Initializing CPU #3
> Waiting for 4 CPUS to stop
> Enabling cache...done.
> Setting up local apic...done.
> CPU #1 Initialized
> Waiting for 3 CPUS to stop
> Setting up local apic...done.
> CPU #2 Initialized
> Waiting for 2 CPUS to stop
> Setting up local apic...done.
> CPU #3 Initialized
> Checking IRQ routing tables...
> /home/yhlu/xx/xx/freebios2/src/arch/i386/boot/pirq_routing.c:
> 41:check_pirq_routing_table() - checksum is: 0x9a but should be: 0x5b
> done.
> Copying IRQ routing tables to 0xf0000...done.
> Verifing copy of IRQ routing tables at 0xf0000...done
>
> Welcome to elfboot, the open sourced starter.
> January 2002, Eric Biederman.
> Version 1.3
>
> Loading Etherboot version: 5.2.4
> ROM segment 0x0000 length 0x0000 reloc 0x00020000
> CPU 2285 Mhz
> Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO]
> Relocating _text from: [0002d2a0,0008e8d0) to [efe9e9d0,eff00000)
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:27
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:28
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> Probing pci disk...
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Thu May 13 15:47:25 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt... timed out
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 00078560
> frame_list is at 00078630
> frame_list_link: addr: 00077570
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 0006f500
> raw frame_list is at 0007a560
> frame_list is at 0007a630
> frame_list_link: addr: 00077590
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 0006f540
> raw frame_list is at 0007c560
> frame_list is at 0007c630
> frame_list_link: addr: 000775b0
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 0006f580
> raw frame_list is at 0007e560
> frame_list is at 0007e630
> frame_list_link: addr: 000775d0
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 0006f5c0
> Found OHCI at 0d181630
> Resetting OHCI
> USB HC reset_hc usb-0d181630: ctrl = 0x00000600 ;ohc_init setting framelist
> to: efef7000
> Starting OHCI
> Found OHCI at 0d182630
> Resetting OHCI
> USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting framelist
> to: efef9000
> Starting OHCI
> Found UHCI at 00002400
> Resetting UHCI
> uhc_init setting framelist to: efefb000
> Starting UHCI
> HCI at 00002400
> Found UHCI at 00002420
> Resetting UHCI
> uhc_init setting framelist to: efefd000
> Starting UHCI
> HCI at 00002420
> poll_usb1 i=0   poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00000100poll_usb1 i=1   poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100poll_usb1 i=2
> poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00001493
> poll_u_root_hub2 v=00001493poll_u_root_hub21 v=00001493    Connection on
> port 00002412
> New USB device, setting address 00000003
> Fetching device descriptor length
> Fetching device descriptor
> Fetching config descriptor length
> Fetching config descriptor
> device:
> bLength: 00000012
> type: 00000001
> bcdVersion: 0000000200000000
> Class: 00000000
> SubClass: 00000000
> protocol: 00000000
> max_packet: 00000040
> idVendor: 00001005
> idProduct: 0000b113
> bcdDeviceVersion: 0000000100000000
> iManufacturor: 00000000
> iProduct: 00000001
> iSerial: 00000002
> bNumConfig: 00000001
> config:
> bLength: 00000009
> type: 00000002
> wTotalLength: 00000020
> bNumInterfaces: 00000001
> bConfigurationValue: 00000001
> iConfiguration: 00000000
> bmAttributes: 00000080
> bMaxPower: 000000fa
>
> Interface(00081057):
>         bLength: 00000009
>         type: 00000004
>         bInterfaceNumber: 00000000
>         bAlternateSetting: 00000000
>         bNumEndpoints: 00000002
>         bInterfaceClass: 00000008
>         bInterfaceSubClass: 00000006
>         bInterfaceProtocol: 00000050
>         iInterface: 00000000
>
>         Endpoint (00081060):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000081
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
>
>         Endpoint (00081067):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000002
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
> Selecting Configuration number 00000001:
> clear stall on ep=00000081
> clear stall on ep=00000002
> 00000008:00000006:00000050
> Manufacturor: unknown
> Product: USB Flash Drive
> Serial: 070B01001340CA0
> Mass storage, bulk only SCSI transparent
> Requesting initial sense data
> sense data
> :00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
> 00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
> 0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
> 000000:00000000:00000000:00000000:00000000:00000000:00000000
>
> code = 00000000 key = 00000000
>
> Info: 00000000
> 536870913 536870912 byte blocks
> ll_read_block returns 512
> 0: boot=00000000, start=00000000 length=00000000
> 1: boot=00000000, start=00000000 length=00000000
> 2: boot=00000000, start=00000000 length=00000000
> 3: boot=00000000, start=00000000 length=00000000
> DEVICE CONFIGURED
> poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
> poll_usb1 i=0   poll_o_root_hub1 v=00000100    poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00000100     poll_usb1 i=1   poll_o_root_hub1 v=00000100
> poll_o_root_hub1 v=00000100     poll_o_root_hub1 v=00000100     poll_usb1
> i=2   poll_u_root_hub1 v=00000480    poll_u_root_hub1 v=00000495
> poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
> Found USB block device 3
> bulk_transfer( dev= 00000003, ep = 00000081, len = 0b8a0000, buffer =
> 000810ac) = 2048:short transaction:
> short_transaction:TD(0006f600):
> short_transaction:type: IN
> short_transaction:retries: 00000000
> short_transaction:active: 00000000
> short_transaction:device_addr: 00000003
> short_transaction:endpoint: 00000001
> short_transaction:data_toggle: 00000001
> short_transaction:max_transfer: 0000003f
> short_transaction:actual: 000007ff
> short_transaction:link:
> short_transaction:STALL
>         short_transaction:addr: 0006f620
>         short_transaction: raw addr: efeedff0
>         short_transaction:terminate: 00000000
>         short_transaction:queue: 00000000
>         short_transaction:depth: 00000001
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From YhLu at tyan.com  Thu May 13 21:35:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 13 21:35:01 2004
Subject: =?gb2312?B?tPC4tDogVVNCIGJvb3Q=?=
Message-ID: <3174569B9743D511922F00A0C943142305063E01@TYANWEB>

There is partition FAT in the flash disk.

Another question. If add code to handle OHCI ED and TD, Can I still use
bulk_transfer and control_message?

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?13? 19:49
???: YhLu
??: Linuxbios; Takeshi Sone
??: Re: USB boot

Greetings,

I'll see if I can dig up the old debugging captures, I may still have
them.

The enumeration of the USB bus looks good. The problems seem to start
with:
536870913 536870912 byte blocks
ll_read_block returns 512
0: boot=00000000, start=00000000 length=00000000
1: boot=00000000, start=00000000 length=00000000
2: boot=00000000, start=00000000 length=00000000
3: boot=00000000, start=00000000 length=00000000

GEt capacity returned a VERY unreasonable result :-)

The read of the partition block seems to have actually read the block.
Does the drive have a partition table on it?

If not, try putting one on it and trying the boot so we can see if it
actually read the block correctly or if the data went to the wrong place.

G'day,
sjames



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


On Thu, 13 May 2004, YhLu wrote:



From ts1 at tsn.or.jp  Thu May 13 22:09:00 2004
From: ts1 at tsn.or.jp (Takeshi Sone)
Date: Thu May 13 22:09:00 2004
Subject: Making payloads
In-Reply-To: <Pine.LNX.4.44.0405131028020.17756-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405130959030.26068-100000@ccs-mail.lanl.gov>
    <Pine.LNX.4.44.0405131028020.17756-100000@maxroach.lanl.gov>
Message-ID: <17587.202.32.178.36.1084505229.squirrel@202.32.178.36>

> On Thu, 13 May 2004, Hendricks David W. wrote:
>
>> Oops, I forgot to mention Stefan's patch for FILO to make IDE work on
>> the
>> S2885. I think this is the one:
>> http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html
>
> can we get this put back into filo?

Actually I have got this fixed in my tree and have prepared it as a
bugfix release (dated Oct-31 2003).

Now I have just put this tarball at
http://te.to/~ts1/filo/filo-0.4.2.tar.bz2 .
PCI_BRUTE_SCAN option should enable PCI IDE on K8 systems.

Please test this, as I have not tested this source tree for 6 months.



From jbors at mail.ru  Fri May 14 01:17:01 2004
From: jbors at mail.ru (=?koi8-r?Q?=22?=Dmitry Borisov=?koi8-r?Q?=22=20?=)
Date: Fri May 14 01:17:01 2004
Subject: EPIA-M startup times
In-Reply-To: <003e01c4391a$896e80f0$8000a8c0@debbie>
Message-ID: <E1BOLUE-000FXx-00.jbors-mail-ru@f22.mail.ru>

-----Original Message-----
From: "John Laur" <johnl at blurbco.com>
> 
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.
> 

John,
Were you able to understand the issue with the bootsplash ? I really want it implemented but just busy with something else now...
Dmitry/


From cforney at opus.com  Fri May 14 04:11:01 2004
From: cforney at opus.com (Craig C Forney)
Date: Fri May 14 04:11:01 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <3174569B9743D511922F00A0C943142305063D81@TYANWEB>
Message-ID: <001d01c43995$efca9d40$6400a8c0@opusone>

I have been trying to boot Suse 9.0 Pro AMD64 distribution DVD, not
i386.

The nomce boot argument allowed me to boot up up the Suse 9.1 Live CD
(at least into single user mode), and get much further with other
distributions.  I'll report back on that in a later email.  

Thanks, Stefan and YH!!

Regards,

Craig Forney
Opus Innovations LLC

> -----Original Message-----
> From: YhLu [mailto:YhLu at tyan.com] 
> Sent: Thursday, May 13, 2004 10:34 AM
> To: Stefan Reinauer; Craig C Forney
> Cc: linuxbios at clustermatic.org
> Subject: ??: HDAMA+FILO booting SUSE Linux
> 
> 
> Are you using Suse 9 pro for AMD64 or for i386?
> 
> I guess you are using for i386. 
> 
> YH
> 
> -----????-----
> ???: Stefan Reinauer [mailto:stepan at openbios.org] 
> ????: 2004?5?13? 1:43
> ???: Craig C Forney
> ??: YhLu; linuxbios at clustermatic.org
> ??: Re: HDAMA+FILO booting SUSE Linux
> 
> * Craig C Forney <cforney at opus.com> [040513 09:54]:
> > LinuxBIOS to boot properly.  I had to make a few changes to the 
> > /etc/rc files (remove the keyboard startup), and I was able 
> to get it 
> > to boot up completely into init state 3.
>  
> This stuff should probably be fixed in LinuxBIOS. 
> 
> > So, I'm still struggling with trying to load off of the Suse 9.0 
> > Distribution DVD.  I'd really like to be able to load a complete 
> > system from scratch using the serial port.  It seems awfully close 
> > (the repair worked fine ... even the update sems to work).
> 
> Hm. I was successful installing SUSE 9 on an AMD64 system 
> (Solo) using filo and I described some stuff here:
>    http://www.openbios.org/linuxbioswiki/Filo_2bAMD64
> 
> One thing that might be worth trying is to disable the nmi 
> watchdog and machine check exceptions via linux kernel boot 
> parameters, ie with
>      nmi_watchdog=0 nomce 
> and probably 
>      acpi=off
> 
> > > 		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
> [..]
> > > 		CPU 0: Machine Check Exception: 0000000000000004
> > > 		Bank 4: b200000000070f0f
> > > 		Kernel panic: CPU context corrupt
> 
>    Stefan
> 
> 
> 




From cforney at opus.com  Fri May 14 04:23:00 2004
From: cforney at opus.com (Craig C Forney)
Date: Fri May 14 04:23:00 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <001c01c4393c$c3f857b0$6400a8c0@opusone>
Message-ID: <001e01c43997$9a1b45a0$6400a8c0@opusone>

I'm still having problems installing a new disk using LinuxBIOS+FILO on
an HDAMA board with a Suse AMD64 distribution.

Although the "nomce" argument helped quite a bit moving things along, I
still can't install a new disk from the Suse 9.0 or 9.1 Pro AMD64
distributions using the serial port only with an Arima HDAMA board with
LinuxBIOS and FILO.  The only way I've gotten an bootable installation
going is to use the Phoenix BIOS to install on a drive, then use the
Suse repair function under LinuxBIOS to clean it up and then boot it. 

I thought the following installation attempts might be interesting to
others.  Except for the Suse 9.1 Live CD attempts, I was attempting to
boot from CD and do a complete install of Suse 9.0 or 9.1 on the hard
drive.  If there are any obvious errors in my FILO boot arguments,
please let me know.  Some of these scenarios just might not be
reasonable things to do at this point, given the state of the
hardware/software components.  That info would be appreciated as well.
If there is a different AMD64 Linux distribution that someone has had
installation success with, that would be nice, as well.

The following scenarios were created using the sourceforge snapshot of
linuxbios from May 10, 2004, compiled for and run on an Arima HDAMA
board with FILO 0.4.1 as the payload with a Maxtor disk drive as
/dev/hda and a Hitachi DVD drive as /dev/hdc:

1. Media: Suse 9.0 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Hangs during YaST after successfully determining the
Partitioning installation settings after the "Evaluating package
selection ..." message disappears
	Partitioning          
	* Format Partition /dev/hda2 15.6 MB (for /boot with ext2)    
	* Format Partition /dev/hda4 3.3 GB (for / with reiser)       
	* Format Partition /dev/hda3 501.4 MB (for swap)

2. Media: Suse 9.0 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 
Results: Same as 1. above

3. Media: Suse 9.1 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Hangs during initial boot of linux after ide1 line as follows:
	...
	Linux agpgart interface v0.100 (c) Dave Jones
	Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
	ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
	RAMDISK driver initialized: 16 RAM disks of 128000K size 1024
blocksize
	loop: loaded (max 8 devices)
	Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
	ide: Assuming 33MHz system bus speed for PIO modes; override
with idebus=xx
	AMD8111: IDE controller at PCI slot 0000:01:04.1
	AMD8111: chipset revision 3
	AMD8111: not 100% native mode: will probe irqs later
	AMD8111: 0000:01:04.1 (rev 03) UDMA133 controller
	    ide0: BM-DMA at 0x2430-0x2437, BIOS settings: hda:pio,
hdb:pio
 	   ide1: BM-DMA at 0x2438-0x243f, BIOS settings: hdc:pio,
hdd:pio
	hda: Maxtor 84320D4, ATA DISK drive
	Using anticipatory io scheduler
	ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
	hdc: HITACHI DVD-ROM GD-7500, ATAPI CD/DVD-ROM drive
	ide1 at 0x170-0x177,0x376 on irq 15                         <--
hangs here

	hda: max request size: 128KiB
<-- never gets here
	hda: 8439184 sectors (4320 MB) w/256KiB Cache, CHS=8930/15/63,
UDMA(33)
 	hda: hda1 hda2 hda3 hda4


4. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 
Results: Panics kernel as follows:
	...
	mtrr: v2.0 (20020519)
	ACPI: Subsystem revision 20040326
	ACPI: Interpreter disabled.
	Linux Plug and Play Support v0.97 (c) Adam Belay
	ACPI: ACPI tables contain no PCI IRQ routing entries
	PCI: Invalid ACPI-PCI IRQ routing table
	PCI: Probing PCI hardware
	PCI: Probing PCI hardware (bus 00)
	 ... the first call_usermodehelper: pci_bus
	CPU 0: Machine Check Exception: 0000000000000004
	Bank 4: b200000000070f0f
	Kernel panic: CPU context corrupt

5. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 nomce
Results: Hangs after setting up ethernet:
	Starting PCMCIA Linux Kernel Card Services
	  options:  [pci] [cardbus] [pm]
	PCI: No IRQ known for interrupt pin D of device 0000:04:00.2.
Please try using pci=biosirq.
	drivers/usb/core/hcd-pci.c: Found HC with no IRQ.  Check
BIOS/PCI 0000:04:00.2 setup!
	startproc:  exit status of parent of /sbin/cardmgr: 1
	
failed
	Shutting down network interfaces:
	    eth0      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Edonenet (rev 02)
	    eth1      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	    eth1      configuration:
done
	Shutting down service network  .  .  .  .  .  .  .  .  .  .  .
.  .  done
	Hint: you may set mandatory devices in
/etc/sysconfig/network/config
	Setting up network interfaces:
 	   lo
	    lo        IP address: 127.0.0.1/8
done
	    eth0      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	SIOCSIFFLAGS: Device or resource busy
	    eth0      (DHCP) . NET: Registered protocol family 17
	. . . . no IP address yet... backgrounding.
waiting
	    eth1      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	    eth1      No configuration found for eth1
unused
	Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .
.  .  Done

6. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 nmi-watchdog=0 acpi=off nomce ide=nodma apm=off
single
Results: Boots into single user mode just fine.

7. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8
Results: Kernel panics
	...
	do_initcalls
	init_elf_binfmt
	NET: Registered protocol family 16
	PCI: Using configuration type 1
	mtrr: v2.0 (20020519)
	ACPI: Subsystem revision 20040326
	ACPI: Interpreter disabled.
	Linux Plug and Play Support v0.97 (c) Adam Belay
	ACPI: ACPI tables contain no PCI IRQ routing entries
	PCI: Invalid ACPI-PCI IRQ routing table
	PCI: Probing PCI hardware
	PCI: Probing PCI hardware (bus 00)
	 ... the first call_usermodehelper: pci_bus
	CPU 0: Machine Check Exception: 0000000000000004
	Bank 4: b200000000070f0f
	Kernel panic: CPU context corrupt

8. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nomce
Results: Installs OK

9. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Installs OK

Whew!

Thanks,

Craig Forney
Opus Innovations LLC




From mdeschamps at mangrove-systems.com  Fri May 14 08:46:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Fri May 14 08:46:00 2004
Subject: EPIA V2 : BTEXT config problems
In-Reply-To: <Pine.LNX.4.44.0405130946460.17756-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405130946460.17756-100000@maxroach.lanl.gov>
Message-ID: <1084543364.15547.36.camel@Calliphara>

I am trying first to get btext config to display something on my screen
but i does nothing. I have no payload, no videoBIOS ROM, and no activate
VGABIOS. 
I have this output (truncat. ) my CyberBlade i3 chipset is in 01:00.0

108     Disabling cache$
109     Clearing mtrr$
110     Setting XIP$
111     Enabled the cache$
112     Copying LinuxBIOS to ram.$
113     Jumping to LinuxBIOS.$
114     POST: 0x39$
115     LinuxBIOS-1.1.6.0Fallback Fri May 14 15:25:51 CEST 2004
booting...$
116     POST: 0x40$
117     Finding PCI configuration type.$
118     PCI: Using configuration type 1$
119     POST: 0x5f$
120     Enumerating static devices...$
121     Enumerating: VIA vt8601 Northbridge$
122     Enumerating: VIA vt8231$
123     Enumerating buses...$
124     PCI: pci_scan_bus for bus 0$
125     POST: 0x24$
126     PCI: 00:00.0 [1106/0601] enabled$
127     PCI: 00:01.0 [1106/8601] enabled$
128     PCI: 00:11.0 [1106/8231] enabled$
129     PCI: 00:11.1 [1106/0571] enabled$
130     PCI: 00:11.2 [1106/3038] enablhi,ed$
131     PCI: 00:11.3 [1106/3038] enabled$
132     PCI: 00:11.4 [1106/8235] enabled$
133     PCI: 00:11.5 [1106/3058] enabled$
134     PCI: 00:11.6 [1106/3068] enabled$
135     PCI: 00:12.0 [1106/3065] enabled$
136     POST: 0x25$
137     PCI: pci_scan_bus for bus 1$
138     POST: 0x24$
139     PCI: 01:00.0 [1023/8500] enabled$
140     POST: 0x25$
141     PCI: pci_scan_bus returning with max=01$
142     POST: 0x55$
143     PCI: pci_scan_bus returning with max=01$
144     POST: 0x55$
145     done$
146     POST: 0x66$
147     Allocating resources...$
148     Allocating VGA resource$
149     ASSIGN RESOURCES, bus 0$
150     PCI: 00:00.0 10 <- [0xe0000000 - 0xefffffff] prefmem$
151     PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io$
152     PCI: 00:01.0 24 <- [0xf1100000 - 0xf10fffff] bus 1 prefmem$
153     PCI: 00:01.0 20 <- [0xf0000000 - 0xf10fffff] bus 1 mem$
154     ASSIGN RESOURCES, bus 1$
155     PCI: 01:00.0 10 <- [0xf0000000 - 0xf07fffff] mem$
156     PCI: 01:00.0 14 <- [0xf1000000 - 0xf101ffff] mem$
157     PCI: 01:00.0 18 <- [0xf0800000 - 0xf0ffffff] mem$
158     ASSIGNED RESOURCES, bus 1$
159     PCI: 00:11.1 20 <- [0x00001c40 - 0x00001c4f] io$
160     PCI: 00:11.2 20 <- [0x00001c00 - 0x00001c1f] io$
161     PCI: 00:11.3 20 <- [0x00001c20 - 0x00001c3f] io$
162     PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io$
163     PCI: 00:11.5 14 <- [0x00001c50 - 0x00001c53] io$
164     PCI: 00:11.5 18 <- [0x00001c60 - 0x00001c63] io$
165     PCI: 00:11.6 10 <- [0x00001400 - 0x000014ff] io$
166     PCI: 00:12.0 10 <- [0x00001800 - 0x000018ff] io$
167     PCI: 00:12.0 14 <- [0xf1100000 - 0xf11000ff] mem$
168     ASSIGNED RESOURCES, bus 0$
169     done.$
170     POST: 0x88$
171     Enabling resourcess...$
172     PCI: 00:00.0 cmd <- 146$
173     PCI: 00:01.0 bridge ctrl <- 000f$
174     PCI: 00:01.0 cmd <- 147$
175     PCI: 01:00.0 cmd <- 147$
176     PCI: 00:11.0 cmd <- 1c7$
177     PCI: 00:11.1 cmd <- 147$
178     PCI: 00:11.2 cmd <- 147$
179     PCI: 00:11.3 cmd <- 147$
180     PCI: 00:11.4 cmd <- 140$
181     PCI: 00:11.5 cmd <- 141$
182     PCI: 00:11.6 cmd <- 141$
183     PCI: 00:12.0 cmd <- 147$
184     done.$
185     Initializing devices...$
186     Devices initialized$
187     POST: 0x89$
188     vt8231 init$
189     IDE enable in reg. 50 is 0x7$
190     set IDE reg. 50 to 0x7$
191     IRQs in reg. 4c are 0x4$
192     setting reg. 4c to 0x4$
193     enables in reg 0x40 0xb$
194     enables in reg 0x40 read back as 0xb$
195     enables in reg 0x9 0x8f$
196     enables in reg 0x9 read back as 0x8f$
197     command in reg 0x4 0x7$
198     command in reg 0x4 reads back as 0x7$
199     Ethernet fixup$
200     Configuring VIA LAN$
201     RTC Init$
202     Invalid CMOS LB checksum$
203     pci_routing_fixup: dev is 0002e098$
204     setting southbridge$
205     Assigning IRQ 11 to 0:11.1$
206       Readback = 255$
207     Assigning IRQ 12 to 0:11.2$
208       Readback = 12$
209     Assigning IRQ 12 to 0:11.3$
210       Readback = 12$
211     Assigning IRQ 10 to 0:11.5$
212       Readback = 10$
213     Assigning IRQ 10 to 0:11.6$
214       Readback = 10$
215     setting ethernet$
216     Assigning IRQ 11 to 0:12.0$
217       Readback = 11$
218     setting pci slot$
219     pci_routing_fixup: DONE$
220     I would set ram size to 0x20000 Kbytes$
221     mem[0].basek = 00000000 mem[0].sizek = 00020000$
222     mem[1].basek = 00000000 mem[1].sizek = 00000000$
223     mem[2].basek = 00000000 mem[2].sizek = 00000000$
224     mem[3].basek = 00000000 mem[3].sizek = 00000000$
225     mem[4].basek = 00000000 mem[4].sizek = 00000000$
226     mem[5].basek = 00000000 mem[5].sizek = 00000000$
227     mem[6].basek = 00000000 mem[6].sizek = 00000000$
228     mem[7].basek = 00000000 mem[7].sizek = 00000000$
229     mem[8].basek = 00000000 mem[8].sizek = 00000000$
230     mem[9].basek = 00000000 mem[9].sizek = 00000000$
231     POST: 0x70$
232     totalram: 128M$
233     Initializing CPU #0$
234     POST: 0x60$
235     Enabling cache...$
236     Setting fixed MTRRs(0-88) type: UC$
237     Setting fixed MTRRs(0-88) type: WB$
238     DONE fixed MTRRs$
239     Setting variable MTRR 0, base:    0MB, range:  128MB, type WB$
240     DONE variable MTRRs$
241     Clear out the extra MTRR's$
242     call intel_enable_fixed_mtrr()$
243     call intel_enable_var_mtrr()$
244     Leave setup_mtrrs$
245     POST: 0x6a$
246     done.$
247     Max cpuid index    : 1$
248     Vendor ID          : CentaurHauls$
249     Processor Type     : 0x00$
250     Processor Family   : 0x06$
251     Processor Model    : 0x07$
252     Processor Mask     : 0x00$
253     Processor Stepping : 0x08$
254     Feature flags      : 0x00803135$
255     POST: 0x92$
256     MTRR check$
257     Fixed MTRRs   : Enabled$
258     Variable MTRRs: Enabled$
259     POST: 0x93$
260     Updating microcode$
261     microcode_info: sig = 0x00000678 pf=0x00000001 rev = 0x0000000al
apic...done.$
262     POSTtirq_routing_table() - irq_rosinuxbios ta 0 00 00 00 00 00
06 11 10 60 $
263     0x7$
264     0x60: 00 00 00 00 00 00 02 08 0100 20 00 00 00 $
265     0x80: 00 00 00 00 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 $
266     0xfodev/hda3 console=tty0 $
267     Welcomeea hard coded delay and longer thaclocks_per_usec: 960$
268     .$
269     found PCI IDE controller 1106:0571 prog_if=0x8f$
270     primary channel: native PCI mode$
271     Waiting for ide0 to become ready for reset... ok$
272     Testing for hda$
273     Probing for hda$
274     LBA mode, sectors=40021632$
275     Init device params... ok$
276     hda: LBA 20GB: Maxtor 32049U3                          $
277     Partition 1 start 63 length 2040192$
278     Unknown filesystem type$
279     command terminated by signal 2
real 13.67
user 0.01
sys 0.01
----------------------------------------------
Comments :

This is a BTEXT_CONFIG test
 no payload, no videoROM, no VGABIOS
from a cold boot : no  screen "video mode on" (led goes green)
from a warn boot : the screen flashes but nothing written (bad init?)




Le jeu 13/05/2004 ? 17:49, ron minnich a ?crit :
> On 13 May 2004, Mathieu Deschamps wrote:
> 
> > hum i see ... but didn't we got native LinuxBIOS VGA up on EPIA-M  ? 
> 
> on V1 not V2. It works fine on V1. But ram detection on V1 is not working. 
> You only get one size ram.
> 



From lbios_kk at redfenix.com  Fri May 14 09:26:01 2004
From: lbios_kk at redfenix.com (lbios_kk at redfenix.com)
Date: Fri May 14 09:26:01 2004
Subject: Hibernation?
Message-ID: <1084545894.40a4db667ef56@www.mailshell.com>

I'm sure if someone has thought of doing this before, but I haven't found mention of it anywhere.

Has any work been done toward the goal of "Hibernation"?  I'm writing of the type that would use a separate partition equal to ram + swap space to store the current memory state.  If no one has done any work to this effect, how difficult would it be?  I may be willing to help the effort.  I've never programmed for a BIOS, but I've done mmap() stuff before.

--Kevin


From adam at cfar.umd.edu  Fri May 14 09:31:01 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May 14 09:31:01 2004
Subject: Hibernation?
In-Reply-To: <1084545894.40a4db667ef56@www.mailshell.com>
Message-ID: <20040514105827.I65075-100000@www.missl.cs.umd.edu>

I don't really think it is BIOS issue.

OS can do it just fine on its own. I don't see why BIOS should be invovled
here.

> Has any work been done toward the goal of "Hibernation"?  I'm writing of
> the type that would use a separate partition equal to ram + swap space
> to store the current memory state.  If no one has done any work to this
> effect, how difficult would it be?  I may be willing to help the effort.
> I've never programmed for a BIOS, but I've done mmap() stuff before.



From lbios_kk at redfenix.com  Fri May 14 09:54:00 2004
From: lbios_kk at redfenix.com (lbios_kk at redfenix.com)
Date: Fri May 14 09:54:00 2004
Subject: Hibernation?
In-Reply-To: <20040514105827.I65075-100000@www.missl.cs.umd.edu>
Message-ID: <1084547563.40a4e1eb1adc0@www.mailshell.com>

If the hibernation restore occurred from the BIOS, then one wouldn't need to boot from disk, right?  Also, if you don't need to boot from disk, the BIOS could restore the entire memory state and then re-initialize any peripherals that need it (PCI, PCMCIA, CF, VGA, etc.)  Should be quicker, elegant, and more effective, right?  (and OS independent if done right.)

Question is, how much memory does LinuxBIOS use for itself?  We'd have to make sure that it doesn't "step on its own feet" trying to get the memory state loaded.

--Kevin


From rminnich at lanl.gov  Fri May 14 09:57:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May 14 09:57:00 2004
Subject: Hibernation?
In-Reply-To: <1084545894.40a4db667ef56@www.mailshell.com>
Message-ID: <Pine.LNX.4.44.0405140915210.30642-100000@maxroach.lanl.gov>

On Fri, 14 May 2004 lbios_kk at redfenix.com wrote:

> Has any work been done toward the goal of "Hibernation"?  

It would sure be nice if you would do it ... you would be very popular!

ron



From adam at cfar.umd.edu  Fri May 14 09:58:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May 14 09:58:00 2004
Subject: Hibernation?
In-Reply-To: <1084547563.40a4e1eb1adc0@www.mailshell.com>
Message-ID: <20040514112347.V65075-100000@www.missl.cs.umd.edu>

well I guess it depends on philosophy. if the idea is to have minimalistic
bios then ability to suspend doesn't belong there.

on the other hand some configurations of "bios" (where "bios" would be the
thing in the thing in FLASH), often include linux kernel and that alone
could be re-used to enable suspend. Although the proper way to do this is
probably to use "management mode" of the recent CPUs.

On Fri, 14 May 2004 lbios_kk at redfenix.com wrote:

> If the hibernation restore occurred from the BIOS, then one wouldn't need to boot from disk, right?  Also, if you don't need to boot from disk, the BIOS could restore the entire memory state and then re-initialize any peripherals that need it (PCI, PCMCIA, CF, VGA, etc.)  Should be quicker, elegant, and more effective, right?  (and OS independent if done right.)
>
> Question is, how much memory does LinuxBIOS use for itself?  We'd have to make sure that it doesn't "step on its own feet" trying to get the memory state loaded.
>
> --Kevin
>
> >From Adam Sulmicki <adam at cfar.umd.edu> on 14 May 2004:
>
> >
> > I don't really think it is BIOS issue.
> >
> > OS can do it just fine on its own. I don't see why BIOS should be
> > invovled
> > here.
> >
> > > Has any work been done toward the goal of "Hibernation"?  I'm writing
> > of
> > > the type that would use a separate partition equal to ram + swap space
> > > to store the current memory state.  If no one has done any work to
> > this
> > > effect, how difficult would it be?  I may be willing to help the
> > effort.
> > > I've never programmed for a BIOS, but I've done mmap() stuff before.
> >
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
> >
>



From jbors at mail.ru  Fri May 14 10:18:01 2004
From: jbors at mail.ru (Dmitry Borisov)
Date: Fri May 14 10:18:01 2004
Subject: EPIA V2 : BTEXT config problems
References: <Pine.LNX.4.44.0405130946460.17756-100000@maxroach.lanl.gov> <1084543364.15547.36.camel@Calliphara>
Message-ID: <014201c439c9$2843acb0$0900a8c0@amr.corp.intel.com>

Mathieu,
You still need VGA bios to be invoked( if it is EPIA-M ). Please see threads
earlier to get more details.
Dmitry/

----- Original Message ----- 
Subject: EPIA V2 : BTEXT config problems


>
> I am trying first to get btext config to display something on my screen
> but i does nothing. I have no payload, no videoBIOS ROM, and no activate
> VGABIOS.
> I have this output (truncat. ) my CyberBlade i3 chipset is in 01:00.0



From lbios_kk at redfenix.com  Fri May 14 10:18:24 2004
From: lbios_kk at redfenix.com (lbios_kk at redfenix.com)
Date: Fri May 14 10:18:24 2004
Subject: Hibernation?
In-Reply-To: <20040514112347.V65075-100000@www.missl.cs.umd.edu>
Message-ID: <1084548982.40a4e77607541@www.mailshell.com>

I'm not necessarily talking about handling a suspend or low-power mode.  I'm talking about copying the memory to disk, then powering off.  Then, upon power-on next time, reload the memory state, re-init peripherals and go!

So, would something like this be contained in a payload?

--Kevin


From rminnich at lanl.gov  Fri May 14 10:27:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May 14 10:27:00 2004
Subject: Hibernation?
In-Reply-To: <1084548982.40a4e77607541@www.mailshell.com>
Message-ID: <Pine.LNX.4.44.0405140945000.30642-100000@maxroach.lanl.gov>

On Fri, 14 May 2004 lbios_kk at redfenix.com wrote:

> So, would something like this be contained in a payload?

you could save the entire state of the physical memeory as an elf ... 

but what about swap? Should be ok ...

ron



From Antony at Soft-Solutions.co.uk  Fri May 14 10:31:00 2004
From: Antony at Soft-Solutions.co.uk (Antony Stone)
Date: Fri May 14 10:31:00 2004
Subject: Hibernation?
In-Reply-To: <1084548982.40a4e77607541@www.mailshell.com>
References: <1084548982.40a4e77607541@www.mailshell.com>
Message-ID: <200405141649.04711.Antony@Soft-Solutions.co.uk>

On Friday 14 May 2004 4:36 pm, lbios_kk at redfenix.com wrote:

> I'm not necessarily talking about handling a suspend or low-power mode. 
> I'm talking about copying the memory to disk, then powering off.  Then,
> upon power-on next time, reload the memory state, re-init peripherals and
> go!

I can't help feeling that it's a bit simplistic to just say "re-init 
peripherals" like that.   Some peripherals can have quite a complex state 
associated with them, and just re-initialising them as though you were 
starting from power-up may not make the O/S happy when it finds itself back 
in control after the hibernation is over?

There has to be some O/S involvement in going into, and returning from, 
hibernation mode - the question for LinuxBIOS is "how much of a task is left 
over once you take out what the Linux kernel can already do for itself?"

Regards,

Antony.

-- 
Microsoft may sell more software than any other company, but McDonald's sell 
more burgers than any other company, and I think the other similarities are 
obvious...

                                                     Please reply to the list;
                                                           please don't CC me.



From adam at cfar.umd.edu  Fri May 14 10:38:00 2004
From: adam at cfar.umd.edu (Adam Sulmicki)
Date: Fri May 14 10:38:00 2004
Subject: Hibernation?
In-Reply-To: <Pine.LNX.4.44.0405140945000.30642-100000@maxroach.lanl.gov>
Message-ID: <20040514120159.U65075-100000@www.missl.cs.umd.edu>

also,you might want to checkout 2.6.x kernels. they seem have a good chunk
of work toward suspend-to-disk done there. so if you can put that code or
2.6.x in BIOS then you would have most of the work done for you already.

On Fri, 14 May 2004, ron minnich wrote:

> On Fri, 14 May 2004 lbios_kk at redfenix.com wrote:
>
> > So, would something like this be contained in a payload?
>
> you could save the entire state of the physical memeory as an elf ...
>
> but what about swap? Should be ok ...
>
> ron
>



From lbios_kk at redfenix.com  Fri May 14 10:55:01 2004
From: lbios_kk at redfenix.com (lbios_kk at redfenix.com)
Date: Fri May 14 10:55:01 2004
Subject: Hibernation?
In-Reply-To: <200405141649.04711.Antony@Soft-Solutions.co.uk>
Message-ID: <1084551236.40a4f04477a3b@www.mailshell.com>

I had looked into this all before, but lost the link to the project.  I just found it again:

http://swsusp.sourceforge.net/

The "Software Suspend" project, as they call it, handles exactly what we're talking about, except that it occurs in the resident OS.  This means that they save only process memory and not kernel memory states.  They also recommend for some peripheral drivers, that one install them as modules and unload them before saving state.  They do, however, compress the memory image and have the option of saving it in swap space.

So, in answer to your question, it may be possible to unload drivers before saving state, then reload them upon restore.  However, this could present some difficulty if the module is in use by a process (e.g. vga driver w/ xwindows) or in use by other modules.  This is something that would need to be addressed.  If you have to shutdown X just to save state, and start X again after restoring state, this wouldn't be nearly as useful.

I guess there are a few options:  Try it without re-initializing (for many, this will work, but not all.)  Unload/load modules (good for non-critical modules)  Figure out way to read/write state to peripheral (messy, many proprietary implementations)

One more question.  To do this effectively we'll need a hook into running a BIOS process from inside the OS (trigger to save state and shutdown.)  How difficult is this to do?

--Kevin

P.S. I've just subscribed to the swsusp-devel list.  I'll be asking questions in there too.


From YhLu at tyan.com  Fri May 14 10:59:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 14 10:59:01 2004
Subject: =?gb2312?B?tPC4tDogSERBTUErRklMTyBib290aW5nIFNVU0UgTGludXg=?=
Message-ID: <3174569B9743D511922F00A0C943142305063E11@TYANWEB>

There is one patch CD for Suse 9 pro for AMD DVD, Did you use it boot to
install?

YH

-----????-----
???: Craig C Forney [mailto:cforney at opus.com] 
????: 2004?5?14? 2:41
???: linuxbios at clustermatic.org
??: Re: HDAMA+FILO booting SUSE Linux


I'm still having problems installing a new disk using LinuxBIOS+FILO on
an HDAMA board with a Suse AMD64 distribution.

Although the "nomce" argument helped quite a bit moving things along, I
still can't install a new disk from the Suse 9.0 or 9.1 Pro AMD64
distributions using the serial port only with an Arima HDAMA board with
LinuxBIOS and FILO.  The only way I've gotten an bootable installation
going is to use the Phoenix BIOS to install on a drive, then use the
Suse repair function under LinuxBIOS to clean it up and then boot it. 

I thought the following installation attempts might be interesting to
others.  Except for the Suse 9.1 Live CD attempts, I was attempting to
boot from CD and do a complete install of Suse 9.0 or 9.1 on the hard
drive.  If there are any obvious errors in my FILO boot arguments,
please let me know.  Some of these scenarios just might not be
reasonable things to do at this point, given the state of the
hardware/software components.  That info would be appreciated as well.
If there is a different AMD64 Linux distribution that someone has had
installation success with, that would be nice, as well.

The following scenarios were created using the sourceforge snapshot of
linuxbios from May 10, 2004, compiled for and run on an Arima HDAMA
board with FILO 0.4.1 as the payload with a Maxtor disk drive as
/dev/hda and a Hitachi DVD drive as /dev/hdc:

1. Media: Suse 9.0 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Hangs during YaST after successfully determining the
Partitioning installation settings after the "Evaluating package
selection ..." message disappears
	Partitioning          
	* Format Partition /dev/hda2 15.6 MB (for /boot with ext2)    
	* Format Partition /dev/hda4 3.3 GB (for / with reiser)       
	* Format Partition /dev/hda3 501.4 MB (for swap)

2. Media: Suse 9.0 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 
Results: Same as 1. above

3. Media: Suse 9.1 amd64 distribution DVD (YaST new installation) 
Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Hangs during initial boot of linux after ide1 line as follows:
	...
	Linux agpgart interface v0.100 (c) Dave Jones
	Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
	ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
	RAMDISK driver initialized: 16 RAM disks of 128000K size 1024
blocksize
	loop: loaded (max 8 devices)
	Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
	ide: Assuming 33MHz system bus speed for PIO modes; override
with idebus=xx
	AMD8111: IDE controller at PCI slot 0000:01:04.1
	AMD8111: chipset revision 3
	AMD8111: not 100% native mode: will probe irqs later
	AMD8111: 0000:01:04.1 (rev 03) UDMA133 controller
	    ide0: BM-DMA at 0x2430-0x2437, BIOS settings: hda:pio,
hdb:pio
 	   ide1: BM-DMA at 0x2438-0x243f, BIOS settings: hdc:pio,
hdd:pio
	hda: Maxtor 84320D4, ATA DISK drive
	Using anticipatory io scheduler
	ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
	hdc: HITACHI DVD-ROM GD-7500, ATAPI CD/DVD-ROM drive
	ide1 at 0x170-0x177,0x376 on irq 15                         <--
hangs here

	hda: max request size: 128KiB
<-- never gets here
	hda: 8439184 sectors (4320 MB) w/256KiB Cache, CHS=8930/15/63,
UDMA(33)
 	hda: hda1 hda2 hda3 hda4


4. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 
Results: Panics kernel as follows:
	...
	mtrr: v2.0 (20020519)
	ACPI: Subsystem revision 20040326
	ACPI: Interpreter disabled.
	Linux Plug and Play Support v0.97 (c) Adam Belay
	ACPI: ACPI tables contain no PCI IRQ routing entries
	PCI: Invalid ACPI-PCI IRQ routing table
	PCI: Probing PCI hardware
	PCI: Probing PCI hardware (bus 00)
	 ... the first call_usermodehelper: pci_bus
	CPU 0: Machine Check Exception: 0000000000000004
	Bank 4: b200000000070f0f
	Kernel panic: CPU context corrupt

5. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 nomce
Results: Hangs after setting up ethernet:
	Starting PCMCIA Linux Kernel Card Services
	  options:  [pci] [cardbus] [pm]
	PCI: No IRQ known for interrupt pin D of device 0000:04:00.2.
Please try using pci=biosirq.
	drivers/usb/core/hcd-pci.c: Found HC with no IRQ.  Check
BIOS/PCI 0000:04:00.2 setup!
	startproc:  exit status of parent of /sbin/cardmgr: 1
	
failed
	Shutting down network interfaces:
	    eth0      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Edonenet (rev 02)
	    eth1      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	    eth1      configuration:
done
	Shutting down service network  .  .  .  .  .  .  .  .  .  .  .
.  .  done
	Hint: you may set mandatory devices in
/etc/sysconfig/network/config
	Setting up network interfaces:
 	   lo
	    lo        IP address: 127.0.0.1/8
done
	    eth0      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	SIOCSIFFLAGS: Device or resource busy
	    eth0      (DHCP) . NET: Registered protocol family 17
	. . . . no IP address yet... backgrounding.
waiting
	    eth1      device: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
	    eth1      No configuration found for eth1
unused
	Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .
.  .  Done

6. Media: Suse 9.1 LIVE CD 
Filo boot arguments: hdc:/vmlinuz initrd=hdc:/initrd.gz
console=ttyS0,115200n8 nmi-watchdog=0 acpi=off nomce ide=nodma apm=off
single
Results: Boots into single user mode just fine.

7. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8
Results: Kernel panics
	...
	do_initcalls
	init_elf_binfmt
	NET: Registered protocol family 16
	PCI: Using configuration type 1
	mtrr: v2.0 (20020519)
	ACPI: Subsystem revision 20040326
	ACPI: Interpreter disabled.
	Linux Plug and Play Support v0.97 (c) Adam Belay
	ACPI: ACPI tables contain no PCI IRQ routing entries
	PCI: Invalid ACPI-PCI IRQ routing table
	PCI: Probing PCI hardware
	PCI: Probing PCI hardware (bus 00)
	 ... the first call_usermodehelper: pci_bus
	CPU 0: Machine Check Exception: 0000000000000004
	Bank 4: b200000000070f0f
	Kernel panic: CPU context corrupt

8. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nomce
Results: Installs OK

9. Media: Suse 9.1 32-bit distribution DVD or CD (YaST new installation)

Filo boot arguments: hdc:/boot/loader/linux
initrd=hdc:/boot/loader/initrd console=ttyS0,115200n8 nmi-watchdog=0
acpi=off nomce ide=nodma apm=off
Results: Installs OK

Whew!

Thanks,

Craig Forney
Opus Innovations LLC


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


From YhLu at tyan.com  Fri May 14 11:01:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 14 11:01:00 2004
Subject: =?gb2312?B?tPC4tDogRVBJQSBWMiA6IEJURVhUIGNvbmZpZyBwcm9ibGVtcw==?=
Message-ID: <3174569B9743D511922F00A0C943142305063E12@TYANWEB>

If you want to use BTEXT config, you need to make sure the VGA driver has
enable the frame buffer and call btext_setup....

Regards

YH

-----????-----
???: Mathieu Deschamps [mailto:mdeschamps at mangrove-systems.com] 
????: 2004?5?14? 7:03
???: Linuxbios at clustermatic.org
??: EPIA V2 : BTEXT config problems


I am trying first to get btext config to display something on my screen
but i does nothing. I have no payload, no videoBIOS ROM, and no activate
VGABIOS. 
I have this output (truncat. ) my CyberBlade i3 chipset is in 01:00.0

108     Disabling cache$
109     Clearing mtrr$
110     Setting XIP$
111     Enabled the cache$
112     Copying LinuxBIOS to ram.$
113     Jumping to LinuxBIOS.$
114     POST: 0x39$
115     LinuxBIOS-1.1.6.0Fallback Fri May 14 15:25:51 CEST 2004
booting...$
116     POST: 0x40$
117     Finding PCI configuration type.$
118     PCI: Using configuration type 1$
119     POST: 0x5f$
120     Enumerating static devices...$
121     Enumerating: VIA vt8601 Northbridge$
122     Enumerating: VIA vt8231$
123     Enumerating buses...$
124     PCI: pci_scan_bus for bus 0$
125     POST: 0x24$
126     PCI: 00:00.0 [1106/0601] enabled$
127     PCI: 00:01.0 [1106/8601] enabled$
128     PCI: 00:11.0 [1106/8231] enabled$
129     PCI: 00:11.1 [1106/0571] enabled$
130     PCI: 00:11.2 [1106/3038] enablhi,ed$
131     PCI: 00:11.3 [1106/3038] enabled$
132     PCI: 00:11.4 [1106/8235] enabled$
133     PCI: 00:11.5 [1106/3058] enabled$
134     PCI: 00:11.6 [1106/3068] enabled$
135     PCI: 00:12.0 [1106/3065] enabled$
136     POST: 0x25$
137     PCI: pci_scan_bus for bus 1$
138     POST: 0x24$
139     PCI: 01:00.0 [1023/8500] enabled$
140     POST: 0x25$
141     PCI: pci_scan_bus returning with max=01$
142     POST: 0x55$
143     PCI: pci_scan_bus returning with max=01$
144     POST: 0x55$
145     done$
146     POST: 0x66$
147     Allocating resources...$
148     Allocating VGA resource$
149     ASSIGN RESOURCES, bus 0$
150     PCI: 00:00.0 10 <- [0xe0000000 - 0xefffffff] prefmem$
151     PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io$
152     PCI: 00:01.0 24 <- [0xf1100000 - 0xf10fffff] bus 1 prefmem$
153     PCI: 00:01.0 20 <- [0xf0000000 - 0xf10fffff] bus 1 mem$
154     ASSIGN RESOURCES, bus 1$
155     PCI: 01:00.0 10 <- [0xf0000000 - 0xf07fffff] mem$
156     PCI: 01:00.0 14 <- [0xf1000000 - 0xf101ffff] mem$
157     PCI: 01:00.0 18 <- [0xf0800000 - 0xf0ffffff] mem$
158     ASSIGNED RESOURCES, bus 1$
159     PCI: 00:11.1 20 <- [0x00001c40 - 0x00001c4f] io$
160     PCI: 00:11.2 20 <- [0x00001c00 - 0x00001c1f] io$
161     PCI: 00:11.3 20 <- [0x00001c20 - 0x00001c3f] io$
162     PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io$
163     PCI: 00:11.5 14 <- [0x00001c50 - 0x00001c53] io$
164     PCI: 00:11.5 18 <- [0x00001c60 - 0x00001c63] io$
165     PCI: 00:11.6 10 <- [0x00001400 - 0x000014ff] io$
166     PCI: 00:12.0 10 <- [0x00001800 - 0x000018ff] io$
167     PCI: 00:12.0 14 <- [0xf1100000 - 0xf11000ff] mem$
168     ASSIGNED RESOURCES, bus 0$
169     done.$
170     POST: 0x88$
171     Enabling resourcess...$
172     PCI: 00:00.0 cmd <- 146$
173     PCI: 00:01.0 bridge ctrl <- 000f$
174     PCI: 00:01.0 cmd <- 147$
175     PCI: 01:00.0 cmd <- 147$
176     PCI: 00:11.0 cmd <- 1c7$
177     PCI: 00:11.1 cmd <- 147$
178     PCI: 00:11.2 cmd <- 147$
179     PCI: 00:11.3 cmd <- 147$
180     PCI: 00:11.4 cmd <- 140$
181     PCI: 00:11.5 cmd <- 141$
182     PCI: 00:11.6 cmd <- 141$
183     PCI: 00:12.0 cmd <- 147$
184     done.$
185     Initializing devices...$
186     Devices initialized$
187     POST: 0x89$
188     vt8231 init$
189     IDE enable in reg. 50 is 0x7$
190     set IDE reg. 50 to 0x7$
191     IRQs in reg. 4c are 0x4$
192     setting reg. 4c to 0x4$
193     enables in reg 0x40 0xb$
194     enables in reg 0x40 read back as 0xb$
195     enables in reg 0x9 0x8f$
196     enables in reg 0x9 read back as 0x8f$
197     command in reg 0x4 0x7$
198     command in reg 0x4 reads back as 0x7$
199     Ethernet fixup$
200     Configuring VIA LAN$
201     RTC Init$
202     Invalid CMOS LB checksum$
203     pci_routing_fixup: dev is 0002e098$
204     setting southbridge$
205     Assigning IRQ 11 to 0:11.1$
206       Readback = 255$
207     Assigning IRQ 12 to 0:11.2$
208       Readback = 12$
209     Assigning IRQ 12 to 0:11.3$
210       Readback = 12$
211     Assigning IRQ 10 to 0:11.5$
212       Readback = 10$
213     Assigning IRQ 10 to 0:11.6$
214       Readback = 10$
215     setting ethernet$
216     Assigning IRQ 11 to 0:12.0$
217       Readback = 11$
218     setting pci slot$
219     pci_routing_fixup: DONE$
220     I would set ram size to 0x20000 Kbytes$
221     mem[0].basek = 00000000 mem[0].sizek = 00020000$
222     mem[1].basek = 00000000 mem[1].sizek = 00000000$
223     mem[2].basek = 00000000 mem[2].sizek = 00000000$
224     mem[3].basek = 00000000 mem[3].sizek = 00000000$
225     mem[4].basek = 00000000 mem[4].sizek = 00000000$
226     mem[5].basek = 00000000 mem[5].sizek = 00000000$
227     mem[6].basek = 00000000 mem[6].sizek = 00000000$
228     mem[7].basek = 00000000 mem[7].sizek = 00000000$
229     mem[8].basek = 00000000 mem[8].sizek = 00000000$
230     mem[9].basek = 00000000 mem[9].sizek = 00000000$
231     POST: 0x70$
232     totalram: 128M$
233     Initializing CPU #0$
234     POST: 0x60$
235     Enabling cache...$
236     Setting fixed MTRRs(0-88) type: UC$
237     Setting fixed MTRRs(0-88) type: WB$
238     DONE fixed MTRRs$
239     Setting variable MTRR 0, base:    0MB, range:  128MB, type WB$
240     DONE variable MTRRs$
241     Clear out the extra MTRR's$
242     call intel_enable_fixed_mtrr()$
243     call intel_enable_var_mtrr()$
244     Leave setup_mtrrs$
245     POST: 0x6a$
246     done.$
247     Max cpuid index    : 1$
248     Vendor ID          : CentaurHauls$
249     Processor Type     : 0x00$
250     Processor Family   : 0x06$
251     Processor Model    : 0x07$
252     Processor Mask     : 0x00$
253     Processor Stepping : 0x08$
254     Feature flags      : 0x00803135$
255     POST: 0x92$
256     MTRR check$
257     Fixed MTRRs   : Enabled$
258     Variable MTRRs: Enabled$
259     POST: 0x93$
260     Updating microcode$
261     microcode_info: sig = 0x00000678 pf=0x00000001 rev = 0x0000000al
apic...done.$
262     POSTtirq_routing_table() - irq_rosinuxbios ta 0 00 00 00 00 00
06 11 10 60 $
263     0x7$
264     0x60: 00 00 00 00 00 00 02 08 0100 20 00 00 00 $
265     0x80: 00 00 00 00 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 $
266     0xfodev/hda3 console=tty0 $
267     Welcomeea hard coded delay and longer thaclocks_per_usec: 960$
268     .$
269     found PCI IDE controller 1106:0571 prog_if=0x8f$
270     primary channel: native PCI mode$
271     Waiting for ide0 to become ready for reset... ok$
272     Testing for hda$
273     Probing for hda$
274     LBA mode, sectors=40021632$
275     Init device params... ok$
276     hda: LBA 20GB: Maxtor 32049U3                          $
277     Partition 1 start 63 length 2040192$
278     Unknown filesystem type$
279     command terminated by signal 2
real 13.67
user 0.01
sys 0.01
----------------------------------------------
Comments :

This is a BTEXT_CONFIG test
 no payload, no videoROM, no VGABIOS
from a cold boot : no  screen "video mode on" (led goes green)
from a warn boot : the screen flashes but nothing written (bad init?)




Le jeu 13/05/2004 ? 17:49, ron minnich a ?crit :
> On 13 May 2004, Mathieu Deschamps wrote:
> 
> > hum i see ... but didn't we got native LinuxBIOS VGA up on EPIA-M  ? 
> 
> on V1 not V2. It works fine on V1. But ram detection on V1 is not working.

> You only get one size ram.
> 

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


From rminnich at lanl.gov  Fri May 14 11:11:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May 14 11:11:01 2004
Subject: Hibernation?
In-Reply-To: <1084551236.40a4f04477a3b@www.mailshell.com>
Message-ID: <Pine.LNX.4.44.0405141028490.30642-100000@maxroach.lanl.gov>

On Fri, 14 May 2004 lbios_kk at redfenix.com wrote:

> One more question.  To do this effectively we'll need a hook into
> running a BIOS process from inside the OS (trigger to save state and
> shutdown.)  How difficult is this to do?

don't assume anything. 

To do this effectively you need a hook into something. Figure out what 
that thing has to do and then lets' see hwo to do it.

ron



From nacho at estudio-verona.com  Fri May 14 16:17:00 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Fri May 14 16:17:00 2004
Subject: Etherboot version
Message-ID: <32786.192.168.1.5.1084570815.squirrel@mail.estudio-verona.com>

Hi! I've been trying to load linuxbios into my Epia MII but first of all,
I've
a problem with etherboot version. It seems that the latest stable release is
5.0.11 but I can't get it to compile correctly because in src/Config I can't
find the line CFLAGS32 += -DPCIBIOS, but the line -DPCBIOS. If if comment out
this line, etherboot will not compile. What is wrong? Should I use other
version of etherboot? If so, where can I find older releases?

Thanks!


From cforney at opus.com  Fri May 14 18:01:01 2004
From: cforney at opus.com (Craig C Forney)
Date: Fri May 14 18:01:01 2004
Subject: HDAMA+FILO booting SUSE Linux
In-Reply-To: <3174569B9743D511922F00A0C943142305063E11@TYANWEB>
Message-ID: <000401c43a09$e8d64650$6400a8c0@opusone>

YH,

I tried the patch CD for Suse 9.0 Pro.  It works the same (meaning it
doesn't work) as the boxed distribution.

Thanks,

Craig

> -----Original Message-----
> From: YhLu [mailto:YhLu at tyan.com] 
> Sent: Friday, May 14, 2004 9:29 AM
> To: cforney at opus.com; linuxbios at clustermatic.org
> Subject: ??: HDAMA+FILO booting SUSE Linux
> 
> 
> There is one patch CD for Suse 9 pro for AMD DVD, Did you use 
> it boot to install?
> 
> YH
> 
> -----????-----
> ???: Craig C Forney [mailto:cforney at opus.com] 
> ????: 2004?5?14? 2:41
> ???: linuxbios at clustermatic.org
> ??: Re: HDAMA+FILO booting SUSE Linux
> 
> 
> I'm still having problems installing a new disk using 
> LinuxBIOS+FILO on an HDAMA board with a Suse AMD64 distribution.
> 
 




From YhLu at tyan.com  Fri May 14 18:04:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 14 18:04:00 2004
Subject: =?gb2312?B?tPC4tDogSERBTUErRklMTyBib290aW5nIFNVU0UgTGludXg=?=
Message-ID: <3174569B9743D511922F00A0C943142305063E5F@TYANWEB>

Weird. The SUSE 9 for AMD works well with Tyan 2881, s2882, s2885.

Did you try to install in LinuxBIOS directly?

regards

YH

-----????-----
???: Craig C Forney [mailto:cforney at opus.com] 
????: 2004?5?14? 16:19
???: YhLu
??: linuxbios at clustermatic.org
??: RE: HDAMA+FILO booting SUSE Linux


YH,

I tried the patch CD for Suse 9.0 Pro.  It works the same (meaning it
doesn't work) as the boxed distribution.

Thanks,

Craig

> -----Original Message-----
> From: YhLu [mailto:YhLu at tyan.com] 
> Sent: Friday, May 14, 2004 9:29 AM
> To: cforney at opus.com; linuxbios at clustermatic.org
> Subject: ??: HDAMA+FILO booting SUSE Linux
> 
> 
> There is one patch CD for Suse 9 pro for AMD DVD, Did you use 
> it boot to install?
> 
> YH
> 
> -----????-----
> ???: Craig C Forney [mailto:cforney at opus.com] 
> ????: 2004?5?14? 2:41
> ???: linuxbios at clustermatic.org
> ??: Re: HDAMA+FILO booting SUSE Linux
> 
> 
> I'm still having problems installing a new disk using 
> LinuxBIOS+FILO on an HDAMA board with a Suse AMD64 distribution.
> 
 



From YhLu at tyan.com  Fri May 14 19:02:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 14 19:02:00 2004
Subject: =?gb2312?B?tPC4tDogRXRoZXJib290IHZlcnNpb24=?=
Message-ID: <3174569B9743D511922F00A0C943142305063E6F@TYANWEB>

www.etherboot.org

also you need to uncomment the line include -DLINUXBIOS

YH

-----????-----
???: Ignacio Verona [mailto:nacho at estudio-verona.com] 
????: 2004?5?14? 14:40
???: linuxbios at clustermatic.org
??: Etherboot version

Hi! I've been trying to load linuxbios into my Epia MII but first of all,
I've
a problem with etherboot version. It seems that the latest stable release is
5.0.11 but I can't get it to compile correctly because in src/Config I can't
find the line CFLAGS32 += -DPCIBIOS, but the line -DPCBIOS. If if comment
out
this line, etherboot will not compile. What is wrong? Should I use other
version of etherboot? If so, where can I find older releases?

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


From YhLu at tyan.com  Fri May 14 19:42:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 14 19:42:01 2004
Subject: USB boot
Message-ID: <3174569B9743D511922F00A0C943142305063E77@TYANWEB>

Here are the new results.

1. for usb_control_msg: every return + 2047 packet????
2. for bulk_transfer: every out is ok, but every in only return fixed 2048
len data.

Regards

YH

Loading Etherboot version: 5.2.4
ROM segment 0x0000 length 0x0000 reloc 0x00020000
CPU 2285 Mhz
Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO]
Relocating _text from: [0002d5f0,0008fc20) to [efe9d9d0,eff00000)
Probing pci nic...
[tg3-5704]Ethernet addr: 00:E0:81:61:8C:27
Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit)
<abort>
Probing pci nic...
[tg3-5704]Ethernet addr: 00:E0:81:61:8C:28
Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
<abort>
Probing pci nic...
Probing pci disk...
[FILO]FILO version 0.4.1 (root at tst2723-rh9) Fri May 14 17:10:13 PDT 2004
Press <Enter> for default boot, or <Esc> for boot prompt...  
boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
LinuxLabs USB bootloader
raw frame_list is at 00079560
frame_list is at 00079630
frame_list_link: addr: 00078570
frame_list_link:  raw addr: efef5f40
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 00070500
raw frame_list is at 0007b560
frame_list is at 0007b630
frame_list_link: addr: 00078590
frame_list_link:  raw addr: efef5f60
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 00070540
raw frame_list is at 0007d560
frame_list is at 0007d630
frame_list_link: addr: 000785b0
frame_list_link:  raw addr: efef5f80
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 00070580
raw frame_list is at 0007f560
frame_list is at 0007f630
frame_list_link: addr: 000785d0
frame_list_link:  raw addr: efef5fa0
frame_list_link: terminate: 00000000
frame_list_link: queue: 00000001
frame_list_link: depth: 00000000
dummy_td = 000705c0
Found OHCI at 0d182630
Resetting OHCI
USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef7000
Starting OHCI
Found OHCI at 0d183630
Resetting OHCI
USB HC reset_hc usb-0d183630: ctrl = 0x00000600 ;ohc_init setting framelist
to: efef9000
Starting OHCI
Found UHCI at 00002400
Resetting UHCI
uhc_init setting framelist to: efefb000
Starting UHCI
HCI at 00002400
Found UHCI at 00002420
Resetting UHCI
uhc_init setting framelist to: efefd000
Starting UHCI
HCI at 00002420
poll_usb1 i=0   poll_usb1 i=1   poll_usb1 i=2   poll_u_root_hub1 v=00000480
poll_u_root_hub1 v=00001493poll_u_root_hub2 v=00001493     poll_u_root_hub21
v=00001493    Connection on port 00002412
New USB device, setting address 00000003
usb_control_msg: request_type = 00000000 request = 00000005 wLength=0
usb_control_message returning 2047
Fetching device descriptor length
usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
usb_control_message returning 2054
Fetching device descriptor
usb_control_msg: request_type = 00000080 request = 00000006 wLength=18
usb_control_message returning 2064
Fetching config descriptor length
usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
usb_control_message returning 2054
Fetching config descriptor
usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
usb_control_message returning 2078
device:
bLength: 00000012
type: 00000001
bcdVersion: 0000000200000000
Class: 00000000
SubClass: 00000000
protocol: 00000000
max_packet: 00000040
idVendor: 00001005
idProduct: 0000b113
bcdDeviceVersion: 0000000100000000
iManufacturor: 00000000
iProduct: 00000001
iSerial: 00000002
bNumConfig: 00000001
config:
bLength: 00000009
type: 00000002
wTotalLength: 00000020
bNumInterfaces: 00000001
bConfigurationValue: 00000001
iConfiguration: 00000000
bmAttributes: 00000080
bMaxPower: 000000fa

Interface(00081e6b):
        bLength: 00000009
        type: 00000004
        bInterfaceNumber: 00000000
        bAlternateSetting: 00000000
        bNumEndpoints: 00000002
        bInterfaceClass: 00000008
        bInterfaceSubClass: 00000006
        bInterfaceProtocol: 00000050
        iInterface: 00000000

        Endpoint (00081e74):
                bLength: 00000007
                type: 00000005
                bEndpointAddress: 00000081
                bmAttributes: 00000002
                wMaxPacketSize: 00000040
                bInterval: 00000000

        Endpoint (00081e7b):
                bLength: 00000007
                type: 00000005
                bEndpointAddress: 00000002
                bmAttributes: 00000002
                wMaxPacketSize: 00000040
                bInterval: 00000000
Selecting Configuration number 00000001:
usb_control_msg: request_type = 00000000 request = 00000009 wLength=0
usb_control_message returning 2047
clear stall on ep=00000081
usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
usb_control_message returning 2047
clear stall on ep=00000002
usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
usb_control_message returning 2047
00000008:00000006:00000050
Manufacturor: unknown
usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
usb_control_message returning 2050
usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
usb_control_message returning 2078
Product: USB Flash Drive
usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
usb_control_message returning 2050
usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
usb_control_message returning 2078
Serial: 070B01001340CA0
desc address (phy) = efeff820, (virt) = 00081e50
conf address (phy) = efeff832, (virt) = 00081e62
Mass storage, bulk only SCSI transparent
Requesting initial sense data
bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
bulk_transfer: ep = 00000081 len=32
bulk_transfer returning 2048
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
sense data
:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
000000:00000000:00000000:00000000:00000000:00000000:00000000

code = 00000000 key = 00000000

Info: 00000000
bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
scsi_command reading 8 bytes
bulk_transfer: ep = 00000081 len=8
bulk_transfer returning 2048
scsi_command read 2048 bytes
scsi_command fetching csw
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
scsi_command csw is 2048 bytes
1 0 byte blocks
part address (phy) = efeff400, (virt) = 00081a30
bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
scsi_command reading 512 bytes
bulk_transfer: ep = 00000081 len=512
bulk_transfer returning 2048
scsi_command read 2048 bytes
scsi_command fetching csw
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
scsi_command csw is 2048 bytes
ll_read_block returns 512
0: boot=00000000, start=00000000 length=00000000
1: boot=00000000, start=00000000 length=00000000
2: boot=00000000, start=00000000 length=00000000
3: boot=00000000, start=00000000 length=00000000
DEVICE CONFIGURED
poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
poll_usb1 i=0   poll_usb1 i=1poll_usb1 i=2   poll_u_root_hub1 v=00000480
poll_u_root_hub1 v=00000495     poll_usb1 i=3   poll_u_root_hub1 v=00000480
poll_u_root_hub1 v=00000480     Found USB block device 3
Requesting initial sense data
bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
bulk_transfer: ep = 00000081 len=32
bulk_transfer returning 2048
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
sense data
:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
000000:00000000:00000000:00000000:00000000:00000000:00000000

code = 00000000 key = 00000000

Info: 00000000
bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
scsi_command reading 512 bytes
bulk_transfer: ep = 00000081 len=512
bulk_transfer returning 2048
scsi_command read 2048 bytes
scsi_command fetching csw
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
scsi_command csw is 2048 bytes
ll_read_block returns 512
part address (phy) = efeffa94, (virt) = 000820c4
0: boot=00000000, start=00000000 length=00000000
1: boot=00000000, start=00000000 length=00000000
2: boot=00000000, start=00000000 length=00000000
3: boot=00000000, start=00000000 length=00000000
sector= 0     bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
scsi_command reading 512 bytes
bulk_transfer: ep = 00000081 len=512
bulk_transfer returning 2048
scsi_command read 2048 bytes
scsi_command fetching csw
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
scsi_command csw is 2048 bytes
sector= 68      bulk_transfer: ep = 00000002 len=31
bulk_transfer returning 31
scsi_command reading 512 bytes
bulk_transfer: ep = 00000081 len=512
bulk_transfer returning 2048
scsi_command read 2048 bytes
scsi_command fetching csw
bulk_transfer: ep = 00000081 len=13
bulk_transfer returning 2048
scsi_command csw is 2048 bytes


From nacho at estudio-verona.com  Sat May 15 02:28:00 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Sat May 15 02:28:00 2004
Subject: =?gb2312?q?=B4=F0=B8=B4=3A_Etherboot?= version
In-Reply-To: <3174569B9743D511922F00A0C943142305063E6F@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063E6F@TYANWEB>
Message-ID: <200405150945.35156.nacho@estudio-verona.com>

Sorry, I forgot to mention that I did also uncomment the line -DLINUXBIOS ... 
but then etherboot do not compile. Also, "make bin32/via-rhine.ebi" doesn't 
work. The only compilation I did get was with default config (Config) and 
using "make". This leaves all the images under bin32, but no .ebi file...


From nacho at estudio-verona.com  Sat May 15 09:52:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Sat May 15 09:52:01 2004
Subject: LinuxBios now working on Epia MII-10000
In-Reply-To: <3174569B9743D511922F00A0C943142305063E11@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063E11@TYANWEB>
Message-ID: <200405151709.40347.nacho@estudio-verona.com>

At least, I've linuxbios booting my kernel with filo. Now I've a few 
questions:

1. When booting, it stops about 2 o 3 secs on "Jumping to entry point". Is 
this normal? Can't I reduce this time? (My main purpouse of using LB is for 
getting as small boot time as possible for my in-car PC)

2. Can I get acpi to work on Epia? I mean, halt and power-off the system?

thanks!!


From yhlu at tyan.com  Sun May 16 00:11:01 2004
From: yhlu at tyan.com (Yinghai Lu)
Date: Sun May 16 00:11:01 2004
Subject: =?gb2312?B?tPC4tDogtPC4tDogRXRoZXJib290IHZlcnNpb24=?=
In-Reply-To: <200405150945.35156.nacho@estudio-verona.com>
Message-ID: <200405160410.i4G4AAK28547@nwn.definitive.org>

There is bug in Etherboot in old version.

So use 
make bin/tg3.zelf

-----????-----
???: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] ?? Ignacio Verona
????: 2004?5?15? 0:46
???: linuxbios at clustermatic.org
??: Re: ??: Etherboot version

Sorry, I forgot to mention that I did also uncomment the line -DLINUXBIOS
... 
but then etherboot do not compile. Also, "make bin32/via-rhine.ebi" doesn't 
work. The only compilation I did get was with default config (Config) and 
using "make". This leaves all the images under bin32, but no .ebi file...
_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios



From stepan at openbios.org  Sun May 16 10:34:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sun May 16 10:34:00 2004
Subject: EPIA-M startup times
In-Reply-To: <003e01c4391a$896e80f0$8000a8c0@debbie>
References: <BAY10-F119gIjOiwsN300005a20@hotmail.com> <003e01c4391a$896e80f0$8000a8c0@debbie>
Message-ID: <20040516155450.GA22889@openbios.org>

* John Laur <johnl at blurbco.com> [040513 20:46]:
> Then you can worry about the kernel. VESA Framebuffer does not work with
> EPIA-M as the VGA bios doesn't initialize the video card up to where
> vesafb can take over. You have to use viafb (part of the -epia patchset)
> to get video on the console. Make sure you have it compiled into the
> kernel and not as a module. Make sure vesafb is NOT compiled in either,
> otherwise you'll need some commandline trickery to make it work. Also,
> viafb doesn't work with bootsplash in silent mode on kernel 2.4 if you
> are using that. I have not tested with kernel 2.6.

Bootsplash as in www.bootsplash.org? Can you provide a log or some
details?

  Stefan



From stepan at openbios.org  Sun May 16 10:53:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sun May 16 10:53:01 2004
Subject: ????: HDAMA+FILO booting SUSE Linux
In-Reply-To: <3174569B9743D511922F00A0C943142305063D81@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063D81@TYANWEB>
Message-ID: <20040516161402.GC22889@openbios.org>

* YhLu <YhLu at tyan.com> [040513 19:33]:
> Are you using Suse 9 pro for AMD64 or for i386?
> 
> I guess you are using for i386. 

Nope, it worked on Solo with both, but I normally only use the AMD64
version.

Stefan




From stepan at openbios.org  Sun May 16 11:25:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sun May 16 11:25:00 2004
Subject: LinuxBios now working on Epia MII-10000
In-Reply-To: <200405151709.40347.nacho@estudio-verona.com>
References: <3174569B9743D511922F00A0C943142305063E11@TYANWEB> <200405151709.40347.nacho@estudio-verona.com>
Message-ID: <20040516164552.GE22889@openbios.org>

* Ignacio Verona <nacho at estudio-verona.com> [040515 17:09]:
> 1. When booting, it stops about 2 o 3 secs on "Jumping to entry point". Is 
> this normal? Can't I reduce this time? (My main purpouse of using LB is for 
> getting as small boot time as possible for my in-car PC)
 
It's probably Linux' setup of internal structures just before output is
made?

> 2. Can I get acpi to work on Epia? I mean, halt and power-off the system?

The framework is there, but support for Epia is not in yet. If you have
some time, give it a try to implement this.. it would be really useful!

Stefan



From nacho at estudio-verona.com  Sun May 16 14:24:00 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Sun May 16 14:24:00 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
Message-ID: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>

Hi! Linuxbios is working prety well now on my Epia mII 10k, but a few
problems:

1. I can't get VGA to work. I've extracted it from a original-bios booted
system with
    dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528
and then appended it to my filo payload like the HOWTO says I've to do,
and modified the config file with all the options in EPIA howto, but
nothing shows up on my monitor (tft screen, has it something to do with?)

2. If I boot up my mobo without the PCMCIA/CF module on, it boots properly
but, if I put it on and try to boot, linux bios does somethings and then
reboot, forever. any known bug about this?

thanks!



From nacho at estudio-verona.com  Sun May 16 14:44:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Sun May 16 14:44:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>
References: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>
Message-ID: <2690.192.168.1.3.1084738051.squirrel@mail.estudio-verona.com>

Here is the complete log of my bootup process, from bios to log-in... I
can't understand so much of the bios part :(

LinuxBIOS-1.0.0 Sun May 16 23:28:22 CEST 2004 starting...
80 08 07 0d 0a 02 40 00 04 60 70 00 82 08 00 01
0e ff 0c ff ff ff ff ff ff ff ff 48 30 ff ff 40
75 75 45 45 00 00 00 00 00 3c 48 30 2d 55 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
c1 49 4e 46 49 4e 45 4f 45 36 34 44 36 34 33 32
30 47 55 36 42 20 20 20 20 20 20 01 09 03 10 02
27 e6 18 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.0.0 Sun May 16 23:28:22 CEST 2004 booting...
Finding PCI configuration type.
PCI: Using configuration type 1
Scanning PCI bus...PCI: pci_scan_bus for bus 0
PCI: 00:00.0 [1106/3123]
PCI: 00:01.0 [1106/b091]
PCI: 00:10.0 [1106/3038]
PCI: 00:10.1 [1106/3038]
PCI: 00:10.2 [1106/3038]
PCI: 00:10.3 [1106/3104]
PCI: 00:11.0 [1106/3177]
PCI: 00:11.1 [1106/0571]
PCI: 00:11.5 [1106/3059]
PCI: 00:12.0 [1106/3065]
PCI: pci_scan_bus for bus 1
PCI: 01:00.0 [1106/3122]
PCI: pci_scan_bus returning with max=01
PCI: pci_scan_bus returning with max=01
done
Allocating PCI resources...
PCI: 00:00.0 register 10(00000008), read-only ignoring it
PCI: 00:00.0 register 10(00000008), read-only ignoring it
PCI: 00:00.0 register 10(00000008), read-only ignoring it
PCI: 00:00.0 register 10(00000008), read-only ignoring it
ASSIGN RESOURCES, bus 0
PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io
PCI: 00:01.0 24 <- [0xf8000000 - 0xfbffffff] bus 1 prefmem
PCI: 00:01.0 20 <- [0xfc000000 - 0xfcffffff] bus 1 mem
ASSIGN RESOURCES, bus 1
PCI: 01:00.0 10 <- [0xf8000000 - 0xfbffffff] prefmem
PCI: 01:00.0 14 <- [0xfc000000 - 0xfcffffff] mem
ASSIGNED RESOURCES, bus 1
PCI: 00:10.0 20 <- [0x00001800 - 0x0000181f] io
PCI: 00:10.1 20 <- [0x00001820 - 0x0000183f] io
PCI: 00:10.2 20 <- [0x00001840 - 0x0000185f] io
PCI: 00:10.3 10 <- [0xfd000000 - 0xfd0000ff] mem
PCI: 00:11.1 20 <- [0x00001860 - 0x0000186f] io
PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io
PCI: 00:12.0 10 <- [0x00001400 - 0x000014ff] io
PCI: 00:12.0 14 <- [0xfd001000 - 0xfd0010ff] mem
ASSIGNED RESOURCES, bus 0
Allocating VGA resource
done.
Enabling PCI resourcess...PCI: 00:00.0 cmd <- 06
PCI: 00:01.0 cmd <- 07
PCI: 00:10.0 cmd <- 01
PCI: 00:10.1 cmd <- 01
PCI: 00:10.2 cmd <- 01
PCI: 00:10.3 cmd <- 02
PCI: 00:11.0 cmd <- 07
PCI: 00:11.1 cmd <- 07
PCI: 00:11.5 cmd <- 01
PCI: 00:12.0 cmd <- 83
PCI: 01:00.0 cmd <- 03
done.
Initializing PCI devices...
PCI devices initialized
totalram: 96M
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:   64MB, type WB
Setting variable MTRR 1, base:   64MB, range:   32MB, 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          : CentaurHauls
Processor Type     : 0x00
Processor Family   : 0x06
Processor Model    : 0x09
Processor Mask     : 0x00
Processor Stepping : 0x05
Feature flags      : 0x0380b13d


MTRR check
Fixed MTRRs   : Enabled
Variable MTRRs: Enabled

Disabling local apic...done.
CPU #0 Initialized
Mainboard fixup
Final mainboard fixup
Southbridge fixup
setting firewire
setting usb
Assigning IRQ 11 to 0:10.0
  Readback = 11
Assigning IRQ 10 to 0:10.1
  Readback = 10
Assigning IRQ 12 to 0:10.2
  Readback = 12
Assigning IRQ 5 to 0:10.3
  Readback = 5
setting vt8235
Assigning IRQ 5 to 0:11.1
  Readback = 5
Assigning IRQ 12 to 0:11.5
  Readback = 12
setting ethernet
Assigning IRQ 11 to 0:12.0
  Readback = 11
setting vga
Assigning IRQ 11 to 1:0.0
  Readback = 11
setting pci slot
setting vt8235 slot
Assigning IRQ 5 to 0:11.1
  Readback = 5
Assigning IRQ 12 to 0:11.5
  Readback = 12
INSTALL REAL-MODE IDT
DO THE VGA BIOS
found VGA: vid=1106, did=3122
write_protect_vgabios
0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca 0x83 0x0 0x0 0x0
0x0 bus/
devfn = 0x100
biosint: # 0x15, eax 0x5f00 ebx 0x100 ecx 0x100 edx 0xa1ff
biosint: ebp 0x123a0 esp 0xff2 edi 0xe40c esi 0x12c04
biosint: ip 0x641c cs 0xc000 flags 0x46
biosint: # 0x1a, eax 0xb108 ebx 0x0 ecx 0x0 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfcc edi 0xf6 esi 0x1c01b
biosint: ip 0x40f0 cs 0xc000 flags 0x46
0xb108: bus 0 devfn 0x0 reg 0xf6 val 0x11
biosint: # 0x15, eax 0x5f02 ebx 0x100 ecx 0x101 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfdc edi 0x44 esi 0x1c01b
biosint: ip 0x6468 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x5 edx 0x112
biosint: ebp 0x123a0 esp 0xfa4 edi 0x44 esi 0x1aacd
biosint: ip 0x6448 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x5 edx 0x112
biosint: ebp 0x123a0 esp 0xfa4 edi 0x44 esi 0x1aacd
biosint: ip 0x6448 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x5 edx 0x112
biosint: ebp 0x123a0 esp 0xf92 edi 0x44 esi 0x1aacd
biosint: ip 0x6448 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f02 ebx 0x300 ecx 0x1 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfb8 edi 0x44 esi 0x1c01b
biosint: ip 0x6468 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f02 ebx 0x300 ecx 0x1 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfb8 edi 0x44 esi 0x1c01b
biosint: ip 0x6468 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f02 ebx 0x300 ecx 0x1 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfb8 edi 0x44 esi 0x1c01b
biosint: ip 0x6468 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f0f ebx 0x100 ecx 0x100 edx 0x3d5
biosint: ebp 0x123a0 esp 0xfee edi 0x44 esi 0x12c04
biosint: ip 0x651b cs 0xc000 flags 0x2
biosint: # 0x15, eax 0x5f02 ebx 0x0 ecx 0x1 edx 0x0
biosint: ebp 0x123a0 esp 0xfdc edi 0x44 esi 0x12c04
biosint: ip 0x6468 cs 0xc000 flags 0x46
biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x700 edx 0x112
biosint: ebp 0x10fca esp 0xf8e edi 0xac51 esi 0x1aacd
biosint: ip 0x6448 cs 0xc000 flags 0x46
biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
biosint: ebp 0x10fca esp 0xfc0 edi 0xb880 esi 0x1010a
biosint: ip 0x188 cs 0xc000 flags 0x246
biosint: Unsupport int #0xb8
Checking IRQ routing tables...
/usr/src/freebios/src/arch/i386/lib/pirq_routing.c:   
30:check_pirq_routing_tab
le() - irq_routing_table located at: 0x0000a400
done.
Copying IRQ routing tables to 0xf0000...done.
Verifing priq routing tables copy at 0xf0000...failed
Wrote linuxbios table at: 00000500 - 00000670  checksum e006

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

    37:init_bytes() - zkernel_start:0xfffd0000  zkernel_mask:0x0000ffff
Found ELF candiate at offset 0
New segment addr 0x100000 size 0x20fb0 offset 0xa0 filesize 0x7000
(cleaned up) New segment addr 0x100000 size 0x20fb0 offset 0xa0 filesize
0x7000
New segment addr 0x120fc0 size 0x60 offset 0x70a0 filesize 0x60
(cleaned up) New segment addr 0x120fc0 size 0x60 offset 0x70a0 filesize 0x60
Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000020fb0
filesz: 0x00
00000000007000
Clearing Segment: addr: 0x0000000000107000 memsz: 0x0000000000019fb0
Loading Segment: addr: 0x0000000000120fc0 memsz: 0x0000000000000060
filesz: 0x00
00000000000060
Jumping to boot code at 0x104c1c
FILO version 0.4 (root at AMBox) Sun May 16 11:57:40 CEST 2004
boot: hda1:/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200
hda: LBA 78GB: ST380021A
Mounted ext2fs
Found Linux version 2.6.5 (root at AMBox) #5 Sun May 16 23:27:43 CEST 2004
bzImage.
Loading kernel... ok
Jumping to entry point...
Linux version 2.6.5 (root at AMBox) (gcc version 2.95.4 20011002 (Debian
prerelease
)) #5 Sun May 16 23:27:43 CEST 2004
BIOS-provided physical RAM map:
 BIOS-e820: 00000000000006d8 - 00000000000a0000 (usable)
 BIOS-e820: 0000000000100000 - 0000000006000000 (usable)
96MB LOWMEM available.
On node 0 totalpages: 24576
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 20480 pages, LIFO batch:5
  HighMem zone: 0 pages, LIFO batch:1
DMI not present.
ACPI: Unable to locate RSDP
Built 1 zonelists
Kernel command line: root=/dev/hda1 console=tty0 console=ttyS0,115200
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Detected 999.655 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Memory: 94924k/98304k available (1201k kernel code, 2860k reserved, 470k
data, 8
8k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1974.27 BogoMIPS
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: Centaur VIA Nehemiah stepping 05
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: Using configuration type 1
Linux Kernel Card Services
  options:  [pci] [cardbus]
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
udf: registering filesystem
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
via-rhine.c:v1.10-LK1.1.19-2.5  July-12-2003  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
eth0: VIA VT6102 Rhine-II at 0x1400, 00:40:63:d5:8b:8e, IRQ 11.
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: ST380021A, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63
 hda: hda1 hda2 hda3
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT2-fs warning (device hda1): ext2_fill_super: mounting ext3 filesystem
as ext2

VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 88k freed
INIT: version 2.84 booting
Loading /etc/console/boottime.kmap.gz
Activating swap.
Adding 240964k swap on /dev/hda2.  Priority:-1 extents:1
Checking root file system...
fsck 1.27 (8-Mar-2002)
/dev/hda1: clean, 62343/1221600 files, 250294/2441872 blocks
System time was Sun May 16 21:29:54 UTC 2004.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Sun May 16 21:29:54 UTC 2004.
Checking all file systems...
fsck 1.27 (8-Mar-2002)
Setting kernel variables.
Loading the saved-state of the serial devices...
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1: LSR safety check engaged!
ttyS1: LSR safety check engaged!
/dev/ttyS1 at 0x02f8 (irq = 3) is a 16550A
Mounting local filesystems...
nothing was mounted
Running 0dns-down to make sure resolv.conf is ok...done.
Cleaning: /etc/network/ifstate.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces: eth0: Setting full-duplex based on MII #1
link p
artner capability of 45e1.
done.
Starting portmap daemon: portmap.
R
Setting the System Clock using the Hardware Clock as reference...
System Clock set. Local time: Sun May 16 23:29:57 CEST 2004

Cleaning: /tmp /var/lock /var/run.
Initializing random number generator... done.
Recovering nvi editor sessions... done.
INIT: Entering runlevel: 2
Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting internet superserver: inetd.
Starting MySQL database server: mysqld.
Starting PCMCIA services: cardmgr.
Starting OpenBSD Secure Shell server: sshd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.

Debian GNU/Linux 3.0 AMBox ttyS0

AMBox login:


From rminnich at lanl.gov  Sun May 16 20:49:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Sun May 16 20:49:00 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>
Message-ID: <Pine.LNX.4.44.0405162006580.3792-100000@maxroach.lanl.gov>

On Sun, 16 May 2004, Ignacio Verona wrote:

> 1. I can't get VGA to work. I've extracted it from a original-bios booted
> system with
>     dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528
> and then appended it to my filo payload like the HOWTO says I've to do,
> and modified the config file with all the options in EPIA howto, but
> nothing shows up on my monitor (tft screen, has it something to do with?)
                                  ^^^
uh oh. Send me serial output.

> 2. If I boot up my mobo without the PCMCIA/CF module on, it boots properly
> but, if I put it on and try to boot, linux bios does somethings and then
> reboot, forever. any known bug about this?

sounds like you just found one :-)

need serial output.

ron



From rminnich at lanl.gov  Sun May 16 20:51:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Sun May 16 20:51:00 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <2690.192.168.1.3.1084738051.squirrel@mail.estudio-verona.com>
Message-ID: <Pine.LNX.4.44.0405162008110.3792-100000@maxroach.lanl.gov>

On Sun, 16 May 2004, Ignacio Verona wrote:

> biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
> biosint: ebp 0x10fca esp 0xfc0 edi 0xb880 esi 0x1010a
> biosint: ip 0x188 cs 0xc000 flags 0x246
> biosint: Unsupport int #0xb8

b8? Anybody know what that one is?

ron



From nacho at estudio-verona.com  Mon May 17 02:39:00 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Mon May 17 02:39:00 2004
Subject: Epia-MII VGA not working ...
In-Reply-To: <1084779446.15547.52.camel@Calliphara>
References: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>
    <1084779446.15547.52.camel@Calliphara>
Message-ID: <2963.192.168.1.3.1084780948.squirrel@mail.estudio-verona.com>

Ron:
Thanks for your answ. Reading the serial output can you say something
about the PCMCIA problem?
And what about tft? May be cause VGA no to work? Right now I do not have
any CRTs here...

Mathieu:
Yes, I'm on v1 right now. And about the combined filo+vgabios payload this
is what I do for creating:
      dd if=filo.elf of=vga+filo.bin bs=1 seek=65536
And using vga+filo.bin as my payload linuxbios still boot up to the
kernel, but VGA does not come up.

Maybe could I go to V2 for beeing exactly on the same point as you? I
could give it a try this tonight.

Also: Do you know if acpi is working on V2? I've plans to "try" (only try,
I don't know if I've the required programming skills) to implement it on
v1, but if it's working on v2 I could skip this step and do all the job on
VGA.

Thanks!

> Hi
>
> It seems i am on the same point as you. This project is simply
> fascinating, and so much time consuming :)
>
> I've done this famous dd with the kcore and so on, but i think to do
> miss something.
> I've got a classic crt screen but nothing appear either.  Also I'am
> working with v2 . my Linuxbios is booting to the kernel so this is ok.
>
> What is not, is that VGABIOS on V2 LB is not fully operationnal, i want
> to make it be. Please could you tell me how you did "append it to my
> filo payload like the HOWTO says and modified the config file" as ?
> It could geratly help me in trying to make a port to V2 since i've
> understood you are in V1, don't you ?
>
> Though the details of your experiments could unstuck me.
>
>
> Le dim 16/05/2004 ?? 21:47, Ignacio Verona a ??crit :
>> Hi! Linuxbios is working prety well now on my Epia mII 10k, but a few
>> problems:
>>
>> 1. I can't get VGA to work. I've extracted it from a original-bios
>> booted
>> system with
>>     dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528
>> and then appended it to my filo payload like the HOWTO says I've to do,
>> and modified the config file with all the options in EPIA howto, but
>> nothing shows up on my monitor (tft screen, has it something to do
>> with?)
>>
>> 2. If I boot up my mobo without the PCMCIA/CF module on, it boots
>> properly
>> but, if I put it on and try to boot, linux bios does somethings and then
>> reboot, forever. any known bug about this?
>>
>> thanks!
>>
>> _______________________________________________
>> Linuxbios mailing list
>> Linuxbios at clustermatic.org
>> http://www.clustermatic.org/mailman/listinfo/linuxbios
>>
>



From mdeschamps at mangrove-systems.com  Mon May 17 03:35:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Mon May 17 03:35:01 2004
Subject: Epia-MII VGA not working ...
In-Reply-To: <2963.192.168.1.3.1084780948.squirrel@mail.estudio-verona.com>
References: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com>
	 <1084779446.15547.52.camel@Calliphara>
	 <2963.192.168.1.3.1084780948.squirrel@mail.estudio-verona.com>
Message-ID: <1084783954.15547.81.camel@Calliphara>

well you can try to V2 but you'll see that VGA bios isn't as far
"worked" as it is in v1.
I'am not as far as you've gone, because you have this i don't:

INSTALL REAL-MODE IDT
DO THE VGA BIOS
found VGA: vid=1106, did=3122
write_protect_vgabios
0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca 0x83 0x0 0x0 0x0
0x0 bus/

in fact i'am still seeking the HOWTOs of this (even for V1) in maillist
and such, i've found some piece of info but nothing explaining what to
do like some sort of step by step experiment... that is why I was likely
to ask your way :) or your links to theses howto. 

I know almost only V2, i've been working on V1 only a few weeks, then i 
fork to V2 and still work mainly on it.
V2 is totaly refactored, romcc compiler is a central part. Probally the
harder as I felt, is to find the good combinaison of config option
corresponding to v1 ones. for example, if i'am not mistaken, v2 has no
IDT config option for VGA bios, thus making you wonder where to start
with V2 VGAbios. All that said, i found in V2 an answer to the need 
of structure/architecture V1 spotted, and the source tree is a lot
"clearer" and  "close" solutions were incorporated .. 

Also i think acpi isn't more worked on v2, i've read to deact. it
anytime i could as i done; but I'am not sure maybe some other people
won't confirm.

mathieu
 


Le lun 17/05/2004 ? 10:02, Ignacio Verona a ?crit :
> Ron:
> Thanks for your answ. Reading the serial output can you say something
> about the PCMCIA problem?
> And what about tft? May be cause VGA no to work? Right now I do not have
> any CRTs here...
> 
> Mathieu:
> Yes, I'm on v1 right now. And about the combined filo+vgabios payload this
> is what I do for creating:
>       dd if=filo.elf of=vga+filo.bin bs=1 seek=65536
> And using vga+filo.bin as my payload linuxbios still boot up to the
> kernel, but VGA does not come up.
> 
> Maybe could I go to V2 for beeing exactly on the same point as you? I
> could give it a try this tonight.
> 
> Also: Do you know if acpi is working on V2? I've plans to "try" (only try,
> I don't know if I've the required programming skills) to implement it on
> v1, but if it's working on v2 I could skip this step and do all the job on
> VGA.
> 
> Thanks!
> 
> > Hi
> >
> > It seems i am on the same point as you. This project is simply
> > fascinating, and so much time consuming :)
> >
> > I've done this famous dd with the kcore and so on, but i think to do
> > miss something.
> > I've got a classic crt screen but nothing appear either.  Also I'am
> > working with v2 . my Linuxbios is booting to the kernel so this is ok.
> >
> > What is not, is that VGABIOS on V2 LB is not fully operationnal, i want
> > to make it be. Please could you tell me how you did "append it to my
> > filo payload like the HOWTO says and modified the config file" as ?
> > It could geratly help me in trying to make a port to V2 since i've
> > understood you are in V1, don't you ?
> >
> > Though the details of your experiments could unstuck me.
> >
> >
> > Le dim 16/05/2004 ?  21:47, Ignacio Verona a ??crit :
> >> Hi! Linuxbios is working prety well now on my Epia mII 10k, but a few
> >> problems:
> >>
> >> 1. I can't get VGA to work. I've extracted it from a original-bios
> >> booted
> >> system with
> >>     dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528
> >> and then appended it to my filo payload like the HOWTO says I've to do,
> >> and modified the config file with all the options in EPIA howto, but
> >> nothing shows up on my monitor (tft screen, has it something to do
> >> with?)
> >>
> >> 2. If I boot up my mobo without the PCMCIA/CF module on, it boots
> >> properly
> >> but, if I put it on and try to boot, linux bios does somethings and then
> >> reboot, forever. any known bug about this?
> >>
> >> thanks!
> >>
> >> _______________________________________________
> >> 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
> 


From nacho at estudio-verona.com  Mon May 17 05:42:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Mon May 17 05:42:01 2004
Subject: AW: LinuxBios now working on Epia MII-10000
In-Reply-To:      <CFE6A2529AC5FA439B3D852B0F2A68372A15D6@OEKAW2EXVS02.hbi.ad.harman.com
     >
References:     <CFE6A2529AC5FA439B3D852B0F2A68372A15D6@OEKAW2EXVS02.hbi.ad.harman.com>
Message-ID: <1171.130.206.72.205.1084791928.squirrel@mail.estudio-verona.com>

Ingo: I've been working on linuxbios for 2 weeks or so (Delayed by
BiosSavior not working properly :( ) and what I have now is (as I've said
in subject, Epia mII-10000 but I think almost everything should work on
epia-m as well):

LinuxBios booting, from hw detection to linux login on serial console,
with on-board ethernet. I haven't tested sound so far, my main goal was to
boot with linuxbios.

what I do not have is:
VGA working (It seems to detect, but monitor doesn't show anything).
PCMCIA/CF slot. If I boot with them on board linuxbios will reboot forever.

More about car-pc: Is my final course proyect, and I will do an interface
for controlling mp3/video playing, maybe a modification to GiantDisc, but
I'm still not sure.

If u want to know anything else, please, let me know.


> Hello Ignacio,
> I want to start also a in-car-project, can you
> inform me about the state of your project?
> How far are you, what is working ;))?
> Thank You,
> -Ingo from Germany
>
> -----Urspr??ngliche Nachricht-----
> Von: Ignacio Verona [mailto:nacho at estudio-verona.com]
> Gesendet: Samstag, 15. Mai 2004 17:10
> An: linuxbios at clustermatic.org
> Betreff: LinuxBios now working on Epia MII-10000
>
>
> At least, I've linuxbios booting my kernel with filo. Now I've a few
> questions:
>
> 1. When booting, it stops about 2 o 3 secs on "Jumping to entry point". Is
> this normal? Can't I reduce this time? (My main purpouse of using LB is
> for
> getting as small boot time as possible for my in-car PC)
>
> 2. Can I get acpi to work on Epia? I mean, halt and power-off the system?
>
> thanks!!
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>
>
> *******************************************
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
> loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the contents in this
> e-mail is strictly forbidden.
> *******************************************
>
>



From nacho at estudio-verona.com  Mon May 17 07:43:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Mon May 17 07:43:01 2004
Subject: AW: LinuxBios now working on Epia MII-10000
In-Reply-To:      <CFE6A2529AC5FA439B3D852B0F2A68372A15D8@OEKAW2EXVS02.hbi.ad.harman.com
     >
References:     <CFE6A2529AC5FA439B3D852B0F2A68372A15D8@OEKAW2EXVS02.hbi.ad.harman.com>
Message-ID: <3332.130.206.72.205.1084799199.squirrel@mail.estudio-verona.com>

Ok, tonight I'll send you a ready-to-burn image, and please, if you burn
it with bios savior, try to write your experience. I've had a lot of
problems using it, and finally, i'm using two flash I get from a local
distributor (for free :D), but biosSavior is not working.

> Sounds interessting, I want a simialr thing (for private)
> but didn't start for now..  I bought This Bios-Savior now, -
> can you provide me a bootable "ready ROM" for a quick test?
>
> Regards,
> -Ingo
>
>
> -----Urspr?ngliche Nachricht-----
> Von: Ignacio Verona [mailto:nacho at estudio-verona.com]
> Gesendet: Montag, 17. Mai 2004 13:05
> An: Baab, Ingo
> Cc: linuxbios at clustermatic.org
> Betreff: AW: LinuxBios now working on Epia MII-10000
>
>
> Ingo: I've been working on linuxbios for 2 weeks or so (Delayed by
> BiosSavior not working properly :( ) and what I have now is (as I've said
> in subject, Epia mII-10000 but I think almost everything should work on
> epia-m as well):
>
> LinuxBios booting, from hw detection to linux login on serial console,
> with on-board ethernet. I haven't tested sound so far, my main goal was to
> boot with linuxbios.
>
> what I do not have is:
> VGA working (It seems to detect, but monitor doesn't show anything).
> PCMCIA/CF slot. If I boot with them on board linuxbios will reboot
> forever.
>
> More about car-pc: Is my final course proyect, and I will do an interface
> for controlling mp3/video playing, maybe a modification to GiantDisc, but
> I'm still not sure.
>
> If u want to know anything else, please, let me know.
>
>
>> Hello Ignacio,
>> I want to start also a in-car-project, can you
>> inform me about the state of your project?
>> How far are you, what is working ;))?
>> Thank You,
>> -Ingo from Germany
>>
>> -----Urspr??ngliche Nachricht-----
>> Von: Ignacio Verona [mailto:nacho at estudio-verona.com]
>> Gesendet: Samstag, 15. Mai 2004 17:10
>> An: linuxbios at clustermatic.org
>> Betreff: LinuxBios now working on Epia MII-10000
>>
>>
>> At least, I've linuxbios booting my kernel with filo. Now I've a few
>> questions:
>>
>> 1. When booting, it stops about 2 o 3 secs on "Jumping to entry point".
>> Is
>> this normal? Can't I reduce this time? (My main purpouse of using LB is
>> for
>> getting as small boot time as possible for my in-car PC)
>>
>> 2. Can I get acpi to work on Epia? I mean, halt and power-off the
>> system?
>>
>> thanks!!
>> _______________________________________________
>> Linuxbios mailing list
>> Linuxbios at clustermatic.org
>> http://www.clustermatic.org/mailman/listinfo/linuxbios
>>
>>
>> *******************************************
>> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
>> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
>> E-Mail
>> irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender
>> und
>> loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
>> Weitergabe dieser Mail ist nicht gestattet.
>>
>> This e-mail may contain confidential and/or privileged information. If
>> you
>> are not the intended recipient (or have received this e-mail in error)


>> please notify the sender immediately and delete this e-mail. Any
>> unauthorized copying, disclosure or distribution of the contents in this
>> e-mail is strictly forbidden.
>> *******************************************
>>
>>
>
>
> *******************************************
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
> loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the contents in this
> e-mail is strictly forbidden.
> *******************************************
>
>



From pyro at linuxlabs.com  Mon May 17 07:55:00 2004
From: pyro at linuxlabs.com (Steven James)
Date: Mon May 17 07:55:00 2004
Subject: USB boot
In-Reply-To: <3174569B9743D511922F00A0C943142305063E77@TYANWEB>
References: <3174569B9743D511922F00A0C943142305063E77@TYANWEB>
Message-ID: <Pine.LNX.4.58.0405171303210.26413@ucontrol.mobiledns.com>

Greetings,

Sorry about the delay in replying.

The length field is encoded as n-1 with 0x7ff a special value meaning 0.

IIRC, a USB protocol error would cause a stall condition. A 0 transfer
when data is expected is a SCSI level error.

As you can see, the USB code doesn't have nearly enough error checking.

It looks like control messages are fine since the device gets configured,
but the bulk transfers seem to be broken.

It might be good to write poison to the buffers to verify that no data
goes to them.

Since everything seems to be returning no data, probably the SCSI command
is not being sent to the device correctly.

Hopefully, this week, I can get my test board going again so I can do some
debugging as well.

G'day,
sjames


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


On Fri, 14 May 2004, YhLu wrote:

> Here are the new results.
>
> 1. for usb_control_msg: every return + 2047 packet????
> 2. for bulk_transfer: every out is ok, but every in only return fixed 2048
> len data.
>
> Regards
>
> YH
>
> Loading Etherboot version: 5.2.4
> ROM segment 0x0000 length 0x0000 reloc 0x00020000
> CPU 2285 Mhz
> Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO]
> Relocating _text from: [0002d5f0,0008fc20) to [efe9d9d0,eff00000)
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:27
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:28
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> Probing pci disk...
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Fri May 14 17:10:13 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt...
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 00079560
> frame_list is at 00079630
> frame_list_link: addr: 00078570
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070500
> raw frame_list is at 0007b560
> frame_list is at 0007b630
> frame_list_link: addr: 00078590
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070540
> raw frame_list is at 0007d560
> frame_list is at 0007d630
> frame_list_link: addr: 000785b0
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070580
> raw frame_list is at 0007f560
> frame_list is at 0007f630
> frame_list_link: addr: 000785d0
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705c0
> Found OHCI at 0d182630
> Resetting OHCI
> USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting framelist
> to: efef7000
> Starting OHCI
> Found OHCI at 0d183630
> Resetting OHCI
> USB HC reset_hc usb-0d183630: ctrl = 0x00000600 ;ohc_init setting framelist
> to: efef9000
> Starting OHCI
> Found UHCI at 00002400
> Resetting UHCI
> uhc_init setting framelist to: efefb000
> Starting UHCI
> HCI at 00002400
> Found UHCI at 00002420
> Resetting UHCI
> uhc_init setting framelist to: efefd000
> Starting UHCI
> HCI at 00002420
> poll_usb1 i=0   poll_usb1 i=1   poll_usb1 i=2   poll_u_root_hub1 v=00000480
> poll_u_root_hub1 v=00001493poll_u_root_hub2 v=00001493     poll_u_root_hub21
> v=00001493    Connection on port 00002412
> New USB device, setting address 00000003
> usb_control_msg: request_type = 00000000 request = 00000005 wLength=0
> usb_control_message returning 2047
> Fetching device descriptor length
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
> usb_control_message returning 2054
> Fetching device descriptor
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=18
> usb_control_message returning 2064
> Fetching config descriptor length
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
> usb_control_message returning 2054
> Fetching config descriptor
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> device:
> bLength: 00000012
> type: 00000001
> bcdVersion: 0000000200000000
> Class: 00000000
> SubClass: 00000000
> protocol: 00000000
> max_packet: 00000040
> idVendor: 00001005
> idProduct: 0000b113
> bcdDeviceVersion: 0000000100000000
> iManufacturor: 00000000
> iProduct: 00000001
> iSerial: 00000002
> bNumConfig: 00000001
> config:
> bLength: 00000009
> type: 00000002
> wTotalLength: 00000020
> bNumInterfaces: 00000001
> bConfigurationValue: 00000001
> iConfiguration: 00000000
> bmAttributes: 00000080
> bMaxPower: 000000fa
>
> Interface(00081e6b):
>         bLength: 00000009
>         type: 00000004
>         bInterfaceNumber: 00000000
>         bAlternateSetting: 00000000
>         bNumEndpoints: 00000002
>         bInterfaceClass: 00000008
>         bInterfaceSubClass: 00000006
>         bInterfaceProtocol: 00000050
>         iInterface: 00000000
>
>         Endpoint (00081e74):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000081
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
>
>         Endpoint (00081e7b):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000002
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
> Selecting Configuration number 00000001:
> usb_control_msg: request_type = 00000000 request = 00000009 wLength=0
> usb_control_message returning 2047
> clear stall on ep=00000081
> usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
> usb_control_message returning 2047
> clear stall on ep=00000002
> usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
> usb_control_message returning 2047
> 00000008:00000006:00000050
> Manufacturor: unknown
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
> usb_control_message returning 2050
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> Product: USB Flash Drive
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
> usb_control_message returning 2050
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> Serial: 070B01001340CA0
> desc address (phy) = efeff820, (virt) = 00081e50
> conf address (phy) = efeff832, (virt) = 00081e62
> Mass storage, bulk only SCSI transparent
> Requesting initial sense data
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> bulk_transfer: ep = 00000081 len=32
> bulk_transfer returning 2048
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> sense data
> :00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
> 00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
> 0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
> 000000:00000000:00000000:00000000:00000000:00000000:00000000
>
> code = 00000000 key = 00000000
>
> Info: 00000000
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 8 bytes
> bulk_transfer: ep = 00000081 len=8
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> 1 0 byte blocks
> part address (phy) = efeff400, (virt) = 00081a30
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> ll_read_block returns 512
> 0: boot=00000000, start=00000000 length=00000000
> 1: boot=00000000, start=00000000 length=00000000
> 2: boot=00000000, start=00000000 length=00000000
> 3: boot=00000000, start=00000000 length=00000000
> DEVICE CONFIGURED
> poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1 v=00000480
> poll_usb1 i=0   poll_usb1 i=1poll_usb1 i=2   poll_u_root_hub1 v=00000480
> poll_u_root_hub1 v=00000495     poll_usb1 i=3   poll_u_root_hub1 v=00000480
> poll_u_root_hub1 v=00000480     Found USB block device 3
> Requesting initial sense data
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> bulk_transfer: ep = 00000081 len=32
> bulk_transfer returning 2048
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> sense data
> :00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
> 00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
> 0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
> 000000:00000000:00000000:00000000:00000000:00000000:00000000
>
> code = 00000000 key = 00000000
>
> Info: 00000000
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> ll_read_block returns 512
> part address (phy) = efeffa94, (virt) = 000820c4
> 0: boot=00000000, start=00000000 length=00000000
> 1: boot=00000000, start=00000000 length=00000000
> 2: boot=00000000, start=00000000 length=00000000
> 3: boot=00000000, start=00000000 length=00000000
> sector= 0     bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> sector= 68      bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
>


From jmiller at actuality-systems.com  Mon May 17 08:04:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Mon May 17 08:04:00 2004
Subject: mkElfimage-1.6 & .zelf payloads
Message-ID: <E8F8DBCB0468204E856114A2CD20741F116487@mail.local.ActualitySystems.com>

Two more newbie problems:

1) I've read on the mailing list archives that we need to use
mkElfImage-1.6 from the freebios tree in order for things to work
properly.  When I checked-out the freebios tree I only got sources for
mkElfImage, the mkElfImage-1.6 directory was empty.  Is this normal?

2) I can build an image with FILO 0.4.2 and it works great.  But when I
try and build an image with a .zelf payload, elfboot complains that it
can't load the elf image.  What am I doing wrong?

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From stepan at openbios.org  Mon May 17 08:14:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May 17 08:14:01 2004
Subject: mkElfimage-1.6 & .zelf payloads
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F116487@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F116487@mail.local.ActualitySystems.com>
Message-ID: <20040517133538.GA32416@openbios.org>

* Jay Miller <jmiller at actuality-systems.com> [040517 15:21]:
> 1) I've read on the mailing list archives that we need to use
> mkElfImage-1.6 from the freebios tree in order for things to work
> properly.  When I checked-out the freebios tree I only got sources for
> mkElfImage, the mkElfImage-1.6 directory was empty.  Is this normal?
 
You should use mkelfImage 2.5 which is the latest version. 

 Stefan




From mdeschamps at mangrove-systems.com  Mon May 17 09:56:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Mon May 17 09:56:01 2004
Subject: List of V2 Config.lb's options
Message-ID: <1084806805.15547.147.camel@Calliphara>

Hi,

I don't know if it could help, i've gathered every used options in
V2. It helped me because of V1 to V2 port : some options aren't used
any more (e.g. side solutions incorporated  in LB becoming "standards"
needn't a activated option to be taken into consideration in build)
while some other options change their name..

It maybe miss someones.



mathieu.
--------------------------

LIST OF THE DIFFERENT OPTIONS FOUND IN CONFIG.LBs, IN *.C
(this means not all are usable into config.lb)

AUTOBOOT_CMDLINE
__BIG_ENDIAN
__BIG_ENDIAN__
CHECK_FOR_SLAVES
CONFIG_BRIQ_7400
CONFIG_BRIQ_750FX
CONFIG_CONSOLE_BTEXT
CONFIG_CONSOLE_LOGBUF
CONFIG_CONSOLE_SERIAL8250
CONFIG_CONSOLE_SROM
CONFIG_CONSOLE_VGA
CONFIG_FS_EXT2
CONFIG_FS_FAT
CONFIG_FS_ISO9660
CONFIG_FS_STREAM
CONFIG_IDE
CONFIG_IDE_STREAM
CONFIG_IOAPIC
CONFIG_LEGACY_VGABIOS
CONFIG_MAX_CPUS
CONFIG_ROM_STREAM
CONFIG_ROM_STREAM_START
CONFIG_SANDPOINT_ALTIMUS
CONFIG_SANDPOINT_GYRUS
CONFIG_SANDPOINT_TALUS
CONFIG_SANDPOINT_UNITY
CONFIG_SANDPOINT_VALIS
CONFIG_SDRAM_BANK0
CONFIG_SMP
CONFIG_UDELAY_TSC
CONFIG_USE_INIT
CPU_FIXUP
DCACHE_RAM_BASE
DCACHE_RAM_SIZE
DEBUG
DEBUG_BOOT
DEBUG_CONSOLE
DEBUG_CONSOLE_SERIAL
DEBUG_CONSOLE_VGA
DEBUG_GDB
DEBUG_SETNORTHB
DECODE
DRAM_MIN_CYCLE_TIME
E2DEBUG
ENCODE
FALLBACK_SIZE
HARD_RESET_BUS
HARD_RESET_DEVICE
HARD_RESET_FUNCTION
HAVE_ACPI_HPET
HAVE_ACPI_TABLES
HAVE_FALLBACK_BOOT
HAVE_HARD_RESET
HAVE_MP_TABLE
HAVE_OPTION_TABLE
HAVE_PIRQ_TABLE
HEAP_SIZE
IN_MODULE
INTEL_PPRO_MTRR
_IO_BASE
IRQ_SLOT_COUNT
ISA_IO_BASE
ISA_MEM_BASE
k8
LB_CKS_LOC
LB_CKS_RANGE_END
LB_CKS_RANGE_START
MAIN
MAINBOARD
MAINBOARD_PART_NUMBER
MAINBOARD_VENDOR
ONE_TRACK
PAYLOAD_SIZE
PCIC0_CFGADDR
PCIC0_CFGDATA
PNP_CFGADDR
PNP_CFGDATA
_RAMBASE
_ROMBASE
ROM_IMAGE_SIZE
ROM_SECTION_OFFSET
ROM_SECTION_SIZE
ROM_SIZE
SAFE
STACK_SIZE
SWD_BEST_OFF
TTYS0_BASE
UCL_DEBUG
USE_DCACHE_RAM
USE_FALLBACK_IMAGE
USE_OPTION_TABLE
VERBOSE
VGABIOS_START
X86EMU_FPU_PRESENT
XIP_ROM_BASE
XIP_ROM_SIZ



COMPLETE LIST OF EVERY OPTIONS USED AND THEIR EXACT LOCATIONS:

# cat options.list 
Here are listed the options in the if directive in source's Config.lb

FILE                                    LINE            OPTIONS
-------------------------------------------------------

./arch/i386/boot/Config.lb      10      if HAVE_ACPI_TABLES
./arch/i386/boot/Config.lb      7       if HAVE_PIRQ_TABLE
./arch/i386/Config.lb   42      if CONFIG_SMP
./arch/i386/smp/Config.lb       4       if HAVE_MP_TABLE
./arch/i386/smp/Config.lb       8       if CONFIG_SMP
./boot/Config.lb        3       if CONFIG_FS_STREAM
./config/Config.lb      142     if HAVE_OPTION_TABLE
./console/Config.lb     12      if CONFIG_CONSOLE_BTEXT
./console/Config.lb     15      if CONFIG_CONSOLE_LOGBUF
./console/Config.lb     18      if CONFIG_CONSOLE_SROM
./console/Config.lb     24      if CONFIG_USE_INIT
./console/Config.lb     6       if CONFIG_CONSOLE_SERIAL8250
./console/Config.lb     9       if CONFIG_CONSOLE_VGA
./cpu/k8/Config.lb      9       if CPU_FIXUP
./cpu/p5/Config.lb      4       if CONFIG_UDELAY_TSC object delay_tsc.o 
end
./lib/Config.lb 12      if HAVE_FALLBACK_BOOT
./lib/Config.lb 20      if CONFIG_USE_INIT
./mainboard/amd/quartet/Config.lb       125     if USE_FALLBACK_IMAGE
./mainboard/amd/quartet/Config.lb       168     if HAVE_MP_TABLE object
mptable.o end
./mainboard/amd/quartet/Config.lb       169     if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/amd/quartet/Config.lb       205     if USE_FALLBACK_IMAGE 
./mainboard/amd/quartet/Config.lb       232     if USE_FALLBACK_IMAGE
./mainboard/amd/solo/Config.lb  124     if USE_FALLBACK_IMAGE
./mainboard/amd/solo/Config.lb  167     if HAVE_MP_TABLE object
mptable.o end
./mainboard/amd/solo/Config.lb  168     if HAVE_PIRQ_TABLE object
irq_tables.o end
./mainboard/amd/solo/Config.lb  204     if USE_FALLBACK_IMAGE
./mainboard/amd/solo/Config.lb  231     if USE_FALLBACK_IMAGE
./mainboard/arima/hdama/Config.lb       125     if USE_FALLBACK_IMAGE
./mainboard/arima/hdama/Config.lb       168     if HAVE_MP_TABLE object
mptable.o end
./mainboard/arima/hdama/Config.lb       169     if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/arima/hdama/Config.lb       205     if USE_FALLBACK_IMAGE 
./mainboard/arima/hdama/Config.lb       232     if USE_FALLBACK_IMAGE
./mainboard/ibm/e325/Config.lb  125     if USE_FALLBACK_IMAGE
./mainboard/ibm/e325/Config.lb  168     if HAVE_MP_TABLE object
mptable.o end
./mainboard/ibm/e325/Config.lb  169     if HAVE_PIRQ_TABLE object
irq_tables.o end
./mainboard/ibm/e325/Config.lb  205     if USE_FALLBACK_IMAGE 
./mainboard/ibm/e325/Config.lb  232     if USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8S2/Config.lb       112     if USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8S2/Config.lb       157     if HAVE_MP_TABLE object
mptable.o end
./mainboard/Iwill/DK8S2/Config.lb       158     if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/Iwill/DK8S2/Config.lb       193     if USE_FALLBACK_IMAGE 
./mainboard/Iwill/DK8S2/Config.lb       220     if USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8X/Config.lb        112     if USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8X/Config.lb        157     if HAVE_MP_TABLE object
mptable.o end
./mainboard/Iwill/DK8X/Config.lb        158     if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/Iwill/DK8X/Config.lb        193     if USE_FALLBACK_IMAGE 
./mainboard/Iwill/DK8X/Config.lb        220     if USE_FALLBACK_IMAGE
./mainboard/motorola/sandpoint/Config.lb        39      if
CONFIG_SANDPOINT_ALTIMUS
./mainboard/motorola/sandpoint/Config.lb        44      if
CONFIG_SANDPOINT_TALUS
./mainboard/motorola/sandpoint/Config.lb        48      if
CONFIG_SANDPOINT_UNITY
./mainboard/motorola/sandpoint/Config.lb        51      if
CONFIG_SANDPOINT_VALIS
./mainboard/motorola/sandpoint/Config.lb        54      if
CONFIG_SANDPOINT_GYRUS
./mainboard/newisys/khepri/Config.lb    125     if USE_FALLBACK_IMAGE
./mainboard/newisys/khepri/Config.lb    168     if HAVE_MP_TABLE object
mptable.o end
./mainboard/newisys/khepri/Config.lb    169     if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/newisys/khepri/Config.lb    207     if USE_FALLBACK_IMAGE 
./mainboard/newisys/khepri/Config.lb    234     if USE_FALLBACK_IMAGE
./mainboard/totalimpact/briq/Config.lb  36      if CONFIG_BRIQ_750FX
./mainboard/totalimpact/briq/Config.lb  39      if CONFIG_BRIQ_7400
./mainboard/tyan/s2850/Config.lb        101     if USE_FALLBACK_IMAGE
./mainboard/tyan/s2850/Config.lb        43      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s2850/Config.lb        44      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s2850/Config.lb        65      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s2850/Config.lb        88      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2880/Config.lb        41      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s2880/Config.lb        42      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s2880/Config.lb        62      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s2880/Config.lb        85      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2880/Config.lb        98      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2881/Config.lb        101     if USE_FALLBACK_IMAGE
./mainboard/tyan/s2881/Config.lb        43      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s2881/Config.lb        44      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s2881/Config.lb        65      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s2881/Config.lb        88      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2882/Config.lb        41      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s2882/Config.lb        42      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s2882/Config.lb        63      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s2882/Config.lb        86      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2882/Config.lb        99      if USE_FALLBACK_IMAGE
./mainboard/tyan/s2885/Config.lb        103     if USE_FALLBACK_IMAGE
./mainboard/tyan/s2885/Config.lb        43      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s2885/Config.lb        44      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s2885/Config.lb        67      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s2885/Config.lb        90      if USE_FALLBACK_IMAGE
./mainboard/tyan/s4880/Config.lb        100     if USE_FALLBACK_IMAGE
./mainboard/tyan/s4880/Config.lb        42      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s4880/Config.lb        43      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s4880/Config.lb        64      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s4880/Config.lb        87      if USE_FALLBACK_IMAGE
./mainboard/tyan/s4882/Config.lb        101     if USE_FALLBACK_IMAGE
./mainboard/tyan/s4882/Config.lb        43      if HAVE_MP_TABLE object
mptable.o end
./mainboard/tyan/s4882/Config.lb        44      if HAVE_PIRQ_TABLE
object irq_tables.o end
./mainboard/tyan/s4882/Config.lb        65      if USE_FALLBACK_IMAGE 
./mainboard/tyan/s4882/Config.lb        88      if USE_FALLBACK_IMAGE
./mainboard/via/epia/Config.lb  162     if USE_FALLBACK_IMAGE 
./mainboard/via/epia/Config.lb  189     if USE_FALLBACK_IMAGE
./mainboard/via/epia/Config.lb  84      if USE_FALLBACK_IMAGE
./pc80/Config.lb        14      if CONFIG_IDE
./pc80/Config.lb        20      if CONFIG_LEGACY_VGABIOS
./stream/Config.lb      10      if CONFIG_IDE_STREAM
./stream/Config.lb      15      if CONFIG_FS_STREAM
./stream/Config.lb      6       if CONFIG_ROM_STREAM
./stream/fs/Config.lb   12      if CONFIG_FS_ISO9660
./stream/fs/Config.lb   16      if CONFIG_FS_FAT
./stream/fs/Config.lb   8       if CONFIG_FS_EXT2

Here are listed the options in the uses  directive in source's Config.lb
-------------------------------------------------------------------------


FILE                                    LINE            OPTIONS
-------------------------------------------------------

./arch/i386/boot/Config.lb      1       uses HAVE_PIRQ_TABLE
./arch/i386/boot/Config.lb      2       uses HAVE_ACPI_TABLES
./arch/i386/Config.lb   1       uses CONFIG_SMP
./arch/i386/smp/Config.lb       1       uses HAVE_MP_TABLE
./arch/i386/smp/Config.lb       2       uses CONFIG_SMP
./config/Config.lb      3       uses HAVE_OPTION_TABLE
./console/Config.lb     1       uses CONFIG_CONSOLE_SERIAL8250
CONFIG_CONSOLE_VGA CONFIG_CONSOLE_BTEXT
./console/Config.lb     2       uses CONFIG_CONSOLE_LOGBUF
CONFIG_CONSOLE_SROM
./console/Config.lb     3       uses CONFIG_USE_INIT
./cpu/k7/Config.lb      1       uses k7
./cpu/k7/Config.lb      2       uses CPU_FIXUP
./cpu/k8/Config.lb      4       uses k8
./cpu/k8/Config.lb      5       uses CPU_FIXUP
./cpu/p5/Config.lb      1       uses  CONFIG_UDELAY_TSC
./cpu/p6/Config.lb      1       uses INTEL_PPRO_MTRR
./cpu/ppc/mpc74xx/Config.lb     4       uses _RAMBASE
./cpu/ppc/mpc74xx/Config.lb     5       uses USE_DCACHE_RAM
./cpu/ppc/mpc74xx/Config.lb     6       uses DCACHE_RAM_BASE
./cpu/ppc/mpc74xx/Config.lb     7       uses DCACHE_RAM_SIZE
./cpu/ppc/ppc4xx/Config.lb      4       uses _RAMBASE
./cpu/ppc/ppc4xx/Config.lb      5       uses USE_DCACHE_RAM
./cpu/ppc/ppc4xx/Config.lb      6       uses DCACHE_RAM_BASE
./cpu/ppc/ppc4xx/Config.lb      7       uses DCACHE_RAM_SIZE
./cpu/ppc/ppc7xx/Config.lb      4       uses _RAMBASE
./cpu/ppc/ppc7xx/Config.lb      5       uses USE_DCACHE_RAM
./cpu/ppc/ppc7xx/Config.lb      6       uses DCACHE_RAM_BASE
./cpu/ppc/ppc7xx/Config.lb      7       uses DCACHE_RAM_SIZE
./lib/Config.lb 1       uses HAVE_FALLBACK_BOOT
./lib/Config.lb 2       uses CONFIG_USE_INIT
./mainboard/amd/quartet/Config.lb       10      uses HAVE_OPTION_TABLE
./mainboard/amd/quartet/Config.lb       11      uses CONFIG_MAX_CPUS
./mainboard/amd/quartet/Config.lb       12      uses CONFIG_IOAPIC
./mainboard/amd/quartet/Config.lb       13      uses CONFIG_SMP
./mainboard/amd/quartet/Config.lb       14      uses FALLBACK_SIZE
./mainboard/amd/quartet/Config.lb       15      uses ROM_SIZE
./mainboard/amd/quartet/Config.lb       16      uses ROM_SECTION_SIZE
./mainboard/amd/quartet/Config.lb       17      uses ROM_IMAGE_SIZE
./mainboard/amd/quartet/Config.lb       18      uses ROM_SECTION_SIZE
./mainboard/amd/quartet/Config.lb       19      uses ROM_SECTION_OFFSET
./mainboard/amd/quartet/Config.lb       1       uses HAVE_MP_TABLE
./mainboard/amd/quartet/Config.lb       20      uses CONFIG_ROM_STREAM
./mainboard/amd/quartet/Config.lb       21      uses
CONFIG_ROM_STREAM_START
./mainboard/amd/quartet/Config.lb       22      uses PAYLOAD_SIZE
./mainboard/amd/quartet/Config.lb       23      uses _ROMBASE
./mainboard/amd/quartet/Config.lb       24      uses XIP_ROM_SIZE
./mainboard/amd/quartet/Config.lb       25      uses XIP_ROM_BASE
./mainboard/amd/quartet/Config.lb       26      uses STACK_SIZE
./mainboard/amd/quartet/Config.lb       27      uses HEAP_SIZE
./mainboard/amd/quartet/Config.lb       28      uses USE_OPTION_TABLE
./mainboard/amd/quartet/Config.lb       29      uses LB_CKS_RANGE_START
./mainboard/amd/quartet/Config.lb       2       uses HAVE_PIRQ_TABLE
./mainboard/amd/quartet/Config.lb       30      uses LB_CKS_RANGE_END
./mainboard/amd/quartet/Config.lb       31      uses LB_CKS_LOC
./mainboard/amd/quartet/Config.lb       32      uses
MAINBOARD_PART_NUMBER
./mainboard/amd/quartet/Config.lb       33      uses MAINBOARD_VENDOR
./mainboard/amd/quartet/Config.lb       3       uses USE_FALLBACK_IMAGE
./mainboard/amd/quartet/Config.lb       4       uses HAVE_FALLBACK_BOOT
./mainboard/amd/quartet/Config.lb       5       uses HAVE_HARD_RESET
./mainboard/amd/quartet/Config.lb       6       uses HARD_RESET_BUS
./mainboard/amd/quartet/Config.lb       7       uses HARD_RESET_DEVICE
./mainboard/amd/quartet/Config.lb       8       uses HARD_RESET_FUNCTION
./mainboard/amd/quartet/Config.lb       9       uses IRQ_SLOT_COUNT
./mainboard/amd/solo/Config.lb  10      uses HAVE_OPTION_TABLE
./mainboard/amd/solo/Config.lb  11      uses CONFIG_MAX_CPUS
./mainboard/amd/solo/Config.lb  12      uses CONFIG_IOAPIC
./mainboard/amd/solo/Config.lb  13      uses CONFIG_SMP
./mainboard/amd/solo/Config.lb  14      uses FALLBACK_SIZE
./mainboard/amd/solo/Config.lb  15      uses ROM_SIZE
./mainboard/amd/solo/Config.lb  16      uses ROM_SECTION_SIZE
./mainboard/amd/solo/Config.lb  17      uses ROM_IMAGE_SIZE
./mainboard/amd/solo/Config.lb  18      uses ROM_SECTION_SIZE
./mainboard/amd/solo/Config.lb  19      uses ROM_SECTION_OFFSET
./mainboard/amd/solo/Config.lb  1       uses HAVE_MP_TABLE
./mainboard/amd/solo/Config.lb  20      uses CONFIG_ROM_STREAM
./mainboard/amd/solo/Config.lb  21      uses CONFIG_ROM_STREAM_START
./mainboard/amd/solo/Config.lb  22      uses PAYLOAD_SIZE
./mainboard/amd/solo/Config.lb  23      uses _ROMBASE
./mainboard/amd/solo/Config.lb  24      uses XIP_ROM_SIZE
./mainboard/amd/solo/Config.lb  25      uses XIP_ROM_BASE
./mainboard/amd/solo/Config.lb  26      uses STACK_SIZE
./mainboard/amd/solo/Config.lb  27      uses HEAP_SIZE
./mainboard/amd/solo/Config.lb  28      uses USE_OPTION_TABLE
./mainboard/amd/solo/Config.lb  29      uses LB_CKS_RANGE_START
./mainboard/amd/solo/Config.lb  2       uses HAVE_PIRQ_TABLE
./mainboard/amd/solo/Config.lb  30      uses LB_CKS_RANGE_END
./mainboard/amd/solo/Config.lb  31      uses LB_CKS_LOC
./mainboard/amd/solo/Config.lb  32      uses MAINBOARD_PART_NUMBER
./mainboard/amd/solo/Config.lb  33      uses MAINBOARD_VENDOR
./mainboard/amd/solo/Config.lb  3       uses USE_FALLBACK_IMAGE
./mainboard/amd/solo/Config.lb  4       uses HAVE_FALLBACK_BOOT
./mainboard/amd/solo/Config.lb  5       uses HAVE_HARD_RESET
./mainboard/amd/solo/Config.lb  6       uses HARD_RESET_BUS
./mainboard/amd/solo/Config.lb  7       uses HARD_RESET_DEVICE
./mainboard/amd/solo/Config.lb  8       uses HARD_RESET_FUNCTION
./mainboard/amd/solo/Config.lb  9       uses IRQ_SLOT_COUNT
./mainboard/arima/hdama/Config.lb       10      uses HAVE_OPTION_TABLE
./mainboard/arima/hdama/Config.lb       11      uses CONFIG_MAX_CPUS
./mainboard/arima/hdama/Config.lb       12      uses CONFIG_IOAPIC
./mainboard/arima/hdama/Config.lb       13      uses CONFIG_SMP
./mainboard/arima/hdama/Config.lb       14      uses FALLBACK_SIZE
./mainboard/arima/hdama/Config.lb       15      uses ROM_SIZE
./mainboard/arima/hdama/Config.lb       16      uses ROM_SECTION_SIZE
./mainboard/arima/hdama/Config.lb       17      uses ROM_IMAGE_SIZE
./mainboard/arima/hdama/Config.lb       18      uses ROM_SECTION_SIZE
./mainboard/arima/hdama/Config.lb       19      uses ROM_SECTION_OFFSET
./mainboard/arima/hdama/Config.lb       1       uses HAVE_MP_TABLE
./mainboard/arima/hdama/Config.lb       20      uses CONFIG_ROM_STREAM
./mainboard/arima/hdama/Config.lb       21      uses
CONFIG_ROM_STREAM_START
./mainboard/arima/hdama/Config.lb       22      uses PAYLOAD_SIZE
./mainboard/arima/hdama/Config.lb       23      uses _ROMBASE
./mainboard/arima/hdama/Config.lb       24      uses XIP_ROM_SIZE
./mainboard/arima/hdama/Config.lb       25      uses XIP_ROM_BASE
./mainboard/arima/hdama/Config.lb       26      uses STACK_SIZE
./mainboard/arima/hdama/Config.lb       27      uses HEAP_SIZE
./mainboard/arima/hdama/Config.lb       28      uses USE_OPTION_TABLE
./mainboard/arima/hdama/Config.lb       29      uses LB_CKS_RANGE_START
./mainboard/arima/hdama/Config.lb       2       uses HAVE_PIRQ_TABLE
./mainboard/arima/hdama/Config.lb       30      uses LB_CKS_RANGE_END
./mainboard/arima/hdama/Config.lb       31      uses LB_CKS_LOC
./mainboard/arima/hdama/Config.lb       32      uses
MAINBOARD_PART_NUMBER
./mainboard/arima/hdama/Config.lb       33      uses MAINBOARD_VENDOR
./mainboard/arima/hdama/Config.lb       3       uses USE_FALLBACK_IMAGE
./mainboard/arima/hdama/Config.lb       4       uses HAVE_FALLBACK_BOOT
./mainboard/arima/hdama/Config.lb       5       uses HAVE_HARD_RESET
./mainboard/arima/hdama/Config.lb       6       uses HARD_RESET_BUS

./mainboard/arima/hdama/Config.lb       5       uses HAVE_HARD_RESET
./mainboard/arima/hdama/Config.lb       6       uses HARD_RESET_BUS
./mainboard/arima/hdama/Config.lb       7       uses HARD_RESET_DEVICE
./mainboard/arima/hdama/Config.lb       8       uses HARD_RESET_FUNCTION
./mainboard/arima/hdama/Config.lb       9       uses IRQ_SLOT_COUNT
./mainboard/embeddedplanet/ep405pc/Config.lb    10      uses _IO_BASE 
./mainboard/embeddedplanet/ep405pc/Config.lb    5       uses
PCIC0_CFGADDR 
./mainboard/embeddedplanet/ep405pc/Config.lb    6       uses
PCIC0_CFGDATA 
./mainboard/embeddedplanet/ep405pc/Config.lb    7       uses ISA_IO_BASE
./mainboard/embeddedplanet/ep405pc/Config.lb    8       uses
ISA_MEM_BASE 
./mainboard/embeddedplanet/ep405pc/Config.lb    9       uses TTYS0_BASE 
./mainboard/ibm/e325/Config.lb  10      uses HAVE_OPTION_TABLE
./mainboard/ibm/e325/Config.lb  11      uses CONFIG_MAX_CPUS
./mainboard/ibm/e325/Config.lb  12      uses CONFIG_IOAPIC
./mainboard/ibm/e325/Config.lb  13      uses CONFIG_SMP
./mainboard/ibm/e325/Config.lb  14      uses FALLBACK_SIZE
./mainboard/ibm/e325/Config.lb  15      uses ROM_SIZE
./mainboard/ibm/e325/Config.lb  16      uses ROM_SECTION_SIZE
./mainboard/ibm/e325/Config.lb  17      uses ROM_IMAGE_SIZE
./mainboard/ibm/e325/Config.lb  18      uses ROM_SECTION_SIZE
./mainboard/ibm/e325/Config.lb  19      uses ROM_SECTION_OFFSET
./mainboard/ibm/e325/Config.lb  1       uses HAVE_MP_TABLE
./mainboard/ibm/e325/Config.lb  20      uses CONFIG_ROM_STREAM
./mainboard/ibm/e325/Config.lb  21      uses CONFIG_ROM_STREAM_START
./mainboard/ibm/e325/Config.lb  22      uses PAYLOAD_SIZE
./mainboard/ibm/e325/Config.lb  23      uses _ROMBASE
./mainboard/ibm/e325/Config.lb  24      uses XIP_ROM_SIZE
./mainboard/ibm/e325/Config.lb  25      uses XIP_ROM_BASE
./mainboard/ibm/e325/Config.lb  26      uses STACK_SIZE
./mainboard/ibm/e325/Config.lb  27      uses HEAP_SIZE
./mainboard/ibm/e325/Config.lb  28      uses USE_OPTION_TABLE
./mainboard/ibm/e325/Config.lb  29      uses LB_CKS_RANGE_START
./mainboard/ibm/e325/Config.lb  2       uses HAVE_PIRQ_TABLE
./mainboard/ibm/e325/Config.lb  30      uses LB_CKS_RANGE_END
./mainboard/ibm/e325/Config.lb  31      uses LB_CKS_LOC
./mainboard/ibm/e325/Config.lb  32      uses MAINBOARD_PART_NUMBER
./mainboard/ibm/e325/Config.lb  33      uses MAINBOARD_VENDOR
./mainboard/ibm/e325/Config.lb  3       uses USE_FALLBACK_IMAGE
./mainboard/ibm/e325/Config.lb  4       uses HAVE_FALLBACK_BOOT
./mainboard/ibm/e325/Config.lb  5       uses HAVE_HARD_RESET
./mainboard/ibm/e325/Config.lb  6       uses HARD_RESET_BUS
./mainboard/ibm/e325/Config.lb  7       uses HARD_RESET_DEVICE
./mainboard/ibm/e325/Config.lb  8       uses HARD_RESET_FUNCTION
./mainboard/ibm/e325/Config.lb  9       uses IRQ_SLOT_COUNT
./mainboard/Iwill/DK8S2/Config.lb       10      uses HAVE_OPTION_TABLE
./mainboard/Iwill/DK8S2/Config.lb       11      uses CONFIG_MAX_CPUS
./mainboard/Iwill/DK8S2/Config.lb       12      uses CONFIG_IOAPIC
./mainboard/Iwill/DK8S2/Config.lb       13      uses CONFIG_SMP
./mainboard/Iwill/DK8S2/Config.lb       14      uses FALLBACK_SIZE
./mainboard/Iwill/DK8S2/Config.lb       15      uses ROM_SIZE
./mainboard/Iwill/DK8S2/Config.lb       16      uses ROM_SECTION_SIZE
./mainboard/Iwill/DK8S2/Config.lb       17      uses ROM_IMAGE_SIZE
./mainboard/Iwill/DK8S2/Config.lb       18      uses ROM_SECTION_SIZE
./mainboard/Iwill/DK8S2/Config.lb       19      uses ROM_SECTION_OFFSET
./mainboard/Iwill/DK8S2/Config.lb       1       uses HAVE_MP_TABLE
./mainboard/Iwill/DK8S2/Config.lb       20      uses CONFIG_ROM_STREAM
./mainboard/Iwill/DK8S2/Config.lb       21      uses
CONFIG_ROM_STREAM_START
./mainboard/Iwill/DK8S2/Config.lb       22      uses PAYLOAD_SIZE
./mainboard/Iwill/DK8S2/Config.lb       23      uses _ROMBASE
./mainboard/Iwill/DK8S2/Config.lb       24      uses XIP_ROM_SIZE
./mainboard/Iwill/DK8S2/Config.lb       25      uses XIP_ROM_BASE
./mainboard/Iwill/DK8S2/Config.lb       26      uses STACK_SIZE
./mainboard/Iwill/DK8S2/Config.lb       27      uses HEAP_SIZE
./mainboard/Iwill/DK8S2/Config.lb       28      uses USE_OPTION_TABLE
./mainboard/Iwill/DK8S2/Config.lb       2       uses HAVE_PIRQ_TABLE
./mainboard/Iwill/DK8S2/Config.lb       3       uses USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8S2/Config.lb       4       uses HAVE_FALLBACK_BOOT
./mainboard/Iwill/DK8S2/Config.lb       5       uses HAVE_HARD_RESET
./mainboard/Iwill/DK8S2/Config.lb       6       uses HARD_RESET_BUS
./mainboard/Iwill/DK8S2/Config.lb       7       uses HARD_RESET_DEVICE
./mainboard/Iwill/DK8S2/Config.lb       8       uses HARD_RESET_FUNCTION
./mainboard/Iwill/DK8S2/Config.lb       9       uses IRQ_SLOT_COUNT
./mainboard/Iwill/DK8X/Config.lb        10      uses HAVE_OPTION_TABLE
./mainboard/Iwill/DK8X/Config.lb        11      uses CONFIG_MAX_CPUS
./mainboard/Iwill/DK8X/Config.lb        12      uses CONFIG_IOAPIC
./mainboard/Iwill/DK8X/Config.lb        13      uses CONFIG_SMP
./mainboard/Iwill/DK8X/Config.lb        14      uses FALLBACK_SIZE
./mainboard/Iwill/DK8X/Config.lb        15      uses ROM_SIZE
./mainboard/Iwill/DK8X/Config.lb        16      uses ROM_SECTION_SIZE
./mainboard/Iwill/DK8X/Config.lb        17      uses ROM_IMAGE_SIZE
./mainboard/Iwill/DK8X/Config.lb        18      uses ROM_SECTION_SIZE
./mainboard/Iwill/DK8X/Config.lb        19      uses ROM_SECTION_OFFSET
./mainboard/Iwill/DK8X/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/Iwill/DK8X/Config.lb        20      uses CONFIG_ROM_STREAM
./mainboard/Iwill/DK8X/Config.lb        21      uses
CONFIG_ROM_STREAM_START
./mainboard/Iwill/DK8X/Config.lb        22      uses PAYLOAD_SIZE
./mainboard/Iwill/DK8X/Config.lb        23      uses _ROMBASE
./mainboard/Iwill/DK8X/Config.lb        24      uses XIP_ROM_SIZE
./mainboard/Iwill/DK8X/Config.lb        25      uses XIP_ROM_BASE
./mainboard/Iwill/DK8X/Config.lb        26      uses STACK_SIZE
./mainboard/Iwill/DK8X/Config.lb        27      uses HEAP_SIZE
./mainboard/Iwill/DK8X/Config.lb        28      uses USE_OPTION_TABLE
./mainboard/Iwill/DK8X/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/Iwill/DK8X/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/Iwill/DK8X/Config.lb        4       uses HAVE_FALLBACK_BOOT
./mainboard/Iwill/DK8X/Config.lb        5       uses HAVE_HARD_RESET
./mainboard/Iwill/DK8X/Config.lb        6       uses HARD_RESET_BUS
./mainboard/Iwill/DK8X/Config.lb        7       uses HARD_RESET_DEVICE
./mainboard/Iwill/DK8X/Config.lb        8       uses HARD_RESET_FUNCTION
./mainboard/Iwill/DK8X/Config.lb        9       uses IRQ_SLOT_COUNT
./mainboard/motorola/sandpoint/Config.lb        10      uses ISA_IO_BASE
./mainboard/motorola/sandpoint/Config.lb        11      uses
ISA_MEM_BASE
./mainboard/motorola/sandpoint/Config.lb        12      uses
PCIC0_CFGADDR
./mainboard/motorola/sandpoint/Config.lb        13      uses
PCIC0_CFGDATA
./mainboard/motorola/sandpoint/Config.lb        14      uses PNP_CFGADDR
./mainboard/motorola/sandpoint/Config.lb        15      uses PNP_CFGDATA
./mainboard/motorola/sandpoint/Config.lb        16      uses _IO_BASE
./mainboard/motorola/sandpoint/Config.lb        5       uses
CONFIG_SANDPOINT_ALTIMUS
./mainboard/motorola/sandpoint/Config.lb        6       uses
CONFIG_SANDPOINT_TALUS
./mainboard/motorola/sandpoint/Config.lb        7       uses
CONFIG_SANDPOINT_UNITY
./mainboard/motorola/sandpoint/Config.lb        8       uses
CONFIG_SANDPOINT_VALIS
./mainboard/motorola/sandpoint/Config.lb        9       uses
CONFIG_SANDPOINT_GYRUS
./mainboard/newisys/khepri/Config.lb    10      uses HAVE_OPTION_TABLE
./mainboard/newisys/khepri/Config.lb    11      uses CONFIG_MAX_CPUS
./mainboard/newisys/khepri/Config.lb    12      uses CONFIG_IOAPIC
./mainboard/newisys/khepri/Config.lb    13      uses CONFIG_SMP
./mainboard/newisys/khepri/Config.lb    14      uses FALLBACK_SIZE
./mainboard/newisys/khepri/Config.lb    15      uses ROM_SIZE
./mainboard/newisys/khepri/Config.lb    16      uses ROM_SECTION_SIZE
./mainboard/newisys/khepri/Config.lb    17      uses ROM_IMAGE_SIZE
./mainboard/newisys/khepri/Config.lb    18      uses ROM_SECTION_SIZE
./mainboard/newisys/khepri/Config.lb    19      uses ROM_SECTION_OFFSET
./mainboard/newisys/khepri/Config.lb    1       uses HAVE_MP_TABLE
./mainboard/newisys/khepri/Config.lb    20      uses CONFIG_ROM_STREAM
./mainboard/newisys/khepri/Config.lb    21      uses
CONFIG_ROM_STREAM_START
./mainboard/newisys/khepri/Config.lb    22      uses PAYLOAD_SIZE
./mainboard/newisys/khepri/Config.lb    23      uses _ROMBASE
./mainboard/newisys/khepri/Config.lb    24      uses XIP_ROM_SIZE
./mainboard/newisys/khepri/Config.lb    25      uses XIP_ROM_BASE
./mainboard/newisys/khepri/Config.lb    26      uses STACK_SIZE
./mainboard/newisys/khepri/Config.lb    27      uses HEAP_SIZE
./mainboard/newisys/khepri/Config.lb    28      uses USE_OPTION_TABLE
./mainboard/newisys/khepri/Config.lb    29      uses LB_CKS_RANGE_START
./mainboard/newisys/khepri/Config.lb    2       uses HAVE_PIRQ_TABLE
./mainboard/newisys/khepri/Config.lb    30      uses LB_CKS_RANGE_END
./mainboard/newisys/khepri/Config.lb    31      uses LB_CKS_LOC
./mainboard/newisys/khepri/Config.lb    32      uses
MAINBOARD_PART_NUMBER
./mainboard/newisys/khepri/Config.lb    33      uses MAINBOARD_VENDOR
./mainboard/newisys/khepri/Config.lb    3       uses USE_FALLBACK_IMAGE
./mainboard/newisys/khepri/Config.lb    4       uses HAVE_FALLBACK_BOOT
./mainboard/newisys/khepri/Config.lb    5       uses HAVE_HARD_RESET
./mainboard/newisys/khepri/Config.lb    6       uses HARD_RESET_BUS
./mainboard/newisys/khepri/Config.lb    7       uses HARD_RESET_DEVICE
./mainboard/newisys/khepri/Config.lb    8       uses HARD_RESET_FUNCTION
./mainboard/newisys/khepri/Config.lb    9       uses IRQ_SLOT_COUNT
./mainboard/totalimpact/briq/Config.lb  5       uses PCIC0_CFGADDR 
./mainboard/totalimpact/briq/Config.lb  6       uses PCIC0_CFGDATA 
./mainboard/totalimpact/briq/Config.lb  7       uses TTYS0_BASE
./mainboard/totalimpact/briq/Config.lb  8       uses CONFIG_BRIQ_750FX
./mainboard/totalimpact/briq/Config.lb  9       uses CONFIG_BRIQ_7400
./mainboard/tyan/s2850/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s2850/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s2850/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s2850/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s2850/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s2850/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s2850/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s2850/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s2850/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s2850/Config.lb        8       uses ARCH
./mainboard/tyan/s2850/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s2880/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s2880/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s2880/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s2880/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s2880/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s2880/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s2880/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s2880/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s2880/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s2880/Config.lb        8       uses ARCH
./mainboard/tyan/s2880/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s2881/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s2881/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s2881/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s2881/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s2881/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s2881/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s2881/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s2881/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s2881/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s2881/Config.lb        8       uses ARCH
./mainboard/tyan/s2881/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s2882/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s2882/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s2882/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s2882/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s2882/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s2882/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s2882/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s2882/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s2882/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s2882/Config.lb        8       uses ARCH
./mainboard/tyan/s2882/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s2885/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s2885/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s2885/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s2885/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s2885/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s2885/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s2885/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s2885/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s2885/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s2885/Config.lb        8       uses ARCH
./mainboard/tyan/s2885/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s4880/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s4880/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s4880/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s4880/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s4880/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s4880/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s4880/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s4880/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s4880/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s4880/Config.lb        8       uses ARCH
./mainboard/tyan/s4880/Config.lb        9       uses HARD_RESET_BUS
./mainboard/tyan/s4882/Config.lb        10      uses HARD_RESET_DEVICE
./mainboard/tyan/s4882/Config.lb        11      uses HARD_RESET_FUNCTION
./mainboard/tyan/s4882/Config.lb        1       uses HAVE_MP_TABLE
./mainboard/tyan/s4882/Config.lb        2       uses HAVE_PIRQ_TABLE
./mainboard/tyan/s4882/Config.lb        3       uses USE_FALLBACK_IMAGE
./mainboard/tyan/s4882/Config.lb        4       uses LB_CKS_RANGE_START
./mainboard/tyan/s4882/Config.lb        5       uses LB_CKS_RANGE_END
./mainboard/tyan/s4882/Config.lb        6       uses LB_CKS_LOC
./mainboard/tyan/s4882/Config.lb        7       uses MAINBOARD
./mainboard/tyan/s4882/Config.lb        8       uses ARCH
./mainboard/tyan/s4882/Config.lb        9       uses HARD_RESET_BUS
./mainboard/via/epia/Config.lb  10      uses HAVE_FALLBACK_BOOT
./mainboard/via/epia/Config.lb  11      uses HAVE_HARD_RESET
./mainboard/via/epia/Config.lb  12      uses HAVE_OPTION_TABLE
./mainboard/via/epia/Config.lb  13      uses USE_OPTION_TABLE
./mainboard/via/epia/Config.lb  14      uses CONFIG_ROM_STREAM
./mainboard/via/epia/Config.lb  15      uses IRQ_SLOT_COUNT
./mainboard/via/epia/Config.lb  16      uses MAINBOARD
./mainboard/via/epia/Config.lb  17      uses ARCH
./mainboard/via/epia/Config.lb  18      uses FALLBACK_SIZE
./mainboard/via/epia/Config.lb  19      uses STACK_SIZE
./mainboard/via/epia/Config.lb  20      uses HEAP_SIZE
./mainboard/via/epia/Config.lb  21      uses ROM_SIZE
./mainboard/via/epia/Config.lb  22      uses ROM_SECTION_SIZE
./mainboard/via/epia/Config.lb  23      uses ROM_IMAGE_SIZE
./mainboard/via/epia/Config.lb  24      uses ROM_SECTION_SIZE
./mainboard/via/epia/Config.lb  25      uses ROM_SECTION_OFFSET
./mainboard/via/epia/Config.lb  26      uses CONFIG_ROM_STREAM_START
./mainboard/via/epia/Config.lb  27      uses PAYLOAD_SIZE
./mainboard/via/epia/Config.lb  28      uses _ROMBASE
./mainboard/via/epia/Config.lb  29      uses XIP_ROM_SIZE
./mainboard/via/epia/Config.lb  30      uses XIP_ROM_BASE
./mainboard/via/epia/Config.lb  31      uses HAVE_MP_TABLE
./mainboard/via/epia/Config.lb  7       uses HAVE_MP_TABLE
./mainboard/via/epia/Config.lb  8       uses HAVE_PIRQ_TABLE
./mainboard/via/epia/Config.lb  9       uses USE_FALLBACK_IMAGE
./pc80/Config.lb        1       uses CONFIG_IDE
./pc80/Config.lb        2       uses CONFIG_LEGACY_VGABIOS
./stream/Config.lb      1       uses CONFIG_ROM_STREAM
./stream/Config.lb      2       uses CONFIG_IDE_STREAM
./stream/Config.lb      3       uses CONFIG_FS_STREAM
./stream/Config.lb      4       uses CONFIG_IDE
./stream/fs/Config.lb   1       uses CONFIG_FS_EXT2
./stream/fs/Config.lb   2       uses CONFIG_FS_ISO9660
./stream/fs/Config.lb   3       uses CONFIG_FS_FAT



From nathanael at gnat.ca  Mon May 17 10:00:01 2004
From: nathanael at gnat.ca (Nathanael Noblet)
Date: Mon May 17 10:00:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <Pine.LNX.4.44.0405162008110.3792-100000@maxroach.lanl.gov>
Message-ID: <80DEBC52-A815-11D8-B852-0003931B4D6A@gnat.ca>

On Sunday, May 16, 2004, at 07:08 PM, ron minnich wrote:

> On Sun, 16 May 2004, Ignacio Verona wrote:
>
>> biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
>> biosint: ebp 0x10fca esp 0xfc0 edi 0xb880 esi 0x1010a
>> biosint: ip 0x188 cs 0xc000 flags 0x246
>> biosint: Unsupport int #0xb8
>
> b8? Anybody know what that one is?

It has something to do with VGA, I had similar problems (have been back 
to them so they are most likely still there). The Unsupported int 
number would change for me. If I powered down (hold power button down) 
the machine it would start up properly the next time. It wasn't 
something that ALWAYS happened, but fairly often it would.

-- 
Nathanael D. Noblet
Gnat Solutions
412 - 135 Gorge Road E
Victoria, BC V9A 1L1

T/F 250.385.4613

http://www.gnat.ca/



From stepan at openbios.org  Mon May 17 10:07:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May 17 10:07:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <80DEBC52-A815-11D8-B852-0003931B4D6A@gnat.ca>
References: <Pine.LNX.4.44.0405162008110.3792-100000@maxroach.lanl.gov> <80DEBC52-A815-11D8-B852-0003931B4D6A@gnat.ca>
Message-ID: <20040517152845.GA1833@openbios.org>

* Nathanael Noblet <nathanael at gnat.ca> [040517 17:18]:
> >>biosint: Unsupport int #0xb8
> >
> >b8? Anybody know what that one is?
> 
> It has something to do with VGA, I had similar problems (have been back 
> to them so they are most likely still there). The Unsupported int 
> number would change for me. If I powered down (hold power button down) 
> the machine it would start up properly the next time. It wasn't 
> something that ALWAYS happened, but fairly often it would.

Ralph Brown's Interrupt List is not very helpful either:
    http://www.ctyme.com/intr/int-b8.htm

Looks rather like a bug elsewhere.. 

Stefan



From jmiller at actuality-systems.com  Mon May 17 10:18:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Mon May 17 10:18:00 2004
Subject: USB boot
Message-ID: <E8F8DBCB0468204E856114A2CD20741F11648F@mail.local.ActualitySystems.com>

Has the code for USB support been committed, and if so, where?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From stepan at openbios.org  Mon May 17 10:30:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May 17 10:30:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <2690.192.168.1.3.1084738051.squirrel@mail.estudio-verona.com>
References: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com> <2690.192.168.1.3.1084738051.squirrel@mail.estudio-verona.com>
Message-ID: <20040517155133.GA2115@openbios.org>

* Ignacio Verona <nacho at estudio-verona.com> [040516 22:07]:
> biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x700 edx 0x112
> biosint: ebp 0x10fca esp 0xf8e edi 0xac51 esi 0x1aacd
> biosint: ip 0x6448 cs 0xc000 flags 0x46
> biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
> biosint: ebp 0x10fca esp 0xfc0 edi 0xb880 esi 0x1010a
> biosint: ip 0x188 cs 0xc000 flags 0x246
> biosint: Unsupport int #0xb8

Hm. The problem happens earlier. int 0x15 is something that the VGA BIOS
would probably install, but this does not seem to work. Thus there's a
hardcoded response handled in src/mainboard/via/epia-m/mainboard.c (v1)
function handleint21()

Looking at above code, int0x15 gets called with eax=0x5f01 (besides lots
of other values) - a case that is not handled in handleint21() at all.

There needs to be some way to call into interrupts set up by the
executed option rom, or otherwise functions like handleint21() will have
to be added and changed for every minor release of a vga bios update.

 Stefan



From stepan at openbios.org  Mon May 17 10:49:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Mon May 17 10:49:00 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <20040517155133.GA2115@openbios.org>
References: <2584.192.168.1.3.1084736850.squirrel@mail.estudio-verona.com> <2690.192.168.1.3.1084738051.squirrel@mail.estudio-verona.com> <20040517155133.GA2115@openbios.org>
Message-ID: <20040517161017.GA2551@openbios.org>

* Stefan Reinauer <stepan at openbios.org> [040517 17:51]:
> There needs to be some way to call into interrupts set up by the
> executed option rom, or otherwise functions like handleint21() will have
> to be added and changed for every minor release of a vga bios update.

There's a potential hint in src/arch/i386/lib/idt.c:biosint():

        // cases in a good compiler are just as good as your own tables. 
        switch (intnumber) {
        case 0 ... 15:
                [..]
#ifdef CONFIG_PCIBIOS
        case PCIBIOS:
                [..]
#endif
        case MEMSIZE: 
                [..]
#ifdef CONFIG_INT21HANDLER
        case 0x15:
                [..]
#endif
        default:
                [..]
        }

It looks like this case construct was done for readability, but in fact 
some kind of interrupt lookup table is needed to handle things
correctly.

         Stefan




From YhLu at tyan.com  Mon May 17 11:25:01 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 17 11:25:01 2004
Subject: USB boot
Message-ID: <3174569B9743D511922F00A0C943142305063E9B@TYANWEB>

Let me know if your testbed is ready, and I would send my last usb dir tar
ball to you.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?17? 6:14
???: YhLu
??: Linuxbios; Takeshi Sone
??: Re: USB boot

Greetings,

Sorry about the delay in replying.

The length field is encoded as n-1 with 0x7ff a special value meaning 0.

IIRC, a USB protocol error would cause a stall condition. A 0 transfer
when data is expected is a SCSI level error.

As you can see, the USB code doesn't have nearly enough error checking.

It looks like control messages are fine since the device gets configured,
but the bulk transfers seem to be broken.

It might be good to write poison to the buffers to verify that no data
goes to them.

Since everything seems to be returning no data, probably the SCSI command
is not being sent to the device correctly.

Hopefully, this week, I can get my test board going again so I can do some
debugging as well.

G'day,
sjames


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


On Fri, 14 May 2004, YhLu wrote:

> Here are the new results.
>
> 1. for usb_control_msg: every return + 2047 packet????
> 2. for bulk_transfer: every out is ok, but every in only return fixed 2048
> len data.
>
> Regards
>
> YH
>
> Loading Etherboot version: 5.2.4
> ROM segment 0x0000 length 0x0000 reloc 0x00020000
> CPU 2285 Mhz
> Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO]
> Relocating _text from: [0002d5f0,0008fc20) to [efe9d9d0,eff00000)
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:27
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> [tg3-5704]Ethernet addr: 00:E0:81:61:8C:28
> Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
> <abort>
> Probing pci nic...
> Probing pci disk...
> [FILO]FILO version 0.4.1 (root at tst2723-rh9) Fri May 14 17:10:13 PDT 2004
> Press <Enter> for default boot, or <Esc> for boot prompt...
> boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> LinuxLabs USB bootloader
> raw frame_list is at 00079560
> frame_list is at 00079630
> frame_list_link: addr: 00078570
> frame_list_link:  raw addr: efef5f40
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070500
> raw frame_list is at 0007b560
> frame_list is at 0007b630
> frame_list_link: addr: 00078590
> frame_list_link:  raw addr: efef5f60
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070540
> raw frame_list is at 0007d560
> frame_list is at 0007d630
> frame_list_link: addr: 000785b0
> frame_list_link:  raw addr: efef5f80
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 00070580
> raw frame_list is at 0007f560
> frame_list is at 0007f630
> frame_list_link: addr: 000785d0
> frame_list_link:  raw addr: efef5fa0
> frame_list_link: terminate: 00000000
> frame_list_link: queue: 00000001
> frame_list_link: depth: 00000000
> dummy_td = 000705c0
> Found OHCI at 0d182630
> Resetting OHCI
> USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting
framelist
> to: efef7000
> Starting OHCI
> Found OHCI at 0d183630
> Resetting OHCI
> USB HC reset_hc usb-0d183630: ctrl = 0x00000600 ;ohc_init setting
framelist
> to: efef9000
> Starting OHCI
> Found UHCI at 00002400
> Resetting UHCI
> uhc_init setting framelist to: efefb000
> Starting UHCI
> HCI at 00002400
> Found UHCI at 00002420
> Resetting UHCI
> uhc_init setting framelist to: efefd000
> Starting UHCI
> HCI at 00002420
> poll_usb1 i=0   poll_usb1 i=1   poll_usb1 i=2   poll_u_root_hub1
v=00000480
> poll_u_root_hub1 v=00001493poll_u_root_hub2 v=00001493
poll_u_root_hub21
> v=00001493    Connection on port 00002412
> New USB device, setting address 00000003
> usb_control_msg: request_type = 00000000 request = 00000005 wLength=0
> usb_control_message returning 2047
> Fetching device descriptor length
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
> usb_control_message returning 2054
> Fetching device descriptor
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=18
> usb_control_message returning 2064
> Fetching config descriptor length
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=8
> usb_control_message returning 2054
> Fetching config descriptor
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> device:
> bLength: 00000012
> type: 00000001
> bcdVersion: 0000000200000000
> Class: 00000000
> SubClass: 00000000
> protocol: 00000000
> max_packet: 00000040
> idVendor: 00001005
> idProduct: 0000b113
> bcdDeviceVersion: 0000000100000000
> iManufacturor: 00000000
> iProduct: 00000001
> iSerial: 00000002
> bNumConfig: 00000001
> config:
> bLength: 00000009
> type: 00000002
> wTotalLength: 00000020
> bNumInterfaces: 00000001
> bConfigurationValue: 00000001
> iConfiguration: 00000000
> bmAttributes: 00000080
> bMaxPower: 000000fa
>
> Interface(00081e6b):
>         bLength: 00000009
>         type: 00000004
>         bInterfaceNumber: 00000000
>         bAlternateSetting: 00000000
>         bNumEndpoints: 00000002
>         bInterfaceClass: 00000008
>         bInterfaceSubClass: 00000006
>         bInterfaceProtocol: 00000050
>         iInterface: 00000000
>
>         Endpoint (00081e74):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000081
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
>
>         Endpoint (00081e7b):
>                 bLength: 00000007
>                 type: 00000005
>                 bEndpointAddress: 00000002
>                 bmAttributes: 00000002
>                 wMaxPacketSize: 00000040
>                 bInterval: 00000000
> Selecting Configuration number 00000001:
> usb_control_msg: request_type = 00000000 request = 00000009 wLength=0
> usb_control_message returning 2047
> clear stall on ep=00000081
> usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
> usb_control_message returning 2047
> clear stall on ep=00000002
> usb_control_msg: request_type = 00000002 request = 00000001 wLength=0
> usb_control_message returning 2047
> 00000008:00000006:00000050
> Manufacturor: unknown
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
> usb_control_message returning 2050
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> Product: USB Flash Drive
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=4
> usb_control_message returning 2050
> usb_control_msg: request_type = 00000080 request = 00000006 wLength=32
> usb_control_message returning 2078
> Serial: 070B01001340CA0
> desc address (phy) = efeff820, (virt) = 00081e50
> conf address (phy) = efeff832, (virt) = 00081e62
> Mass storage, bulk only SCSI transparent
> Requesting initial sense data
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> bulk_transfer: ep = 00000081 len=32
> bulk_transfer returning 2048
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> sense data
>
:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
>
00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
>
0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
> 000000:00000000:00000000:00000000:00000000:00000000:00000000
>
> code = 00000000 key = 00000000
>
> Info: 00000000
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 8 bytes
> bulk_transfer: ep = 00000081 len=8
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> 1 0 byte blocks
> part address (phy) = efeff400, (virt) = 00081a30
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> ll_read_block returns 512
> 0: boot=00000000, start=00000000 length=00000000
> 1: boot=00000000, start=00000000 length=00000000
> 2: boot=00000000, start=00000000 length=00000000
> 3: boot=00000000, start=00000000 length=00000000
> DEVICE CONFIGURED
> poll_usb1 i=3   poll_u_root_hub1 v=00000480     poll_u_root_hub1
v=00000480
> poll_usb1 i=0   poll_usb1 i=1poll_usb1 i=2   poll_u_root_hub1 v=00000480
> poll_u_root_hub1 v=00000495     poll_usb1 i=3   poll_u_root_hub1
v=00000480
> poll_u_root_hub1 v=00000480     Found USB block device 3
> Requesting initial sense data
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> bulk_transfer: ep = 00000081 len=32
> bulk_transfer returning 2048
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> sense data
>
:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000
>
00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000
>
0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00
> 000000:00000000:00000000:00000000:00000000:00000000:00000000
>
> code = 00000000 key = 00000000
>
> Info: 00000000
> bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> ll_read_block returns 512
> part address (phy) = efeffa94, (virt) = 000820c4
> 0: boot=00000000, start=00000000 length=00000000
> 1: boot=00000000, start=00000000 length=00000000
> 2: boot=00000000, start=00000000 length=00000000
> 3: boot=00000000, start=00000000 length=00000000
> sector= 0     bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
> sector= 68      bulk_transfer: ep = 00000002 len=31
> bulk_transfer returning 31
> scsi_command reading 512 bytes
> bulk_transfer: ep = 00000081 len=512
> bulk_transfer returning 2048
> scsi_command read 2048 bytes
> scsi_command fetching csw
> bulk_transfer: ep = 00000081 len=13
> bulk_transfer returning 2048
> scsi_command csw is 2048 bytes
>


From YhLu at tyan.com  Mon May 17 11:29:00 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 17 11:29:00 2004
Subject: =?GB2312?B?tPC4tDogVVNCIGJvb3Q=?=
Message-ID: <3174569B9743D511922F00A0C943142305063E9E@TYANWEB>

Not yet.

Status:
1. UHCI support: bulk transfer not working.
2. OHCI support: need add code to support ED and TD this week.

Regards

YH

-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?17? 8:36
???: YhLu
??: linuxbios at clustermatic.org; pyro at linuxlabs.com
??: Re: USB boot

Has the code for USB support been committed, and if so, where?

Thanks,

Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com




From rminnich at lanl.gov  Mon May 17 15:30:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 17 15:30:01 2004
Subject: Epia-MII VGA not working ...
In-Reply-To: <1084783954.15547.81.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405171448070.11030-100000@maxroach.lanl.gov>

On 17 May 2004, Mathieu Deschamps wrote:

> INSTALL REAL-MODE IDT
> DO THE VGA BIOS
> found VGA: vid=1106, did=3122
> write_protect_vgabios
> 0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca 0x83 0x0 0x0 0x0
> 0x0 bus/

that means it is ok.




From rminnich at lanl.gov  Mon May 17 15:38:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 17 15:38:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <20040517161017.GA2551@openbios.org>
Message-ID: <Pine.LNX.4.44.0405171456570.11030-100000@maxroach.lanl.gov>

On Mon, 17 May 2004, Stefan Reinauer wrote:

> There's a potential hint in src/arch/i386/lib/idt.c:biosint():
> 
>         // cases in a good compiler are just as good as your own tables. 
>         switch (intnumber) {
>         case 0 ... 15:
>                 [..]
> #ifdef CONFIG_PCIBIOS
>         case PCIBIOS:
>                 [..]
> #endif
>         case MEMSIZE: 
>                 [..]
> #ifdef CONFIG_INT21HANDLER
>         case 0x15:
>                 [..]
> #endif
>         default:
>                 [..]
>         }
> 
> It looks like this case construct was done for readability, but in fact 
> some kind of interrupt lookup table is needed to handle things
> correctly.
> 

guilty as charged. I tried to make it readable but had no idea that we 
would need a table. Ignorance on my part.

ron



From linuxbios at xdr.com  Mon May 17 19:20:00 2004
From: linuxbios at xdr.com (Dave Ashley)
Date: Mon May 17 19:20:00 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
Message-ID: <200405180039.i4I0dPxs012035@xdr.com>

> b8? Anybody know what that one is?

The vgabios itself has a bug in it. The b8 is an invalid INT # and
what has happened is the vgabios code itself has crashed and is executing
randomly. On the EPIA-M I had seen this problem on certain units where if
the motherboard got too hot (but not really that hot) and you reboot, it
would just sit there beeping forever with its onboard noisemaker. This was
with the stock AWARD bios. The problem would go away if I set up a fan to
blow on the motherboard and cool it down.

Under linuxbios the problem would manifest itself where during the vgabios
init code you'd get into an endless loop of invalid INT callbacks. So it
would stop the system from booting.

My "fix" was to only allow certain INT's in the callback and so if an
invalid one happens, we just abort out of the VGA init code. This worked fine
for our purposes, the vgabios had been able to init the hardware enough to
get the system working, and life could go on. Note also when this endless
INT callback thingy happened in linuxbios, if I blasted the fan on the
motherboard to cool it down, that would fix the problem.

I really don't know how a bug in the vgabios could manifest itself only on
certain motherboards and only when they get hot. But it's not impossible.

Note these int21 handler code was required for getting the vgabios working
on the EPIA-M. Whether the thing is a case statement or a table is
irrelevant, the case statement approach allows for endless customization.
The point is the int21 callbacks must be implemented. That's how a black
box like the vgabios can be delivered to VIA without source, yet VIA can
integrate it into their AWARD bios. The INT 21 callbacks like 4F01 are for
the vgabios to query the system to find out how much video ram has been
reserved for the display (I default to 8M), what is the preferred output
device, and other mysterious and poorly documented settings. The documentation
I was going on was the CLE266 BIOS PORTING GUIDE from VIA, an NDA document.
It is cryptic and incomplete (typical). It doesn't cover all of the INT21
callbacks that the vgabios makes use of.

Even if you boot off the AWARD bios, then run the vgabios with the emulator
and make use of the AWARD bios to know what to return for these 4fxx INT21
callbacks, you're still left with the bug in the vgabios itself. I'm satisfied
there is a bug there so I haven't spent any more time trying to improve the
situation.

Long story short I don't know why Ignacio Verona's not getting VGA output
on his EPIA-MII. However there is a reason for all the business in linuxbios
with the unsupport int printing + aborting the vgabios execution and the
code in the epia-m tree that handles the callbacks, so don't start thinking
about ripping it out unless you really know what you're doing.

-Dave



From mdeschamps at mangrove-systems.com  Tue May 18 02:19:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 18 02:19:01 2004
Subject: bios documentation
Message-ID: <1084865829.11334.10.camel@Calliphara>

Hello,

Here's what i've found for low level programmers :]
It's a doc on PCAT BIOS, detailling every interruptions
and their values  .This is just fine a trusted adress 
but it's all in french. 
If you're looking for these type of infos
go and have a look : http://www.qsl.net/f6flv

mathieu.


From mdeschamps at mangrove-systems.com  Tue May 18 02:49:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 18 02:49:00 2004
Subject: Epia-MII VGA not working ...
In-Reply-To: <Pine.LNX.4.44.0405171448070.11030-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405171448070.11030-100000@maxroach.lanl.gov>
Message-ID: <1084867552.11334.40.camel@Calliphara>

ok so this is what i aim to.


Le lun 17/05/2004 ? 22:48, ron minnich a ?crit :
> On 17 May 2004, Mathieu Deschamps wrote:
> 
> > INSTALL REAL-MODE IDT
> > DO THE VGA BIOS
> > found VGA: vid=1106, did=3122
> > write_protect_vgabios
> > 0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca 0x83 0x0 0x0 0x0
> > 0x0 bus/
> 
> that means it is ok.
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


From mdeschamps at mangrove-systems.com  Tue May 18 03:29:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 18 03:29:00 2004
Subject: Config.lb language
Message-ID: <1084869949.11334.75.camel@Calliphara>

Hello,

I'am looking for a while to set a new options in Config.lb to test
my V2 VGABIOS code : i need VGABIOS_START options and ZKERNEL
START also, theses are deprecated in V2. Is the config python script
openned to user's new entries ? 
I've read in Stefan Reinauer's AMD 64 port guide in Command definitions
section from Language that he declares option A=(1+2) or option B=0xa.
Why not... but in this case wouldn't the script complains while using
a undeclared option ? Further in, if declared it'll complained it is
a unexistant option ... so how could I add my option entry in the
config dictionnary without making any DIY fixup nor breaking rules of
use ? 
BTW i know this question may be senstive (but sensible:) couldn't
it be possible that the config.py  dictionnary  be external
and no longer err.. BTW where is it holds exactly ?!?
I mean to be able to see in a external file (i let external to
config.py)  commands and codes it triggers (commands and available
options). Then this file could be parse by config.py. IHMO, add a
options would be far easier :)

mathieu. 




From stepan at openbios.org  Tue May 18 04:06:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue May 18 04:06:01 2004
Subject: Config.lb language
In-Reply-To: <1084869949.11334.75.camel@Calliphara>
References: <1084869949.11334.75.camel@Calliphara>
Message-ID: <20040518092800.GA11087@openbios.org>

* Mathieu Deschamps <mdeschamps at mangrove-systems.com> [040518 10:45]:
> I'am looking for a while to set a new options in Config.lb to test
> my V2 VGABIOS code : i need VGABIOS_START options and ZKERNEL
> START also, theses are deprecated in V2. Is the config python script
> openned to user's new entries ? 

This is probably what you are looking for:
     freebios2/src/config/Options.lb

Stefan



From pk at mailamig.nu  Tue May 18 05:30:01 2004
From: pk at mailamig.nu (Peter Karlsson)
Date: Tue May 18 05:30:01 2004
Subject: bios documentation
Message-ID: <20040518104945.9A26B3963@sitemail.everyone.net>

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

From stepan at openbios.org  Tue May 18 05:44:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue May 18 05:44:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <200405180039.i4I0dPxs012035@xdr.com>
References: <200405180039.i4I0dPxs012035@xdr.com>
Message-ID: <20040518110624.GA12249@openbios.org>

* Dave Ashley <linuxbios at xdr.com> [040518 02:39]:
> Note these int21 handler code was required for getting the vgabios working
> on the EPIA-M. Whether the thing is a case statement or a table is
> irrelevant, the case statement approach allows for endless customization.

So, in an award setup this is provided by award bios rather than being
setup by the video bios itself? Sounds like a specific issue of Via
onboard graphics in this case then.

Thus the way it is implemented is perfectly fine, except that the int21 
handler has to be advanced to cope with all the AX values fed into it.
I suggest also adding a default case to notify the user about
unimplemented values for AX.

    Stefan




From stepan at openbios.org  Tue May 18 05:54:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue May 18 05:54:01 2004
Subject: Epia-MII VGA not working and PCMCIA rebooting
In-Reply-To: <Pine.LNX.4.44.0405171456570.11030-100000@maxroach.lanl.gov>
References: <20040517161017.GA2551@openbios.org> <Pine.LNX.4.44.0405171456570.11030-100000@maxroach.lanl.gov>
Message-ID: <20040518111534.GB12249@openbios.org>

* ron minnich <rminnich at lanl.gov> [040517 22:57]:
> guilty as charged. I tried to make it readable but had no idea that we 
> would need a table. Ignorance on my part.

Not in this case as David explained. I actually assumed there was some
problem with 16<-->32bit jumping if an option rom is allowed to set up 
it's own int-handler or something. This question will come back when we
want to have raid controllers or scsi adapters installing their own
int 13 for booting from attached disks though.

    Stefan



From mdeschamps at mangrove-systems.com  Tue May 18 06:12:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 18 06:12:01 2004
Subject: bios documentation
In-Reply-To: <20040518104945.9A26B3963@sitemail.everyone.net>
References: <20040518104945.9A26B3963@sitemail.everyone.net>
Message-ID: <1084879701.11806.1.camel@Calliphara>

I haven't check this out, anyway some good technical
translator in computing could do the job...

mathieu

Le mar 18/05/2004 ? 12:49, Peter Karlsson a ?crit :
> --- Mathieu Deschamps <mdeschamps at mangrove-systems.com> wrote:
> >Hello,
> >
> >Here's what i've found for low level programmers :]
> >It's a doc on PCAT BIOS, detailling every interruptions
> >and their values  .This is just fine a trusted adress 
> >but it's all in french. 
> >If you're looking for these type of infos
> >go and have a look : http://www.qsl.net/f6flv
> 
> Is there an english version of this
> (http://www.qsl.net/f6flv/docbios.html)?
> 
> Best regards
> 
> Peter Karlsson
> 
> 
> _____________________________________________________________
> Gratis e-postadress ---> http://www.mailamig.nu
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


From jmiller at actuality-systems.com  Tue May 18 07:03:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Tue May 18 07:03:00 2004
Subject: Getting Started with freebios2!
Message-ID: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>

Disclaimer:  I too am a N00B and these are my observations thus far.
They may not be 100% correct, but these things have worked for me.  I
hope that they'll help other N00Bz get started.

WHAT IS FREEBIOS2?

Well I stumbled upon freebios2 when I couldn't find support in the
freebios tree for my Tyan s2885.  Then I noticed under the CVSWeb
browser for the project the freebios2 directory.

Apparently, this is what will be LinuxBIOS V2.  They've done away with
kernel patches, so you don't need to worry about patching the kernel
like in V1.  Instead there is an intermediary payload that can be
Etherboot, FILO, or some other loader to get your Linux kernel into
memory.

WHY CAN'T I GET THE SOURCES FROM SOURCEFORGE (ANYMORE)?

If you're like me, all of a sudden CVS access stopped working.  Well,
they changed the BIND implementation, so the documentation is out of
date.  You need to use, "cvs
-d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios login".
There is still no password for anonymous login.

WHERE DO I START?

Build the documentation under freebios2/documentation.  It will give you
a solid overview of how the project works, including how to download the
source you just downloaded. ;-)

Freebios2 supports a number of newer boards.  Tyan are particularly
well-supported and the EPIA boards are actively being worked on.  Look
under, "freebios2/targets..." for the collection.	

HOW DO I BUILD FREEBIOS2?
	
Once you've selected a vendor and mainboard you should execute,
"./buildtarget <vendor>/<board>".  This will generate all sources
specific to your mainboard.  To make a rom image, start your make in the
freebios2/targets/<vendor>/<board>/<board> directory.  If all goes
smoothly you should get a linuxbios.rom image.

HOW DO I FLASH A ROM?

There are a number of methods and I'm not versed enough to cover them
all.  But I have successfully used the BIOS flash utility from AMI, and
I currently use a professional Data I/O burner.  I spent a lot of time
trying to figure out the proper format to use on my burner.  There is no
format; it's just a straight binary image, so use binary mode (on the
Data I/O it's "absolute binary (16)").

There is also a flash-n-burn utility in the source tree.  Perhaps
someone on the list can add the specifics of how to get that going on
this thread.


HOW DO I CHANGE CONFIGURATION OF MY IMAGE?

First take a look at freebios2/targets/<vendor>/<board>/Config.lb.  This
is the main configuration file for your ROM image.  This is where you
specify what payload to use, and most of the settings that anyone would
care about.  Make sure to do a "./buildtarget <vendor>/<board>" whenever
you modify this file.

However, in my case I was running into issues running my dual-processor
board with only one processor.  As it turns out there is another
Config.lb located in freebios2/src/mainboard/<vendor>/<board>.  This
file controls the contents of some of the generated sources for your
board.  To date, this is the only way I was able to prevent my ROM image
from trying to initialize a CPU that wasn't there. 

WHY DON'T I SEE ANYTHING HAPPENING?

In most cases the VGA support just isn't there yet.  So go find yourself
a null modem cable and hook up your console at 15200-8-N-1, and sit back
and watch the fireworks!


WHAT ABOUT PAYLOADS?

I'm currently exploring this area.  The first payload I used
successfully was FILO.  No you don't make pastry with it.  It is a
bootloader that acts much like LILO.  You can get the source here:
http://felixx.tsn.or.jp/~ts1/filo.

If you have an IDE disk with a Linux kernel on it, this is the way to
get started.

If you're diskless then you may want to try Etherboot:
http://etherboot.sourceforge.net.  This payload gives you the ability to
load over the network, but requires you to configure a DHCP server and
TFTP server at a minimum.  

Like LinuxBIOS, Etherboot expects an ELF formatted image, so if you're
loading a kernel across the network you need to run it through
mkelfImage.  As of now the correct version to use is 2.5.  You can get
the latest sources here:
ftp://ftp.lnxi.com/pub/mkelfImage/mkelfImage-2.5.tar.gz.


WHAT ABOUT ZELF?

This is my latest N00B stumbling block, and unfortunately I haven't
found an answer.  I know that it's a compressed elf format, but I can't
figure out what I need to do to get elfboot (part of LinuxBIOS) to load
payloads with the ZELF extension.  So for now I would recommend N00Bz
stick with ELF format, until we get a definitive answer.


Hope this is helpful, good luck!


Jay Miller
Actuality Systems, Inc.
jmiller at acutality-systems.com





From kfuchs at winternet.com  Tue May 18 09:36:01 2004
From: kfuchs at winternet.com (Ken Fuchs)
Date: Tue May 18 09:36:01 2004
Subject: bios documentation
Message-ID: <200405181455.i4IEtJFs006799@tundra.winternet.com>

Peter Karlsson wrote:

>Is there an English version of this
>(http://www.qsl.net/f6flv/docbios.html)?

Here's what http://translate.google.com offers:

http://translate.google.com/translate?hl=en&sl=fr&u=http://www.qsl.net/f6flv/docbios.html&prev=/search%3Fq%3Dsite:qsl.net%2BPROM%2BBIOS%26num%3D100%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DG

I don't think it's a very good translation, but it's better than
nothing, perhaps?

Other free machine translation web servers may a do better job.

Sincerely,

Ken Fuchs <kfuchs at winternet.com>


From mdeschamps at mangrove-systems.com  Tue May 18 10:02:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 18 10:02:01 2004
Subject: bios documentation
In-Reply-To: <200405181455.i4IEtJFs006799@tundra.winternet.com>
References: <200405181455.i4IEtJFs006799@tundra.winternet.com>
Message-ID: <1084893452.11806.6.camel@Calliphara>

I've been also told systran is one of the best
in this situation. I'am not sure but i think
now their online translation are limited to
a 200 char or so... to be testified...

mathieu


Le mar 18/05/2004 ? 16:55, Ken Fuchs a ?crit :
> Peter Karlsson wrote:
> 
> >Is there an English version of this
> >(http://www.qsl.net/f6flv/docbios.html)?
> 
> Here's what http://translate.google.com offers:
> 
> http://translate.google.com/translate?hl=en&sl=fr&u=http://www.qsl.net/f6flv/docbios.html&prev=/search%3Fq%3Dsite:qsl.net%2BPROM%2BBIOS%26num%3D100%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DG
> 
> I don't think it's a very good translation, but it's better than
> nothing, perhaps?
> 
> Other free machine translation web servers may a do better job.
> 
> Sincerely,
> 
> Ken Fuchs <kfuchs at winternet.com>
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


From rminnich at lanl.gov  Tue May 18 12:41:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Tue May 18 12:41:01 2004
Subject: Config.lb language
In-Reply-To: <1084869949.11334.75.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405180732190.17693-100000@maxroach.lanl.gov>

On 18 May 2004, Mathieu Deschamps wrote:

> I'am looking for a while to set a new options in Config.lb to test
> my V2 VGABIOS code : i need VGABIOS_START options and ZKERNEL
> START also, theses are deprecated in V2. Is the config python script
> openned to user's new entries ? 

you don't need these any more, hence they are deprecated. 

> I've read in Stefan Reinauer's AMD 64 port guide in Command definitions
> section from Language that he declares option A=(1+2) or option B=0xa.

Yes, should work ...

> Why not... but in this case wouldn't the script complains while using
> a undeclared option ? Further in, if declared it'll complained it is
> a unexistant option ... so how could I add my option entry in the
> config dictionnary without making any DIY fixup nor breaking rules of
> use ? 

you have to do things in order, it is single pass. Hence the 'use' 
command.

> BTW i know this question may be senstive (but sensible:) couldn't
> it be possible that the config.py  dictionnary  be external
> and no longer err.. BTW where is it holds exactly ?!?

src/Config/Options.lb

It's an external file.

ron



From dwh at lanl.gov  Tue May 18 14:58:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Tue May 18 14:58:00 2004
Subject: Getting Started with freebios2!
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>
Message-ID: <Pine.LNX.4.44.0405181336250.17043-100000@ccs-mail.lanl.gov>

Excellent work! This should prove helpful to those new to the project get 
started. I'd like to elaborate on a few points you have made.
 
On Tue, 18 May 2004, Jay Miller wrote:
>
> HOW DO I FLASH A ROM?
> There is also a flash-n-burn utility in the source tree.  Perhaps
> someone on the list can add the specifics of how to get that going on
> this thread.

Flash-n-burn should work on many newer mainboards, particularly those 
supported by LinuxBIOS such as your Tyan S2885 with an AMD8111 
southbridge. It is currently not capable of flashing in "parallel 
programming" mode like many older chipsets and flash parts require. It 
should work with many newer SST parts and with the PM that comes on your 
S2885. If you require support for another part, let us know and we'll try 
to add it in.


On Tue, 18 May 2004, Jay Miller wrote:
> HOW DO I CHANGE CONFIGURATION OF MY IMAGE?
> 
> First take a look at freebios2/targets/<vendor>/<board>/Config.lb.  This
> is the main configuration file for your ROM image.  This is where you
> specify what payload to use, and most of the settings that anyone would
> care about.  Make sure to do a "./buildtarget <vendor>/<board>" whenever
> you modify this file.

Also, one must run "make" in the <vendor>/<board>/<board> directory. If 
all goes well, linuxbios.rom should appear and will be the appropriate 
size (A power of two, like 2^19 for a half meg part). The size can be set 
in the <vendor>/<board>/Config.lb file.

On Tue, 18 May 2004, Jay Miller wrote:
>
> WHY DON'T I SEE ANYTHING HAPPENING?
> 
> In most cases the VGA support just isn't there yet.  So go find yourself
> a null modem cable and hook up your console at 15200-8-N-1, and sit back
> and watch the fireworks!

We have limited support right now. If you cvs update, you should be able 
to boot LinuxBIOS, run the VGABIOS with the "testbios" utility, and get X 
up and running fully accelerated with an nVidia card (GeForce FX) on that 
S2885 of yours. Here's how you get your VGABIOS (This might have to be 
done with the factory AWARD BIOS): dd if=/dev/mem of=vgabios.bin 
skip=1536 count=128

Ollie Lo is making a lot of progress on support for add-in cards. Please 
check back in upcoming weeks for updates (Ollie is currently in Austin, 
Texas for a conference).

For those wishing to use their integrated RageXL chips, which are common 
for many Tyan mainboards and others like the Arima HDAMA, YhLu has 
recently added support for those as well. Add this to your 
src/mainboard/<vendor>/<board>/Config.lb file:
## ATI Rage XL framebuffering graphics driver
dir /drivers/ati/ragexl

Then add these lines to your targets/<vendor>/<board>/Config.lb file:
uses CONFIG_CONSOLE_BTEXT
option CONFIG_CONSOLE_BTEXT=1

YhLu has a modified version of FILO available which should be used for 
this. I think it's here: 
http://www.clustermatic.org/pipermail/linuxbios/2004-April/007650.html

And lastly, apply YhLu's kernel patch ( 
http://www.clustermatic.org/pipermail/linuxbios/2004-May/007734.html ) and 
enable framebuffering in your kernel. This should allow you to see 
LinuxBIOS, FILO, and your kernel coming up on screen. X should work, too.

I'll get patches and stuff up on personal webspace at a later date. Good 
luck!



From rminnich at lanl.gov  Tue May 18 15:36:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Tue May 18 15:36:01 2004
Subject: Content violation (fwd)
Message-ID: <Pine.LNX.4.44.0405181454410.20513-100000@maxroach.lanl.gov>

Don't let your stupid virus scanner do this :-)

if you can imagine ... the word free in the subject is lo longer allowed 
at some sites.

ron

---------- Forwarded message ----------
Date: Tue, 18 May 2004 15:18:47 -0400
From: Symantec_AntiVirus_for_SMTP_Gateways at amcc.com
To: linuxbios-admin at clustermatic.org
Subject: Content violation

Content violation found in email message.

From: linuxbios-admin at clustermatic.org
To: tdeclerck at 3ware.com

Subject: Re: Getting Started with freebios2!

Matching Subject: *free*




From rminnich at lanl.gov  Tue May 18 15:58:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Tue May 18 15:58:00 2004
Subject: Content violation (fwd)
Message-ID: <Pine.LNX.4.44.0405181516130.20513-100000@maxroach.lanl.gov>

even better. I get this bounce all the time. 

And no, the whitelist registration did not work at all :-)

ron

---------- Forwarded message ----------
Date: Tue, 18 May 2004 23:00:23 +02120 (MEST)
From: contentfilter at becker.de
To: linuxbios-admin at clustermatic.org
Subject: RE: Content violation (fwd)

Absender/Sender: linuxbios-admin at clustermatic.org
Betreff/Subject: Content violation (fwd)
Datum/Date: Tue, 18 May 2004 14:55:21 -0600 (MDT)
Empf?nger/Recipients: IBaab at becker.de

Nachrichten-ID/Message ID: T69a6c0d26eac10df0fa3c

[DEUTSCHER TEXT - SIEHE UNTEN]

The message has not been delivered! It has been classified as unsolicited
automatic mass advertising email (spam) by our content filtering systems.
If this happened in error please send your mail again with the following
keyword added somewhere to the message body: nospam231 If your emails
frequently get misclassified as spam, please contact us at the address
below and we will add you to our whitelist of known senders.

This is an automatically generated email.Do not reply directly. For further inquiry please contact mailsweeper at harmanbecker.com

**************************************************

Die Nachricht wurde nicht zugestellt!
Sie wurde von unseren Content Filtern als unerwuenschte automatische Massenwerbemail (Spam) klassifiziert und gesperrt.
Falls es sich hierbei um einen Irrtum handelt, senden Sie Ihre Nachricht bitte noch einmal, indem Sie an beliebiger Stelle im Nachrichtentext folgendes Schluesselwort hinzufuegen: nospam231
Falls Ihre Nachrichten haeufig faelschlicherweise als Spam klassifiziert werden, benachrichtigen Sie uns bitte unter nachfolgender Mailadresse. Wir werden Sie dann in unsere Liste bekannter Sender aufnehmen.

Dies ist eine automatisch generierte EMail! Antworten Sie nicht direkt darauf. Bei Rueckfragen wenden Sie sich bitte an mailsweeper at harmanbecker.com



From backblue at netcabo.pt  Tue May 18 20:55:01 2004
From: backblue at netcabo.pt (backblue)
Date: Tue May 18 20:55:01 2004
Subject: Getting Started with freebios2!
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>
Message-ID: <20040518031820.2963d0ad@fork.ketic.com>

I like to develop, linuxbios to my motherboards, but none of them are suported, i will show you some lspci of them:

#1:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 [SiS5582] (rev 02)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 01)
00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06)
00:13.0 VGA compatible controller: Silicon Integrated Systems [SiS] 5597/5598/6326 VGA (rev 65)


#2:

00:00.0 Host bridge: Intel Corp. 430VX - 82437VX TVX [Triton VX] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]
00:13.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)


#3:

00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 01)
00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
00:0e.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+]
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)


#4:

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. USB (rev 16)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0d.0 SCSI storage controller: Initio Corporation 360P (rev 02)
01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 02)


I have some more machines, but i would like to know if any of these ones it's suported?

Tks

On Tue, 18 May 2004 08:20:49 -0400
"Jay Miller" <jmiller at actuality-systems.com> wrote:

> Disclaimer:  I too am a N00B and these are my observations thus far.
> They may not be 100% correct, but these things have worked for me.  I
> hope that they'll help other N00Bz get started.
> 
> WHAT IS FREEBIOS2?
> 
> Well I stumbled upon freebios2 when I couldn't find support in the
> freebios tree for my Tyan s2885.  Then I noticed under the CVSWeb
> browser for the project the freebios2 directory.
> 
> Apparently, this is what will be LinuxBIOS V2.  They've done away with
> kernel patches, so you don't need to worry about patching the kernel
> like in V1.  Instead there is an intermediary payload that can be
> Etherboot, FILO, or some other loader to get your Linux kernel into
> memory.
> 
> WHY CAN'T I GET THE SOURCES FROM SOURCEFORGE (ANYMORE)?
> 
> If you're like me, all of a sudden CVS access stopped working.  Well,
> they changed the BIND implementation, so the documentation is out of
> date.  You need to use, "cvs
> -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios login".
> There is still no password for anonymous login.
> 
> WHERE DO I START?
> 
> Build the documentation under freebios2/documentation.  It will give you
> a solid overview of how the project works, including how to download the
> source you just downloaded. ;-)
> 
> Freebios2 supports a number of newer boards.  Tyan are particularly
> well-supported and the EPIA boards are actively being worked on.  Look
> under, "freebios2/targets..." for the collection.	
> 
> HOW DO I BUILD FREEBIOS2?
> 	
> Once you've selected a vendor and mainboard you should execute,
> "./buildtarget <vendor>/<board>".  This will generate all sources
> specific to your mainboard.  To make a rom image, start your make in the
> freebios2/targets/<vendor>/<board>/<board> directory.  If all goes
> smoothly you should get a linuxbios.rom image.
> 
> HOW DO I FLASH A ROM?
> 
> There are a number of methods and I'm not versed enough to cover them
> all.  But I have successfully used the BIOS flash utility from AMI, and
> I currently use a professional Data I/O burner.  I spent a lot of time
> trying to figure out the proper format to use on my burner.  There is no
> format; it's just a straight binary image, so use binary mode (on the
> Data I/O it's "absolute binary (16)").
> 
> There is also a flash-n-burn utility in the source tree.  Perhaps
> someone on the list can add the specifics of how to get that going on
> this thread.
> 
> 
> HOW DO I CHANGE CONFIGURATION OF MY IMAGE?
> 
> First take a look at freebios2/targets/<vendor>/<board>/Config.lb.  This
> is the main configuration file for your ROM image.  This is where you
> specify what payload to use, and most of the settings that anyone would
> care about.  Make sure to do a "./buildtarget <vendor>/<board>" whenever
> you modify this file.
> 
> However, in my case I was running into issues running my dual-processor
> board with only one processor.  As it turns out there is another
> Config.lb located in freebios2/src/mainboard/<vendor>/<board>.  This
> file controls the contents of some of the generated sources for your
> board.  To date, this is the only way I was able to prevent my ROM image
> from trying to initialize a CPU that wasn't there. 
> 
> WHY DON'T I SEE ANYTHING HAPPENING?
> 
> In most cases the VGA support just isn't there yet.  So go find yourself
> a null modem cable and hook up your console at 15200-8-N-1, and sit back
> and watch the fireworks!
> 
> 
> WHAT ABOUT PAYLOADS?
> 
> I'm currently exploring this area.  The first payload I used
> successfully was FILO.  No you don't make pastry with it.  It is a
> bootloader that acts much like LILO.  You can get the source here:
> http://felixx.tsn.or.jp/~ts1/filo.
> 
> If you have an IDE disk with a Linux kernel on it, this is the way to
> get started.
> 
> If you're diskless then you may want to try Etherboot:
> http://etherboot.sourceforge.net.  This payload gives you the ability to
> load over the network, but requires you to configure a DHCP server and
> TFTP server at a minimum.  
> 
> Like LinuxBIOS, Etherboot expects an ELF formatted image, so if you're
> loading a kernel across the network you need to run it through
> mkelfImage.  As of now the correct version to use is 2.5.  You can get
> the latest sources here:
> ftp://ftp.lnxi.com/pub/mkelfImage/mkelfImage-2.5.tar.gz.
> 
> 
> WHAT ABOUT ZELF?
> 
> This is my latest N00B stumbling block, and unfortunately I haven't
> found an answer.  I know that it's a compressed elf format, but I can't
> figure out what I need to do to get elfboot (part of LinuxBIOS) to load
> payloads with the ZELF extension.  So for now I would recommend N00Bz
> stick with ELF format, until we get a definitive answer.
> 
> 
> Hope this is helpful, good luck!
> 
> 
> Jay Miller
> Actuality Systems, Inc.
> jmiller at acutality-systems.com
> 
> 
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios


From mdeschamps at mangrove-systems.com  Wed May 19 10:39:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Wed May 19 10:39:01 2004
Subject: EPIA V2 VGA build succeeded, getting inspired from tyan ?
Message-ID: <1084982217.1205.14.camel@Calliphara>

Hello,

I've been making some port/adapt for epiam vgabios V2  for a few days
now ... and it *seems* my build have succeeded :).
Still have some minor warning though...

I've seen in the tyan source (in the mainboard.c) that the 
DO VGA was *called* here (setup_realmode_idt() and do_vgabios()).
Am I on the good way doing same with via/epia/mainboard.c ?
In other words, is there another c file called first ? If not so
it's obvious it's in it to call the vga init, isn't ?


Thanks for your help, advices, and your good work ...of course. :)
mathieu



From firstone5 at hotmail.com  Thu May 20 14:22:01 2004
From: firstone5 at hotmail.com (M. Renee Hopkins)
Date: Thu May 20 14:22:01 2004
Subject: 256MB or 512MB on EPIA-M
Message-ID: <BAY19-F22tQQC1Stvpt00004c86@hotmail.com>

Does anyone have ideas about modifications to support higher DDR RAM than 
128MB?

I've read some attempts in the list, but they seem to be in error as far as 
I can tell.

Many thanks...

MR

_________________________________________________________________
Get 200+ ad-free, high-fidelity stations and LIVE Major League Baseball 
Gameday Audio! http://radio.msn.click-url.com/go/onm00200491ave/direct/01/



From dwh at lanl.gov  Thu May 20 16:22:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 20 16:22:00 2004
Subject: Making payloads
In-Reply-To: <17587.202.32.178.36.1084505229.squirrel@202.32.178.36>
Message-ID: <Pine.LNX.4.44.0405201540590.17043-100000@ccs-mail.lanl.gov>

It works, I have successfully used it on the Arima HDAMA.

On Fri, 14 May 2004, Takeshi Sone wrote:

> > On Thu, 13 May 2004, Hendricks David W. wrote:
> >
> >> Oops, I forgot to mention Stefan's patch for FILO to make IDE work on
> >> the
> >> S2885. I think this is the one:
> >> http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html
> >
> > can we get this put back into filo?
> 
> Actually I have got this fixed in my tree and have prepared it as a
> bugfix release (dated Oct-31 2003).
> 
> Now I have just put this tarball at
> http://te.to/~ts1/filo/filo-0.4.2.tar.bz2 .
> PCI_BRUTE_SCAN option should enable PCI IDE on K8 systems.
> 
> Please test this, as I have not tested this source tree for 6 months.
> 



From rminnich at lanl.gov  Thu May 20 18:22:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 20 18:22:01 2004
Subject: 256MB or 512MB on EPIA-M
In-Reply-To: <BAY19-F22tQQC1Stvpt00004c86@hotmail.com>
Message-ID: <Pine.LNX.4.44.0405201741180.7676-100000@maxroach.lanl.gov>

On Thu, 20 May 2004, M. Renee Hopkins wrote:

> Does anyone have ideas about modifications to support higher DDR RAM than 
> 128MB?

V2. 

ron



From jbors at mail.ru  Thu May 20 23:15:01 2004
From: jbors at mail.ru (Dmitry Borisov)
Date: Thu May 20 23:15:01 2004
Subject: EPIA V2 VGA build succeeded, getting inspired from tyan ?
References: <1084982217.1205.14.camel@Calliphara>
Message-ID: <00d801c43eec$fa593210$0900a8c0@amr.corp.intel.com>

----- Original Message ----- 
From: "Mathieu Deschamps" <mdeschamps at mangrove-systems.com>
Subject: EPIA V2 VGA build succeeded, getting inspired from tyan ?


> Hello,
> 
> I've been making some port/adapt for epiam vgabios V2  for a few days
> now ... and it *seems* my build have succeeded :).
> Still have some minor warning though...
> 
> I've seen in the tyan source (in the mainboard.c) that the 
> DO VGA was *called* here (setup_realmode_idt() and do_vgabios()).
> Am I on the good way doing same with via/epia/mainboard.c ?
> In other words, is there another c file called first ? If not so
> it's obvious it's in it to call the vga init, isn't ?

Good news. Can we all try it out also from CVS or not yet ?
I would be interested to tweak it the way V1 works now.
Keep it up.
Dmitry/


From YhLu at tyan.com  Fri May 21 15:45:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 21 15:45:01 2004
Subject: =?GB2312?B?tPC4tDogVVNCIGJvb3Q=?=
Message-ID: <3174569B9743D511922F00A0C943142305064229@TYANWEB>

Steven,

I have moved ED/TD processing from 2.4.22 to the usb support of
FILO/Etherboot. the ED and TD have been linked already, but the HC didn't
precess the list???

Please let me know if you want my latest tar ball.

Regards

YH



From mdeschamps at mangrove-systems.com  Mon May 24 02:21:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Mon May 24 02:21:00 2004
Subject: Hear.sh
In-Reply-To: <BAY2-F500z0plqqFGOc00025960@hotmail.com>
References: <BAY2-F500z0plqqFGOc00025960@hotmail.com>
Message-ID: <1085384335.12788.18.camel@Calliphara>

Typically this is a ' or a " that's not close where it should, maybe
have i missed copy/paste the script. Anyhow here are a new version. Let
me know if it goes wrong. Both theses script in the same directory.


Hear script--------------

#!/bin/sh
#
# Hear script  listen & log onto ttyS0 (serial port a.k.a COM1)
#
#
VERSION="24/05/04|09:32:49 MD"
SPEED="115200"
i="Bienvenu(e) dans Hear! v. $VERSION j'ecoute sur ttyS0 ..."
ter=`tty`
if [ "x$1" = "x" ]; then
  echo "Usage $0 log_to_file"
  exit 0
 else
  LOG="$1"
fi
echo $i
echo  "Logging in $LOG"
stty ispeed $SPEED
stty | tee -a "$LOG"
echo "****************************************************" >>"$LOG" 
echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> "$LOG"
echo "  tty in use : $ter  from ttyS0 " >>"$LOG"
echo "****************************************************" >>"$LOG"

  /usr/bin/time -pao "$LOG" -- cat -sbA </dev/ttyS0 | tee -a "$LOG" 
  
  ./digest.sh "$LOG" -s

  echo "----------------------------------------------" >> "$LOG"
  echo -e "\n"
  echo "Please add a comment to this boot log .."
  sleep 3 
  vi tmp
  echo -e "Comments :\n" >> "$LOG"
  cat tmp >> "$LOG"
  rm -f tmp

  echo "done."




Digest script--------------



#!/bin/bash
#
# Script to digest hard-human readable hear! logs
#  Mathieu Deschamps for mangrove-systems
#
VERSION="11/05/04|09:40:28 MD"
SUPP=0
DAT="`date +%d\-%m\-%y\ %T`"
if  [ "x$1" = "x"  ]; then
        echo "usage: $0 hear!_log_file [--suppress-log,-s] " 
        echo "v. $VERSION"
        exit 0
  else
        FIL="$1"
fi

[ "x$2" = "x-s" ] || [ "x$2" = "x--suppress-log" ]  && SUPP=1

if [ -f "$FIL.adv" ]; then
  mv "$FIL.adv"  "$FIL.adv.$DAT"
fi



cat $FIL | while read line; 
        do 
                [ "x$line" != "x$" ] && echo "$line"
        done >  "$FIL.adv"

mv -f $FIL $FIL.digested
mv -f $FIL.adv $FIL
( [ $? -eq 0 ];  echo "$FIL digested, rename old as $FIL.digested" ) ||
echo "Digestion gets harden ...blurp (error) "

[ $SUPP -eq 1 ] && rm -f $FIL.digested 2>&1 >/dev/null 



Le ven 21/05/2004 ? 17:28, Thomas Spear a ?crit :
> Mathieu -
> 
> I can't run your hear.sh script.  I get "Line 25: unexpected end of file" 
> when I try.  What do I need to do to fix it?  Thanks.
> 
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar  get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> 
> 


From mdeschamps at mangrove-systems.com  Mon May 24 03:21:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Mon May 24 03:21:00 2004
Subject: Lbcc tool
Message-ID: <1085388000.12788.54.camel@Calliphara>

Hello,

I use a home made tool since the beginnig and during my test it goes 
more and more powerful and usefull. through making and using it I've
understood the build process, may it be the same for you. There is
nothing really new in it, it centralize and does everything in one
command (prior settings needed of course) ... 
finally i'll name it lbcc.

Lbcc
  a script that does build your target machine (ex : VIA config)
  and build your rom with log and so on. Heavily refactored
  and strenghen to be more portable and robust. Form it
  you can control the whole process of making a LinuxBIOS
  booting a payload.

                It does :
                                - config LinuxBios
                                - Log ALL activity
                                - Calculate build time
                                - Display rom bindings
                                - Choose payload
                                - Configure payload
                                - Make payload
                                - Make the rom
                                - Flash the rom
                                - Make coffee .. err .. no still not :)
		To come :
				- Itegrate videobios
 
some advices :

It needs to be copied into the freebios2/target and it need lb_flash,
think of making symbolic link to it and after to the lbcc generated logs
like buildtaget.log and make.log, etc..

It'll *NEED* some of *YOUR* path fix into its head. If it bugs, think
of this, anyway, find in script bug's exact place. Since this logs
everything think of having a look to theses and often you'll get your
answer (that's the aim of this facility :)
If you are lost into it or troubled with a bug I can reply/explain to
detailed requested. 

disclaim:
Actually, this is a comfort and maybe it *couldn't be usefull to
everyone*, ask yourself if some necessary adapt time is worth this ease.
A last number : It is 400 lines of bash script code



any comments, ideas, etc.. reply onto this thread.

Good lxbiosing.

mathieu.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lbcc
Type: text/x-sh
Size: 10850 bytes
Desc: 
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040524/a4ddebeb/attachment.bin>

From rminnich at lanl.gov  Mon May 24 10:36:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 24 10:36:01 2004
Subject: Lbcc tool
In-Reply-To: <1085388000.12788.54.camel@Calliphara>
Message-ID: <Pine.LNX.4.44.0405240956430.22054-100000@maxroach.lanl.gov>

I will try this tool and if it looks good perhaps we can put it into 
freebios2/util/lbcc

ron



From YhLu at tyan.com  Mon May 24 11:23:00 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 24 11:23:00 2004
Subject: =?GB2312?B?tPC4tDogTGJjYyB0b29s?=
Message-ID: <3174569B9743D511922F00A0C9431423050642B7@TYANWEB>

 I wonder what is your develop configuration.

For me there is 
Dev server: compile linuxbios + dhcp server + tftp server.
Testbed: S2882
Terminal Machine: ....

After booting up, I use ftp to get rom image in dev server and flash that
into rom.

I'm curious that how you can use the flash tool in DEV server???

Regards

YH



-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?24? 8:57
???: Mathieu Deschamps
??: Linuxbios at clustermatic.org
??: Re: Lbcc tool

I will try this tool and if it looks good perhaps we can put it into 
freebios2/util/lbcc

ron

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


From ollie at lanl.gov  Mon May 24 13:52:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Mon May 24 13:52:01 2004
Subject: AGP VGA support committed
Message-ID: <1085425926.5653.8.camel@exponential.lanl.gov>

Hello,

I committed the support for AGP/VGA in AMD K8. The IO/MEM resources
should be set correctly and the only thing one have to do to init
an Nvidia AGP card is run the testbios emulator with the VGA BIOS.

I am going to move the emulator into LinuxBIOS in the near future
so we can have VGA console earilier.

Ollie




From YhLu at tyan.com  Mon May 24 14:30:00 2004
From: YhLu at tyan.com (YhLu)
Date: Mon May 24 14:30:00 2004
Subject: =?GB2312?B?tPC4tDogQUdQIFZHQSBzdXBwb3J0IGNvbW1pdHRlZA==?=
Message-ID: <3174569B9743D511922F00A0C943142305064302@TYANWEB>

Does the emulator works with ATI vgabios?

After execute the vgabios, do you get the normal text console?

Regards

YH

-----????-----
???: Li-Ta Lo [mailto:ollie at lanl.gov] 
????: 2004?5?24? 12:12
???: LinuxBIOS
??: AGP VGA support committed

Hello,

I committed the support for AGP/VGA in AMD K8. The IO/MEM resources
should be set correctly and the only thing one have to do to init
an Nvidia AGP card is run the testbios emulator with the VGA BIOS.

I am going to move the emulator into LinuxBIOS in the near future
so we can have VGA console earilier.

Ollie


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


From rminnich at lanl.gov  Mon May 24 14:35:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Mon May 24 14:35:00 2004
Subject: =?GB2312?B?tPC4tDogQUdQIFZHQSBzdXBwb3J0IGNvbW1pdHRlZA==?=
In-Reply-To: <3174569B9743D511922F00A0C943142305064302@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405241354580.22054-100000@maxroach.lanl.gov>

On Mon, 24 May 2004, YhLu wrote:

> Does the emulator works with ATI vgabios?
> 

not yet, this is due to the long-standing INT 10 problem

That fix is on our to-do list.

ron



From ollie at lanl.gov  Mon May 24 14:43:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Mon May 24 14:43:00 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= AGP VGA support committed
In-Reply-To: <3174569B9743D511922F00A0C943142305064302@TYANWEB>
References: <3174569B9743D511922F00A0C943142305064302@TYANWEB>
Message-ID: <1085429002.5653.18.camel@exponential.lanl.gov>

On Mon, 2004-05-24 at 14:02, YhLu wrote:
> Does the emulator works with ATI vgabios?
> 
> After execute the vgabios, do you get the normal text console?
> 

Not yet, I just came from the conference and I also want to clean
up the current code a little bit. I will try to support other vga
cards asap. My goal is to support major vga brands in LinuxBIOS
before end of June.

Ollie




From mdeschamps at mangrove-systems.com  Tue May 25 02:26:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Tue May 25 02:26:00 2004
Subject: Experimental layout
In-Reply-To: <3174569B9743D511922F00A0C9431423050642B7@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050642B7@TYANWEB>
Message-ID: <1085471056.12788.110.camel@Calliphara>

ahh. I see the point :
it's because it's used on build machine. When i say build
machine, i mean linuxbios is getting built on this machine
so it can run for itself. 
and so on, ROM chip is flashed by the build machine for itself. 
If it wrecks, i pull it away and plug back a backup. 
that's just it. hey, it's a low-cost project isn't it :) ? 
I know this layout isn't suitable for networking, but for now
the only build machine(client) is at hand reach.And it's not my
intention to get Linuxbios to boot a cluster of machines (for now
maybe)
i seek to experiment on VIA EPIA build machine, by the time it is
working, i store lb configs, patchs to apply(if any), parameters to
issue on lbcc and logs rendered onto my other machine that's a server
vsftp. Later, i would like to deal roms with my database server like you
do provided the client has the flash_rom code to start it on, on the
same go. 

ok i've said everything :) hope it answers.

Cordialy
mathieu.

Le lun 24/05/2004 ? 18:56, YhLu a ?crit :
>  I wonder what is your develop configuration.
> 
> For me there is 
> Dev server: compile linuxbios + dhcp server + tftp server.
> Testbed: S2882
> Terminal Machine: ....
> 
> After booting up, I use ftp to get rom image in dev server and flash that
> into rom.
> 
> I'm curious that how you can use the flash tool in DEV server???
> 
> Regards
> 
> YH
> 
> 
> 
> -----????-----
> ???: ron minnich [mailto:rminnich at lanl.gov] 
> ????: 2004?5?24? 8:57
> ???: Mathieu Deschamps
> ??: Linuxbios at clustermatic.org
> ??: Re: Lbcc tool
> 
> I will try this tool and if it looks good perhaps we can put it into 
> freebios2/util/lbcc
> 
> ron
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 


From dwh at lanl.gov  Wed May 26 12:09:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May 26 12:09:01 2004
Subject: Iwill DK8S2
Message-ID: <Pine.LNX.4.44.0405261121350.12573-100000@ccs-mail.lanl.gov>

I'm committing some new stuff for the Iwill DK8S2 mainboard to replace the 
old stuff in src/mainboard/Iwill/DK8S2. I'm also adding a 
targets/Iwill/dk8s2 directory. Looks a lot like the HDAMA, but some 
tweaking is needed and VGA has not yet been tested, I'll look into it 
further today.

So far I've tested it and it boots into Linux.



From lists at braindonors.net  Wed May 26 15:13:00 2004
From: lists at braindonors.net (Jacob Alifrangis (LISTS))
Date: Wed May 26 15:13:00 2004
Subject: Add-in cards
Message-ID: <200405261912.i4QJCYK24748@nwn.definitive.org>

How does linuxbios handle add-in cards that may need special boot-roms like
the promise raid controllers, if I am going to startup from one?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040526/cc2186b9/attachment.html>

From dwh at lanl.gov  Wed May 26 15:21:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May 26 15:21:01 2004
Subject: Add-in cards
In-Reply-To: <200405261912.i4QJCYK24748@nwn.definitive.org>
Message-ID: <Pine.LNX.4.44.0405261438120.12573-100000@ccs-mail.lanl.gov>

This isn't my area of expertise, but you might want to look into YhLu's 
work on the Tyan mainboards concerning the Silicon Image serial ATA 
controller. 

This has been a problem for a long time with things like SCSI controllers 
as well.

On Wed, 26 May 2004, Jacob Alifrangis (LISTS) wrote:

> How does linuxbios handle add-in cards that may need special boot-roms like
> the promise raid controllers, if I am going to startup from one?
> 
> 



From rminnich at lanl.gov  Wed May 26 15:23:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May 26 15:23:01 2004
Subject: Add-in cards
In-Reply-To: <200405261912.i4QJCYK24748@nwn.definitive.org>
Message-ID: <Pine.LNX.4.44.0405261443470.12949-100000@maxroach.lanl.gov>

On Wed, 26 May 2004, Jacob Alifrangis (LISTS) wrote:

> How does linuxbios handle add-in cards that may need special boot-roms like
> the promise raid controllers, if I am going to startup from one?

we don't yet. We may in future handle it but have avoided it. 

Personally, I think this is a kernel issue but others may disagree.

ron



From rminnich at lanl.gov  Wed May 26 15:43:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Wed May 26 15:43:00 2004
Subject: Add-in cards
In-Reply-To: <Pine.LNX.4.44.0405261438120.12573-100000@ccs-mail.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405261502590.12949-100000@maxroach.lanl.gov>

On Wed, 26 May 2004, Hendricks David W. wrote:

> This has been a problem for a long time with things like SCSI controllers 
> as well.

yes, in private email I told Jacob that the eventual long term goal is 
that linux is in flash and we get all the power of linux to handle this 
problem. 

There's a general problem here for add-ins. We can't simply have ever
module in kernel to support every card. This problem will get harder.

ron



From dwh at lanl.gov  Wed May 26 15:53:00 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Wed May 26 15:53:00 2004
Subject: Add-in cards
In-Reply-To: <Pine.LNX.4.44.0405261502590.12949-100000@maxroach.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405261509240.12573-100000@ccs-mail.lanl.gov>

I heard you the first 1000+ times you said it :-)

Let Linux do it!

On Wed, 26 May 2004, ron minnich wrote:
> yes, in private email I told Jacob that the eventual long term goal is 
> that linux is in flash and we get all the power of linux to handle this 
> problem. 



From YhLu at tyan.com  Wed May 26 16:02:01 2004
From: YhLu at tyan.com (YhLu)
Date: Wed May 26 16:02:01 2004
Subject: =?GB2312?B?tPC4tDogQWRkLWluIGNhcmRz?=
Message-ID: <3174569B9743D511922F00A0C9431423050644AC@TYANWEB>

What do you want?
 
Boot from SATA disk?
 
If so, it is already solved.
 
Option rom does two things
1.       Init Controller to fix bugs in chip design or HW design.
2.       boot disk?.
 
I have make the FILO can boot from SATA disk. After I make boot from USB
disk, I will update the patch to FILO in Etherboot.
 
Regards
 
YH
 
  _____  

???: Jacob Alifrangis (LISTS) [mailto:lists at braindonors.net] 
????: 2004?5?26? 13:35
???: linuxbios at clustermatic.org
??: Add-in cards
 
How does linuxbios handle add-in cards that may need special boot-roms like
the promise raid controllers, if I am going to startup from one?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20040526/ffe67116/attachment.html>

From ebiederman at lnxi.com  Thu May 27 00:29:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 00:29:00 2004
Subject: Getting Started with freebios2!
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F1164E1@mail.local.ActualitySystems.com>
Message-ID: <m3vfiito2p.fsf@maxwell.lnxi.com>

"Jay Miller" <jmiller at actuality-systems.com> writes:

> Disclaimer:  I too am a N00B and these are my observations thus far.
> They may not be 100% correct, but these things have worked for me.  I
> hope that they'll help other N00Bz get started.

Nice....
 
> This is my latest N00B stumbling block, and unfortunately I haven't
> found an answer.  I know that it's a compressed elf format, but I can't
> figure out what I need to do to get elfboot (part of LinuxBIOS) to load
> payloads with the ZELF extension.  So for now I would recommend N00Bz
> stick with ELF format, until we get a definitive answer.

zelf == elf.  The file format is identical.

It separates images that are self extracting from those images
that are not compressed at all.

Eric


From ebiederman at lnxi.com  Thu May 27 09:02:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 09:02:00 2004
Subject: Getting Started with freebios2!
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F14AD06@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F14AD06@mail.local.ActualitySystems.com>
Message-ID: <m3hdu2hrrm.fsf@maxwell.lnxi.com>

Please CC the list on questions like this.  


"Jay Miller" <jmiller at actuality-systems.com> writes:

> Hi Eric,
> 
> Perhaps you can help me, seeing that you wrote elfboot.  This is the
> output that I get when I use a .zelf image:
> 
> Welcome to elfboot, the open sourced starter.
> January 2002, Eric Biederman.
> Version 1.3
> 
>     23:stream_init() - rom_stream: 0xfffe0000 - 0xfffeffff
> Found ELF candiate at offset 0
> Dropping non PT_LOAD segment
> New segment addr 0x20000 size 0x27200000 offset 0xb0 filesize 0xa7c29fc3
> (cleaned up) New segment addr 0x20000 size 0x27200000 offset 0xb0
> filesize 0x272
> 00000
> Cannot Load ELF Image
> 
> Do you see anything glaringly wrong here?

size = 626 MB .... and filesize = 2685MB

Something is badly wrong there.

Eric


From jmiller at actuality-systems.com  Thu May 27 09:39:00 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Thu May 27 09:39:00 2004
Subject: Getting Started with freebios2!
Message-ID: <E8F8DBCB0468204E856114A2CD20741F14AD0E@mail.local.ActualitySystems.com>

That's why I thought that elfboot couldn't read .zelf, because the image
sizes are incorrect.    Actual image size for the tg3--filo.zelf image
is 43,153 bytes, which is smaller than the file.elf image 43,472 bytes.
But when I make a linuxbios.rom with the tg3--filo.zelf as the payload,
elfboot generates the output I sent you.

-J

-----Original Message-----
From: Eric W. Biederman [mailto:eric at lnxi.com] On Behalf Of Eric W.
Biederman
Sent: Thursday, May 27, 2004 10:25 AM
To: Jay Miller
Cc: LinuxBIOS
Subject: Re: Getting Started with freebios2!


Please CC the list on questions like this.  


"Jay Miller" <jmiller at actuality-systems.com> writes:

> Hi Eric,
> 
> Perhaps you can help me, seeing that you wrote elfboot.  This is the
> output that I get when I use a .zelf image:
> 
> Welcome to elfboot, the open sourced starter.
> January 2002, Eric Biederman.
> Version 1.3
> 
>     23:stream_init() - rom_stream: 0xfffe0000 - 0xfffeffff
> Found ELF candiate at offset 0
> Dropping non PT_LOAD segment
> New segment addr 0x20000 size 0x27200000 offset 0xb0 filesize
0xa7c29fc3
> (cleaned up) New segment addr 0x20000 size 0x27200000 offset 0xb0
> filesize 0x272
> 00000
> Cannot Load ELF Image
> 
> Do you see anything glaringly wrong here?

size = 626 MB .... and filesize = 2685MB

Something is badly wrong there.

Eric




From ollie at lanl.gov  Thu May 27 11:16:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 11:16:01 2004
Subject: Testbios works for ATI too !!!
Message-ID: <1085675839.5653.36.camel@exponential.lanl.gov>

Hello,

I just tried my "imporved" testbios on ATI 9800PRO
under LinuxBIOS. It can init the card. The only problem
is that the normal BIOS store the PCIDEVFN at some bytes
in the C segment so I have to change the vbios.bin a
little bit.

I will commit the current testbios into V2 tree after
doing some clean up.

Ollie





From rsmith at bitworks.com  Thu May 27 11:38:01 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Thu May 27 11:38:01 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <1085675839.5653.36.camel@exponential.lanl.gov>
References: <1085675839.5653.36.camel@exponential.lanl.gov>
Message-ID: <40B61E51.2080208@bitworks.com>

Li-Ta Lo wrote:

> Hello,
> 
> I just tried my "imporved" testbios on ATI 9800PRO
> under LinuxBIOS. It can init the card. The only problem
> is that the normal BIOS store the PCIDEVFN at some bytes
> in the C segment so I have to change the vbios.bin a
> little bit.
> 
> I will commit the current testbios into V2 tree after
> doing some clean up.

Can you send me a tarball of your code?  I want to test it on my M1 card.




From ebiederman at lnxi.com  Thu May 27 13:25:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 13:25:01 2004
Subject: Getting Started with freebios2!
In-Reply-To: <E8F8DBCB0468204E856114A2CD20741F14AD0E@mail.local.ActualitySystems.com>
References: <E8F8DBCB0468204E856114A2CD20741F14AD0E@mail.local.ActualitySystems.com>
Message-ID: <m3pt8pyaeh.fsf@maxwell.lnxi.com>

"Jay Miller" <jmiller at actuality-systems.com> writes:

> That's why I thought that elfboot couldn't read .zelf, because the image
> sizes are incorrect.    Actual image size for the tg3--filo.zelf image
> is 43,153 bytes, which is smaller than the file.elf image 43,472 bytes.
> But when I make a linuxbios.rom with the tg3--filo.zelf as the payload,
> elfboot generates the output I sent you.

Run ``readelf -h -l'' on the problem image to see what the values
are before it is combined into LinuxBIOS.  I suspect you have a
build problem, possible a messed up version of perl installed.

Eric


From YhLu at tyan.com  Thu May 27 13:36:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 27 13:36:00 2004
Subject: =?GB2312?B?tPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGggZnJlZWJpb3MyIQ==?=
Message-ID: <3174569B9743D511922F00A0C94314230506453A@TYANWEB>

Did you use 
export LANG=en_US
before make bin/tg3--filo.zelf?

Or I could send one tg3_filo.zelf to you?

Regards

YH

-----????-----
???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
????: 2004?5?27? 11:48
???: Jay Miller
??: Eric W. Biederman; LinuxBIOS
??: Re: Getting Started with freebios2!

"Jay Miller" <jmiller at actuality-systems.com> writes:

> That's why I thought that elfboot couldn't read .zelf, because the image
> sizes are incorrect.    Actual image size for the tg3--filo.zelf image
> is 43,153 bytes, which is smaller than the file.elf image 43,472 bytes.
> But when I make a linuxbios.rom with the tg3--filo.zelf as the payload,
> elfboot generates the output I sent you.

Run ``readelf -h -l'' on the problem image to see what the values
are before it is combined into LinuxBIOS.  I suspect you have a
build problem, possible a messed up version of perl installed.

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


From jmiller at actuality-systems.com  Thu May 27 13:38:01 2004
From: jmiller at actuality-systems.com (Jay Miller)
Date: Thu May 27 13:38:01 2004
Subject: Getting Started with freebios2!
Message-ID: <E8F8DBCB0468204E856114A2CD20741F14AD3C@mail.local.ActualitySystems.com>

I think that I've been lucky using a stock RH9 distro.  I'm going to make sure I've got the latest binutils, etc... and retry.

By the way, what is the status on USB support?  I know you were getting close.

Thanks,
J

-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, May 27, 2004 3:10 PM
To: ebiederman at lnxi.com; Jay Miller
Cc: LinuxBIOS
Subject: ??: Getting Started with freebios2!

Did you use 
export LANG=en_US
before make bin/tg3--filo.zelf?

Or I could send one tg3_filo.zelf to you?

Regards

YH

-----????-----
???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
????: 2004?5?27? 11:48
???: Jay Miller
??: Eric W. Biederman; LinuxBIOS
??: Re: Getting Started with freebios2!

"Jay Miller" <jmiller at actuality-systems.com> writes:

> That's why I thought that elfboot couldn't read .zelf, because the image
> sizes are incorrect.    Actual image size for the tg3--filo.zelf image
> is 43,153 bytes, which is smaller than the file.elf image 43,472 bytes.
> But when I make a linuxbios.rom with the tg3--filo.zelf as the payload,
> elfboot generates the output I sent you.

Run ``readelf -h -l'' on the problem image to see what the values
are before it is combined into LinuxBIOS.  I suspect you have a
build problem, possible a messed up version of perl installed.

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




From YhLu at tyan.com  Thu May 27 13:46:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 27 13:46:01 2004
Subject: =?GB2312?B?tPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGggZnJlZWJpb3MyIQ==?=
Message-ID: <3174569B9743D511922F00A0C94314230506453C@TYANWEB>

USB support status:

For OHCI (AMD8111) support, it can do ED-TD process well.

Only one problem left:

When it using bulk transfer (ed 1 and 2) to talk to the USB disk, it gets
the USB ERR 5, that means device does not response. But control ed (0) works
well, can get the USB disk serial number.

Regards

YH

sector= 0       SUB URB:[00003c08]
dev:2,ep:2-O,type:BULK,flags:00000000,len:0/31,stat:0(00000000)
ohci.c: data(0/31): 00000055 00000053 00000042 00000043 00000009 00000003
00000000 00000000 00000000 00000002 00000000 00000000 00000080 00000000
0000000a 00000028... stat:0
td_fill 4 ed->dma=efe835e0, ed->hwHeadP=efe82ee0, ed->hwTailP=efe82f10 
ohci->hcca->done_head = efe82ee0 ohci->hcca=fffff3d0 ohci=00071604
ohci->regs->donehead=00000000
td_list_hc = efe82ee0
 USB-error/status: 00000005 : ffffe7b0

-----????-----
???: Jay Miller [mailto:jmiller at actuality-systems.com] 
????: 2004?5?27? 11:57
???: YhLu; ebiederman at lnxi.com
??: LinuxBIOS
??: RE: Getting Started with freebios2!

I think that I've been lucky using a stock RH9 distro.  I'm going to make
sure I've got the latest binutils, etc... and retry.

By the way, what is the status on USB support?  I know you were getting
close.

Thanks,
J

-----Original Message-----
From: YhLu [mailto:YhLu at tyan.com] 
Sent: Thursday, May 27, 2004 3:10 PM
To: ebiederman at lnxi.com; Jay Miller
Cc: LinuxBIOS
Subject: ??: Getting Started with freebios2!

Did you use 
export LANG=en_US
before make bin/tg3--filo.zelf?

Or I could send one tg3_filo.zelf to you?

Regards

YH

-----????-----
???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
????: 2004?5?27? 11:48
???: Jay Miller
??: Eric W. Biederman; LinuxBIOS
??: Re: Getting Started with freebios2!

"Jay Miller" <jmiller at actuality-systems.com> writes:

> That's why I thought that elfboot couldn't read .zelf, because the image
> sizes are incorrect.    Actual image size for the tg3--filo.zelf image
> is 43,153 bytes, which is smaller than the file.elf image 43,472 bytes.
> But when I make a linuxbios.rom with the tg3--filo.zelf as the payload,
> elfboot generates the output I sent you.

Run ``readelf -h -l'' on the problem image to see what the values
are before it is combined into LinuxBIOS.  I suspect you have a
build problem, possible a messed up version of perl installed.

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




From rsmith at bitworks.com  Thu May 27 14:18:00 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Thu May 27 14:18:00 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <40B61E51.2080208@bitworks.com>
References: <1085675839.5653.36.camel@exponential.lanl.gov> <40B61E51.2080208@bitworks.com>
Message-ID: <40B643D1.1020803@bitworks.com>

Richard Smith wrote:

I don't suppose there is a way to use testbios with a system having 2 
video cards is there?

I got a pci developemnt card from ATI that has an M1 on it stuck in a 
sytems that also has a agp card.  I tell the bios to init the AGP card 
first so the PCI card only gets POR.  I've been using this to test my 
init code on known good hardware rather than my target system.

Running my ATI bios under testbios appears to do something but since I 
think the bios is enabling the legacy IO ranges it makes my AGP card go 
crazy and locks up the machine.

I'm about to try it on my target.





From ollie at lanl.gov  Thu May 27 14:21:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 14:21:01 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <40B643D1.1020803@bitworks.com>
References: <1085675839.5653.36.camel@exponential.lanl.gov>
	 <40B61E51.2080208@bitworks.com>  <40B643D1.1020803@bitworks.com>
Message-ID: <1085686956.5653.46.camel@exponential.lanl.gov>

On Thu, 2004-05-27 at 13:38, Richard Smith wrote:
> Richard Smith wrote:
> 
> I don't suppose there is a way to use testbios with a system having 2 
> video cards is there?
> 

Your are asking too much ;-). It is not that smart yet.

> I got a pci developemnt card from ATI that has an M1 on it stuck in a 
> sytems that also has a agp card.  I tell the bios to init the AGP card 
> first so the PCI card only gets POR.  I've been using this to test my 
> init code on known good hardware rather than my target system.
> 
> Running my ATI bios under testbios appears to do something but since I 
> think the bios is enabling the legacy IO ranges it makes my AGP card go 
> crazy and locks up the machine.
> 

Can you just install one VGA card and use telnet/rlogin ?

Ollie

> I'm about to try it on my target.
> 
> 
> 



From ollie at lanl.gov  Thu May 27 14:31:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 14:31:01 2004
Subject: Resource Allocation for Option Rom
Message-ID: <1085687516.5653.51.camel@exponential.lanl.gov>

Hello,

It seems that the resource allocation for option rom
is not implemented in LinuxBIOS, is it ? Is there one
have any idea how to add this ?

Ollie




From ebiederman at lnxi.com  Thu May 27 14:54:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 14:54:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085687516.5653.51.camel@exponential.lanl.gov>
References: <1085687516.5653.51.camel@exponential.lanl.gov>
Message-ID: <m3d64ptylq.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> Hello,
> 
> It seems that the resource allocation for option rom
> is not implemented in LinuxBIOS, is it ? Is there one
> have any idea how to add this ?

We could probably reserve a hole for this purpose, which
is a good idea except for bridges. 

Be very careful here.  The PCI spec allows the option rom BAR
to be mutually exclusive with the other BARS so in general
they both can not be enabled.

Eric


From dwh at lanl.gov  Thu May 27 15:01:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Thu May 27 15:01:01 2004
Subject: Iwill DK8S2
In-Reply-To: <Pine.LNX.4.44.0405261121350.12573-100000@ccs-mail.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405271419160.12573-100000@ccs-mail.lanl.gov>

Follow up: VGA works, the system boots, keyboard + mouse work. There are a 
couple resource allocation errors that show up during LInuxBIOS boot, but 
Linux seems unaffected. 

On Wed, 26 May 2004, Hendricks David W. wrote:

> I'm committing some new stuff for the Iwill DK8S2 mainboard to replace the 
> old stuff in src/mainboard/Iwill/DK8S2. I'm also adding a 
> targets/Iwill/dk8s2 directory. Looks a lot like the HDAMA, but some 
> tweaking is needed and VGA has not yet been tested, I'll look into it 
> further today.
> 
> So far I've tested it and it boots into Linux.
> 
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From stepan at openbios.org  Thu May 27 15:09:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May 27 15:09:00 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <m3d64ptylq.fsf@maxwell.lnxi.com>
References: <1085687516.5653.51.camel@exponential.lanl.gov> <m3d64ptylq.fsf@maxwell.lnxi.com>
Message-ID: <20040527203030.GA8565@openbios.org>

* Eric W. Biederman <ebiederman at lnxi.com> [040527 22:16]:
> We could probably reserve a hole for this purpose, which
> is a good idea except for bridges. 
 
Also, the graphics card option roms are usually hardcoded to 0xc0000

> Be very careful here.  The PCI spec allows the option rom BAR
> to be mutually exclusive with the other BARS so in general
> they both can not be enabled.

The only safe way to go is probably to probe one after the other while
leaving the rest untouched, i.e

 1) probe option rom, if it doesn't exist go to 6.
 2) enable option rom
 3) evtl. copy rom code to ram (in case it installs an 
    int13 handler or such)
 4) execute option rom code.
 5) disable option rom
 6) repeat this for all pci devices.

This procedure should be a part of "testbios" rather than LinuxBIOS' PCI
code, but reserving some space for it early might be the way to go
indeed.


   Stefan


From ollie at lanl.gov  Thu May 27 15:23:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 15:23:00 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <m3d64ptylq.fsf@maxwell.lnxi.com>
References: <1085687516.5653.51.camel@exponential.lanl.gov>
	 <m3d64ptylq.fsf@maxwell.lnxi.com>
Message-ID: <1085690660.5653.72.camel@exponential.lanl.gov>

On Thu, 2004-05-27 at 14:16, Eric W. Biederman wrote:
> We could probably reserve a hole for this purpose, which
> is a good idea except for bridges. 
> 

Can we just treat it as MEM resource and reuse the MEM resource
allocation code ?

> Be very careful here.  The PCI spec allows the option rom BAR
> to be mutually exclusive with the other BARS so in general
> they both can not be enabled.
> 

Where is this stated in the spec ?

Ollie




From ollie at lanl.gov  Thu May 27 15:28:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 15:28:00 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <20040527203030.GA8565@openbios.org>
References: <1085687516.5653.51.camel@exponential.lanl.gov>
	 <m3d64ptylq.fsf@maxwell.lnxi.com>  <20040527203030.GA8565@openbios.org>
Message-ID: <1085690965.5653.77.camel@exponential.lanl.gov>

On Thu, 2004-05-27 at 14:30, Stefan Reinauer wrote:
> * Eric W. Biederman <ebiederman at lnxi.com> [040527 22:16]:
> > We could probably reserve a hole for this purpose, which
> > is a good idea except for bridges. 
>  
> Also, the graphics card option roms are usually hardcoded to 0xc0000
> 

Do you mean the expansion rom BAR is hard coded to 0xc0000 ?
The how does the bios copy the bios in ROM at 0xc0000 to memory
in DRAM at 0xc0000 as stated in PCI spec 6.3.3.1.1 ?

> > Be very careful here.  The PCI spec allows the option rom BAR
> > to be mutually exclusive with the other BARS so in general
> > they both can not be enabled.
> 
> The only safe way to go is probably to probe one after the other while
> leaving the rest untouched, i.e
> 
>  1) probe option rom, if it doesn't exist go to 6.
>  2) enable option rom
>  3) evtl. copy rom code to ram (in case it installs an 
>     int13 handler or such)
>  4) execute option rom code.
>  5) disable option rom
>  6) repeat this for all pci devices.
> 

If I am right you should disable option rom BEFORE execute the
code in DRAM. The spec says it is possible that the other BAR
shares the same address decoder with ROM BAR.

Ollie

> This procedure should be a part of "testbios" rather than LinuxBIOS' PCI
> code, but reserving some space for it early might be the way to go
> indeed.
> 
> 
>    Stefan
> 



From stepan at openbios.org  Thu May 27 15:47:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May 27 15:47:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085690965.5653.77.camel@exponential.lanl.gov>
References: <1085687516.5653.51.camel@exponential.lanl.gov> <m3d64ptylq.fsf@maxwell.lnxi.com> <20040527203030.GA8565@openbios.org> <1085690965.5653.77.camel@exponential.lanl.gov>
Message-ID: <20040527210837.GA8689@openbios.org>

* Li-Ta Lo <ollie at lanl.gov> [040527 22:49]:
> > Also, the graphics card option roms are usually hardcoded to 0xc0000
> 
> Do you mean the expansion rom BAR is hard coded to 0xc0000 ?
> The how does the bios copy the bios in ROM at 0xc0000 to memory
> in DRAM at 0xc0000 as stated in PCI spec 6.3.3.1.1 ?
 
I know some intel chipsets did this by forwarding reads from 0xc0000 to rom
and writes to 0xc0000 to ram, then reading and rewriting the whole area
to the same address. I'd assume that this is still handled similar but
on AMD64 rather using the MEM maps?

> >  1) probe option rom, if it doesn't exist go to 6.
> >  2) enable option rom
> >  3) evtl. copy rom code to ram (in case it installs an 
> >     int13 handler or such)
> >  4) execute option rom code.
> >  5) disable option rom
> >  6) repeat this for all pci devices.
> > 
> 
> If I am right you should disable option rom BEFORE execute the
> code in DRAM. The spec says it is possible that the other BAR
> shares the same address decoder with ROM BAR.

D'uh, of course! First 5 then 4, i mixed it up. Otherwise you risk
running into exactly the mutual exclusive BAR problem that Eric
described.


   Stefan


From rminnich at lanl.gov  Thu May 27 15:53:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:53:00 2004
Subject: =?GB2312?B?tPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGggZnJlZWJpb3MyIQ==?=
In-Reply-To: <3174569B9743D511922F00A0C94314230506453C@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405271513580.23982-100000@maxroach.lanl.gov>

now we need usb output. The HP node we got has no serial port!

ouch!

ron



From rminnich at lanl.gov  Thu May 27 15:54:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:54:00 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <40B643D1.1020803@bitworks.com>
Message-ID: <Pine.LNX.4.44.0405271515070.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Richard Smith wrote:

> I don't suppose there is a way to use testbios with a system having 2 
> video cards is there?

the spec says that you can call a card bios with a devfn and it should all 
work. Not all cards work however as their bios is brain-dead.

ron



From rminnich at lanl.gov  Thu May 27 15:56:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:56:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085687516.5653.51.camel@exponential.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405271516071.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Li-Ta Lo wrote:

> It seems that the resource allocation for option rom
> is not implemented in LinuxBIOS, is it ? Is there one
> have any idea how to add this ?

When I borrowed that code originally from linux I believe it always 
disabled option roms. You should be able to extend the code to 
1- allocate a chunk of physical address space (using the pci allocate
   code)
2- set the special option rom BAR to that space

I don't think it should be too hard.

ron



From rminnich at lanl.gov  Thu May 27 15:56:25 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:56:25 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <m3d64ptylq.fsf@maxwell.lnxi.com>
Message-ID: <Pine.LNX.4.44.0405271517260.23982-100000@maxroach.lanl.gov>

On 27 May 2004, Eric W. Biederman wrote:

> Be very careful here.  The PCI spec allows the option rom BAR
> to be mutually exclusive with the other BARS so in general
> they both can not be enabled.

should not matter if you are running an emulator. 

ron



From YhLu at tyan.com  Thu May 27 15:57:00 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 27 15:57:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGggZnJlZWJp?=
	=?GB2312?B?b3MyIQ==?=
Message-ID: <3174569B9743D511922F00A0C943142305064552@TYANWEB>

Usb to serial ???

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?27? 14:14
???: YhLu
??: Jay Miller; ebiederman at lnxi.com; LinuxBIOS
??: Re: ??: Getting Started with freebios2!

now we need usb output. The HP node we got has no serial port!

ouch!

ron


From rminnich at lanl.gov  Thu May 27 15:58:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:58:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <20040527203030.GA8565@openbios.org>
Message-ID: <Pine.LNX.4.44.0405271518280.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Stefan Reinauer wrote:

> This procedure should be a part of "testbios" rather than LinuxBIOS' PCI
> code, but reserving some space for it early might be the way to go
> indeed.

just remember you're in an emulator. If you can get option rom contents 
copied out then the emulator will put it somewhere internally and pretend 
it's at the option rom address.

ron



From rminnich at lanl.gov  Thu May 27 15:59:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 15:59:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085690965.5653.77.camel@exponential.lanl.gov>
Message-ID: <Pine.LNX.4.44.0405271519370.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Li-Ta Lo wrote:

> Do you mean the expansion rom BAR is hard coded to 0xc0000 ?

it's not. It can be anywhere. For dumping vgabios I would actually set it 
by setpci to an unused place, mmap /dev/mem, and dump it out. It can go 
anywhere.

ron



From stepan at openbios.org  Thu May 27 16:00:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May 27 16:00:00 2004
Subject: ????: Getting Started with freebios2!
In-Reply-To: <Pine.LNX.4.44.0405271513580.23982-100000@maxroach.lanl.gov>
References: <3174569B9743D511922F00A0C94314230506453C@TYANWEB> <Pine.LNX.4.44.0405271513580.23982-100000@maxroach.lanl.gov>
Message-ID: <20040527212107.GA9223@openbios.org>

* ron minnich <rminnich at lanl.gov> [040527 23:14]:
> now we need usb output. The HP node we got has no serial port!

No JTAG either? I'd assume serial-via-usb console needs a lot more
hardware initialized than a simple serial port before one can see
anything..





From rsmith at bitworks.com  Thu May 27 16:00:21 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Thu May 27 16:00:21 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <Pine.LNX.4.44.0405271515070.23982-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405271515070.23982-100000@maxroach.lanl.gov>
Message-ID: <40B65BD9.8060200@bitworks.com>

ron minnich wrote:

> On Thu, 27 May 2004, Richard Smith wrote:
> 
> 
>>I don't suppose there is a way to use testbios with a system having 2 
>>video cards is there?
> 
> the spec says that you can call a card bios with a devfn and it should all 
> work. Not all cards work however as their bios is brain-dead.

The bios also has to know if it should enable decode of the legacy vga 
IO registers.  How would you tell it that?






From rminnich at lanl.gov  Thu May 27 16:00:27 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 16:00:27 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <20040527210837.GA8689@openbios.org>
Message-ID: <Pine.LNX.4.44.0405271520460.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Stefan Reinauer wrote:

> * Li-Ta Lo <ollie at lanl.gov> [040527 22:49]:
> > > Also, the graphics card option roms are usually hardcoded to 0xc0000
> > 
> > Do you mean the expansion rom BAR is hard coded to 0xc0000 ?
> > The how does the bios copy the bios in ROM at 0xc0000 to memory
> > in DRAM at 0xc0000 as stated in PCI spec 6.3.3.1.1 ?
>  
> I know some intel chipsets did this by forwarding reads from 0xc0000 to rom
> and writes to 0xc0000 to ram, then reading and rewriting the whole area
> to the same address. I'd assume that this is still handled similar but
> on AMD64 rather using the MEM maps?

again, you do not need to map option roms at 0c0000 in the emulator!

Map it anywhere, tell the emulator the location, and the emulator can 
satisfy memory "fetches" for c0000 by fetching from that location. 

Emulators are good.

ron



From rminnich at lanl.gov  Thu May 27 16:01:00 2004
From: rminnich at lanl.gov (ron minnich)
Date: Thu May 27 16:01:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGggZnJlZWJp?=
 =?GB2312?B?b3MyIQ==?=
In-Reply-To: <3174569B9743D511922F00A0C943142305064552@TYANWEB>
Message-ID: <Pine.LNX.4.44.0405271522230.23982-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, YhLu wrote:

> Usb to serial ???

yes, it's now needed :-(

ron



From stepan at openbios.org  Thu May 27 16:04:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Thu May 27 16:04:00 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <Pine.LNX.4.44.0405271520460.23982-100000@maxroach.lanl.gov>
References: <20040527210837.GA8689@openbios.org> <Pine.LNX.4.44.0405271520460.23982-100000@maxroach.lanl.gov>
Message-ID: <20040527212505.GA9346@openbios.org>

* ron minnich <rminnich at lanl.gov> [040527 23:21]:
> again, you do not need to map option roms at 0c0000 in the emulator!
> 
> Map it anywhere, tell the emulator the location, and the emulator can 
> satisfy memory "fetches" for c0000 by fetching from that location. 

indeed true. But for x86 hardware, putting all of the x86 emulator in
rom is less elegant than vm86 stuff, even though I have no clue about
the later.

Stefan



From YhLu at tyan.com  Thu May 27 16:08:01 2004
From: YhLu at tyan.com (YhLu)
Date: Thu May 27 16:08:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGgg?=
	=?GB2312?B?ZnJlZWJpb3MyIQ==?=
Message-ID: <3174569B9743D511922F00A0C943142305064554@TYANWEB>

So the LinuxBIOS need to 
1. init USB controller
2. create usb_dev to be serial.
3. use usb_control_msg and usb_bulk_msg to talk with the serial device.

What the USB type, OHCI or UCHI or EHCI??

I wonder if some source code or documents that define No 3 above?

Regards

YH

-----????-----
???: ron minnich [mailto:rminnich at lanl.gov] 
????: 2004?5?27? 14:23
???: YhLu
??: Jay Miller; ebiederman at lnxi.com; LinuxBIOS
??: Re: ??: ??: Getting Started with freebios2!

On Thu, 27 May 2004, YhLu wrote:

> Usb to serial ???

yes, it's now needed :-(

ron


From ollie at lanl.gov  Thu May 27 16:11:01 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 16:11:01 2004
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Getting Started with
	freebios2!
In-Reply-To: <Pine.LNX.4.44.0405271513580.23982-100000@maxroach.lanl.gov>
References: <Pine.LNX.4.44.0405271513580.23982-100000@maxroach.lanl.gov>
Message-ID: <1085693556.5653.79.camel@exponential.lanl.gov>

On Thu, 2004-05-27 at 15:14, ron minnich wrote:
> now we need usb output. The HP node we got has no serial port!
> 
> ouch!
> 

I thought we don;t care about those HP nodes due to it
"management" processor".

Ollie

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



From ollie at lanl.gov  Thu May 27 16:14:00 2004
From: ollie at lanl.gov (Li-Ta Lo)
Date: Thu May 27 16:14:00 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <40B65BD9.8060200@bitworks.com>
References: <Pine.LNX.4.44.0405271515070.23982-100000@maxroach.lanl.gov>
	 <40B65BD9.8060200@bitworks.com>
Message-ID: <1085693713.5653.81.camel@exponential.lanl.gov>

On Thu, 2004-05-27 at 15:21, Richard Smith wrote:
> ron minnich wrote:
> 
> > On Thu, 27 May 2004, Richard Smith wrote:
> > 
> > 
> >>I don't suppose there is a way to use testbios with a system having 2 
> >>video cards is there?
> > 
> > the spec says that you can call a card bios with a devfn and it should all 
> > work. Not all cards work however as their bios is brain-dead.
> 
> The bios also has to know if it should enable decode of the legacy vga 
> IO registers.  How would you tell it that?

There is a terrible way to do that. There is some INT 10 call which
can disable the legacy vga decode for the "current" vga device.

Ollie




From pyro at linuxlabs.com  Thu May 27 17:34:00 2004
From: pyro at linuxlabs.com (Steven James)
Date: Thu May 27 17:34:00 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVkIHdpdGgg?=
 =?GB2312?B?ZnJlZWJpb3MyIQ==?=
In-Reply-To: <3174569B9743D511922F00A0C943142305064554@TYANWEB>
References: <3174569B9743D511922F00A0C943142305064554@TYANWEB>
Message-ID: <Pine.LNX.4.58.0405272232110.26413@ucontrol.mobiledns.com>

Greetings,

I'm finally getting dug out after being snowed under :-)

The spec is probably part of:
http://www.usb.org/developers/devclass_docs/usbcdc11.pdf

The communications class. I'm guessing it would be a subset of POTS modem
with a transparent data protocol. That would imply line contol on the
control ep, and either bulk transfer or isochronous pipe pairs for the
serial data.

It's a lot more involved than a simple UART, that's for sure.

On a side note, I THOUGHT I would have time by now to bang on the USB
boot. Hopefully, I'll be able to do more with it now (so I say :-)

As soon as I get up to speed on freebios2, I'll have a good test platform.

For the serial, UHCI and OHCI will be good. EHCI can likely be ignored for
the BIOS since fast devices are required to fall back and EHCI always has
one of UHCI or OHCI to handle low speed USB.

G'day,
sjames


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


On Thu, 27 May 2004, YhLu wrote:

> So the LinuxBIOS need to
> 1. init USB controller
> 2. create usb_dev to be serial.
> 3. use usb_control_msg and usb_bulk_msg to talk with the serial device.
>
> What the USB type, OHCI or UCHI or EHCI??
>
> I wonder if some source code or documents that define No 3 above?
>
> Regards
>
> YH
>
> -----????-----
> ???: ron minnich [mailto:rminnich at lanl.gov]
> ????: 2004?5?27? 14:23
> ???: YhLu
> ??: Jay Miller; ebiederman at lnxi.com; LinuxBIOS
> ??: Re: ??: ??: Getting Started with freebios2!
>
> On Thu, 27 May 2004, YhLu wrote:
>
> > Usb to serial ???
>
> yes, it's now needed :-(
>
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From ebiederman at lnxi.com  Thu May 27 20:41:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 20:41:01 2004
Subject: =?gb2312?b?tPC4tA==?=: =?gb2312?b?tPC4tA==?=:
  =?gb2312?b?tPC4tA==?=: Getting Started with freebios2!
In-Reply-To: <Pine.LNX.4.58.0405272232110.26413@ucontrol.mobiledns.com>
References: <3174569B9743D511922F00A0C943142305064554@TYANWEB>
	<Pine.LNX.4.58.0405272232110.26413@ucontrol.mobiledns.com>
Message-ID: <m3y8ndqpej.fsf@maxwell.lnxi.com>

Steven James <pyro at linuxlabs.com> writes:

> For the serial, UHCI and OHCI will be good. EHCI can likely be ignored for
> the BIOS since fast devices are required to fall back and EHCI always has
> one of UHCI or OHCI to handle low speed USB.

Actually not.  At least not for serial before the memory is initialized.

For early serial only EHCI is an option.  The EHCI debug port can be used
with just I/O to the EHCI, no DMA is require.  OHCI, UHCI, and normal
EHCI require DMA transfers so they are not an option.

Eric


From ebiederman at lnxi.com  Thu May 27 23:50:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 23:50:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085690660.5653.72.camel@exponential.lanl.gov>
References: <1085687516.5653.51.camel@exponential.lanl.gov>
	<m3d64ptylq.fsf@maxwell.lnxi.com>
	<1085690660.5653.72.camel@exponential.lanl.gov>
Message-ID: <m3fz9lnnie.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> On Thu, 2004-05-27 at 14:16, Eric W. Biederman wrote:
> > We could probably reserve a hole for this purpose, which
> > is a good idea except for bridges. 
> > 
> 
> Can we just treat it as MEM resource and reuse the MEM resource
> allocation code ?

Yes that would be the easy way to reserver an area for the rom
to be enabled.  If the BAR is not large this should not be a problem.
 
> > Be very careful here.  The PCI spec allows the option rom BAR
> > to be mutually exclusive with the other BARS so in general
> > they both can not be enabled.
> > 
> 
> Where is this stated in the spec ?

I saw it once long ago.  And the kernel avoids it.
But enabling just that BAR copying the data out,
and then reenabling the rest should not be a problem.

Eric


From ebiederman at lnxi.com  Thu May 27 23:50:54 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Thu May 27 23:50:54 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <1085690660.5653.72.camel@exponential.lanl.gov>
References: <1085687516.5653.51.camel@exponential.lanl.gov>
	<m3d64ptylq.fsf@maxwell.lnxi.com>
	<1085690660.5653.72.camel@exponential.lanl.gov>
Message-ID: <m3fz9lnnie.fsf@maxwell.lnxi.com>

Li-Ta Lo <ollie at lanl.gov> writes:

> On Thu, 2004-05-27 at 14:16, Eric W. Biederman wrote:
> > We could probably reserve a hole for this purpose, which
> > is a good idea except for bridges. 
> > 
> 
> Can we just treat it as MEM resource and reuse the MEM resource
> allocation code ?

Yes that would be the easy way to reserver an area for the rom
to be enabled.  If the BAR is not large this should not be a problem.
 
> > Be very careful here.  The PCI spec allows the option rom BAR
> > to be mutually exclusive with the other BARS so in general
> > they both can not be enabled.
> > 
> 
> Where is this stated in the spec ?

I saw it once long ago.  And the kernel avoids it.
But enabling just that BAR copying the data out,
and then reenabling the rest should not be a problem.

Eric


From mdeschamps at mangrove-systems.com  Fri May 28 08:58:00 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Fri May 28 08:58:00 2004
Subject: Native LinuxBios Support
Message-ID: <1085753160.17249.22.camel@Calliphara>

Hello,

I've rere-reread  LinuxBios port to AMD64 guide during some
documentation making.

I am wondering about Linuxbios Native Support and VGA init... 

Linuxbios is supposed to support "Trident Cyberblade 3d" natively
and I have a Cyberblade/i1 rev 6a in my chipset...

Please don't tell me that I've spend time making it work, though
it isn't really, while there is a native support ?!?

this must be a joke ! 

If not and that is tue and after i eat my jeans on the go,
is that meaning that i've just  to set CONFIG_VGABIOS and that 
would be all ?


mathieu



From ebiederman at lnxi.com  Fri May 28 09:04:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 09:04:01 2004
Subject: [COMMIT] romcc 0.63 and some fixes...
Message-ID: <m3pt8ok4qf.fsf@maxwell.lnxi.com>

I finally have romcc to the point where I can seriously look
at size optimizations.  I am finally there after a lot of bug fixing
and experimentation. 

Because of added correctness in handling of small types I have
measured about a 1K growth on the hdama port or about 3%.  But things
should start shrinking soon.

More optimization opportunities have been exposed so which breaks
some code that was not right but lucky.

Have fun with this.

Eric


- Upgrade to romcc version 0.63
  This includes more test cases
  Lots of small bug fixes
  A complete C preprocessor is now built in
  Initial support for not inlining everything
  __attribute__((noinline)) works
  Better command line options and help
  Constants arrays can be read at compile time
  Asm statements that are not volatile will now be removed when their outputs go unused
  Loads and stores that are not volatile will be removed when their values go unused
  The number of FIXMES in the code is finally starting to go down.

Tags romcc_0_38 and romcc_0_63 are present.  In case you need to regress the
version of romcc.


- Added volatile to asm statements in auto.c and failover.c
- Updated the romcc version in Config.lb
- Fixed type sizes in romcc_io.h and io.h inl() returning a byte was nasty

 Modified Files:
    src/arch/i386/include/arch/romcc_io.h
    src/arch/i386/include/arch/io.h
    src/mainboard/arima/hdama/auto.c
    src/mainboard/arima/hdama/failover.c src/config/Config.lb




From stepan at openbios.org  Fri May 28 09:34:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Fri May 28 09:34:01 2004
Subject: Native LinuxBios Support
In-Reply-To: <1085753160.17249.22.camel@Calliphara>
References: <1085753160.17249.22.camel@Calliphara>
Message-ID: <20040528145535.GA1715@openbios.org>

* Mathieu Deschamps <mdeschamps at mangrove-systems.com> [040528 16:06]:
> I've rere-reread  LinuxBios port to AMD64 guide during some
> documentation making.
 
If you or anyone else have additions to this document, let me know. It
waits desperately for more detailed explanations and restructuring in
many places.

> Linuxbios is supposed to support "Trident Cyberblade 3d" natively
> and I have a Cyberblade/i1 rev 6a in my chipset...
 
> Please don't tell me that I've spend time making it work, though
> it isn't really, while there is a native support ?!?
 
I have no idea whether the Cyberblade i1 and 3d are the same. If your
device has the following PCI id it is the same:
        .vendor = 0x1023,
        .device = 0x9880,

The Cyberblade code is not working though. If it would work, you would
not even need to set CONFIG_VGABIOS to get something on the screen.
It might be as simple as adding a delay to the outp() function but I
have no idea. It is enabled in the newisys/khepri build. I added some 
debug output to the driver.

If you have some time, feel free to fix the cyberblade code. This would
be valuable for quite some AMD64 systems, including the Newisys 2100 and
Sun Fire V20z display.

Stefan




From mdeschamps at mangrove-systems.com  Fri May 28 10:45:01 2004
From: mdeschamps at mangrove-systems.com (Mathieu Deschamps)
Date: Fri May 28 10:45:01 2004
Subject: Native LinuxBios Support
In-Reply-To: <20040528145535.GA1715@openbios.org>
References: <1085753160.17249.22.camel@Calliphara>
	 <20040528145535.GA1715@openbios.org>
Message-ID: <1085759565.17249.55.camel@Calliphara>

Thanks Stefan for your answer,


Le ven 28/05/2004 ? 16:55, Stefan Reinauer a ?crit :
> * Mathieu Deschamps <mdeschamps at mangrove-systems.com> [040528 16:06]:
> > I've rere-reread  LinuxBios port to AMD64 guide during some
> > documentation making.
>  
> If you or anyone else have additions to this document, let me know. It
> waits desperately for more detailed explanations and restructuring in
> many places.
> 
> > Linuxbios is supposed to support "Trident Cyberblade 3d" natively
> > and I have a Cyberblade/i1 rev 6a in my chipset...
>  
> > Please don't tell me that I've spend time making it work, though
> > it isn't really, while there is a native support ?!?
>  
> I have no idea whether the Cyberblade i1 and 3d are the same. If your
> device has the following PCI id it is the same:
>         .vendor = 0x1023,
>         .device = 0x9880,

I've check my device out it is :
 1023 : 8500
oh. It may be compromised.

> 
> The Cyberblade code is not working though. If it would work, you would
> not even need to set CONFIG_VGABIOS to get something on the screen.
> It might be as simple as adding a delay to the outp() function but I
> have no idea. It is enabled in the newisys/khepri build. I added some 
> debug output to the driver.
> 
It is a way out for me.. and for others as you say below.

In what part of the code is this writing outp() ? It is not in vgabios.c
is it ? 
i say that that because i believe it was a common file for every
build... 
thanks again.
> If you have some time, feel free to fix the cyberblade code. This would
> be valuable for quite some AMD64 systems, including the Newisys 2100 and
> Sun Fire V20z display.
> 
> Stefan

For the time being, i'am at writing doc and well
this is a needed step, first it helps me understand in the whole,
second i've been ordered to do so.

I would gladly help ... what I could is bringing my doc to you and
LinuxBios people.
But I write it in french since i'll prepare a 'conference'  at
my university based upon it: hey, my intented audience is frenchy.

Moreover, i've led it as a study of project, well sure that's no 
a burden it but for example it's a bit offside the way you 
present the topic in your doc.

But it is detailled, stuffed with example and very newbie friendly, 
at least I could swear :) Though it need some reform to fit your
structure.

Listen, if you or anyone is interested in it, knowing that and, 
is a somewhat good french to english translator I'll share with'
glad to have a early point of view ... and correction.

mathieu



From stepan at openbios.org  Fri May 28 10:50:01 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Fri May 28 10:50:01 2004
Subject: Native LinuxBios Support
In-Reply-To: <1085759565.17249.55.camel@Calliphara>
References: <1085753160.17249.22.camel@Calliphara> <20040528145535.GA1715@openbios.org> <1085759565.17249.55.camel@Calliphara>
Message-ID: <20040528161114.GA3248@openbios.org>

* Mathieu Deschamps <mdeschamps at mangrove-systems.com> [040528 17:52]:
> It is a way out for me.. and for others as you say below.
> 
> In what part of the code is this writing outp() ? It is not in vgabios.c
> is it ? 

src/drivers/trident/blade3d/blade3d.c


Stefan



From maillists at petrolhead.com  Fri May 28 10:59:01 2004
From: maillists at petrolhead.com (maillists at petrolhead.com)
Date: Fri May 28 10:59:01 2004
Subject: Questions about Quartet build
Message-ID: <10D204DE080CA744A64FC11EBC67A17728DCD8@portacabin.no-ip.org>

Hi,

I've been trying to understand mp_table.c and irq_tables.c for the Quartet,
these files don't seem to match the Quartet architecture and I'm a little
bit confused as to why. My questions regarding these files are;

1) It appears that these files are expecting certain 8111 devices (PCI
bridge, LPC bridge, etc.) to be on PCI bus number 1. Shouldn't they really
be on bus number 0? The Linux BIOS seems to enumerate this as bus 0.

2) The code in mptable.c looks for the 8111 on bus 1 and so would default
bus_8111_1 to 4 and bus_isa to 5. Bus 5 conflicts with the enumeration of
the second 8131. Is this correct or should it just be looking on bus 0?

3) Is bus_8131_1 and bus_8131_2 supposed to represent both PCI bridge
devices within a single 8131? I can't see anywhere in the code where it
fills out the MPS table for the fixed devices like the inbuilt NIC or SCSI.

Many thanks for the help

Chris


From nathanael at gnat.ca  Fri May 28 11:04:01 2004
From: nathanael at gnat.ca (Nathanael Noblet)
Date: Fri May 28 11:04:01 2004
Subject: Native LinuxBios Support
In-Reply-To: <1085759565.17249.55.camel@Calliphara>
Message-ID: <9C391686-B0C3-11D8-B4CF-0003931B4D6A@gnat.ca>

On Friday, May 28, 2004, at 08:52 AM, Mathieu Deschamps wrote:
> For the time being, i'am at writing doc and well
> this is a needed step, first it helps me understand in the whole,
> second i've been ordered to do so.
>
> I would gladly help ... what I could is bringing my doc to you and
> LinuxBios people.
> But I write it in french since i'll prepare a 'conference'  at
> my university based upon it: hey, my intented audience is frenchy.

I can translate it to english for you.

-- 
Nathanael D. Noblet
Gnat Solutions
412 - 135 Gorge Road E
Victoria, BC V9A 1L1

T/F 250.385.4613

http://www.gnat.ca/



From YhLu at tyan.com  Fri May 28 11:15:00 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 28 11:15:00 2004
Subject: =?GB2312?B?tPC4tDogW0NPTU1JVF0gcm9tY2MgMC42MyBhbmQgc29tZSBmaXhl?=
	=?GB2312?B?cy4uLg==?=
Message-ID: <3174569B9743D511922F00A0C94314230506459F@TYANWEB>

I'd like to wait it to produce smaller code. Otherwise if I enable superio +
ati support, It will be greater than 64K in debug mode.

When will that be ready?

Regards

YH

-----????-----
???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
????: 2004?5?28? 7:26
???: LinuxBIOS
??: [COMMIT] romcc 0.63 and some fixes...


I finally have romcc to the point where I can seriously look
at size optimizations.  I am finally there after a lot of bug fixing
and experimentation. 

Because of added correctness in handling of small types I have
measured about a 1K growth on the hdama port or about 3%.  But things
should start shrinking soon.

More optimization opportunities have been exposed so which breaks
some code that was not right but lucky.

Have fun with this.

Eric


- Upgrade to romcc version 0.63
  This includes more test cases
  Lots of small bug fixes
  A complete C preprocessor is now built in
  Initial support for not inlining everything
  __attribute__((noinline)) works
  Better command line options and help
  Constants arrays can be read at compile time
  Asm statements that are not volatile will now be removed when their
outputs go unused
  Loads and stores that are not volatile will be removed when their values
go unused
  The number of FIXMES in the code is finally starting to go down.

Tags romcc_0_38 and romcc_0_63 are present.  In case you need to regress the
version of romcc.


- Added volatile to asm statements in auto.c and failover.c
- Updated the romcc version in Config.lb
- Fixed type sizes in romcc_io.h and io.h inl() returning a byte was nasty

 Modified Files:
    src/arch/i386/include/arch/romcc_io.h
    src/arch/i386/include/arch/io.h
    src/mainboard/arima/hdama/auto.c
    src/mainboard/arima/hdama/failover.c src/config/Config.lb


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


From YhLu at tyan.com  Fri May 28 11:20:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 28 11:20:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVk?=
	=?GB2312?B?IHdpdGggZnJlZWJpb3MyIQ==?=
Message-ID: <3174569B9743D511922F00A0C9431423050645A3@TYANWEB>

You got time for USB boot debug?

Do you have any idea about:
USB device control ed works well, but the bulk ed doesn't work, USB report
device not responding?

Does the code in baremetal work?
In the code, signature of cbw and csw define missed 0x.

Regards

YH

-----????-----
???: Steven James [mailto:pyro at linuxlabs.com] 
????: 2004?5?27? 15:56
???: YhLu
??: ron minnich; Jay Miller; ebiederman at lnxi.com; LinuxBIOS
??: Re: ??: ??: ??: Getting Started with freebios2!

Greetings,

I'm finally getting dug out after being snowed under :-)

The spec is probably part of:
http://www.usb.org/developers/devclass_docs/usbcdc11.pdf

The communications class. I'm guessing it would be a subset of POTS modem
with a transparent data protocol. That would imply line contol on the
control ep, and either bulk transfer or isochronous pipe pairs for the
serial data.

It's a lot more involved than a simple UART, that's for sure.

On a side note, I THOUGHT I would have time by now to bang on the USB
boot. Hopefully, I'll be able to do more with it now (so I say :-)

As soon as I get up to speed on freebios2, I'll have a good test platform.

For the serial, UHCI and OHCI will be good. EHCI can likely be ignored for
the BIOS since fast devices are required to fall back and EHCI always has
one of UHCI or OHCI to handle low speed USB.

G'day,
sjames


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


On Thu, 27 May 2004, YhLu wrote:

> So the LinuxBIOS need to
> 1. init USB controller
> 2. create usb_dev to be serial.
> 3. use usb_control_msg and usb_bulk_msg to talk with the serial device.
>
> What the USB type, OHCI or UCHI or EHCI??
>
> I wonder if some source code or documents that define No 3 above?
>
> Regards
>
> YH
>
> -----????-----
> ???: ron minnich [mailto:rminnich at lanl.gov]
> ????: 2004?5?27? 14:23
> ???: YhLu
> ??: Jay Miller; ebiederman at lnxi.com; LinuxBIOS
> ??: Re: ??: ??: Getting Started with freebios2!
>
> On Thu, 27 May 2004, YhLu wrote:
>
> > Usb to serial ???
>
> yes, it's now needed :-(
>
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
>


From jcantara at comcast.net  Fri May 28 11:23:01 2004
From: jcantara at comcast.net (jcantara at comcast.net)
Date: Fri May 28 11:23:01 2004
Subject: Greetings
Message-ID: <052820041644.25716.40B76C56000E12930000647422007340760E9D0E9B020E0C06@comcast.net>

Hello,

I'm new to: This List, and Linux in general.

Why I joined: I have a keen interest in both Linux and BIOSs, and may be able to provide some help on the BIOS and hardware end of things.

Some about me: I work for a company that provides "aftermarket" Award BIOSs, built from source provided to us through an agreement with Award themselves. I'm a semi-recent graduate of Electrical Engineering, and live in Massachusetts. I actually concentrated in embedded systems design, but I ended up here, configuring BIOSs, and working on the company website, go figure :)

I thought I might be able to provide some help on the hardware side of things, having a lot of insight into the BIOS. Obviously I can't share the source code we have, or violate any of the agreements my company has though.

This list seems fairly busy, from the few mails I've already received today since I signed up.

-Jesse


From rsmith at bitworks.com  Fri May 28 11:31:01 2004
From: rsmith at bitworks.com (Richard Smith)
Date: Fri May 28 11:31:01 2004
Subject: Testbios works for ATI too !!!
In-Reply-To: <1085693713.5653.81.camel@exponential.lanl.gov>
References: <Pine.LNX.4.44.0405271515070.23982-100000@maxroach.lanl.gov>	 <40B65BD9.8060200@bitworks.com> <1085693713.5653.81.camel@exponential.lanl.gov>
Message-ID: <40B76E4F.50000@bitworks.com>

Li-Ta Lo wrote:

>>>>I don't suppose there is a way to use testbios with a system having 2 
>>>>video cards is there?

I need to try and make this work.

I've sucessfully run the new emulator on my PCI dev card in a desktop 
system with the PCI card as its only display and received a bios init 
message.  Yah! The most progress I've had in weeks since ATI's tech help 
is proving to not be so helpful.

It still does not work on my target system.  Going over the IO dumps 
between the 2 systems I find that some of the ins get different info and 
then the bios does different stuff.  Some of the bits that are different 
are CRT enabled bits.

So my guess is that based on if the CRT is already up (ie warm boot) the 
BIOS takes a differnt path than that of a cold boot.

So I really need to run the emulator on my PCI card with only a POR.

What I'm currently doing is using setpci to disable the primary mem and 
IO responses and then enabling the secondary card.  This is the same 
method I used in my previous bios setup to init 2 video chips.  Just in 
the BIOS at boot time rather than from user space.

Then I run testbios.

I'm running it from a remote ssh login because it dosn't seem to work 
properly if I run from a console session.

Anyway it does something differnt and does not init the card.  However 
its not the same as what it does on my target.  I'm still reviewing the 
io log files.

Any reason why the enable/disable via setpci might not work from user 
space like does in BIOS land.




From dwh at lanl.gov  Fri May 28 11:31:25 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Fri May 28 11:31:25 2004
Subject: Greetings
In-Reply-To: <052820041644.25716.40B76C56000E12930000647422007340760E9D0E9B020E0C06@comcast.net>
Message-ID: <Pine.LNX.4.44.0405281049160.12573-100000@ccs-mail.lanl.gov>

Welcome! Did you have anything specific in mind? A specific mainboard 
that you want to work on, perhaps?

On Fri, 28 May 2004 jcantara at comcast.net wrote:

> Hello,
> 
> I'm new to: This List, and Linux in general.
> 
> Why I joined: I have a keen interest in both Linux and BIOSs, and may be able to provide some help on the BIOS and hardware end of things.
> 
> Some about me: I work for a company that provides "aftermarket" Award BIOSs, built from source provided to us through an agreement with Award themselves. I'm a semi-recent graduate of Electrical Engineering, and live in Massachusetts. I actually concentrated in embedded systems design, but I ended up here, configuring BIOSs, and working on the company website, go figure :)
> 
> I thought I might be able to provide some help on the hardware side of things, having a lot of insight into the BIOS. Obviously I can't share the source code we have, or violate any of the agreements my company has though.
> 
> This list seems fairly busy, from the few mails I've already received today since I signed up.
> 
> -Jesse
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From ebiederman at lnxi.com  Fri May 28 11:33:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 11:33:00 2004
Subject: =?gb2312?b?tPC4tA==?=: [COMMIT] romcc 0.63 and some fixes...
In-Reply-To: <3174569B9743D511922F00A0C94314230506459F@TYANWEB>
References: <3174569B9743D511922F00A0C94314230506459F@TYANWEB>
Message-ID: <m3r7t4cwz3.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> I'd like to wait it to produce smaller code. Otherwise if I enable superio +
> ati support, It will be greater than 64K in debug mode.
> 
> When will that be ready?

The code is feature complete so it will correctly not inline functions
(producing smaller code) if it does not run out of registers.

My simple test cases have worked well.

My complicated test case that uses an old version of production code
ran out of registers after consuming just the 8 general purpose
registers.  So mostly it is a matter of playing with the code, and
figuring out why weird things are happening.

Eric


From YhLu at tyan.com  Fri May 28 11:35:01 2004
From: YhLu at tyan.com (YhLu)
Date: Fri May 28 11:35:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogW0NPTU1JVF0gcm9tY2MgMC42MyBhbmQgc29t?=
	=?GB2312?B?ZSBmaXhlcy4uLg==?=
Message-ID: <3174569B9743D511922F00A0C9431423050645A9@TYANWEB>

After I get USB boot done, I will try that and modify the auto.c.....

Regards

YH

-----????-----
???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
????: 2004?5?28? 9:56
???: YhLu
??: LinuxBIOS
??: Re: ??: [COMMIT] romcc 0.63 and some fixes...

YhLu <YhLu at tyan.com> writes:

> I'd like to wait it to produce smaller code. Otherwise if I enable superio
+
> ati support, It will be greater than 64K in debug mode.
> 
> When will that be ready?

The code is feature complete so it will correctly not inline functions
(producing smaller code) if it does not run out of registers.

My simple test cases have worked well.

My complicated test case that uses an old version of production code
ran out of registers after consuming just the 8 general purpose
registers.  So mostly it is a matter of playing with the code, and
figuring out why weird things are happening.

Eric


From backblue at netcabo.pt  Fri May 28 12:45:01 2004
From: backblue at netcabo.pt (backblue)
Date: Fri May 28 12:45:01 2004
Subject: Greetings
In-Reply-To: <Pine.LNX.4.44.0405281049160.12573-100000@ccs-mail.lanl.gov>
References: <052820041644.25716.40B76C56000E12930000647422007340760E9D0E9B020E0C06@comcast.net>
	<Pine.LNX.4.44.0405281049160.12573-100000@ccs-mail.lanl.gov>
Message-ID: <20040527191053.14a64489@fork.ketic.com>

Hi,

I'm interested in developing linuxbios for the mainboards i have, but i dont find any kind of help, any where, can you help me?

On Fri, 28 May 2004 10:52:55 -0600 (MDT)
"Hendricks David W." <dwh at lanl.gov> wrote:

> Welcome! Did you have anything specific in mind? A specific mainboard 
> that you want to work on, perhaps?
> 
> On Fri, 28 May 2004 jcantara at comcast.net wrote:
> 
> > Hello,
> > 
> > I'm new to: This List, and Linux in general.
> > 
> > Why I joined: I have a keen interest in both Linux and BIOSs, and may be able to provide some help on the BIOS and hardware end of things.
> > 
> > Some about me: I work for a company that provides "aftermarket" Award BIOSs, built from source provided to us through an agreement with Award themselves. I'm a semi-recent graduate of Electrical Engineering, and live in Massachusetts. I actually concentrated in embedded systems design, but I ended up here, configuring BIOSs, and working on the company website, go figure :)
> > 
> > I thought I might be able to provide some help on the hardware side of things, having a lot of insight into the BIOS. Obviously I can't share the source code we have, or violate any of the agreements my company has though.
> > 
> > This list seems fairly busy, from the few mails I've already received today since I signed up.
> > 
> > -Jesse
> > _______________________________________________
> > 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


From ebiederman at lnxi.com  Fri May 28 13:19:00 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 13:19:00 2004
Subject: =?gb2312?b?tPC4tA==?=: =?gb2312?b?tPC4tA==?=: [COMMIT] romcc
  0.63 and some fixes...
In-Reply-To: <3174569B9743D511922F00A0C9431423050645A9@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050645A9@TYANWEB>
Message-ID: <m365ag9yxn.fsf@maxwell.lnxi.com>

YhLu <YhLu at tyan.com> writes:

> After I get USB boot done, I will try that and modify the auto.c.....

Ok.  

A quick update.

In playing around I wrote the function:

static void printo_debug(const char *str) __attribute__((noinline))
{
	print_debug(str);
}

And started replacing the calls to print_debug one by one.
On the port I am currently working on I managed to shave off 4K
pretty quickly.

So it looks like for the really commonly called functions we
will need 2 names.  One inline that will be inlined the other that won't.

It is not a very elegant solution but it works and is not very hard to
manage.

Eric


From rminnich at lanl.gov  Fri May 28 14:04:01 2004
From: rminnich at lanl.gov (ron minnich)
Date: Fri May 28 14:04:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <20040527212505.GA9346@openbios.org>
Message-ID: <Pine.LNX.4.44.0405281325130.32601-100000@maxroach.lanl.gov>

On Thu, 27 May 2004, Stefan Reinauer wrote:

> indeed true. But for x86 hardware, putting all of the x86 emulator in
> rom is less elegant than vm86 stuff, even though I have no clue about
> the later.

yes but recall that the emulator lets you support systems like power pc.

ron



From joshua at joshuawise.com  Fri May 28 15:48:01 2004
From: joshua at joshuawise.com (Joshua Wise)
Date: Fri May 28 15:48:01 2004
Subject: Chipsets: status page?
Message-ID: <200405281631.04833.joshua@joshuawise.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I read the FAQ looking for information on chipsets supported in LinuxBIOS, and 
it pointed me towards the status page, however I can only find information 
about mainboards on that page. Am I looking in the wrong place? For 
reference, I'm wondering if the AMD-760 and the VIA VT82C686 are supported.

Thanks,
joshua

- -- 
Joshua Wise | www.joshuawise.com
GPG Key     | 0xEA80E0B3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAt6GIPn9tWOqA4LMRAv+PAJ9UATxRWjvrc3RCuXSeuZlT5DuWFwCfdk8u
JgBq6tZPGH9xZhz4adcmH6Y=
=ndYm
-----END PGP SIGNATURE-----


From joshua at joshuawise.com  Fri May 28 15:51:22 2004
From: joshua at joshuawise.com (Joshua Wise)
Date: Fri May 28 15:51:22 2004
Subject: testbios: other chips?
Message-ID: <200405281632.28416.joshua@joshuawise.com>

I've seen various success stories of testbios being used to execute VGA BIOSes 
and get VGA cards running. This led me to ask the question of whether it 
would be feasible to get BIOSes from other option cards, such as my "00:13.0 
Unknown mass storage controller: Triones Technologies, Inc. 
HPT366/368/370/370A/372 (rev 04)" to execute and initialize.

Thanks,
joshua

-- 
Joshua Wise | www.joshuawise.com
GPG Key     | 0xEA80E0B3


From dwh at lanl.gov  Fri May 28 16:26:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Fri May 28 16:26:01 2004
Subject: Chipsets: status page?
In-Reply-To: <200405281631.04833.joshua@joshuawise.com>
Message-ID: <Pine.LNX.4.44.0405281539390.12573-100000@ccs-mail.lanl.gov>

There is some support for the AMD760 in the freebios1 tree:
http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/northbridge/amd/amd76x/

Not sure what the status is on the 82c686. Isn't that what what the 
Epia uses (cyrix/eden platform)? If so, check the Epia stuff in the 
freebios2 tree: 
http://cvs.sourceforge.net/viewcvs.py/freebios/freebios2/src/mainboard/via/

On Fri, 28 May 2004, Joshua Wise wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I read the FAQ looking for information on chipsets supported in LinuxBIOS, and 
> it pointed me towards the status page, however I can only find information 
> about mainboards on that page. Am I looking in the wrong place? For 
> reference, I'm wondering if the AMD-760 and the VIA VT82C686 are supported.
> 
> Thanks,
> joshua
> 
> - -- 
> Joshua Wise | www.joshuawise.com
> GPG Key     | 0xEA80E0B3
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
> 
> iD8DBQFAt6GIPn9tWOqA4LMRAv+PAJ9UATxRWjvrc3RCuXSeuZlT5DuWFwCfdk8u
> JgBq6tZPGH9xZhz4adcmH6Y=
> =ndYm
> -----END PGP SIGNATURE-----
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



From joshua at joshuawise.com  Fri May 28 16:31:00 2004
From: joshua at joshuawise.com (Joshua Wise)
Date: Fri May 28 16:31:00 2004
Subject: Chipsets: status page?
In-Reply-To: <Pine.LNX.4.44.0405281539390.12573-100000@ccs-mail.lanl.gov>
References: <Pine.LNX.4.44.0405281539390.12573-100000@ccs-mail.lanl.gov>
Message-ID: <200405281752.54169.joshua@joshuawise.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 28 May 2004 5:47 pm, Hendricks David W. wrote:
> There is some support for the AMD760 in the freebios1 tree:
> http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/northbridge/amd
>/amd76x/
Ok, what's the difference between freebios1 and freebios2? Which should I be 
using?

> Not sure what the status is on the 82c686. Isn't that what what the
> Epia uses (cyrix/eden platform)? If so, check the Epia stuff in the
> freebios2 tree:
> http://cvs.sourceforge.net/viewcvs.py/freebios/freebios2/src/mainboard/via/
I think Epia uses vt8231 or vt8235, one of those. In any event, I don't see a 
southbridge/via/82c686...

joshua

- -- 
Joshua Wise | www.joshuawise.com
GPG Key     | 0xEA80E0B3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAt7S1Pn9tWOqA4LMRAhYyAJ948E4s/LzHrHQXNXBewvEcvS7ieQCfbTSq
aTk/YcAMc/YB52pdLQsrkZI=
=528o
-----END PGP SIGNATURE-----


From pyro at linuxlabs.com  Fri May 28 18:29:01 2004
From: pyro at linuxlabs.com (Steven James)
Date: Fri May 28 18:29:01 2004
Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogtPC4tDogR2V0dGluZyBTdGFydGVk?=
 =?GB2312?B?IHdpdGggZnJlZWJpb3MyIQ==?=
In-Reply-To: <3174569B9743D511922F00A0C9431423050645A3@TYANWEB>
References: <3174569B9743D511922F00A0C9431423050645A3@TYANWEB>
Message-ID: <Pine.LNX.4.58.0405282347220.26413@ucontrol.mobiledns.com>

Greetings,

I will have time over the weekend and hopefully next week. First, I'll
have to get my replacement board flashed up (but that shouldn't be too
bad).

The baremetal code did/does work on the flash device I have (Trekstore).

Probably the first thing for me is to see if FILO works with my device. It
may be a case of different interpretations of the spec, and just a need to
work out details like that.

G'day,
sjames


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


On Fri, 28 May 2004, YhLu wrote:

> You got time for USB boot debug?
>
> Do you have any idea about:
> USB device control ed works well, but the bulk ed doesn't work, USB report
> device not responding?
>
> Does the code in baremetal work?
> In the code, signature of cbw and csw define missed 0x.
>
> Regards
>
> YH
>
> -----????-----
> ???: Steven James [mailto:pyro at linuxlabs.com]
> ????: 2004?5?27? 15:56
> ???: YhLu
> ??: ron minnich; Jay Miller; ebiederman at lnxi.com; LinuxBIOS
> ??: Re: ??: ??: ??: Getting Started with freebios2!
>
> Greetings,
>
> I'm finally getting dug out after being snowed under :-)
>
> The spec is probably part of:
> http://www.usb.org/developers/devclass_docs/usbcdc11.pdf
>
> The communications class. I'm guessing it would be a subset of POTS modem
> with a transparent data protocol. That would imply line contol on the
> control ep, and either bulk transfer or isochronous pipe pairs for the
> serial data.
>
> It's a lot more involved than a simple UART, that's for sure.
>
> On a side note, I THOUGHT I would have time by now to bang on the USB
> boot. Hopefully, I'll be able to do more with it now (so I say :-)
>
> As soon as I get up to speed on freebios2, I'll have a good test platform.
>
> For the serial, UHCI and OHCI will be good. EHCI can likely be ignored for
> the BIOS since fast devices are required to fall back and EHCI always has
> one of UHCI or OHCI to handle low speed USB.
>
> G'day,
> sjames
>
>
> -------------------------steven james, director of research, linux labs
> ... ........ ..... ....                    230 peachtree st nw ste 2701
> the original linux labs                             atlanta.ga.us 30303
>       -since 1995                              http://www.linuxlabs.com
>                                               office & fax 866.545.6306
> -----------------------------------------------------------------------
>
>
> On Thu, 27 May 2004, YhLu wrote:
>
> > So the LinuxBIOS need to
> > 1. init USB controller
> > 2. create usb_dev to be serial.
> > 3. use usb_control_msg and usb_bulk_msg to talk with the serial device.
> >
> > What the USB type, OHCI or UCHI or EHCI??
> >
> > I wonder if some source code or documents that define No 3 above?
> >
> > Regards
> >
> > YH
> >
> > -----????-----
> > ???: ron minnich [mailto:rminnich at lanl.gov]
> > ????: 2004?5?27? 14:23
> > ???: YhLu
> > ??: Jay Miller; ebiederman at lnxi.com; LinuxBIOS
> > ??: Re: ??: ??: Getting Started with freebios2!
> >
> > On Thu, 27 May 2004, YhLu wrote:
> >
> > > Usb to serial ???
> >
> > yes, it's now needed :-(
> >
> > ron
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
> >
>


From dwh at lanl.gov  Fri May 28 18:34:01 2004
From: dwh at lanl.gov (Hendricks David W.)
Date: Fri May 28 18:34:01 2004
Subject: Know someone available for a freebios port to an SMP Opteron
 motherboard? (fwd)
Message-ID: <Pine.LNX.4.44.0405281754570.12573-100000@ccs-mail.lanl.gov>

Any takers?

---------- Forwarded message ----------
Date: Fri, 28 May 2004 13:52:18 -0700
From: William J. Earl <earl at agami.com>
To: ollie at users.sourceforge.net, ebiederm at users.sourceforge.net,
     dhendricks at users.sourceforge.net
Subject: Know someone available for a freebios port to an SMP Opteron
    motherboard?

      I am working with freebios for an SMP Opteron motherboard,
but I am very new to the source base.  Would you know of anyone
who might be available for a short contract to configure and
bring up freebios on a new Opteron motherboard?  I have the
relevant documentation and the cooperation of the vendor,
and working boards.

      I am writing to you as you have recently been checking in
improvements to freebios for Opteron.




From ebiederman at lnxi.com  Fri May 28 21:33:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 21:33:01 2004
Subject: testbios: other chips?
In-Reply-To: <200405281632.28416.joshua@joshuawise.com>
References: <200405281632.28416.joshua@joshuawise.com>
Message-ID: <m33c5kymac.fsf@maxwell.lnxi.com>

Joshua Wise <joshua at joshuawise.com> writes:

> I've seen various success stories of testbios being used to execute VGA BIOSes 
> and get VGA cards running. This led me to ask the question of whether it 
> would be feasible to get BIOSes from other option cards, such as my "00:13.0 
> Unknown mass storage controller: Triones Technologies, Inc. 
> HPT366/368/370/370A/372 (rev 04)" to execute and initialize.

That is currently not being considered.  That is territory for ADLO.
And full pcbios compatibility. 

My experience has been that the Linux drivers are good enough that
except for video this is not an issue.

Eric


From ebiederman at lnxi.com  Fri May 28 22:07:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 22:07:01 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <20040527212505.GA9346@openbios.org>
References: <20040527210837.GA8689@openbios.org>
	<Pine.LNX.4.44.0405271520460.23982-100000@maxroach.lanl.gov>
	<20040527212505.GA9346@openbios.org>
Message-ID: <m3fz9jvrk8.fsf@maxwell.lnxi.com>

Stefan Reinauer <stepan at openbios.org> writes:

> * ron minnich <rminnich at lanl.gov> [040527 23:21]:
> > again, you do not need to map option roms at 0c0000 in the emulator!
> > 
> > Map it anywhere, tell the emulator the location, and the emulator can 
> > satisfy memory "fetches" for c0000 by fetching from that location. 
> 
> indeed true. But for x86 hardware, putting all of the x86 emulator in
> rom is less elegant than vm86 stuff, even though I have no clue about
> the later.

Last I heard some Option Roms switch to 32bit mode.  You can't do
that in vm86 mode.  In general using vm86 is a way to put your fate
in someone else's hands.

We could possibly call the option roms directly but unless the space
cost is high an open source emulator is a good choice.

Eric


From ebiederman at lnxi.com  Fri May 28 22:13:01 2004
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: Fri May 28 22:13:01 2004
Subject: Greetings
In-Reply-To: <20040527191053.14a64489@fork.ketic.com>
References: <052820041644.25716.40B76C56000E12930000647422007340760E9D0E9B020E0C06@comcast.net>
	<Pine.LNX.4.44.0405281049160.12573-100000@ccs-mail.lanl.gov>
	<20040527191053.14a64489@fork.ketic.com>
Message-ID: <m3isefsy63.fsf@maxwell.lnxi.com>

backblue <backblue at netcabo.pt> writes:

> Hi,
> 
> I'm interested in developing linuxbios for the mainboards i have, but i dont
> find any kind of help, any where, can you help me?

We can obviously try.  Who knows if we will succeed.  The code
is available and we have done many ports previously. So...

Eric


From stepan at openbios.org  Sat May 29 04:35:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat May 29 04:35:00 2004
Subject: Greetings
In-Reply-To: <20040527191053.14a64489@fork.ketic.com>
References: <052820041644.25716.40B76C56000E12930000647422007340760E9D0E9B020E0C06@comcast.net> <Pine.LNX.4.44.0405281049160.12573-100000@ccs-mail.lanl.gov> <20040527191053.14a64489@fork.ketic.com>
Message-ID: <20040529095614.GB7236@openbios.org>

* backblue <backblue at netcabo.pt> [040527 20:10]:
> Hi,
> 
> I'm interested in developing linuxbios for the mainboards i have, but
> i dont find any kind of help, any where, can you help me?

Where have you been looking? Did you see below document?

   http://www.openbios.org/LinuxBIOS-AMD64.pdf

It gives some insight on non-AMD64 systems as well (and should be
enhanced to be a generic LinuxBIOS document) 

Besides, you need data sheets for your motherboard's components, if they
are not supported already. Check the source whether a component is
supported or not (northbridge, southbridge, superio)

Also, there is a whole lot of information stored in the LinuxBIOS
mailinglist archive which is no doubt a good reading.

   Stefan


From stepan at openbios.org  Sat May 29 04:38:00 2004
From: stepan at openbios.org (Stefan Reinauer)
Date: Sat May 29 04:38:00 2004
Subject: Resource Allocation for Option Rom
In-Reply-To: <m3fz9jvrk8.fsf@maxwell.lnxi.com>
References: <20040527210837.GA8689@openbios.org> <Pine.LNX.4.44.0405271520460.23982-100000@maxroach.lanl.gov> <20040527212505.GA9346@openbios.org> <m3fz9jvrk8.fsf@maxwell.lnxi.com>
Message-ID: <20040529095934.GC7236@openbios.org>

* Eric W. Biederman <ebiederman at lnxi.com> [040529 05:29]:
> Stefan Reinauer <stepan at openbios.org> writes:
> > indeed true. But for x86 hardware, putting all of the x86 emulator in
> > rom is less elegant than vm86 stuff, even though I have no clue about
> > the later.
> 
> Last I heard some Option Roms switch to 32bit mode.  You can't do
> that in vm86 mode.  In general using vm86 is a way to put your fate
> in someone else's hands.
 
Uh, this was the kind of thing I was scared would be the case. what
happens in such a case? Is there any way to trap this and at least
safely state that the device can't be supported?

> We could possibly call the option roms directly but unless the space
> cost is high an open source emulator is a good choice.

So the goal should rather be to reduce the size of the emulator than to
introduce different code paths for different platforms it seems.

Stefan


From nacho at estudio-verona.com  Mon May 31 22:46:01 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Mon May 31 22:46:01 2004
Subject: Has anyone heard about EPIA MII FastBoot ROM Utility?
Message-ID: <2880.192.168.1.3.1086063198.squirrel@mail.estudio-verona.com>

Hi! Here http://www.viaarena.com/?PageID=343 under Booting Utility I've
found what via calls FastBoot ROM. It says we can boot from
PCMCIA-CompactFlash and MDOC on epia MII, and source code is provided.
I'll be givin a try this week, because it will be nice to my proyect if I
can boot from CF, so I can forgot about using harddisk. What do you think
about? Anyone has used this?


From nacho at estudio-verona.com  Mon May 31 23:12:00 2004
From: nacho at estudio-verona.com (Ignacio Verona)
Date: Mon May 31 23:12:00 2004
Subject: Has anyone heard about EPIA MII FastBoot ROM Utility?
In-Reply-To: <2880.192.168.1.3.1086063198.squirrel@mail.estudio-verona.com>
References: <2880.192.168.1.3.1086063198.squirrel@mail.estudio-verona.com>
Message-ID: <3022.192.168.1.3.1086064740.squirrel@mail.estudio-verona.com>

Sorry, I think source code is not provided, only the one necessary for
boot customizing.