From liutao1980 at gmail.com  Fri Apr  1 03:33:02 2005
From: liutao1980 at gmail.com (Tao Liu)
Date: Fri, 1 Apr 2005 09:33:02 +0800
Subject: [LinuxBIOS] [PATCH] small fixes
In-Reply-To: <2ea3fae1050331094070af6f56@mail.gmail.com>
References: <8eca059b05033022304a8eb64@mail.gmail.com>
	<2ea3fae1050331094070af6f56@mail.gmail.com>
Message-ID: <8eca059b05033117332de4a7f8@mail.gmail.com>

OK, thanks!


On Thu, 31 Mar 2005 09:40:53 -0800, yhlu <yinghailu at gmail.com> wrote:
> you need to use tla to get latest source code.
> 
> YH
>



From liutao1980 at gmail.com  Fri Apr  1 03:48:30 2005
From: liutao1980 at gmail.com (Tao Liu)
Date: Fri, 1 Apr 2005 09:48:30 +0800
Subject: [LinuxBIOS] [PATCH 2/2] amd8111_nic: Set MAC address in linux bios
In-Reply-To: <3174569B9743D511922F00A0C943142309348DB5@TYANWEB>
References: <3174569B9743D511922F00A0C943142309348DB5@TYANWEB>
Message-ID: <8eca059b050331174838b0ede5@mail.gmail.com>

Our mainboard don't have the SEEPROM :(
I think have an individual SEEPROM for MAC is correct.

--
Liu Tao

On Thu, 31 Mar 2005 12:04:30 -0800, YhLu <YhLu at tyan.com> wrote:
> Should be in BIOS.because different MB use different MAC assigned in
> Factory.
> 
> But in MB design, it should use another SEEPROM to store that. So the BIOS
> or NIC get it.
> 
> YH
>



From petekarl at student.chalmers.se  Fri Apr  1 11:16:43 2005
From: petekarl at student.chalmers.se (Peter Karlsson)
Date: Fri, 1 Apr 2005 11:16:43 +0200 (MEST)
Subject: [LinuxBIOS] Re: RTC and linuxbios checksum versus pc checksum
In-Reply-To: <20050401073519.56036.qmail@web30003.mail.mud.yahoo.com>
References: <20050401073519.56036.qmail@web30003.mail.mud.yahoo.com>
Message-ID: <Pine.GSO.4.62.0504011108380.18292@bilbo.dd.chalmers.se>

On Thu, 31 Mar 2005, ramesh bios wrote:

> Well, I got things to work in the end by copying the
> standard bios's CR bit settings for the W83977AF.
> Regretably though, I have gained no understanding of
> why or how it's working. Amazingly, the standard bios
> sets CR30 on the W83977AF, ie: the RTC enable/disable
> bit to disabled. So the RTC appears to increment
> properly when that bit is disabled (which makes no
> sense to me at all, ie: disable the RTC and it ticks
> properly?). When that bit is enabled, and no other
> changes, the RTC has weird incrementation behavior.
> Almost seemed like random bits in mm:ss were changing.
> Also, I never understood why bytes in 0E-7F, the user
> ram changes during normal ticking of the clock. Oh
> well, it's working now so I guess I'll just push this
> mystery to the back of my mind. If anyone happens to
> understand this stuff, I'll sleep better once I've
> understood this.
>
> Thanks.
>
> --- ramesh bios <ramesh_bios at yahoo.com> wrote:
>> I was looking through linuxbios' freebios (v1) code
>> and see the following:
>>
>> rtc_checksum_valid(PC_CKS_RANGE_START,
>>
>> PC_CKS_RANGE_END,PC_CKS_LOC);
>> then
>> rtc_checksum_valid(LB_CKS_RANGE_START,
>>
>> LB_CKS_RANGE_END,LB_CKS_LOC);
>> then finally
>> rtc_set_checksum(PC_CKS_RANGE_START,
>>
>> PC_CKS_RANGE_END,PC_CKS_LOC);
>>
>> I looked in 2.6.11's mc146818 code and I don't see
>> it
>> writing a checksum so I'm not certain it's valid to
>> check for a checksum on boot since stuff like
>> hwclock
>> may/would have written to the cmos during normal
>> operation. Out of curiosity, how come there is a LB
>> checksum and then a PC checksum and then we write a
>> PC
>> checksum at the end. Is it for legacy compatibility,
>> I
>> didn't find any mention of it in the mailing list
>> and
>> google.
>>
>> Thanks.

The @clustermatic.org mail address is not to be used anymore.

If anyone knows anything about the above question please put this in the 
wiki-faq...

Best regards

Peter K




From petekarl at student.chalmers.se  Fri Apr  1 11:29:32 2005
From: petekarl at student.chalmers.se (Peter Karlsson)
Date: Fri, 1 Apr 2005 11:29:32 +0200 (MEST)
Subject: [LinuxBIOS] Glossary update...
Message-ID: <Pine.GSO.4.62.0504011116580.18292@bilbo.dd.chalmers.se>

Here's another update of the glossary of acronyms I've found on this list 
(and other's). Unfortunately it is quite hard (sometimes impossible) to 
dig up information about the acronym/definition on the internet (I'm 
planning to buy that book that someone recommended on this list) so some 
info is marked with '???'. If anyone wants to update that feel free to do 
so, it is much appreciated. I've attached a tar-ball containing the 
original glossary, a diff, and the updated glossary to hopefully make it 
easier (?) to update the wiki. Some info may or may not be relevant (I'm 
on ivtv, v4l, mesa, xorg, gentoo-users, linux-from-scratch, unichrome, 
opengfx amongst other mail-lists so I pick up a few things)...

Best regards

Peter K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glossary.tar.gz
Type: application/octet-stream
Size: 5056 bytes
Desc: 
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20050401/e4faae3b/attachment.obj>

From rminnich at lanl.gov  Fri Apr  1 16:56:15 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri, 1 Apr 2005 07:56:15 -0700 (MST)
Subject: [LinuxBIOS] Re: RTC and linuxbios checksum versus pc checksum
In-Reply-To: <Pine.GSO.4.62.0504011108380.18292@bilbo.dd.chalmers.se>
References: <20050401073519.56036.qmail@web30003.mail.mud.yahoo.com>
	<Pine.GSO.4.62.0504011108380.18292@bilbo.dd.chalmers.se>
Message-ID: <Pine.LNX.4.58.0504010755330.7511@enigma.lanl.gov>



On Fri, 1 Apr 2005, Peter Karlsson wrote:

> 
> If anyone knows anything about the above question please put this in the
> wiki-faq...

I think it's another hardware bug, and I think the description as ramesh 
wrote it would be nice to have in the FAQ. One of these "set this bit, 
don't ask why" type situations. 

ron



From smithbone at gmail.com  Fri Apr  1 17:25:19 2005
From: smithbone at gmail.com (Richard Smith)
Date: Fri, 1 Apr 2005 09:25:19 -0600
Subject: [LinuxBIOS] Re: RTC and linuxbios checksum versus pc checksum
In-Reply-To: <Pine.LNX.4.58.0504010755330.7511@enigma.lanl.gov>
References: <20050401073519.56036.qmail@web30003.mail.mud.yahoo.com>
	<Pine.GSO.4.62.0504011108380.18292@bilbo.dd.chalmers.se>
	<Pine.LNX.4.58.0504010755330.7511@enigma.lanl.gov>
Message-ID: <8a0c36780504010725656b0eb3@mail.gmail.com>

>mystery to the back of my mind. If anyone happens to
>understand this stuff, I'll sleep better once I've
>understood this.
 
> I think it's another hardware bug, and I think the description as ramesh
> wrote it would be nice to have in the FAQ. One of these "set this bit,
> don't ask why" type situations.

Check for errata notes on the part.  Perhaps the polarity of the
enable/disable bit is flipped and incorrect in datasheet.

-- 
Richard A. Smith



From okajima at digitalinfra.co.jp  Tue Apr  5 18:31:44 2005
From: okajima at digitalinfra.co.jp (Jun OKAJIMA)
Date: Wed, 06 Apr 2005 01:31:44 +0900
Subject: [LinuxBIOS] Boot Time
Message-ID: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>


Hello.

I understand one of the biggest merits of LinuxBIOS is fast booting.

Then, how fast it is? The top page of the Wiki says 3 sec, 
and "7/25/01: Dual Athlon update " issue says about 2 sec to
boot a kernel. But this log shows it took 20 sec.
http://www.carbotpc.com/linux/boottiming.log.txt
It is too big difference between 2 sec and 20 sec, dont you?

Especially, I would want to know the figures on VIA mini-ITX
mothres with USB memory booting. It is very good that if I could
get /bin/init started within 3 sec or such.

                --- Okajima, Jun. Tokyo, Japan.



From smithbone at gmail.com  Tue Apr  5 18:50:01 2005
From: smithbone at gmail.com (Richard Smith)
Date: Tue, 5 Apr 2005 11:50:01 -0500
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
Message-ID: <8a0c367805040509504abea033@mail.gmail.com>

> http://www.carbotpc.com/linux/boottiming.log.txt
> It is too big difference between 2 sec and 20 sec, dont you?

If you search the mailing list you will probally find a thread on that
report.  There is something wrong with his setup but rather than fix
it they seem to just want to post thier results.  2 and 3 seconds is
the norm.

-- 
Richard A. Smith



From tyson at irobot.com  Tue Apr  5 19:05:14 2005
From: tyson at irobot.com (Tyson Sawyer)
Date: Tue, 05 Apr 2005 13:05:14 -0400
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
Message-ID: <4252C54A.6010506@irobot.com>

Jun OKAJIMA wrote:
> Hello.
> 
> I understand one of the biggest merits of LinuxBIOS is fast booting.
> 
> Then, how fast it is? The top page of the Wiki says 3 sec, 
> and "7/25/01: Dual Athlon update " issue says about 2 sec to
> boot a kernel. But this log shows it took 20 sec.

The dominant factors are device driver init/probing and starting 
services.  Thus, boot time will be very dependent on system 
configuration.  For the the 3 second example I booted to a shell prompt 
using an initrd image, serial console and not much else.  Most real 
systems are going to take a fair bit longer than that.

The main difference w/linuxbios is that the kernel is loaded and running 
in under 1 second vs. 10-50 seconds for a COTS bios.  How fast things go 
once the kernel is booted is up to you.

Cheers!
Ty

-- 
Tyson D Sawyer                     iRobot Corporation
Lead Systems Engineer              Government & Industrial Robotics
tsawyer at irobot.com                 Robots for the Real World
781-345-0200 ext 3329              http://www.irobot.com



From talbotx at comcast.net  Tue Apr  5 19:20:00 2005
From: talbotx at comcast.net (Adam Talbot)
Date: Tue, 5 Apr 2005 10:20:00 -0700
Subject: [LinuxBIOS] EPIA-M code still seems to be broken
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<8a0c367805040509504abea033@mail.gmail.com>
Message-ID: <004101c53a03$b2a0e950$c501a8c0@newflame>

Any one have any luck on fixing the EPIA-M code?
-Adam




From stepan at openbios.org  Tue Apr  5 21:47:09 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue, 5 Apr 2005 21:47:09 +0200
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
Message-ID: <20050405194709.GA26424@openbios.org>

* Jun OKAJIMA <okajima at digitalinfra.co.jp> [050405 18:31]:
> Then, how fast it is? The top page of the Wiki says 3 sec, 
> and "7/25/01: Dual Athlon update " issue says about 2 sec to
> boot a kernel. But this log shows it took 20 sec.
> http://www.carbotpc.com/linux/boottiming.log.txt
> It is too big difference between 2 sec and 20 sec, dont you?

>From the log you can see that Linux starts booting after 13.252secs.
This is the value the above 2-3 seconds have to be measured against.

Another thing that is needed to get to 2-3secs is to disable most 
debugging. 
With serial speed at 9600 you will spend an extra second for
each kilobyte of debugging output. Go disable serial POST.

Disabling sound support in filo might be a win, I have not checked
though.

4 seconds are spent in the Linux kernel for IDE probing. There are
better mechanisms to probe for IDE devices than what Linux does. 
OpenBIOS and filo are two examples of how to do it a lot quicker. I
think some of this went into kernel 2.6, or at least I saw patches
floating around that pushed IDE probing below 1s.

> Especially, I would want to know the figures on VIA mini-ITX
> mothres with USB memory booting. It is very good that if I could
> get /bin/init started within 3 sec or such.
 
Use an initrd and remove the IDE driver completely from Linux. That will
speed things up a lot when using 2.4


Stefan




From smithbone at gmail.com  Tue Apr  5 22:21:25 2005
From: smithbone at gmail.com (Richard Smith)
Date: Tue, 5 Apr 2005 15:21:25 -0500
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <20050405194709.GA26424@openbios.org>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<20050405194709.GA26424@openbios.org>
Message-ID: <8a0c3678050405132162f6ba6d@mail.gmail.com>

On Apr 5, 2005 2:47 PM, Stefan Reinauer <stepan at openbios.org> wrote:

> Another thing that is needed to get to 2-3secs is to disable most
> debugging.
> With serial speed at 9600 you will spend an extra second for
> each kilobyte of debugging output. Go disable serial POST.

Why disable debugging output when you can just bump the serial speed
up to 115200.  Thats the way I've always run my setups. Then you still
get debugging output but its plenty fast.

Although if you are going for raw speed then yeah disable the serial
debugging output

-- 
Richard A. Smith



From Peter.VanEchaute at bench.com  Wed Apr  6 15:47:05 2005
From: Peter.VanEchaute at bench.com (Peter.VanEchaute at bench.com)
Date: Wed, 6 Apr 2005 09:47:05 -0400
Subject: [LinuxBIOS] irq_tables.c
Message-ID: <9B124F08B3EFDA4F8813B05102DC7195035C3914@nh-ex01.bench.com>

Hello,
 
I am trying to understand the "linka, linkb, linkc, linkd" part of this table.  I understand the rest of the table, just not those pieces.  Can someone give me a brief explanation?  Thank you for your time.
 
Cheers,
Peter Van Echaute
Email: Peter.VanEchaute at bench.com <mailto:Peter.VanEchaute at bench.com> 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20050406/f840f66e/attachment.html>

From hamishl at dplanet.ch  Wed Apr  6 16:39:01 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Wed, 6 Apr 2005 16:39:01 +0200
Subject: [LinuxBIOS] Geode in Linuxbios v2
Message-ID: <LDEKLCIFJMAFIOPNLICOEECLEMAA.hamishl@dplanet.ch>

Hi,

I have been following with interest discussions from Ramesh Bios and others
relating to the Geode processor. I have a few boards here with GX1's with
the CX5530 and PC97307/PC97317 superio, and am getting started with getting
LinuxBIOS onto those boards.

I have a board booting up to the point of attempting to load an ELF image,
at which point it craps out! This is using the v1 code tree. My project
would appear to be a long-term one and I was wondering if it would not be
beneficial to all to port all of the GX1 related code to LinuxBIOS v2.
Ramesh, I saw in one of your posts that you had mentioned willingness to
start working on this - if you have started, maybe we could work together on
this?

I have had a brief look at the code in question to attempt to see why the
elfboot code is failing, but have not found a logical reason yet. The one
scarry debug message I get is the following:

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

null

op: 0x07  eax:0x00000000  ebx:0x00000000  ecx:0x00000000  edx:0x00000000
op: 0x08  eax:0x00000000  ebx:0x00000000  ecx:0x00000000  edx:0x00000000
op: 0x09  eax:0x00000000  ebx:0x00000000  ecx:0x00000000  edx:0x00000000
op: 0x0a  eax:0x00000000  ebx:0x00000000  ecx:0x00000000  edx:0x00000000
...
...
...

It would appear as though the null is being printed out by the
stream->init() call in the elfboot function in $(TOP)/lib/elfboot.c. I have
had a further look into the code and do not see anywhere where the init
function pointer within the stream struct in question is initialised.

I have noticed in v2 that there is a completely different code interface to
the stream stuff, and rather than patching broken code, maybe it is a good
idea to look at moving the working GX1 code to v2.

I have not looked at the v2 tree much, and am sure there is a learning curve
to start porting the stuff across. Any pointers as to where there may be
some docs relating to the porting process?

Thanks in advance

Hamish
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 05.04.2005




From smithbone at gmail.com  Wed Apr  6 16:59:57 2005
From: smithbone at gmail.com (Richard Smith)
Date: Wed, 6 Apr 2005 14:59:57 +0000
Subject: [LinuxBIOS] Geode in Linuxbios v2
In-Reply-To: <LDEKLCIFJMAFIOPNLICOEECLEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOEECLEMAA.hamishl@dplanet.ch>
Message-ID: <8a0c3678050406075923954325@mail.gmail.com>

> I have noticed in v2 that there is a completely different code interface to
> the stream stuff, and rather than patching broken code, maybe it is a good
> idea to look at moving the working GX1 code to v2.

It's not just a good idea its _required_.  No active development has
been going on in the V1 tree for a long time which means none of the
linuxbios developers have been working with that code.

V2 is better than V1 in almost all cases.  And where its not it needs
to be fixed.
V1 is a dead end street.  Its deprecated and largely unsupported.

So if you want any real support from most of the developers on this
list you will have to move to V2.

Now thats not to say we won't answer questions about v1 its just most
of the developers haven't looked at that code in a long while and we
forget easily.

Now unfortunately there still isn't much info on porting to V2. 
There's lots of stuff on the wiki but not much with starting a low
level port.

The only real documentation is the V2 code.  If you want I can send
you my 440bx patch for V2 which only has the raw framework in it.  If
you model your port after whats done in that patch you will get a V2
framework that will boot and display serial stuff (once you add
support for your serial ports).  You will then have to do all the RAM
init, etc. but that should be enough to get you started.
  
-- 
Richard A. Smith



From YhLu at tyan.com  Wed Apr  6 21:42:00 2005
From: YhLu at tyan.com (YhLu)
Date: Wed, 6 Apr 2005 12:42:00 -0700 
Subject: [LinuxBIOS] readl and read32
Message-ID: <3174569B9743D511922F00A0C943142309349131@TYANWEB>

Do you think 
read32 arch/i386/include/arch/romcc_io.h
and
readl in arch/i386/include/arch/io.h
should be removed one?

YH



From YhLu at tyan.com  Wed Apr  6 21:49:06 2005
From: YhLu at tyan.com (YhLu)
Date: Wed, 6 Apr 2005 12:49:06 -0700 
Subject: [LinuxBIOS] readl and read32
Message-ID: <3174569B9743D511922F00A0C943142309349132@TYANWEB>

arch/ppc/lib/pci_ppc_conf1_ops.c:       .read32 = ppc_conf1_read_config32,
arch/i386/lib/pci_ops_conf1.c:  .read32 = pci_conf1_read_config32,
arch/i386/lib/pci_ops_conf2.c:  .read32 = pci_conf2_read_config32,
arch/i386/include/arch/romcc_io.h:static inline uint32_t read32(unsigned
long addr)
devices/pci_ops.c:      return ops_pci_bus(pbus)->read32(pbus,
dev->bus->secondary, dev->path.u.pci.devfn, where);
include/device/pci.h:   uint32_t (*read32) (struct bus *pbus, unsigned char
bus, int devfn, int where);

read32 in pci should be changed to pci_read32.... 

> -----Original Message-----
> From: YhLu 
> Sent: Wednesday, April 06, 2005 12:42 PM
> To: ebiederman at lnxi.com
> Cc: linuxbios at openbios.org
> Subject: [LinuxBIOS] readl and read32
> 
> Do you think
> read32 arch/i386/include/arch/romcc_io.h and readl in 
> arch/i386/include/arch/io.h should be removed one?
> 
> YH
> 
> _______________________________________________
> LinuxBIOS mailing list
> LinuxBIOS at openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios
> 



From liutao1980 at gmail.com  Thu Apr  7 03:25:40 2005
From: liutao1980 at gmail.com (Tao Liu)
Date: Thu, 7 Apr 2005 09:25:40 +0800
Subject: [LinuxBIOS] irq_tables.c
In-Reply-To: <9B124F08B3EFDA4F8813B05102DC7195035C3914@nh-ex01.bench.com>
References: <9B124F08B3EFDA4F8813B05102DC7195035C3914@nh-ex01.bench.com>
Message-ID: <8eca059b05040618252792b0f1@mail.gmail.com>

That describes how the slot's INTA# INTB# INTC# INTD# pins are routed
to the irq router's PIRQA# PIRQB# PIRQC# PIRQD# pins

for example on my board I have such routings
PCI-X G2A1 OEM-slot 1
       INTA#   -> ->   AMD8111 PIRQA#
       INTB#   -> ->   AMD8111 PIRQB#
       INTC#   -> ->   AMD8111 PIRQC#
       INTD#   -> ->   AMD8111 PIRQD#
       IDSEL   =       AD18
       DEVNUM  =       2
       BUSNUM  =       9

PCI-X G2A2 OEM-slot 2
       INTA#   -> ->   AMD8111 PIRQB#
       INTB#   -> ->   AMD8111 PIRQC#
       INTC#   -> ->   AMD8111 PIRQD#
       INTD#   -> ->   AMD8111 PIRQA#
       IDSEL   =       AD19
       DEVNUM  =       3
       BUSNUM  =       9

so I have following entries in irq_table
               IRQ_SLOT(1,   9,2,0, 1,2,3,4 ),
               IRQ_SLOT(2,   9,3,0, 2,3,4,1 ),

wish that helps

Liu Tao

On Apr 6, 2005 9:47 PM, Peter.VanEchaute at bench.com
<Peter.VanEchaute at bench.com> wrote:
> I am trying to understand the "linka, linkb, linkc, linkd" part of this
> table.  I understand the rest of the table, just not those pieces.  Can
> someone give me a brief explanation?  Thank you for your time.



From ramesh_bios at yahoo.com  Thu Apr  7 09:29:45 2005
From: ramesh_bios at yahoo.com (ramesh bios)
Date: Thu, 7 Apr 2005 00:29:45 -0700 (PDT)
Subject: [LinuxBIOS] Geode in Linuxbios v2
In-Reply-To: 6667
Message-ID: <20050407072945.76571.qmail@web30002.mail.mud.yahoo.com>

> Ramesh, I saw in one of your posts that you had
> mentioned willingness to
> start working on this - if you have started, maybe
> we could work together on
> this?
> 

Definitely, I'd be happy to work with you on the V2
conversion. I haven't done anything on V2 yet. Maybe
I'll go do a V2 build sometime this weekend and get a
feel for how things are laid out there.

Ramesh



		
__________________________________ 
Yahoo! Messenger 
Show us what our next emoticon should look like. Join the fun. 
http://www.advision.webevents.yahoo.com/emoticontest



From hamishl at dplanet.ch  Thu Apr  7 09:40:13 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Thu, 7 Apr 2005 09:40:13 +0200
Subject: [LinuxBIOS] Geode in Linuxbios v2
In-Reply-To: <20050407072945.76571.qmail@web30002.mail.mud.yahoo.com>
Message-ID: <LDEKLCIFJMAFIOPNLICOAEEAEMAA.hamishl@dplanet.ch>

I have started looking at the V2 tree - looks like a bit of a learning
curve!

Richard Smith sent me a raw framework for an Intel 440BX based system from
which to start working, and I am just starting to look at what is required
at the moment. I will keep you posted as to where I get to.

Hamish

-----Original Message-----
From: ramesh bios [mailto:ramesh_bios at yahoo.com]
Sent: Donnerstag, 7. April 2005 09:30
To: Hamish Guthrie; Linuxbios
Subject: Re: [LinuxBIOS] Geode in Linuxbios v2


> Ramesh, I saw in one of your posts that you had
> mentioned willingness to
> start working on this - if you have started, maybe
> we could work together on
> this?
>

Definitely, I'd be happy to work with you on the V2
conversion. I haven't done anything on V2 yet. Maybe
I'll go do a V2 build sometime this weekend and get a
feel for how things are laid out there.

Ramesh




__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.4 - Release Date: 06.04.2005

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.4 - Release Date: 06.04.2005




From twocats at hotmail.com  Fri Apr  8 01:52:56 2005
From: twocats at hotmail.com (Thomas Spear)
Date: Thu, 07 Apr 2005 23:52:56 +0000
Subject: [LinuxBIOS] Mainboard Question
Message-ID: <BAY102-F3C386EA701E45F9DCB1C9A63E0@phx.gbl>



I'm considering a mainboard that has a via C3 cpu and uses a chipset 
comprised of a via CLE266 and a via VT8235; it uses ddr266 and has 
integrated via 2 channel audio, 10/100 lan and UniChrome vga (64M shared 
mamory).  I'm hoping that since this is almost identical to an epia-m board, 
the epia linux bios should work "as is".  Is that correct?  If I got a 
working image from someone, would the odds be good that it would work on 
this board?





From hamishl at dplanet.ch  Sun Apr 10 15:04:22 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Sun, 10 Apr 2005 15:04:22 +0200
Subject: [LinuxBIOS] Questions about romcc
Message-ID: <LDEKLCIFJMAFIOPNLICOEEIBEMAA.hamishl@dplanet.ch>

I am busy doing a port of the Geode code to V2, and am running into
difficulty with the RAM sizing. The issue is not the RAM sizing itself, but
the behaviour of romcc.

I have not looked into romcc in any depth at all, but am guessing that my
problem results either from the declaration of too many variables or nesting
function calls too deeply.

Are there any guidelines as to variable usage and function call nesting, and
will romcc give any warning messages when all the registers are used up?

TIA, Hamish

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From hamishl at dplanet.ch  Sun Apr 10 16:56:04 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Sun, 10 Apr 2005 16:56:04 +0200
Subject: [LinuxBIOS] Speed up flash programming!
Message-ID: <LDEKLCIFJMAFIOPNLICOAEIDEMAA.hamishl@dplanet.ch>

Hi,

Just a small note:

In order to speed up flash programming, I have a small note which may be
useful - when a flash device is erased, all bits are set to 0xff - when
programming the device, any bit which is not a 1 is changed to a 0,
therefore, it is advantageous for speed purposes to have any byte which does
not need to be programmed in the flash device set to 0xff. Currently,
objcopy sets all padding bytes to 0x00 which adds to the programming time
considerably. If you merely insert '--gap-fill 0xff' into all lines in
freebios2/src/config/Config.lb where OBJCOPY appears, the resultant binary
will have 0xff's as the fill character instead of 0x00's.

There are 2 ocurrences of this in the Config.lb file, and the lines should
read:

	action "$(OBJCOPY) --gap-fill 0xff -O binary linuxbios linuxbios.strip"

and

	action "$(OBJCOPY) --gap-fill 0xff -O binary $< $@"

respectively.

Regards

Hamish


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From hamishl at dplanet.ch  Sun Apr 10 17:17:41 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Sun, 10 Apr 2005 17:17:41 +0200
Subject: [LinuxBIOS] Feature request - romcc
Message-ID: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>

Hi,

It would be really nice if the default in code generation from romcc would
generate constant values as hex values, rather than decimal values - I have
been looking at the generated code in auto.inc and $1016 really means
nothing to me as opposed to 0x3f8, which means a lot to me.

I have had a brief look at romcc.c, and it is a HUGE piece of code, and I do
not think that it is of merit for me to look at that code while actually
trying to get something else working!

TIA

Regards

Hamish

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From steve at nexpath.com  Sun Apr 10 22:33:13 2005
From: steve at nexpath.com (Steve Gehlbach)
Date: Sun, 10 Apr 2005 13:33:13 -0700
Subject: [LinuxBIOS] Feature request - romcc
In-Reply-To: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>
Message-ID: <42598D89.7020901@nexpath.com>


>I have had a brief look at romcc.c, and it is a HUGE piece of code, and I do
>not think that it is of merit for me to look at that code while actually
>trying to get something else working!
>  
>
Hamish:

IMHO, romcc is a very remarkable piece of work by Eric Biederman. I 
argued against it at the time as being too ambitious, but of course, 
Eric proved it could be done.  It really should be put up on its own web 
site as a separate project.  There are probably other projects that 
could benefit from a C code compiler that operates purely in registers 
without RAM enabled.

Steve G.




From hamishl at dplanet.ch  Mon Apr 11 08:48:04 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Mon, 11 Apr 2005 08:48:04 +0200
Subject: [LinuxBIOS] Feature request - romcc
In-Reply-To: <42598D89.7020901@nexpath.com>
Message-ID: <LDEKLCIFJMAFIOPNLICOEEJAEMAA.hamishl@dplanet.ch>

Steve:

I concur 100% with your comments, and must congratulate Eric on this
remarkable piece of work. All I am looking for is a few pointers as to
limitations, register usage etc., which I can then probably document for a
small HOWTO on ROMCC so that other newbies to ROMCC do not fall into the
holes I have apparently dug for myself!!! I am also now writing a few bits
of test code to try to figure out how registers are allocated and consumed
for variables/function calls, and thus maybe glean a bit more insight into
the issue.

-----Original Message-----
From: Steve Gehlbach [mailto:steve at nexpath.com]
Sent: Sonntag, 10. April 2005 22:33
To: Hamish Guthrie
Cc: Linuxbios
Subject: Re: [LinuxBIOS] Feature request - romcc



>I have had a brief look at romcc.c, and it is a HUGE piece of code, and I
do
>not think that it is of merit for me to look at that code while actually
>trying to get something else working!
>
>
Hamish:

IMHO, romcc is a very remarkable piece of work by Eric Biederman. I
argued against it at the time as being too ambitious, but of course,
Eric proved it could be done.  It really should be put up on its own web
site as a separate project.  There are probably other projects that
could benefit from a C code compiler that operates purely in registers
without RAM enabled.

Steve G.

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From ebiederman at lnxi.com  Mon Apr 11 17:03:57 2005
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: 11 Apr 2005 09:03:57 -0600
Subject: [LinuxBIOS] Questions about romcc
In-Reply-To: <LDEKLCIFJMAFIOPNLICOEEIBEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOEEIBEMAA.hamishl@dplanet.ch>
Message-ID: <m38y3picde.fsf@maxwell.lnxi.com>

"Hamish Guthrie" <hamishl at dplanet.ch> writes:

> I am busy doing a port of the Geode code to V2, and am running into
> difficulty with the RAM sizing. The issue is not the RAM sizing itself, but
> the behaviour of romcc.
> 
> I have not looked into romcc in any depth at all, but am guessing that my
> problem results either from the declaration of too many variables or nesting
> function calls too deeply.
> 
> Are there any guidelines as to variable usage and function call nesting, and
> will romcc give any warning messages when all the registers are used up?

romcc inlines everything so function nesting depth is not a problem
as there is no return state.

romcc keeps track of which variables have live values and so there is
a limit on the total number of live values (8 unless you have sse or
mmx registers).

Eric



From ebiederman at lnxi.com  Mon Apr 11 17:07:16 2005
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: 11 Apr 2005 09:07:16 -0600
Subject: [LinuxBIOS] Feature request - romcc
In-Reply-To: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>
Message-ID: <m34qedic7v.fsf@maxwell.lnxi.com>

"Hamish Guthrie" <hamishl at dplanet.ch> writes:

> Hi,
> 
> It would be really nice if the default in code generation from romcc would
> generate constant values as hex values, rather than decimal values - I have
> been looking at the generated code in auto.inc and $1016 really means
> nothing to me as opposed to 0x3f8, which means a lot to me.

I can probably be persuaded to implement a switch that changes the default.

For some uses hex values are very nice, for others decimal values are nice,
and there is really no perfect default.

Eric



From ebiederman at lnxi.com  Mon Apr 11 17:09:46 2005
From: ebiederman at lnxi.com (Eric W. Biederman)
Date: 11 Apr 2005 09:09:46 -0600
Subject: [LinuxBIOS] Feature request - romcc
In-Reply-To: <42598D89.7020901@nexpath.com>
References: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>
	<42598D89.7020901@nexpath.com>
Message-ID: <m3zmw5gxj9.fsf@maxwell.lnxi.com>

Steve Gehlbach <steve at nexpath.com> writes:

> >I have had a brief look at romcc.c, and it is a HUGE piece of code, and I do
> >not think that it is of merit for me to look at that code while actually
> >trying to get something else working!
> >
> Hamish:
> 
> IMHO, romcc is a very remarkable piece of work by Eric Biederman. I argued
> against it at the time as being too ambitious, but of course, Eric proved it
> could be done.  It really should be put up on its own web site as a separate
> project.  There are probably other projects that could benefit from a C code
> compiler that operates purely in registers without RAM enabled.

If the interest develops I will be happy to.  But until then that simply
generates more maintenance work, and I'd rather spend my time developing things.

Eric



From hamishl at dplanet.ch  Mon Apr 11 17:20:49 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Mon, 11 Apr 2005 17:20:49 +0200
Subject: [LinuxBIOS] Feature request - romcc
In-Reply-To: <m34qedic7v.fsf@maxwell.lnxi.com>
Message-ID: <LDEKLCIFJMAFIOPNLICOKEJPEMAA.hamishl@dplanet.ch>

Hi Eric,

Thanks for the replies.

I am now starting to get into romcc, and I am really impressed. I have
hacked my copy to give me HEX values for constants, but a switch would be
really great.

Hamish

-----Original Message-----
From: Eric W. Biederman [mailto:eric at lnxi.com]On Behalf Of Eric W. Biederman
Sent: Montag, 11. April 2005 17:07
To: Hamish Guthrie
Cc: Linuxbios
Subject: Re: [LinuxBIOS] Feature request - romcc


"Hamish Guthrie" <hamishl at dplanet.ch> writes:

> Hi,
>
> It would be really nice if the default in code generation from romcc would
> generate constant values as hex values, rather than decimal values - I
have
> been looking at the generated code in auto.inc and $1016 really means
> nothing to me as opposed to 0x3f8, which means a lot to me.

I can probably be persuaded to implement a switch that changes the default.

For some uses hex values are very nice, for others decimal values are nice,
and there is really no perfect default.

Eric
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From hamishl at dplanet.ch  Mon Apr 11 18:03:47 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Mon, 11 Apr 2005 18:03:47 +0200
Subject: [LinuxBIOS] Where should stuff go?
Message-ID: <LDEKLCIFJMAFIOPNLICOKEKBEMAA.hamishl@dplanet.ch>

Hi All, and particularly Eric or Ron,

I am busy doing a port of the Geode code to v2, and similar to most of the
x86 SoC's the GX1 has a lot of locally memory mapped registers to configure
stuff before the chip is useful at all.

These registers have to be configured before RAM initialisation etc., and I
was just wondering if I should do a dirty hack to include the assembler for
this, or if it would be better to recode in C and create a section of code
which resides in the cpu tree as opposed to the mainboard tree which is
executed prior to the auto.c code.

I could of course also chuck this code into the auto.c file, but with auto.c
being in the mainboard section, it is not totally appropriate, because for
most of these SoC's this particular code is the same for all mainboards - it
is really silicon dependant, not mainboard dependant.

If I were to create a new cpu init code section, how exactly would I go
about incorporating this into the build structure so it will execute before
auto.c?

TIA

Hamish
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005




From stepan at openbios.org  Tue Apr 12 13:20:12 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Tue, 12 Apr 2005 13:20:12 +0200
Subject: [LinuxBIOS] Re: post code "fe" means what ?
In-Reply-To: <4325815c05041201462a9b9fec@mail.gmail.com>
References: <4325815c05041121102934858a@mail.gmail.com>
	<20050412070402.GA7144@openbios.org>
	<4325815c05041201462a9b9fec@mail.gmail.com>
Message-ID: <20050412112012.GA15674@openbios.org>

* Huang-Jen Wang <huangjen.wang at gmail.com> [050412 10:46]:
> Hi Stefan,
> The message as follow:
 
> setup_timers: CPU 2005 MHz
> pci_init: Scanning PCI: found 4 devices
> malloc_diag: alloc: 184 bytes (4 blocks), free: 16192 bytes (1 blocks)
> pci_init: 00:18.0 1022:1100 0600 00
> pci_init: 00:18.1 1022:1101 0600 00
> pci_init: 00:18.2 1022:1102 0600 00
> pci_init: 00:18.3 1022:1103 0600 00
> Press <Enter> for default boot, or <Esc> for boot prompt... timed out
> boot: hda2:/boot/vmlinuz root=/dev/hda2 console=tty0 console=ttyS0,115200
> malloc_diag: alloc: 264 bytes (5 blocks), free: 16112 bytes (1 blocks)
> malloc_diag: alloc: 280 bytes (6 blocks), free: 16096 bytes (1 blocks)
> file_open: dev=hda2, path=/boot/vmlinuz
> find_ide_controller: PCI IDE #0 not found
> IDE channel 0 not found
> devopen: failed to open ide

The IDE controller is not detected. Did you set PCI_BRUTE_SCAN = 1
in the filo config file?

Stefan







From rminnich at lanl.gov  Tue Apr 12 17:41:29 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 09:41:29 -0600 (MDT)
Subject: [LinuxBIOS] a great quote
Message-ID: <Pine.LNX.4.58.0504120940370.3607@enigma.lanl.gov>

"You'd need to know the confidential information about the chips to write" 
a free BIOS, Insyde Software's Joseph said. Right now, "that info is only 
available on old hardware that nobody really cares about anymore." 


http://news.com.com/Battle+brews+over+unlocking+PC+secrets/2100-1016_3-5654272.html?tag=nefd.lede


garsh, didn't know that opterons are so obsolete. It's amazing how much 
lack-of-clue there is out there masquerading as knowledge.

ron



From rminnich at lanl.gov  Tue Apr 12 17:44:56 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 09:44:56 -0600 (MDT)
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
Message-ID: <Pine.LNX.4.58.0504120944150.3607@enigma.lanl.gov>



On Wed, 6 Apr 2005, Jun OKAJIMA wrote:

> 
> I understand one of the biggest merits of LinuxBIOS is fast booting.

one of the least important. Actually the least important. It's nice but 
not the reason we wrote it.

> Then, how fast it is? The top page of the Wiki says 3 sec, 
> and "7/25/01: Dual Athlon update " issue says about 2 sec to
> boot a kernel. But this log shows it took 20 sec.
> http://www.carbotpc.com/linux/boottiming.log.txt
> It is too big difference between 2 sec and 20 sec, dont you?

seems like different hardware takes different times.

ron



From rminnich at lanl.gov  Tue Apr 12 17:45:41 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 09:45:41 -0600 (MDT)
Subject: [LinuxBIOS] Boot Time
In-Reply-To: <4252C54A.6010506@irobot.com>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
Message-ID: <Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>



On Tue, 5 Apr 2005, Tyson Sawyer wrote:

> Jun OKAJIMA wrote:
> > Hello.
> > 
> > I understand one of the biggest merits of LinuxBIOS is fast booting.
> > 
> > Then, how fast it is? The top page of the Wiki says 3 sec, and "7/25/01:
> > Dual Athlon update " issue says about 2 sec to
> > boot a kernel. But this log shows it took 20 sec.
> 
> The dominant factors are device driver init/probing and starting services.
> Thus, boot time will be very dependent on system configuration.  For the the 3
> second example I booted to a shell prompt using an initrd image, serial
> console and not much else.  Most real systems are going to take a fair bit
> longer than that.
> 
> The main difference w/linuxbios is that the kernel is loaded and running in
> under 1 second vs. 10-50 seconds for a COTS bios.  How fast things go once the
> kernel is booted is up to you.
> 
> Cheers!
> Ty

FAQ entry anyone?

ron




From rminnich at lanl.gov  Tue Apr 12 17:46:02 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 09:46:02 -0600 (MDT)
Subject: [LinuxBIOS] EPIA-M code still seems to be broken
In-Reply-To: <004101c53a03$b2a0e950$c501a8c0@newflame>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<8a0c367805040509504abea033@mail.gmail.com>
	<004101c53a03$b2a0e950$c501a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0504120945480.3607@enigma.lanl.gov>



On Tue, 5 Apr 2005, Adam Talbot wrote:

> Any one have any luck on fixing the EPIA-M code?

working on it, hang in there. It got pretty badly messed up.

ron



From rminnich at lanl.gov  Tue Apr 12 18:14:12 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 10:14:12 -0600 (MDT)
Subject: [LinuxBIOS] Geode in Linuxbios v2
In-Reply-To: <LDEKLCIFJMAFIOPNLICOEECLEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOEECLEMAA.hamishl@dplanet.ch>
Message-ID: <Pine.LNX.4.58.0504121014040.3607@enigma.lanl.gov>

move to V2. 

V1 is just wasting your time. 

ron




From talbotx at comcast.net  Tue Apr 12 18:22:01 2005
From: talbotx at comcast.net (Adam Talbot)
Date: Tue, 12 Apr 2005 09:22:01 -0700
Subject: [LinuxBIOS] EPIA-M code still seems to be broken
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<8a0c367805040509504abea033@mail.gmail.com>
	<004101c53a03$b2a0e950$c501a8c0@newflame>
	<Pine.LNX.4.58.0504120945480.3607@enigma.lanl.gov>
Message-ID: <003301c53f7b$c22b6bc0$c501a8c0@newflame>

Thank you for the update.
-Adam
----- Original Message ----- 
From: "Ronald G. Minnich" <rminnich at lanl.gov>
To: "Adam Talbot" <talbotx at comcast.net>
Cc: <linuxbios at openbios.org>
Sent: Tuesday, April 12, 2005 8:46 AM
Subject: Re: [LinuxBIOS] EPIA-M code still seems to be broken


> 
> 
> On Tue, 5 Apr 2005, Adam Talbot wrote:
> 
>> Any one have any luck on fixing the EPIA-M code?
> 
> working on it, hang in there. It got pretty badly messed up.
> 
> ron
>




From rminnich at lanl.gov  Tue Apr 12 18:29:20 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 10:29:20 -0600 (MDT)
Subject: [LinuxBIOS] readl and read32
In-Reply-To: <3174569B9743D511922F00A0C943142309349131@TYANWEB>
References: <3174569B9743D511922F00A0C943142309349131@TYANWEB>
Message-ID: <Pine.LNX.4.58.0504121029060.3607@enigma.lanl.gov>



On Wed, 6 Apr 2005, YhLu wrote:

> Do you think 
> read32 arch/i386/include/arch/romcc_io.h
> and
> readl in arch/i386/include/arch/io.h
> should be removed one?
> 

yes, that is going to bite somebody. get rid of readl.

ron



From rminnich at lanl.gov  Tue Apr 12 19:21:53 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 11:21:53 -0600 (MDT)
Subject: [LinuxBIOS] Speed up flash programming!
In-Reply-To: <LDEKLCIFJMAFIOPNLICOAEIDEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOAEIDEMAA.hamishl@dplanet.ch>
Message-ID: <Pine.LNX.4.58.0504121121440.17080@enigma.lanl.gov>

good one! thanks. 

if you want, send me a patch and I can apply.

ron




From rminnich at lanl.gov  Tue Apr 12 19:35:10 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Tue, 12 Apr 2005 11:35:10 -0600 (MDT)
Subject: [LinuxBIOS] Where should stuff go?
In-Reply-To: <LDEKLCIFJMAFIOPNLICOKEKBEMAA.hamishl@dplanet.ch>
References: <LDEKLCIFJMAFIOPNLICOKEKBEMAA.hamishl@dplanet.ch>
Message-ID: <Pine.LNX.4.58.0504121134500.17080@enigma.lanl.gov>

typically you create a .c file for the cpu and include it in auto.c. 

see the amd k8 for examples.

ron




From YhLu at tyan.com  Tue Apr 12 23:21:34 2005
From: YhLu at tyan.com (YhLu)
Date: Tue, 12 Apr 2005 14:21:34 -0700
Subject: [LinuxBIOS] RE: Tyan 2850 video output
Message-ID: <3174569B9743D511922F00A0C94314230934940E@TYANWEB>

did you get the atix.rom using dd?

YH 

> -----Original Message-----
> From: Alex [mailto:alex301 at bezeqint.net] 
> Sent: Tuesday, April 12, 2005 2:59 PM
> To: YhLu
> Cc: linuxbios at clustermatic.org
> Subject: Re: Tyan 2850 video output
> 
> Hi YhLu,
> 
> The binary image you sent me works fine.
> Would you please help me to build LinuxBIOS properly?
> 
> I got the latest development tree (thru tla tool).
> I tried to compile it - it failed with a segment overlap error.
> So I changed the LOG_LEVEL from 8 to 7.
> Also I set the ROM_SIZE to 524288 instead of 475136.
> The last thing I changed - was using the r8169.zelf 
> (etherboot 5.2.6) instead of tg3 one.
> In etherboot I've set direct_vga and keyboard (I also 
> experimented with some other options afterwards)
> 
> I built the linuxbios.rom and burned it onto the chip. It 
> works fine, prints the output to the RS232 console and 
> DOESN'T print anything on the screen.
> 
> (CONFIG_OPTION_ROM_RUN and CONFIG_VGA_CONSOLE are both set to 1)
> 
> Appreciate your help,
> Alex
> 
> PS Should I use FILO support in etherboot? I tried - 
> compilation failed...
> 



From steve at nexpath.com  Wed Apr 13 01:46:16 2005
From: steve at nexpath.com (Steve Gehlbach)
Date: Tue, 12 Apr 2005 16:46:16 -0700
Subject: [LinuxBIOS] VIA releases driver source packages
In-Reply-To: <m3zmw5gxj9.fsf@maxwell.lnxi.com>
References: <LDEKLCIFJMAFIOPNLICOKEIEEMAA.hamishl@dplanet.ch>	<42598D89.7020901@nexpath.com>
	<m3zmw5gxj9.fsf@maxwell.lnxi.com>
Message-ID: <425C5DC8.2060408@nexpath.com>

Is this new? I don't recall Via providing source before, or was it just 
that they were tight with their CLE266 datasheets?  Seems like this 
ought to help with the EPIA.  Source is at www.viaarena.com.

article:
http://lwn.net/Articles/131777/    (sub req'd)

---------------------------------------------
VIA Releases Linux Driver Source Packages 

Freely available driver source code eases the development of tailor-made
applications for the latest Linux distributions

Taipei, Taiwan, 12 April 2005 - VIA Technologies, Inc, a leading innovator
and developer of silicon chip technologies and PC platform solutions, today
announced the extension of its open source support with the release of driver
source codes for specific VIA hardware.

.....
--------------------------------------------------------------

-Steve




From talbotx at comcast.net  Wed Apr 13 08:13:59 2005
From: talbotx at comcast.net (Adam Talbot)
Date: Tue, 12 Apr 2005 23:13:59 -0700
Subject: [LinuxBIOS] Console debug (boot time)
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp><4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
Message-ID: <008601c53fef$fb9d97b0$c501a8c0@newflame>

At what speed do I need to set my console output in linux bios to have it 
not effect boot time of linux bios? 19200, 9600, 4800? This is in standard 
debug, I dont need to see all the information on the screen. Just the key 
points.
-Adam 





From rminnich at lanl.gov  Wed Apr 13 13:45:33 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed, 13 Apr 2005 05:45:33 -0600 (MDT)
Subject: [LinuxBIOS] Re: Console debug (boot time)
In-Reply-To: <008601c53fef$fb9d97b0$c501a8c0@newflame>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp><4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0504130545200.16700@enigma.lanl.gov>

115200 is really good. 9600 noticeably slows it down.

ron




From stepan at openbios.org  Wed Apr 13 16:18:42 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed, 13 Apr 2005 16:18:42 +0200
Subject: [LinuxBIOS] Re: post code "fe" means what ?
In-Reply-To: <4325815c05041305156dae822f@mail.gmail.com>
References: <4325815c05041121102934858a@mail.gmail.com>
	<20050412070402.GA7144@openbios.org>
	<4325815c05041201462a9b9fec@mail.gmail.com>
	<20050412112012.GA15674@openbios.org>
	<4325815c050412203618e6caf4@mail.gmail.com>
	<20050413072739.GA11937@openbios.org>
	<4325815c05041305156dae822f@mail.gmail.com>
Message-ID: <20050413141842.GB28292@openbios.org>

* Huang-Jen Wang <huangjen.wang at gmail.com> [050413 14:15]:
> Thank you for your suggestions, I solved the problems
> But I got new problems now, I want to add VGA functionality
> and I follow the  illustration of Filo_on_the_Arima_Hdama on linuxbios
> main page, the address is here:
> http://wiki.linuxbios.org/index.php/Filo_on_the_Arima_Hdama
> 
> I add "dir /drivers/ati/ragexl" to src/mainboard/arima/hdama/Config.lb
> and add 
> "uses CONFIG_CONSOLE_BTEXT
> option CONFIG_CONSOLE_BTEXT=1"
> to targets/arima/hdama/Config.lb
> 
> When I  Run "buildtarget arima/hdama" , it has error  message: 

Using drivers/ati/ragexl is probably obsolete and replaced by the
vgabios stuff. Go look for "x86emu" in the list archive.

Stefan








From smithbone at gmail.com  Wed Apr 13 17:14:38 2005
From: smithbone at gmail.com (Richard Smith)
Date: Wed, 13 Apr 2005 10:14:38 -0500
Subject: [LinuxBIOS] Console debug (boot time)
In-Reply-To: <008601c53fef$fb9d97b0$c501a8c0@newflame>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
Message-ID: <8a0c36780504130814490f9a6f@mail.gmail.com>

On 4/13/05, Adam Talbot <talbotx at comcast.net> wrote:
> At what speed do I need to set my console output in linux bios to have it
> not effect boot time of linux bios? 19200, 9600, 4800? This is in standard
> debug, I dont need to see all the information on the screen. Just the key
> points.

Well ouptut at any speed at all affects the boot time so as terse of
output as you can stand is the best speed up.  But if you want ot
minimize the impact of the serial delay then set it as fast as
possible.  I run mine at 115200.

9600 baud    = 1.042 mS per byte.
115200 baud = 86 uS per byte.  

So @115200 in 1 second you can dump 11,500 characters vs 960 @ 9600.

-- 
Richard A. Smith



From hansolofalcon at worldnet.att.net  Wed Apr 13 18:42:49 2005
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Wed, 13 Apr 2005 12:42:49 -0400
Subject: [LinuxBIOS] New version of ROM posting app
In-Reply-To: <9e4733910503261136395beac2@mail.gmail.com>
Message-ID: <003801c54047$da82fb80$6401a8c0@who5>

Hello (again) from Gregg C Levine
Jon, is your BK repository offline? Early this morning I needed to
resynch my cloned posting with yours, following your excellent
instructions, (CF. Also on March 26, 2005), and I received a
"Connection timed out error" message.

However, the same thing happens with regards to the clone made
following the instructions from the company, so I'm thinking its my
ISP acting up.

When you get a chance can you create a tar file of your ROM posting
app? If you want to send it to me as an FTP transfer, rather then as
an attachment, I've got an FTP server running here, it can accept
uploads. Write me off list with the details you'll need, and I'll do
the 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

> -----Original Message-----
> From: linuxbios-bounces at openbios.org
[mailto:linuxbios-bounces at openbios.org]
> On Behalf Of Jon Smirl
> Sent: Saturday, March 26, 2005 2:36 PM
> To: Jesse Barnes; Kendall Bennett; Benjamin Herrenschmidt;
> linuxbios at openbios.org
> Subject: [LinuxBIOS] New version of ROM posting app
> 
> I put two new posting apps, a vm86 version and emu86 version out on:
> bk://mesa3d.bkbits.net/rom
> 
> Get klibc from:
> http://kernel.org/pub/linux/libs/klibc/
> 
> Install it somewhere and build it. You need to make a link to the
> kernel source in the top level klibc directory. In this directory
make
> a link from the klibc-xxx directory to klibc.
> 
> Both projects will then build.
> v86bios uses vm86 to run the rom
> post uses emu86
> 
> Use an environment variable to pick the card to be acted on:
> export DEVPATH=/bus/pci/devices/0000:01:00.0
> 
> vm86 is 20K non-debug
> emu86 is 40K non-debug
> 
> Currently they don't use Ben's VGA arbiter which isn't ready yet.
When
> finished these app will automatically be triggered on driver load as
> part of the hotplug process.
> 
> The source to vm86 is from the linux BIOS project where is has been
> worked on to make it substantially smaller. I like to keep everyone
on
> the same source code base if possible.
> 
> Once we get these cleaned up and working I'm hoping to get them
added
> to the klibc project. Once in klibc, klibc is schedule to go into
the
> kernel sooner or later.
> 
> They are both partially working but fail part way through the
posting
> process. I've been playing with them a couple of days and I can't
> figure out why they are failing. They are both failing for different
> reasons. Can anyone help?
> 
> --
> Jon Smirl
> jonsmirl at gmail.com
> 
> _______________________________________________
> LinuxBIOS mailing list
> LinuxBIOS at openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios




From talbotx at comcast.net  Wed Apr 13 19:15:56 2005
From: talbotx at comcast.net (Adam Talbot)
Date: Wed, 13 Apr 2005 10:15:56 -0700
Subject: [LinuxBIOS] Console debug (boot time)
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
	<8a0c36780504130814490f9a6f@mail.gmail.com>
Message-ID: <00a101c5404c$74ddeb00$c501a8c0@newflame>

Hummm.  So if console slows boot time, how about loading the vga bios stuff. 
Does this slow down the overall boot time of linux bios?
-Adam

----- Original Message ----- 
From: "Richard Smith" <smithbone at gmail.com>
To: "Adam Talbot" <talbotx at comcast.net>
Cc: "Ronald G. Minnich" <rminnich at lanl.gov>; <linuxbios at openbios.org>
Sent: Wednesday, April 13, 2005 8:14 AM
Subject: Re: [LinuxBIOS] Console debug (boot time)


On 4/13/05, Adam Talbot <talbotx at comcast.net> wrote:
> At what speed do I need to set my console output in linux bios to have it
> not effect boot time of linux bios? 19200, 9600, 4800? This is in standard
> debug, I dont need to see all the information on the screen. Just the key
> points.

Well ouptut at any speed at all affects the boot time so as terse of
output as you can stand is the best speed up.  But if you want ot
minimize the impact of the serial delay then set it as fast as
possible.  I run mine at 115200.

9600 baud    = 1.042 mS per byte.
115200 baud = 86 uS per byte.

So @115200 in 1 second you can dump 11,500 characters vs 960 @ 9600.

-- 
Richard A. Smith





From jonsmirl at gmail.com  Wed Apr 13 19:47:22 2005
From: jonsmirl at gmail.com (Jon Smirl)
Date: Wed, 13 Apr 2005 13:47:22 -0400
Subject: [LinuxBIOS] New version of ROM posting app
In-Reply-To: <003801c54047$da82fb80$6401a8c0@who5>
References: <9e4733910503261136395beac2@mail.gmail.com>
	<003801c54047$da82fb80$6401a8c0@who5>
Message-ID: <9e4733910504131047346fdfb7@mail.gmail.com>

bkbits.net is offline probably due to the spat between ODSL and
Bitmover.  I think some people are mad and keep taking it down.

I will have to move it to a sourceforge cvs project. I'll post after
it is moved.

On 4/13/05, Gregg C Levine <hansolofalcon at worldnet.att.net> wrote:
> Hello (again) from Gregg C Levine
> Jon, is your BK repository offline? Early this morning I needed to
> resynch my cloned posting with yours, following your excellent
> instructions, (CF. Also on March 26, 2005), and I received a
> "Connection timed out error" message.
> 
> However, the same thing happens with regards to the clone made
> following the instructions from the company, so I'm thinking its my
> ISP acting up.
> 
> When you get a chance can you create a tar file of your ROM posting
> app? If you want to send it to me as an FTP transfer, rather then as
> an attachment, I've got an FTP server running here, it can accept
> uploads. Write me off list with the details you'll need, and I'll do
> the 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
> 
> > -----Original Message-----
> > From: linuxbios-bounces at openbios.org
> [mailto:linuxbios-bounces at openbios.org]
> > On Behalf Of Jon Smirl
> > Sent: Saturday, March 26, 2005 2:36 PM
> > To: Jesse Barnes; Kendall Bennett; Benjamin Herrenschmidt;
> > linuxbios at openbios.org
> > Subject: [LinuxBIOS] New version of ROM posting app
> >
> > I put two new posting apps, a vm86 version and emu86 version out on:
> > bk://mesa3d.bkbits.net/rom
> >
> > Get klibc from:
> > http://kernel.org/pub/linux/libs/klibc/
> >
> > Install it somewhere and build it. You need to make a link to the
> > kernel source in the top level klibc directory. In this directory
> make
> > a link from the klibc-xxx directory to klibc.
> >
> > Both projects will then build.
> > v86bios uses vm86 to run the rom
> > post uses emu86
> >
> > Use an environment variable to pick the card to be acted on:
> > export DEVPATH=/bus/pci/devices/0000:01:00.0
> >
> > vm86 is 20K non-debug
> > emu86 is 40K non-debug
> >
> > Currently they don't use Ben's VGA arbiter which isn't ready yet.
> When
> > finished these app will automatically be triggered on driver load as
> > part of the hotplug process.
> >
> > The source to vm86 is from the linux BIOS project where is has been
> > worked on to make it substantially smaller. I like to keep everyone
> on
> > the same source code base if possible.
> >
> > Once we get these cleaned up and working I'm hoping to get them
> added
> > to the klibc project. Once in klibc, klibc is schedule to go into
> the
> > kernel sooner or later.
> >
> > They are both partially working but fail part way through the
> posting
> > process. I've been playing with them a couple of days and I can't
> > figure out why they are failing. They are both failing for different
> > reasons. Can anyone help?
> >
> > --
> > Jon Smirl
> > jonsmirl at gmail.com
> >
> > _______________________________________________
> > LinuxBIOS mailing list
> > LinuxBIOS at openbios.org
> > http://www.openbios.org/mailman/listinfo/linuxbios
> 
> 


-- 
Jon Smirl
jonsmirl at gmail.com



From smithbone at gmail.com  Wed Apr 13 19:56:15 2005
From: smithbone at gmail.com (Richard Smith)
Date: Wed, 13 Apr 2005 12:56:15 -0500
Subject: [LinuxBIOS] Console debug (boot time)
In-Reply-To: <00a101c5404c$74ddeb00$c501a8c0@newflame>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
	<8a0c36780504130814490f9a6f@mail.gmail.com>
	<00a101c5404c$74ddeb00$c501a8c0@newflame>
Message-ID: <8a0c367805041310562c29a0b9@mail.gmail.com>

On 4/13/05, Adam Talbot <talbotx at comcast.net> wrote:
> Hummm.  So if console slows boot time, how about loading the vga bios stuff.
> Does this slow down the overall boot time of linux bios?
> -Adam

Yep.  Its got run the factory vgabios which has a lot of delays in it
and writeing to video memory is slow in general although no where near
as slow as writeing to the serial port.

-- 
Richard A. Smith



From talbotx at comcast.net  Wed Apr 13 21:35:45 2005
From: talbotx at comcast.net (Adam Talbot)
Date: Wed, 13 Apr 2005 12:35:45 -0700
Subject: [LinuxBIOS] Console debug (boot time)
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
	<8a0c36780504130814490f9a6f@mail.gmail.com>
	<00a101c5404c$74ddeb00$c501a8c0@newflame>
	<8a0c367805041310562c29a0b9@mail.gmail.com>
Message-ID: <00b001c5405f$fd27ec50$c501a8c0@newflame>

Cool, all good things to know.  I will post all this information, and all 
then numbers I can get under the FAQ, when we get a running version of the 
EPIA-M code.
Thx
-Adam
----- Original Message ----- 
From: "Richard Smith" <smithbone at gmail.com>
To: "Adam Talbot" <talbotx at comcast.net>
Cc: <linuxbios at openbios.org>
Sent: Wednesday, April 13, 2005 10:56 AM
Subject: Re: [LinuxBIOS] Console debug (boot time)


On 4/13/05, Adam Talbot <talbotx at comcast.net> wrote:
> Hummm.  So if console slows boot time, how about loading the vga bios 
> stuff.
> Does this slow down the overall boot time of linux bios?
> -Adam

Yep.  Its got run the factory vgabios which has a lot of delays in it
and writeing to video memory is slow in general although no where near
as slow as writeing to the serial port.

-- 
Richard A. Smith





From rminnich at lanl.gov  Thu Apr 14 01:11:17 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed, 13 Apr 2005 17:11:17 -0600 (MDT)
Subject: [LinuxBIOS] Console debug (boot time)
In-Reply-To: <00a101c5404c$74ddeb00$c501a8c0@newflame>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
	<8a0c36780504130814490f9a6f@mail.gmail.com>
	<00a101c5404c$74ddeb00$c501a8c0@newflame>
Message-ID: <Pine.LNX.4.58.0504131711030.17896@enigma.lanl.gov>



On Wed, 13 Apr 2005, Adam Talbot wrote:

> Hummm.  So if console slows boot time, how about loading the vga bios stuff.
> Does this slow down the overall boot time of linux bios?

not from what I have seen. It's fast. 

ron



From rminnich at lanl.gov  Thu Apr 14 01:18:02 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Wed, 13 Apr 2005 17:18:02 -0600 (MDT)
Subject: [LinuxBIOS] Console debug (boot time)
In-Reply-To: <8a0c367805041310562c29a0b9@mail.gmail.com>
References: <200504051631.AA00064@bbb-jz5c7z9hn9y.digitalinfra.co.jp>
	<4252C54A.6010506@irobot.com>
	<Pine.LNX.4.58.0504120945330.3607@enigma.lanl.gov>
	<008601c53fef$fb9d97b0$c501a8c0@newflame>
	<8a0c36780504130814490f9a6f@mail.gmail.com>
	<00a101c5404c$74ddeb00$c501a8c0@newflame>
	<8a0c367805041310562c29a0b9@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0504131717330.17896@enigma.lanl.gov>



On Wed, 13 Apr 2005, Richard Smith wrote:

> Yep.  Its got run the factory vgabios which has a lot of delays in it
> and writeing to video memory is slow in general although no where near
> as slow as writeing to the serial port.

just watching it run, the video startup *seems* fast. Once video is 
running, it's way faster than serial.

ron



From hansolofalcon at worldnet.att.net  Thu Apr 14 22:39:04 2005
From: hansolofalcon at worldnet.att.net (Gregg C Levine)
Date: Thu, 14 Apr 2005 16:39:04 -0400
Subject: [LinuxBIOS] New version of ROM posting app
In-Reply-To: <9e4733910504131047346fdfb7@mail.gmail.com>
Message-ID: <000d01c54132$10010640$6401a8c0@who5>

Hello from Gregg C Levine
Jon, this time the command worked. I was able to have my BitKeeper
client clone your applications to my local directory. I was even able
to build them correctly.

Which was the purpose of my original message. For some reason
yesterday, I was not able to build them correctly, and decided to
repeat the processes. 

I strongly suggest you should copy the contents to an CVS server
someplace, especially since we don't know when the next outage is
planned for bkbits.net, it could be later today, or tomorrow, or not
at all.
-------------------
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-bounces at openbios.org
[mailto:linuxbios-bounces at openbios.org]
> On Behalf Of Jon Smirl
> Sent: Wednesday, April 13, 2005 1:47 PM
> To: Gregg C Levine
> Cc: linuxbios at openbios.org
> Subject: Re: [LinuxBIOS] New version of ROM posting app
> 
> bkbits.net is offline probably due to the spat between ODSL and
> Bitmover.  I think some people are mad and keep taking it down.
> 
> I will have to move it to a sourceforge cvs project. I'll post after
> it is moved.
> 
> On 4/13/05, Gregg C Levine <hansolofalcon at worldnet.att.net> wrote:
> > Hello (again) from Gregg C Levine
> > Jon, is your BK repository offline? Early this morning I needed to
> > resynch my cloned posting with yours, following your excellent
> > instructions, (CF. Also on March 26, 2005), and I received a
> > "Connection timed out error" message.
> >
> > However, the same thing happens with regards to the clone made
> > following the instructions from the company, so I'm thinking its
my
> > ISP acting up.
> >
> > When you get a chance can you create a tar file of your ROM
posting
> > app? If you want to send it to me as an FTP transfer, rather then
as
> > an attachment, I've got an FTP server running here, it can accept
> > uploads. Write me off list with the details you'll need, and I'll
do
> > the 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
> >
> > > -----Original Message-----
> > > From: linuxbios-bounces at openbios.org
> > [mailto:linuxbios-bounces at openbios.org]
> > > On Behalf Of Jon Smirl
> > > Sent: Saturday, March 26, 2005 2:36 PM
> > > To: Jesse Barnes; Kendall Bennett; Benjamin Herrenschmidt;
> > > linuxbios at openbios.org
> > > Subject: [LinuxBIOS] New version of ROM posting app
> > >
> > > I put two new posting apps, a vm86 version and emu86 version out
on:
> > > bk://mesa3d.bkbits.net/rom
> > >
> > > Get klibc from:
> > > http://kernel.org/pub/linux/libs/klibc/
> > >
> > > Install it somewhere and build it. You need to make a link to
the
> > > kernel source in the top level klibc directory. In this
directory
> > make
> > > a link from the klibc-xxx directory to klibc.
> > >
> > > Both projects will then build.
> > > v86bios uses vm86 to run the rom
> > > post uses emu86
> > >
> > > Use an environment variable to pick the card to be acted on:
> > > export DEVPATH=/bus/pci/devices/0000:01:00.0
> > >
> > > vm86 is 20K non-debug
> > > emu86 is 40K non-debug
> > >
> > > Currently they don't use Ben's VGA arbiter which isn't ready
yet.
> > When
> > > finished these app will automatically be triggered on driver
load as
> > > part of the hotplug process.
> > >
> > > The source to vm86 is from the linux BIOS project where is has
been
> > > worked on to make it substantially smaller. I like to keep
everyone
> > on
> > > the same source code base if possible.
> > >
> > > Once we get these cleaned up and working I'm hoping to get them
> > added
> > > to the klibc project. Once in klibc, klibc is schedule to go
into
> > the
> > > kernel sooner or later.
> > >
> > > They are both partially working but fail part way through the
> > posting
> > > process. I've been playing with them a couple of days and I
can't
> > > figure out why they are failing. They are both failing for
different
> > > reasons. Can anyone help?
> > >
> > > --
> > > Jon Smirl
> > > jonsmirl at gmail.com
> > >
> > > _______________________________________________
> > > LinuxBIOS mailing list
> > > LinuxBIOS at openbios.org
> > > http://www.openbios.org/mailman/listinfo/linuxbios
> >
> >
> 
> 
> --
> Jon Smirl
> jonsmirl at gmail.com
> 
> _______________________________________________
> LinuxBIOS mailing list
> LinuxBIOS at openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios




From YhLu at tyan.com  Fri Apr 15 03:58:23 2005
From: YhLu at tyan.com (YhLu)
Date: Thu, 14 Apr 2005 18:58:23 -0700
Subject: [LinuxBIOS] readl and read32
Message-ID: <3174569B9743D511922F00A0C9431423093495E1@TYANWEB>

get rid of read32 or get rid of readl?

YH 

> -----Original Message-----
> From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
> Sent: Tuesday, April 12, 2005 9:29 AM
> To: YhLu
> Cc: ebiederman at lnxi.com; linuxbios at openbios.org
> Subject: Re: [LinuxBIOS] readl and read32
> 
> 
> 
> On Wed, 6 Apr 2005, YhLu wrote:
> 
> > Do you think
> > read32 arch/i386/include/arch/romcc_io.h and readl in 
> > arch/i386/include/arch/io.h should be removed one?
> > 
> 
> yes, that is going to bite somebody. get rid of readl.
> 
> ron
> 



From rminnich at lanl.gov  Fri Apr 15 04:44:55 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu, 14 Apr 2005 20:44:55 -0600 (MDT)
Subject: [LinuxBIOS] readl and read32
In-Reply-To: <3174569B9743D511922F00A0C9431423093495E1@TYANWEB>
References: <3174569B9743D511922F00A0C9431423093495E1@TYANWEB>
Message-ID: <Pine.LNX.4.58.0504142044440.20862@enigma.lanl.gov>



On Thu, 14 Apr 2005, YhLu wrote:

> get rid of read32 or get rid of readl?

I would think get rid of readl. 

ron



From YhLu at tyan.com  Fri Apr 15 05:05:42 2005
From: YhLu at tyan.com (YhLu)
Date: Thu, 14 Apr 2005 20:05:42 -0700
Subject: [LinuxBIOS] readl and read32
Message-ID: <3174569B9743D511922F00A0C9431423093495F8@TYANWEB>

but We got inb, inw, inl....etc.

YH 

> -----Original Message-----
> From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
> Sent: Thursday, April 14, 2005 7:45 PM
> To: YhLu
> Cc: ebiederman at lnxi.com; linuxbios at openbios.org
> Subject: RE: [LinuxBIOS] readl and read32
> 
> 
> 
> On Thu, 14 Apr 2005, YhLu wrote:
> 
> > get rid of read32 or get rid of readl?
> 
> I would think get rid of readl. 
> 
> ron
> 



From YhLu at tyan.com  Fri Apr 15 05:06:56 2005
From: YhLu at tyan.com (YhLu)
Date: Thu, 14 Apr 2005 20:06:56 -0700
Subject: [LinuxBIOS] readl and read32
Message-ID: <3174569B9743D511922F00A0C9431423093495F9@TYANWEB>

Actually, I think read32 is only used by Intel chipset E7501 and
...E7520.... 

YH

> -----Original Message-----
> From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
> Sent: Thursday, April 14, 2005 7:45 PM
> To: YhLu
> Cc: ebiederman at lnxi.com; linuxbios at openbios.org
> Subject: RE: [LinuxBIOS] readl and read32
> 
> 
> 
> On Thu, 14 Apr 2005, YhLu wrote:
> 
> > get rid of read32 or get rid of readl?
> 
> I would think get rid of readl. 
> 
> ron
> 



From rminnich at lanl.gov  Fri Apr 15 04:48:22 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu, 14 Apr 2005 20:48:22 -0600 (MDT)
Subject: [LinuxBIOS] readl and read32
In-Reply-To: <3174569B9743D511922F00A0C9431423093495F8@TYANWEB>
References: <3174569B9743D511922F00A0C9431423093495F8@TYANWEB>
Message-ID: <Pine.LNX.4.58.0504142048110.20862@enigma.lanl.gov>



On Thu, 14 Apr 2005, YhLu wrote:

> but We got inb, inw, inl....etc.

arg. 

I don't know, do what you think best.

ron



From smithbone at gmail.com  Fri Apr 15 14:27:05 2005
From: smithbone at gmail.com (Richard Smith)
Date: Fri, 15 Apr 2005 07:27:05 -0500
Subject: [LinuxBIOS] Re: Is anybody checking in new code in tla?
In-Reply-To: <1113511949.18955.10.camel@em2.my.own.domain>
References: <1113511949.18955.10.camel@em2.my.own.domain>
Message-ID: <8a0c367805041505272c2053e8@mail.gmail.com>

On 4/14/05, Svante Signell <svante.signell at telia.com> wrote:
> Hi,
> 
> Are there any recent checkins made to the arch tree? I'm mostly
> interested in the 440BX v2 development.

There hasn't been any really.  Its still at the get valid data back
from the smbus controller stage.  Are you interested in hacking on
that?
 
None of my patches have been committed.  I can send you what I have
and then commit the stuff this weekend.

Oh and change your linuxbios list address to openbios.org.

-- 
Richard A. Smith



From rminnich at lanl.gov  Sat Apr 16 18:17:32 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sat, 16 Apr 2005 10:17:32 -0600 (MDT)
Subject: [LinuxBIOS] arch hell
Message-ID: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>

I can't get anywhere with arch. No matter what I do I get this:

rminnich at enigma:~/src/bios/freebios2> tla commit
M  src/mainboard/via/epia/Options.lb
arch_commit: unable to acquire revision lock (internal error in 
archive-pfs.c(pfs_lock_revision))
    tree: /home/rminnich/src/bios/freebios2
    revision: 
linuxbios at linuxbios.org--devel/freebios--devel--2.0--patch-14
rminnich at enigma:~/src/bios/freebios2> 


any hints?

ron




From smithbone at gmail.com  Sat Apr 16 22:17:54 2005
From: smithbone at gmail.com (Richard Smith)
Date: Sat, 16 Apr 2005 15:17:54 -0500
Subject: [LinuxBIOS] arch hell
In-Reply-To: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
References: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
Message-ID: <8a0c3678050416131764591095@mail.gmail.com>

On 4/16/05, Ronald G. Minnich <rminnich at lanl.gov> wrote:

> I can't get anywhere with arch. No matter what I do I get this:
 
I'm also having some trouble.

I'm trying to checkout the tree so I can add in my 440bx mods and I get 

gpg: Can't check signature: public key not found

And then

INVALID SIGNATURE ON REVISION
   archive: linuxbios at linuxbios.org--devel
   revision: freebios-devel-2.0--patch-14
   checksum file: checksum


-- 
Richard A. Smith



From stepan at openbios.org  Sun Apr 17 02:56:25 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Sun, 17 Apr 2005 02:56:25 +0200
Subject: [LinuxBIOS] arch hell
In-Reply-To: <8a0c3678050416131764591095@mail.gmail.com>
References: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
	<8a0c3678050416131764591095@mail.gmail.com>
Message-ID: <20050417005625.GC23668@openbios.org>

* Richard Smith <smithbone at gmail.com> [050416 22:17]:
> On 4/16/05, Ronald G. Minnich <rminnich at lanl.gov> wrote:
> 
> > I can't get anywhere with arch. No matter what I do I get this:
>  
> I'm also having some trouble.
> 
> I'm trying to checkout the tree so I can add in my 440bx mods and I get 
> 
> gpg: Can't check signature: public key not found
> 
> And then
> 
> INVALID SIGNATURE ON REVISION
>    archive: linuxbios at linuxbios.org--devel
>    revision: freebios-devel-2.0--patch-14
>    checksum file: checksum
> 
 
Go reimport the gpg keys. Ron's key was missing in the key list.

http://wiki.linuxbios.org/index.php/Download_freebios_v2#Preparation





From rminnich at lanl.gov  Sun Apr 17 19:01:10 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Sun, 17 Apr 2005 11:01:10 -0600 (MDT)
Subject: [LinuxBIOS] arch hell
In-Reply-To: <8a0c3678050416131764591095@mail.gmail.com>
References: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
	<8a0c3678050416131764591095@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0504171100510.16379@enigma.lanl.gov>



On Sat, 16 Apr 2005, Richard Smith wrote:

> I'm also having some trouble.
> 
> I'm trying to checkout the tree so I can add in my 440bx mods and I get 
> 
> gpg: Can't check signature: public key not found
> 
> And then
> 
> INVALID SIGNATURE ON REVISION
>    archive: linuxbios at linuxbios.org--devel
>    revision: freebios-devel-2.0--patch-14
>    checksum file: checksum

sigh. that's my revision!

any idea what went wrong, anyone?

ron



From stepan at openbios.org  Sun Apr 17 19:25:05 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Sun, 17 Apr 2005 19:25:05 +0200
Subject: [LinuxBIOS] arch hell
In-Reply-To: <Pine.LNX.4.58.0504171100510.16379@enigma.lanl.gov>
References: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
	<8a0c3678050416131764591095@mail.gmail.com>
	<Pine.LNX.4.58.0504171100510.16379@enigma.lanl.gov>
Message-ID: <20050417172504.GA8470@openbios.org>

* Ronald G. Minnich <rminnich at lanl.gov> [050417 19:01]:
> > INVALID SIGNATURE ON REVISION
> >    archive: linuxbios at linuxbios.org--devel
> >    revision: freebios-devel-2.0--patch-14
> >    checksum file: checksum
> 
> sigh. that's my revision!
> 
> any idea what went wrong, anyone?
 
If you enable signature checking, you need to have the most recent key
file imported. It basically was a race condition, Richard didn't have
your new gpg key imported yet.

Stefan
 




From smithbone at gmail.com  Mon Apr 18 01:59:53 2005
From: smithbone at gmail.com (Richard Smith)
Date: Sun, 17 Apr 2005 23:59:53 +0000
Subject: [LinuxBIOS] arch hell
In-Reply-To: <20050417172504.GA8470@openbios.org>
References: <Pine.LNX.4.58.0504161015530.25437@enigma.lanl.gov>
	<8a0c3678050416131764591095@mail.gmail.com>
	<Pine.LNX.4.58.0504171100510.16379@enigma.lanl.gov>
	<20050417172504.GA8470@openbios.org>
Message-ID: <8a0c3678050417165944d71f91@mail.gmail.com>

> 
> If you enable signature checking, you need to have the most recent key
> file imported. It basically was a race condition, Richard didn't have
> your new gpg key imported yet.

I suspected that something like this was the case but I could not find
a verbosity option that would tell me what key is was trying to find. 
Adding -vv to gpg added loads of output but none of it was very
helpful.

How did you discover it was Rons key that was missing?

-- 
Richard A. Smith



From hamish at prodigi.ch  Mon Apr 18 18:17:12 2005
From: hamish at prodigi.ch (Hamish Guthrie)
Date: Mon, 18 Apr 2005 18:17:12 +0200
Subject: [LinuxBIOS] Problem with elfboot
Message-ID: <LDEKLCIFJMAFIOPNLICOCEFIENAA.hamish@prodigi.ch>

I am having a stupid problem trying to get etherboot (or anything else for
that matter) to boot using elfboot.

I am testing this with LinuxBIOS V1 because I have no mainboards at the
moment supported by V2, and the port I am doing currently is taking its'
time!

Once my LinuxBIOS has configured everything, the last bit of serial output
is:

Wrote linuxbios table at: 00000500 - 00000670  checksum 320f

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

ROMBase = 0x464c457f
null

The null message appears to be coming from the stream->init() function call
in elfboot.c, and I am having trouble finding out exactly where things are
going wrong.


In my config I have the following:

option USE_GENERIC_ROM=1
option USE_ELF_BOOT=1
option ZKERNEL_START=0xfffc0000

I am guessing that the stream->init() function is attempting to set up a
stream and with the USE_GENERIC_ROM option set, I would imagine that this
should really call the stream init code in rom_fill_inbuf.c, but the debug
statements in that are not getting printed.

I was guessing that maybe elfboot could not find the ROM device, and I have
verified (with the ROMBase = 0x464c457 debug statement above) that I am
indeed able to read valid data from 0xfffc0000. The value printed is the
first 4 bytes of the etherboot elf image I am trying to load, so I
definately have the ROM chip selects enabled.

Any pointers please??

Hamish

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.15 - Release Date: 16.04.2005




From hamish at prodigi.ch  Tue Apr 19 17:27:21 2005
From: hamish at prodigi.ch (Hamish Guthrie)
Date: Tue, 19 Apr 2005 17:27:21 +0200
Subject: [LinuxBIOS] Some success with Geode GX1 and Linuxbios V2
Message-ID: <LDEKLCIFJMAFIOPNLICOIEGKENAA.hamish@prodigi.ch>

Ron,

I thought I would just let you and the list know that I have managed to make
some good progress with porting the Geode GX1/cs5530 code to V2.

At this point I have only tested up to getting a kernel booting - it is not
yet mounting a root filesystem, but that will come soon.

One of the first things I did was to go through the RAM detection code in V1
with a fine toothcomb, and managed to find a number of bugs in that code, so
that now detects every single type of DIMM and SODIMM I have here to test
with correctly, so that can be contributed back to the V1 tree. I then
re-wrote that code in C and managed to get that running under V2 correctly.
The Geode does not have an SMBUS so getting the memory size reported by
LinuxBIOS has required a nasty hack. I have put a hook into the northbridge
code where it probes the pci bus for mc_dev and slotted in some code return
the correct values from the MC_BANK_CFG register of the Geode. This RAM
reporting will also apply to devices like the STPC as well, so there should
probably be a clean way put together to cater for devices without an SMBUS -
I think reporting with a fake smbus routine may be a bit of overkill,
because once memory sizing on the STPC is done correctly, it can be reported
from a single register as well.

I then created an irq_tables.c file from Linux running from the standard
BIOS.

Next step was to get Etherboot running and the elfboot code works like a
charm in V2 - I still cannot figure out what I am doing wrong in the V1
code, but that probably does not matter much any more!

I then set up my DHCP server and a TFTP server and first time round managed
to get the result shown by the serial console output below - I was expecting
the kernel to die because there is in fact no hard drive at /dev/hda3 at the
moment, and for this project I do not need any hard disk, as the filesystems
will all be embedded into on-board NAND flash.

LinuxBIOS-1.1.8.0Normal Tue Apr 19 12:17:40 CEST 2005 starting...
Setting up default parameters for memory
Sizing memory
Probing for DIMM0
    Found DIMM0
    Page Size:       00001000
    Component Banks: 2
    Module Banks:    2
    DIMM size:       02000000
Probing for DIMM1
    Found DIMM1
    Page Size:       00001000
    Component Banks: 4
    Module Banks:    1
    DIMM size:       04000000
MC_BANK_CFG = 14204320
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
LinuxBIOS-1.1.8.0Normal Tue Apr 19 12:17:40 CEST 2005 booting...
Enumerating buses...
Finding PCI configuration type.
PCI: Using configuration type 1
PCI_DOMAIN: 0000 enabled
PCI: pci_scan_bus for bus 0
PCI: 00:00.0 [1078/0001] ops
PCI: 00:00.0 [1078/0001] enabled
PCI: 00:0e.0 [1317/0985] enabled
PCI: 00:12.0 [1078/0100] enabled
PCI: 00:12.1 [1078/0101] enabled
PCI: 00:12.2 [1078/0102] enabled
PCI: 00:12.3 [1078/0103] enabled
PCI: 00:12.4 [1078/0104] enabled
PCI: 00:13.0 [0e11/a0f8] enabled
PCI: pci_scan_bus returning with max=00
done
Allocating resources...
Reading resources...
Done reading resources.
Setting resources...
I would set ram size to 0x18000 Kbytes
PCI: 00:0e.0 10 <- [0x0000001000 - 0x00000010ff] io
PCI: 00:0e.0 14 <- [0x00febe2000 - 0x00febe23ff] mem
PCI: 00:0e.0 30 <- [0x00febc0000 - 0x00febdffff] rom
PCI: 00:12.1 10 <- [0x00febe3000 - 0x00febe30ff] mem
PCI: 00:12.2 20 <- [0x0000001400 - 0x000000147f] io
PCI: 00:12.3 10 <- [0x00febe4000 - 0x00febe407f] mem
PCI: 00:12.4 10 <- [0x00febe0000 - 0x00febe0fff] mem
PCI: 00:13.0 10 <- [0x00febe1000 - 0x00febe1fff] mem
Done setting resources.
Done allocating resources.
Enabling resourcess...
PCI: 00:00.0 cmd <- 147
PCI: 00:0e.0 cmd <- 143
PCI: 00:12.0 cmd <- 14f
PCI: 00:12.1 cmd <- 142
PCI: 00:12.2 cmd <- 141
PCI: 00:12.3 cmd <- 142
PCI: 00:12.4 cmd <- 142
PCI: 00:13.0 cmd <- 142
done.
Initializing devices...
Root Device init
PCI: 00:00.0 init
Devices initialized
Copying IRQ routing tables to 0xf0000...done.
Verifing copy of IRQ routing tables at 0xf0000...failed
Wrote linuxbios table at: 00000500 - 00000690  checksum f8b7

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

    23:stream_init() - rom_stream: 0xfffc0000 - 0xfffcffff
Found ELF candiate at offset 0
Loading Etherboot version: 5.2.6
Dropping non PT_LOAD segment
New segment addr 0x20000 size 0x12740 offset 0xb0 filesize 0x89fc
(cleaned up) New segment addr 0x20000 size 0x12740 offset 0xb0 filesize
0x89fc
Loading Segment: addr: 0x0000000000020000 memsz: 0x0000000000012740 filesz:
0x00000000000089fc
Clearing Segment: addr: 0x00000000000289fc memsz: 0x0000000000009d44
Jumping to boot code at 0x20000
ROM segment 0x0000 length 0x0000 reloc 0x00020000
CPU 238 Mhz
Etherboot 5.2.6 (GPL) http://etherboot.org Tagged ELF for [Tulip]
Relocating _text from: [00020000,00033750) to [05eec8b0,05f00000)
Boot from (N)etwork or (Q)uit?
Probing pci nic...
[centaur-p]
centaur-p: [chip: ADMtek Comet] rev 17 at 1000
centaur-p: Vendor=1317  Device=0985
centaur-p: 00:0C:41:EB:02:45 at ioaddr 1000
Searching for server (DHCP)...
..Me: 192.168.1.153, Server: 192.168.1.201, Gateway 192.168.1.1
Loading 192.168.1.201:vmlinuz.elf ...(ELF)...
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
done
Firmware type: LinuxBIOS
Linux version 2.6.11 (root at monster1) (gcc version 3.3.4 (pre 3.3.5
20040809)) #1 Tue Apr 19 16:09:06 CEST 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 0000000000000700 (reserved)
 BIOS-e820: 0000000000000700 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 00000000000f0400 (reserved)
 BIOS-e820: 0000000000100000 - 0000000006000000 (usable)
96MB LOWMEM available.
DMI not present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 06000000 (gap: 06000000:fa000000)
Built 1 zonelists
Kernel command line: console=ttyS0,38400 root=/dev/hda3
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Detected 233.869 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 94720k/98304k available (1436k kernel code, 3160k reserved, 468k
data, 132k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Working around Cyrix MediaGX virtual DMA bugs.
CPU: Cyrix MediaGXtm MMXtm Enhanced stepping 02
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: Using configuration type 1
ACPI: Subsystem revision 20050211
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
audit: initializing netlink socket (disabled)
audit(3445976884.071:0): initialized
Total HugeTLB memory allocated, 0
Initializing Cryptographic API
PCI: Fixup for MediaGX/Geode Slave Disconnect Boundary (0x41=0x9c)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
i8042: ACPI detection disabled
i8042.c: Can't read CTR while initializing i8042.
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
input: PC Speaker
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

I notice the kernel is not doing a PCI probe - I wonder why?

I obviously have a fair amount more cleanup to do, and to make sure I can
mount filesystems and that the Interrupts do indeed work. There is another
area I may have a look at and that is to attempt to plug in support for the
notorious Geode VSA stuff, which at last AMD have released proper specs for.

Hamish
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.17 - Release Date: 19.04.2005




From stepan at openbios.org  Wed Apr 20 00:27:25 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Wed, 20 Apr 2005 00:27:25 +0200
Subject: [LinuxBIOS] Re: ACPI with LinuxBIOS
In-Reply-To: <9B124F08B3EFDA4F8813B05102DC719503A40C11@nh-ex01.bench.com>
References: <9B124F08B3EFDA4F8813B05102DC719503A40C11@nh-ex01.bench.com>
Message-ID: <20050419222725.GA16712@openbios.org>

* Stephen.Kimball at bench.com <Stephen.Kimball at bench.com> [050420 00:20]:
> I have been trying the get ACPI working on a dual Opteron motherboard. ?I have
> used the island/aruma code as a reference. I have built the dsdt.c and fadt.c
> files from a commercial BIOS with ACPI.? With the commercial BIOS I see this
> message:
> 
> ??? PCI: PCI BIOS revision 2.10 entry at 0xfd73f, last bus=143
> 
> Looking the 2.6.9 kernel module arch/i386/pci/pcbios.c, it seems to want to
> make a PCI BIOS call to the PCI_SERVICE entry point.
 
Not sure if the above message is ACPI related. Can you send the whole
log?

You will likely need to rewrite parts of the dsdt since it contains bus
numbers etc that might be different in LinuxBIOS

> So I?m not sure if you were able to get the island/aruma board to work with
> ACPI?
 
yes. it works fine.

> Does LinuxBIOS need to support PC BIOS calls?

not for ACPI. ACPI was originally designed to provide a callback free 
bios interface. Which is a good thing in theory, LinuxBIOS does similar
with the LinuxBIOS table.

 Stefan



From stuge-linuxbios at cdy.org  Wed Apr 20 01:30:27 2005
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Wed, 20 Apr 2005 01:30:27 +0200
Subject: [LinuxBIOS] Some success with Geode GX1 and Linuxbios V2
In-Reply-To: <LDEKLCIFJMAFIOPNLICOIEGKENAA.hamish@prodigi.ch>
References: <LDEKLCIFJMAFIOPNLICOIEGKENAA.hamish@prodigi.ch>
Message-ID: <20050419233027.GB20393@foo.birdnet.se>

On Tue, Apr 19, 2005 at 05:27:21PM +0200, Hamish Guthrie wrote:
> I thought I would just let you and the list know that I have
> managed to make some good progress with porting the Geode
> GX1/cs5530 code to V2.

I'll say. Great job!


> PCI: Using configuration type 1
[..]
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
[..]
> PCI: Fixup for MediaGX/Geode Slave Disconnect Boundary (0x41=0x9c)
[..]
> VFS: Cannot open root device "hda3" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> I notice the kernel is not doing a PCI probe - I wonder why?

It seems to find the bus according to the (bus 00) message, but no
devices on that bus. I seem to remember the Geode PCI had some
quirks with regard to addressing, but I could be mistaken.


> I obviously have a fair amount more cleanup to do, and to make sure
> I can mount filesystems and that the Interrupts do indeed work.

The kernel output you sent showed no IDE controller being detected,
and hence no hda, but that's just the result of Linux not finding any
PCI devices. Interrupts aren't important just yet either, Linux has
to see the device first.


> There is another area I may have a look at and that is to attempt
> to plug in support for the notorious Geode VSA stuff, which at last
> AMD have released proper specs for.

Nice. It would complete the circle for the Geodes. The VSMs are
binary-only modules though, so I guess they can cause some licensing
problems if linked into LinuxBIOS. :\


//Peter



From Stephen.Kimball at bench.com  Wed Apr 20 15:19:15 2005
From: Stephen.Kimball at bench.com (Stephen.Kimball at bench.com)
Date: Wed, 20 Apr 2005 09:19:15 -0400
Subject: [LinuxBIOS] RE: ACPI with LinuxBIOS
Message-ID: <9B124F08B3EFDA4F8813B05102DC719502905A9C@nh-ex01.bench.com>

Here's our log file.
We set kernel parameters: acpi_dbg_level and acpi_dbg_layer.
The exception in tb_table_override looks like a harmless kernel bug.
The commercial BIOS gets the same error, but works fine.
Any clues on why the handlers are not installed would be appreciated.
Thanks.

Steve
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: acpi.txt
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20050420/bba7a7d0/attachment.txt>

From Stephen.Kimball at bench.com  Wed Apr 20 23:58:46 2005
From: Stephen.Kimball at bench.com (Stephen.Kimball at bench.com)
Date: Wed, 20 Apr 2005 17:58:46 -0400
Subject: [LinuxBIOS] bus numbers
Message-ID: <9B124F08B3EFDA4F8813B05102DC719503A40C14@nh-ex01.bench.com>

Yes.  We found that the nVidia IO4 needs to be on bus 0x80.
Is there an easy way to make this happen with LinuxBIOS?
LinuxBIOS seems to want to put each device on a separate bus starting with zero.

Steve

-----Original Message-----
From: Stefan Reinauer [mailto:stepan at openbios.org] 
Sent: Tuesday, April 19, 2005 6:27 PM
To: Kimball, Stephen
Cc: linuxbios at openbios.org
Subject: Re: ACPI with LinuxBIOS


You will likely need to rewrite parts of the dsdt since it contains bus
numbers etc that might be different in LinuxBIOS




From miernik at ffii.org  Sat Apr 23 22:13:44 2005
From: miernik at ffii.org (Miernik)
Date: Sat, 23 Apr 2005 22:13:44 +0200
Subject: [LinuxBIOS] LinuxBIOS laptop hunt wiki page
Message-ID: <20050423201344.E16.0.NOFFLE@localhost.localdomain.local>

I have started some wikipages about LinuxBIOS laptop hunt.

If anyone would have some time, you could describe what should we look
for in a laptop to find one suitable for LinuxBIOS on
http://wiki.linuxbios.org/index.php/Laptop

and if anything other that I have made colums for in the table here:
http://wiki.linuxbios.org/index.php/Laptop_survey
would be useful, please add a column.

-- 
Miernik             _________________________  xmpp:miernik at amessage.info
___________________/_______________________/      mailto:miernik at ffii.org
Protect Europe from a legal disaster. Petition against software patents
http://www.noepatents.org/index_html?LANG=en




From kfuchs at winternet.com  Mon Apr 25 06:47:12 2005
From: kfuchs at winternet.com (Ken Fuchs)
Date: Sun, 24 Apr 2005 23:47:12 -0500
Subject: [LinuxBIOS] Re: FW: Booting Linux using netboot and HD
References: <92FA936019B4CB4F998F3AFBE8D1C121044DA2@mn-ex1.mn.bench.com>
Message-ID: <200504250447.j3P4lCO02132@ecstasy1.winternet.com>

beneo wrote:

>Does filo support ext3 file system? the introduction say it supports
>ext2, but didn't say anything about ext3. If it doesn't support ext3,
>does it mean I have to re-install Linux to ext2?

No.  The ext3 filesystem is simply ext2 with a journal file and code to
maintain it added.  Linux kernels that lack ext3 support can still mount
ext3 filesystems as ext2, but if done rw, the journal will have to be
rebuilt by possibly forcing a filesystem check prior to mounting as
ext3.  However, filo only needs read access, so it should handle the
ext3 fine as ext2; my primary Linux root filesystem is ext3 and I've
never had a problem with filo related to the root filesystem being ext3.
If /boot is not part of the root filesystem then filo doesn't even
access the root filesystem; it will access the /boot filesystem to get
the kernel and optional initrd files.

>Another question I have is that, if I have LinuxBIOS installed, is
>there a way to install Linux to the HD using Redhad 9.0 distribution
>CDs?

It should work fine under LinuxBIOS.  If not, one can often resort to
the COTS BIOS.

BTW, I strongly suggest that a newer distribution like Fedora Core 3 or
the soon to be released Fedora Core 4 be used instead of Red Hat 9.0.
I've been struggling with Fedora Core 2, until I recently installed
Fedora Core 3.  Fedora Core 3 has much better ACPI debugging code than
Fedora Core 2 for LinuxBIOS ports.  Red Hat 9.0 doesn't even have Linux
2.6 and you really want at least 2.6.9 for good stability, etc.

Sincerely,

Ken Fuchs <kfuchs at winternet.com>



From liutao1980 at gmail.com  Mon Apr 25 10:05:54 2005
From: liutao1980 at gmail.com (Tao Liu)
Date: Mon, 25 Apr 2005 16:05:54 +0800
Subject: [LinuxBIOS] Re: FW: Booting Linux using netboot and HD
In-Reply-To: <200504250447.j3P4lCO02132@ecstasy1.winternet.com>
References: <92FA936019B4CB4F998F3AFBE8D1C121044DA2@mn-ex1.mn.bench.com>
	<200504250447.j3P4lCO02132@ecstasy1.winternet.com>
Message-ID: <8eca059b050425010575e327fa@mail.gmail.com>

On 4/25/05, Ken Fuchs <kfuchs at winternet.com> wrote:
> beneo wrote:
> >Another question I have is that, if I have LinuxBIOS installed, is
> >there a way to install Linux to the HD using Redhad 9.0 distribution
> >CDs?
> 
> It should work fine under LinuxBIOS.  If not, one can often resort to
> the COTS BIOS.
> 

Does any linux distribution CD provide kernels pre-processed
by mkelfimage?

Liu Tao



From stuge-linuxbios at cdy.org  Mon Apr 25 10:30:07 2005
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Mon, 25 Apr 2005 10:30:07 +0200
Subject: [LinuxBIOS] Re: FW: Booting Linux using netboot and HD
In-Reply-To: <8eca059b050425010575e327fa@mail.gmail.com>
References: <92FA936019B4CB4F998F3AFBE8D1C121044DA2@mn-ex1.mn.bench.com>
	<200504250447.j3P4lCO02132@ecstasy1.winternet.com>
	<8eca059b050425010575e327fa@mail.gmail.com>
Message-ID: <20050425083007.GA5833@foo.birdnet.se>

On Mon, Apr 25, 2005 at 04:05:54PM +0800, Tao Liu wrote:
> Does any linux distribution CD provide kernels pre-processed
> by mkelfimage?

Not that I know of, but e.g. FILO will load a normal bzImage without
problems.


//Peter



From hamishl at dplanet.ch  Wed Apr 27 08:20:28 2005
From: hamishl at dplanet.ch (Hamish Guthrie)
Date: Wed, 27 Apr 2005 08:20:28 +0200
Subject: [LinuxBIOS] RE: Geode GX2
In-Reply-To: <Pine.LNX.4.58.0504262204520.16022@enigma.lanl.gov>
Message-ID: <LDEKLCIFJMAFIOPNLICOAEHNEOAA.hamishl@dplanet.ch>

William,

I am currently porting the Geode code to V2 of LinuxBIOS ATM - please send
me the code off list and I will see if there is anything interesting in the
code you have which can go into the new stuff.

Hamish

> -----Original Message-----
> From: linuxbios-admin at clustermatic.org
> [mailto:linuxbios-admin at clustermatic.org]On Behalf Of Ronald G. Minnich
> Sent: Mittwoch, 27. April 2005 06:05
> To: William J Beksi
> Cc: Seb James; LinuxBIOS List
> Subject: Re: Geode GX2
>
>
>
>
> On Wed, 27 Apr 2005, William J Beksi wrote:
>
> > I have the source files (cpu setup, southbridge, northbridge)
> for the NSC
> > Geode GX1/GX2 orginally written by Christer Weinigel. I'm not
> sure, but it may
> > have been in the Linuxbios cvs a long time ago?
>
> it's been in v1 for years.
>
> >
> > I have it working on an Informtech S7 board running an NSC
> Geode GX1 except
> > for the serial console.
> >
> > I believe AMD did not change the architecture after buying out
> the Geode from
> > NSC, so this should work for AMD Geodes.
>
> I guess hamish could use the code, he is the geode guy now.
>
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/linuxbios
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25.04.2005
>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25.04.2005




From stuge-linuxbios at cdy.org  Thu Apr 28 03:13:48 2005
From: stuge-linuxbios at cdy.org (Peter Stuge)
Date: Thu, 28 Apr 2005 03:13:48 +0200
Subject: [LinuxBIOS] Re: DiskOnChip and PLCC32 packages
In-Reply-To: <1114605748.14393.30.camel@circle.hypercube>
References: <LDEKLCIFJMAFIOPNLICOGEIKEOAA.hamish@prodigi.ch>
	<1114605748.14393.30.camel@circle.hypercube>
Message-ID: <20050428011348.GA32063@foo.birdnet.se>

On Wed, Apr 27, 2005 at 01:42:28PM +0100, Seb James wrote:
> Nope :( It has the bios chip (256 KByte/2 MBit PMC PM49FL002T) and
> an Apacer IDE flash DOM plugged onto a 44 pin IDE header.

PMC have an 8 Mbit part as well, it'll probably work too. Then
there's good room for LinuxBIOS and a kernel.


//Peter



From rminnich at lanl.gov  Thu Apr 28 16:38:13 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu, 28 Apr 2005 08:38:13 -0600 (MDT)
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
In-Reply-To: <E3AA489882EF484F9BD56AFD9B4227DE19B05A@INSIDE01>
References: <E3AA489882EF484F9BD56AFD9B4227DE19B05A@INSIDE01>
Message-ID: <Pine.LNX.4.58.0504280837190.20199@enigma.lanl.gov>

be sure to move your questions to linuxbios at openbios.org. 

I don't have root on the box with the mailing list, so turning it off is 
getting messy.


On Thu, 28 Apr 2005, Lasse Jensen wrote:

> Hi
>  
> Why cant I compile that project out of the box?
> Im using the latest snapshot "freebios2-20050305-0000".

because I gave up on it after Intel refused to help. I'm not touching it 
for now.

ron



From lje at kontron.dk  Thu Apr 28 12:27:23 2005
From: lje at kontron.dk (Lasse Jensen)
Date: Thu, 28 Apr 2005 12:27:23 +0200
Subject: [LinuxBIOS] Compiling Digitallogic/adl855pc
Message-ID: <E3AA489882EF484F9BD56AFD9B4227DE19B051@INSIDE01>

Hi
 
Why cant I compile that project out of the box?
Im using the latest snapshot "freebios2-20050305-0000".
 
After I changed the ROM_IMAGE_SIZE=0x10000 to ROM_IMAGE_SIZE=0x20000 it
could almost compile.
When it try's to add the payload (payload /etc/hosts) I gives me a error
saying
 
Linuxbios image is 131087 bytes; only 131072 allowed
 
Where does those extra 15 bytes come from, would be great to get a hint!
 
And btw, I think it would be easier for newbies if all the projects could be
compile from the snapshot... just a thought!
 
Thanks, Lasse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20050428/e04bcb16/attachment.html>

From YhLu at tyan.com  Thu Apr 28 23:30:54 2005
From: YhLu at tyan.com (YhLu)
Date: Thu, 28 Apr 2005 14:30:54 -0700
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
Message-ID: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>

then remove that from the tree.

YH 

> -----Original Message-----
> From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
> Sent: Thursday, April 28, 2005 7:38 AM
> To: Lasse Jensen
> Cc: linuxbios at openbios.org
> Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
> 
> be sure to move your questions to linuxbios at openbios.org. 
> 
> I don't have root on the box with the mailing list, so 
> turning it off is getting messy.
> 
> 
> On Thu, 28 Apr 2005, Lasse Jensen wrote:
> 
> > Hi
> >  
> > Why cant I compile that project out of the box?
> > Im using the latest snapshot "freebios2-20050305-0000".
> 
> because I gave up on it after Intel refused to help. I'm not 
> touching it 
> for now.
> 
> ron
> 
> _______________________________________________
> LinuxBIOS mailing list
> LinuxBIOS at openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios
> 



From rminnich at lanl.gov  Thu Apr 28 23:13:32 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu, 28 Apr 2005 15:13:32 -0600 (MDT)
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
In-Reply-To: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
References: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
Message-ID: <Pine.LNX.4.58.0504281513200.20199@enigma.lanl.gov>



On Thu, 28 Apr 2005, YhLu wrote:

> then remove that from the tree.

well, we can do that, but then nobody else will have a starting point!

ron



From smithbone at gmail.com  Thu Apr 28 23:19:39 2005
From: smithbone at gmail.com (Richard Smith)
Date: Thu, 28 Apr 2005 16:19:39 -0500
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
In-Reply-To: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
References: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
Message-ID: <8a0c367805042814191ca1095d@mail.gmail.com>

On 4/28/05, YhLu <YhLu at tyan.com> wrote:
> then remove that from the tree.
> 

This is the _development_ branch.  Stuff is going to be broken.  We
don't have a stable tree for V2.

What would be better is a properly updated wiki section on the last
known status of each port until such time as a stable tree is
branched.

Also wasn't there some sort of autobuild thing that was setup to check
for compile regressions in the tree?  Is that still active?

-- 
Richard A. Smith



From rminnich at lanl.gov  Thu Apr 28 23:34:49 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Thu, 28 Apr 2005 15:34:49 -0600 (MDT)
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
In-Reply-To: <8a0c367805042814191ca1095d@mail.gmail.com>
References: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
	<8a0c367805042814191ca1095d@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0504281534370.20199@enigma.lanl.gov>



On Thu, 28 Apr 2005, Richard Smith wrote:

> Also wasn't there some sort of autobuild thing that was setup to check
> for compile regressions in the tree?  Is that still active?

stepan had that going, don't know status.

ron



From rminnich at lanl.gov  Fri Apr 29 16:30:44 2005
From: rminnich at lanl.gov (Ronald G. Minnich)
Date: Fri, 29 Apr 2005 08:30:44 -0600 (MDT)
Subject: [LinuxBIOS] RE: Compiling Digitallogic/adl855pc
In-Reply-To: <E3AA489882EF484F9BD56AFD9B4227DE19B108@INSIDE01>
References: <E3AA489882EF484F9BD56AFD9B4227DE19B108@INSIDE01>
Message-ID: <Pine.LNX.4.58.0504290830160.23205@enigma.lanl.gov>

if you don't have yellow or red docs from intel, i.e. you only have what 
is on the intel website, it will be a fun ride, but I hope you can get it 
working.

ron




From lje at kontron.dk  Fri Apr 29 09:28:10 2005
From: lje at kontron.dk (Lasse Jensen)
Date: Fri, 29 Apr 2005 09:28:10 +0200
Subject: [LinuxBIOS] RE: Compiling Digitallogic/adl855pc
Message-ID: <E3AA489882EF484F9BD56AFD9B4227DE19B108@INSIDE01>

Okay, well I have all the docs about the 855GME chipset, so I think I will
try to make a booting version if possible. Im not much into linux, but have
done programming for a long time...

Guess I just have to spend some time on it, please let me know if you are
touching this 855 again ron :)

Thanks, Lasse

-----Original Message-----
From: Ronald G. Minnich [mailto:rminnich at lanl.gov] 
Sent: 28. april 2005 16:38
To: Lasse Jensen
Cc: linuxbios at openbios.org
Subject: Re: Compiling Digitallogic/adl855pc

be sure to move your questions to linuxbios at openbios.org. 

I don't have root on the box with the mailing list, so turning it off is 
getting messy.


On Thu, 28 Apr 2005, Lasse Jensen wrote:

> Hi
>  
> Why cant I compile that project out of the box?
> Im using the latest snapshot "freebios2-20050305-0000".

because I gave up on it after Intel refused to help. I'm not touching it 
for now.

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

From stepan at openbios.org  Fri Apr 29 23:58:37 2005
From: stepan at openbios.org (Stefan Reinauer)
Date: Fri, 29 Apr 2005 23:58:37 +0200
Subject: [LinuxBIOS] Re: Compiling Digitallogic/adl855pc
In-Reply-To: <Pine.LNX.4.58.0504281534370.20199@enigma.lanl.gov>
References: <3174569B9743D511922F00A0C943142309B07A16@TYANWEB>
	<8a0c367805042814191ca1095d@mail.gmail.com>
	<Pine.LNX.4.58.0504281534370.20199@enigma.lanl.gov>
Message-ID: <20050429215837.GB12494@openbios.org>

* Ronald G. Minnich <rminnich at lanl.gov> [050428 23:34]:
> > Also wasn't there some sort of autobuild thing that was setup to check
> > for compile regressions in the tree?  Is that still active?
> 
> stepan had that going, don't know status.

It's still running on the obsolete cvs tree. I'm going to switch it asap




From okajima at digitalinfra.co.jp  Sat Apr 30 10:46:10 2005
From: okajima at digitalinfra.co.jp (Jun OKAJIMA)
Date: Sat, 30 Apr 2005 17:46:10 +0900
Subject: [LinuxBIOS] VIA EPIA build
Message-ID: <200504300846.AA00097@bbb-jz5c7z9hn9y.digitalinfra.co.jp>




Hello Linux BIOS developers.

I have tried to run linuxbios on VIA EPIA-C800 M/B, but failed. I tried
both freebios1 and 2 src trees, but both failed, Sigh. Anyone can help me ?

Source trees:
  freebios-20041019-1200.tar.bz2 
  freebios2-20050305-0000.tar.bz2
     from http://snapshots.linuxbios.org/
in both case, I uses filo/usb from Etherboot 5.4.0 as a payload.


FreeBIOS1:
  I tried with both util/config/epia.conf and epia800.conf, but both failed.
  epia.conf does not run. it shows weird and buggy chars. must be runaway.
  epia800.conf runs. but does not load a payload. just ended up with
  "bad gzip magic numbers" after had execed pc80/ide_* stuff.
  I looked up why epia.conf does not run and found the difference between both
  configurations. it would need these lines to be added, but why?
option BOOT_IDE=1
option IDE_BOOT_DRIVE=0
option ONE_TRACK=63

FreeBIOS2:
  Just did not work. it seems not to work totally, because even VGA sync
  signal does not comes. BTW, how to enable VGA debugging output?
  

                 --- Okajima, Jun. Tokyo, Japan.



From liutao1980 at gmail.com  Sat Apr 30 11:01:49 2005
From: liutao1980 at gmail.com (Tao Liu)
Date: Sat, 30 Apr 2005 17:01:49 +0800
Subject: [LinuxBIOS] Opteron memclk speed/loading fix
Message-ID: <8eca059b050430020113eaa087@mail.gmail.com>

Hello,

the following patch fixes memclk selection on different loadings for opteron,
it is useful if you have more than 4dimms for one opteron cpu. 

Tao

--- freebios2-orig/src/northbridge/amd/amdk8/raminit.c	2005-04-30
16:04:13.000000000 +0800
+++ freebios2/src/northbridge/amd/amdk8/raminit.c	2005-04-30
16:14:59.000000000 +0800
@@ -1227,8 +1227,8 @@
 {
 	/* Compute the minimum cycle time for these dimms */
 	struct spd_set_memclk_result result;
-	unsigned min_cycle_time, min_latency, bios_cycle_time;
-	int i;
+	unsigned min_cycle_time, min_latency, fix_cycle_time;
+	int i, dimm_count, double_rank;
 	uint32_t value;
 
 	static const int latency_indicies[] = { 26, 23, 9 };
@@ -1240,12 +1240,50 @@
 	};
 
 
+	dimm_count = 0;
+	double_rank = 0;
+	for (i = 0; i < DIMM_SOCKETS; i++) {
+		if (dimm_mask & (1 << i)) {
+			dimm_count++;
+			if (spd_read_byte(ctrl->channel0[i], 5) > 1)
+				double_rank++;
+		}
+		if (dimm_mask & (1 << (i + DIMM_SOCKETS))) {
+			dimm_count++;
+			if (spd_read_byte(ctrl->channel1[i], 5) > 1)
+				double_rank++;
+		}
+	}
+
 	value = pci_read_config32(ctrl->f3, NORTHBRIDGE_CAP);
 	min_cycle_time = min_cycle_times[(value >> NBCAP_MEMCLK_SHIFT) &
NBCAP_MEMCLK_MASK];
-	bios_cycle_time = min_cycle_times[
+	/* DDR speed/loading fix */
+	fix_cycle_time = 0x50;
+	if (is_dual_channel(ctrl)) {
+		if (dimm_count > 4) {
+			if (is_cpu_pre_c0())
+				fix_cycle_time = 0x75;
+			else
+				fix_cycle_time = 0x60;
+		} else {
+			if (double_rank > 2)
+				fix_cycle_time = 0x60;
+		}
+	} else {
+		if (dimm_count > 2) {
+			fix_cycle_time = 0x60;
+		} else {
+			if (double_rank > 1)
+				fix_cycle_time = 0x60;
+		}
+	}
+	if (fix_cycle_time > min_cycle_time)
+		min_cycle_time = fix_cycle_time;
+	/* BIOS settings fix */
+	fix_cycle_time = min_cycle_times[
 		read_option(CMOS_VSTART_max_mem_clock, CMOS_VLEN_max_mem_clock, 0)];
-	if (bios_cycle_time > min_cycle_time) {
-		min_cycle_time = bios_cycle_time;
+	if (fix_cycle_time > min_cycle_time) {
+		min_cycle_time = fix_cycle_time;
 	}
 	min_latency = 2;