coreboot June 2005

coreboot@coreboot.org

35 participants
100 discussions

[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

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

28 Jun '05

Hi Anyone know why this happens?! In the old builds I didn't see this error, any hints?! It does this on 4-5 builds... 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 Ps. I know the adl855pc don't work..... /Lasse

3 2

[LinuxBIOS] Re: Linuxbios is always 421bytes larger than allowed
by Steve Magnani 27 Jun '05

27 Jun '05

I ran into something like this not long ago. It might be that _start is too far away from the top of memory. Try editing src/cpu/x86/16bit/reset16.lds and change this: _ROMTOP = (_start >= 0xffff0000) ? 0xfffffff0 : 0xffffffff8; to this: _ROMTOP = (_start >= 0xffff0000) ? 0xfffffff0 : 0xffffffff0; Then re-build. If it builds successfully, that's the problem, and you'll have to juggle your code or reduce it so that _start ends up at 0xFFFF0000 or greater. On an editorial note, it's nice that the build system catches this problem, but I really wish it did it in a way that made it more obvious what the problem is. Steve

4 7

[LinuxBIOS] post code stop in "10"....
by Huang-Jen Wang 27 Jun '05

27 Jun '05

Dear all, I build a rom , but it can't work, I attach a serial console, display nothing, therefore I use post card, it display post code "10", I trace the code , I found it maybe stop in src/cpu/x86/32bit/entry32.inc line 53 I am confused, the part of code , I didn't modified, why it has error? Does it related other files?

1 0

[LinuxBIOS] Linuxbios is always 421bytes larger than allowed
by Tao Liu 26 Jun '05

26 Jun '05

Hello, I updated the code to try amd64's cache_as_ram feature, and during making got the error: ./buildrom linuxbios.strip linuxbios.rom ../../../payloads/eb_8111_filo.zelf 0x17800 0x40000 linuxbios image is 96677 bytes; only 96256 allowed Linuxbios input file larger than allowed size! if I enlarge the ROM_IMAGE_SIZE in Options.lb, the linuxbios image enlarges also, and is always 421bytes larger than ROM_IMAGE_SIZE. Are there some misconfigures for linking the linuxbios image? Regards, Liu Tao

2 1

[LinuxBIOS] more safe stack in ram for cache_as_ram
by YhLu 24 Jun '05

24 Jun '05

just committed some change for cache_as_ram in every cache_as_ram_auto.c __asm__ volatile ( /* set new esp */ /* before _RAMBASE */ "movl %0, %%ebp\n\t" "movl %0, %%esp\n\t" ::"a"( _RAMBASE -4 ) ); ====> __asm__ volatile ( /* set new esp */ /* before _RAMBASE */ "subl %0, %%ebp\n\t" "subl %0, %%esp\n\t" ::"a"( (DCACHE_RAM_BASE + DCACHE_RAM_SIZE)- _RAMBASE ) ); YH

1 0

[LinuxBIOS] RE: E7501 raminit changes
by Steven J. Magnani 24 Jun '05

24 Jun '05

A correction: I'm pretty sure now my RCOMP_MMIO problems were due to "A20 hell", not TOLM. Does anyone know if de-asserting A20M# is enough to cause A20 to behave normally? On our board, after we force A20M# high, the system continues to behave as if A20 is always zero. We're using an embedded board, so there is no keyboard controller in the mix - I/O port 0x92 is enough to toggle A20M#. Some of the Intel documentation mentions an "A20M# interrupt" in passing, but there are no specifics. Is there something else that firmware needs to do after driving A20M# high? Color me confused, Steve -----Original Message----- From: Steven J. Magnani [mailto:steve@digidescorp.com] Sent: Wednesday, June 22, 2005 1:20 PM To: 'linuxbios(a)openbios.org' Subject: E7501 raminit changes Yh Lu, I noticed that you added code to the E7501 raminit to change the mapping between system bus and southbridge stop grants from the default of 1:1 to 2:1 when the file is compiled with CAS_LATENCY defined to CAS_2_0. Is the stop grant change needed only for CL 2.0, or should it be applied to both 2.0 and 2.5? If the former, I'll put it in the function that configures the CAS latency based on SPD info (i.e. make the configuration change programmatic rather than table-driven). If the latter, I'll move the code you added outside the #if block it's currently in. Also, I believe you mentioned earlier (re: s2735 is totally broken) that you were seeing a weird reset in the raminit code. On my platform I was getting an exception during RCOMP configuration (Ram1.00), which I traced to the definition of RCOMP_MMIO as 0x100000. I think because that address lies below the default Top of Low Memory that accesses to that space weren't going to the RCOMP registers. Redefining RCOMP_MMIO as 0x80000000 fixed that problem for me. Regards, Steve Magnani www.digidescorp.com

3 2

[LinuxBIOS] RE: E7501 raminit changes
by Steven J. Magnani 23 Jun '05

23 Jun '05

>Does anyone know if de-asserting A20M# is enough to cause A20 to behave >normally? On our board, after we force A20M# high, the system continues to >behave as if A20 is always zero. We're using an embedded board, so there is no >keyboard controller in the mix - I/O port 0x92 is enough to toggle A20M#. A note for the record. It appears to be a feature of the Xeon that a change in A20M# doesn't take effect until after the processor steps forward at least one instruction. So if you use an emulator to stop the processor and toggle A20M#, you won't see any change in memory behavior until you step through the next instruction. Doh! Steve

1 0

RE: [LinuxBIOS] Merge complete....
by Stephen.Kimball＠bench.com 23 Jun '05

23 Jun '05

OK. Maybe I'm the only one confused but why should the hard_reset called from hardwaremain in C really do a soft reset. Wouldn't it be better to call it soft_reset? Or maybe comment the code if hard_reset needs to do a soft reset? And your sure the cf9 port is enabled? Right? Steve -----Original Message----- From: yhlu [mailto:yinghailu@gmail.com] Sent: Thursday, June 23, 2005 11:30 AM To: Kimball, Stephen Cc: YhLu(a)tyan.com; linuxbios(a)openbios.org Subject: Re: [LinuxBIOS] Merge complete.... stephen, that's right. in auto.c stage, the hard reset is real one it will reset pci space and ht (freq/width). the soft reset will keep the ht (freq/width). the hard_reset is called when ram init exception. in the linuxbios_ram stage totally in c ( from hardwaremain, or the root_reset_bus) is actually a soft reset, it will keep the ht (freq/width) the problem i met is problem ck804 doesn't reconfig ht two times. YH

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot June 2005