coreboot

coreboot@coreboot.org

39717 discussions

[LinuxBIOS] RE: ECC, A function of Hard ware or BIOS
by Steve Magnani 04 Jul '05

04 Jul '05

> Adam Talbot <talbotx(a)comcast.net> writes: > Is ECC memory support a function of BIOS or hard ware? Both. The memory controller and the DIMMs have to support it, and the BIOS has to configure the memory controller to enable it. Steve Magnani www.digidescorp.com

2 1

[LinuxBIOS] Simple complie question
by Steve Casselman 30 Jun '05

30 Jun '05

I'm adding print_debug statements to tyan/s2891 and now I get some code overlap messages /usr/bin/ld: section .reset [00000000fffffff0 -> 00000000ffffffff] overlaps section .rom [00000000ffff6770 -> 000000010000014f] /usr/bin/ld: section .id [00000000ffffff69 -> 00000000ffffff7f] overlaps section .rom [00000000ffff6770 -> 000000010000014f] /usr/bin/ld: section .romstrap [00000000ffffffa0 -> 00000000ffffffef] overlaps section .rom [00000000ffff6770 -> 000000010000014f] I'm not quite sure where this comes from. I've compiled this many times and it works great. Where (options config) are the setting for this? A document pointer or a quick explaination would be great Thanks Steve

2 1

[LinuxBIOS] Local APIC IDs for dual Xeons
by Steve Magnani 30 Jun '05

30 Jun '05

Hi all, I've reached the point where LB is attempting to start the secondary CPU on my custom board. As near as I can tell, LB thinks the secondary CPU isn't responding. This could be a hardware problem, or a LB issue of some sort. CPU 6 would not start! CPU 6 did not initialize! First thing I wanted to check was that LB is using the right APIC ID in the messages it's sending. But I haven't been able to find a good explanation anywhere of how local APIC IDs are assigned in dual-Xeon systems. All Intel says with any certainty is that the power-up sequence includes setting a unique ID for each LAPIC. There is a format to the IDs (i.e. some bits for logical processor, some for socket, some for APIC cluster), but nothing that says (for instance) "One Xeon chip is assigned LAPIC IDs 0 & 1 and the second is assigned LAPIC IDs 6 & 7". Looking over the s2735 config, and anything I found on the Internet, it seems that this is how dual-Xeon boards work. Does anyone know why? Do the addresses come out like this any time you have a dual-Xeon board, and every time you power it up? Or are there some pins that have to be strapped a certain way to end up with these IDs? (Side note, some Xeons support reset-time config of APIC cluster ID - mine don't). The way I'm interpreting the Intel documentation, it looks like the only way to find out a secondary CPU's LAPIC ID is to start it (via an IPI broadcast?) and have it write it somewhere. Thanks, Steve www.digidescorp.com

2 2

[LinuxBIOS] Re: floating irq_table
by yhlu 30 Jun '05

30 Jun '05

just committed the write_pirq_routing_table for s2882 and s2895. for s2882 also move pci_assign_irq from mptable to irq_table.c other x86 irq_table.c all added unsigned long write_pirq_routing_table(unsigned long addr) { return copy_pirq_routing_table(addr); } and table.c will call write_pirq_routing_table instead of copy_pirq_routing_table. YH On 6/29/05, Ronald G. Minnich <rminnich(a)lanl.gov> wrote: > > > On Wed, 29 Jun 2005, yhlu wrote: > > > 2. create irq_table while creating the mptable... > > this is better. > > ron >

1 0

RE: [LinuxBIOS] mianboard Config.lb question....
by Ken Fuchs 29 Jun '05

29 Jun '05

YH, please explain your comment. Sincerely, Ken Fuchs <kfuchs(a)winternet.com> > -----Original Message----- > From: linuxbios-bounces(a)openbios.org > [mailto:linuxbios-bounces@openbios.org] On Behalf Of YhLu > Sent: Tuesday, June 28, 2005 19:45 > To: Huang-Jen Wang; linuxbios(a)openbios.org > Subject: RE: [LinuxBIOS] mianboard Config.lb question.... > > > ha ha, my coding is done and waiting for HW to debug..... > > YH > > > -----Original Message----- > > From: Huang-Jen Wang [mailto:huangjen.wang@gmail.com] > > Sent: Tuesday, June 28, 2005 5:37 PM > > To: linuxbios(a)openbios.org > > Subject: [LinuxBIOS] mianboard Config.lb question.... > > > > Dear all, > > I am porting a new mainboard, and its chipset are ServerWorks > > HT1000 and HT2000, in HT1000, it looks like its SMBUS is not > > a pci device. > > Because I can find it device number and function number, I > > have a very serious problem, how do I edit the mainboard > > Config.lbfile.Dose anyone has the same situation before....or > > any idea? > > > > Thanks

2 1

RE: [LinuxBIOS] mianboard Config.lb question....
by YhLu 28 Jun '05

28 Jun '05

ha ha, my coding is done and waiting for HW to debug..... YH > -----Original Message----- > From: Huang-Jen Wang [mailto:huangjen.wang@gmail.com] > Sent: Tuesday, June 28, 2005 5:37 PM > To: linuxbios(a)openbios.org > Subject: [LinuxBIOS] mianboard Config.lb question.... > > Dear all, > I am porting a new mainboard, and its chipset are ServerWorks > HT1000 and HT2000, in HT1000, it looks like its SMBUS is not > a pci device. > Because I can find it device number and function number, I > have a very serious problem, how do I edit the mainboard > Config.lbfile.Dose anyone has the same situation before....or > any idea? > > Thanks > > _______________________________________________ > LinuxBIOS mailing list > LinuxBIOS(a)openbios.org > http://www.openbios.org/mailman/listinfo/linuxbios >

1 0

[LinuxBIOS] mianboard Config.lb question....
by Huang-Jen Wang 28 Jun '05

28 Jun '05

Dear all, I am porting a new mainboard, and its chipset are ServerWorks HT1000 and HT2000, in HT1000, it looks like its SMBUS is not a pci device. Because I can find it device number and function number, I have a very serious problem, how do I edit the mainboard Config.lbfile.Dose anyone has the same situation before....or any idea? Thanks

1 0

[LinuxBIOS] Abuild test
by Li-Ta Lo 28 Jun '05

28 Jun '05

Hi, I tried to make as many boards to pass abuild test as possible. Now I have most of them working. The non working boards are in three categories: 1. Known to be broken: technologic/ts5300, via/epia-m 2. Bug in ROMCC: island/aruma, ROMCC complain about something in coherent_ht.c:1543.39: coherent_ht.c:1805.27: auto.c:166.47: 0x88cd720 phi Internal compiler error: Cannot find block dominated by 0x83b8150 3. Bug in Abuild: digitallogic/msm586seg, emulation/qemu-i386, Abuild generates incorrect value (0x-5000) for PAYLOAD_SIZE in Makefile.setting. I can figure out why it generate such a insane thing. 4. Bug in ldscript: tyan/s2880, tyan/s4880, the default ROM_IMAGE_SIZE generated by Abuild is wrong for these boards. The value in target Config.lb is good. 5. CAR WIP: tyan/s2735, YhLu, did you ever get CAR working on this one? make[1]: Entering directory `/tmp/freebios2_test/util/abuild/linuxbios- builds/tyan_s2735/normal' make[1]: *** No rule to make target `/tmp/freebios2_test/src/cpu/intel/car/cache_as_ram.inc', needed by `crt0.s'. Stop. -- Li-Ta Lo <ollie(a)lanl.gov> Los Alamos National Lab

4 4

[LinuxBIOS] driver/lsi ??
by Li-Ta Lo 28 Jun '05

28 Jun '05

YhLu, In s2880 and s4880, you referenced driver/lsi/53c1030, do we actually have that in the public tree? -- Li-Ta Lo <ollie(a)lanl.gov> Los Alamos National Lab

2 1

RE: [LinuxBIOS] print_stack() error?
by Lasse Jensen 28 Jun '05

28 Jun '05

When I do a auto build (./abuild) I get this: Processing mainboard/amd/quartet (i386: ok) ( mainboard/amd/quartet previously ok ) Processing mainboard/amd/serenade (i386: ok) ( mainboard/amd/serenade previously ok ) Processing mainboard/amd/solo (i386: ok) ( mainboard/amd/solo previously ok ) Processing mainboard/arima/hdama (i386: ok) ( mainboard/arima/hdama previously ok ) Processing mainboard/densitron/dpx114 (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "densitron_dpx114/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "densitron_dpx114/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/digitallogic/adl855pc (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "digitallogic_adl855pc/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "digitallogic_adl855pc/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/digitallogic/msm586seg (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "digitallogic_msm586seg/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "digitallogic_msm586seg/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/eaglelion/5bcm (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "eaglelion_5bcm/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "eaglelion_5bcm/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/embeddedplanet/ep405pc (ppc: skipped, we're i386) Processing mainboard/emulation/qemu-i386 (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "emulation_qemu-i386/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "emulation_qemu-i386/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/ibm/e325 (i386: ok) ( mainboard/ibm/e325 previously ok ) Processing mainboard/island/aruma (i386: ok) Creating config file... ok Creating builddir...ok Compiling image ..FAILED! Log excerpt: coherent_ht.c:1543.39: coherent_ht.c:1805.27: auto.c:166.47: 0x9f621f8 phi Internal compiler error: Cannot find block dominated by 0x9dc0678 make[1]: *** [auto.inc] Aborted make[1]: Leaving directory `/root/51/freebios/util/abuild/linuxbios-builds/island_aruma/normal' make: *** [normal/linuxbios.rom] Error 1 Processing mainboard/Iwill/DK8S2 (i386: ok) Creating config file... ok Creating builddir...ok Compiling image ..FAILED! Log excerpt: Unexpected token: ) make[1]: *** [auto.inc] Error 1 make[1]: Leaving directory `/root/51/freebios/util/abuild/linuxbios-builds/Iwill_DK8S2/normal' make: *** [normal/linuxbios.rom] Error 1 Processing mainboard/Iwill/DK8X (i386: ok) Creating config file... ok Creating builddir...ok Compiling image ..FAILED! Log excerpt: Unexpected token: ) make[1]: *** [auto.inc] Error 1 make[1]: Leaving directory `/root/51/freebios/util/abuild/linuxbios-builds/Iwill_DK8X/normal' make: *** [normal/linuxbios.rom] Error 1 Processing mainboard/motorola/sandpoint (ppc: skipped, we're i386) Processing mainboard/motorola/sandpointx3_altimus_mpc7410 (: skipped, we're i386) Processing mainboard/newisys/khepri (i386: ok) Creating config file... ok Creating builddir...ok Compiling image ..FAILED! Log excerpt: Unexpected token: ) make[1]: *** [auto.inc] Error 1 make[1]: Leaving directory `/root/51/freebios/util/abuild/linuxbios-builds/newisys_khepri/normal' make: *** [normal/linuxbios.rom] Error 1 Processing mainboard/technologic/ts5300 (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "technologic_ts5300/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "technologic_ts5300/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/totalimpact/briq (ppc: skipped, we're i386) Processing mainboard/tyan/s2735 (i386: ok) Creating config file... ok Creating builddir...ok Compiling image ..FAILED! Log excerpt: then true; else exit 1; fi; make[1]: Entering directory `/root/51/freebios/util/abuild/linuxbios-builds/tyan_s2735/normal' make[1]: *** No rule to make target `/root/51/freebios/src/cpu/intel/car/cache_as_ram.inc', needed by `crt0.s'. Stop. make[1]: Leaving directory `/root/51/freebios/util/abuild/linuxbios-builds/tyan_s2735/normal' make: *** [normal/linuxbios.rom] Error 1 Processing mainboard/tyan/s2850 (i386: ok) ( mainboard/tyan/s2850 previously ok ) Processing mainboard/tyan/s2875 (i386: ok) ( mainboard/tyan/s2875 previously ok ) Processing mainboard/tyan/s2880 (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: ===> NOTE: Option CONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2 using default value 0 ===> ERROR: Could not open file "/root/51/freebios/src/drivers/lsi/53c1030/Config.lb" Config-tyan_s2880.lb:0 mainboard/tyan/s2880/Config.lb:0 drivers/lsi/53c1030/Config.lb:0 Processing mainboard/tyan/s2881 (i386: ok) ( mainboard/tyan/s2881 previously ok ) Processing mainboard/tyan/s2882 (i386: ok) ( mainboard/tyan/s2882 previously ok ) Processing mainboard/tyan/s2885 (i386: ok) ( mainboard/tyan/s2885 previously ok ) Processing mainboard/tyan/s2891 (i386: ok) ( mainboard/tyan/s2891 previously ok ) Processing mainboard/tyan/s2892 (i386: ok) ( mainboard/tyan/s2892 previously ok ) Processing mainboard/tyan/s2895 (i386: ok) ( mainboard/tyan/s2895 previously ok ) Processing mainboard/tyan/s4880 (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: ===> NOTE: Option CONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2 using default value 0 ===> ERROR: Could not open file "/root/51/freebios/src/drivers/lsi/53c1030/Config.lb" Config-tyan_s4880.lb:0 mainboard/tyan/s4880/Config.lb:0 drivers/lsi/53c1030/Config.lb:0 Processing mainboard/tyan/s4882 (i386: ok) ( mainboard/tyan/s4882 previously ok ) Processing mainboard/via/epia (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "via_epia/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "via_epia/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined Processing mainboard/via/epia-m (i386: ok) Creating config file... ok Creating builddir...FAILED! Log excerpt: File "via_epia-m/config.py", line 1058, in getoption v = getoptionvalue(name, o, image) File "via_epia-m/config.py", line 1033, in getoptionvalue print_stack() NameError: global name 'print_stack' is not defined I could build a lot more images a couple of months ago, around Patch 30 I think... -----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: 28. juni 2005 16:17 To: Jason Schildt Cc: Lasse Jensen; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] print_stack() error? oh, heck, I'm not seeing this except in one case where I had a config error. print_stack is only needed when there is a problem. Will someone please try a build for the digitallogic/msm586seg I want to see if it is in the repo or not. ron

5 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot