coreboot January 2005

coreboot@coreboot.org

43 participants
155 discussions

RE: fallback reset_vector offset
by YhLu 25 Jan '05

25 Jan '05

The problem solved. I switch the auto.c... before reset.inc in MB Config.lb Also add two inc in it mainboardinit arch/i386/lib/jmp_auto_out.inc after auto.c segment mainboardinit arch/i386/lib/jmp_auto.inc in old auto.c position please advise where to put these two inc. jmp_auto_out.inc /* -*- asm -*- */ /* clear boot_complete flag */ xorl %ebp, %ebp jmp __main jmp_auto.inc /* -*- asm -*- */ jmp __fpu_start YH > -----Original Message----- > From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] > Sent: Tuesday, January 25, 2005 12:31 AM > To: YhLu > Cc: Ronald G. Minnich; linuxbios(a)clustermatic.org > Subject: Re: fallback reset_vector offset > > YhLu <YhLu(a)tyan.com> writes: > > > in reset16.lds > > > > _ROMTOP = (_start >= 0xffff0000) ? 0xfffffff0 : 0xffffffff8; > > > > > > 0xffffffff8 ????? > > And from the line above. > /* Trigger an error if I have an unuseable start > address */ That is exactly what happens correct? 0xfffffff8 > does not work does it? > > Show me a less confusing way and I will use it. > > Eric >

2 1

RE: fallback reset_vector offset
by YhLu 25 Jan '05

25 Jan '05

I mean 0xffffffff8 is 36 bit. and the ld will take 0xffffffff. YH > -----Original Message----- > From: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com] > Sent: Tuesday, January 25, 2005 12:31 AM > To: YhLu > Cc: Ronald G. Minnich; linuxbios(a)clustermatic.org > Subject: Re: fallback reset_vector offset > > YhLu <YhLu(a)tyan.com> writes: > > > in reset16.lds > > > > _ROMTOP = (_start >= 0xffff0000) ? 0xfffffff0 : 0xffffffff8; > > > > > > 0xffffffff8 ????? > > And from the line above. > /* Trigger an error if I have an unuseable start > address */ That is exactly what happens correct? 0xfffffff8 > does not work does it? > > Show me a less confusing way and I will use it. > > Eric >

1 0

RE: fallback reset_vector offset
by YhLu 25 Jan '05

25 Jan '05

Thanks. I found the reason. the crt0.s (from reset16.....failover....auto...) is too big. So the _start is across the 0xffff0000. unless move reset16 and entry16 near reset_vector. We have to make crt0.s is in 64K. the linuxbios_ram.rom could cross the 64K limit above the crt0.s YH > -----Original Message----- > From: Ronald G. Minnich [mailto:rminnich@lanl.gov] > Sent: Tuesday, January 25, 2005 7:40 AM > To: YhLu > Cc: linuxbios(a)clustermatic.org > Subject: Re: fallback reset_vector offset > > send me the config file you are using. This is weird. > > ron >

1 0

fallback reset_vector offset
by YhLu 25 Jan '05

25 Jan '05

sometime the linuxbios.strip for fallback reset_vector will have 15 more offset. here I set ROM_IMAGE_SIZE 0x19200, and the linuxbios.strip will be 15 bytes longer. weird? 00191f0: 0000 0000 0000 0000 0000 0000 0000 e900 0019200: eeca fffe 0000 e900 ef18 fffe 0000 0000 YH

3 2

generic_dump_spd memory channel error
by Richard Smith 25 Jan '05

25 Jan '05

dump_spd_registers in generic_dump_spd.c isn't really so generic. It assumes that you have 2 memory channels which fails to build for me. Is there already some method of indicating how many memory channels you have our should I just create a #define option that you set when you need to use this diagnositc. -- Richard A. Smith

2 1

RE: fallback reset_vector offset
by YhLu 24 Jan '05

24 Jan '05

in reset16.lds _ROMTOP = (_start >= 0xffff0000) ? 0xfffffff0 : 0xffffffff8; 0xffffffff8 ?????

2 1

RE: fallback reset_vector offset
by YhLu 24 Jan '05

24 Jan '05

you are right. in linuxbios.map _start become to 0xfffeeecc and ROM_TOP and reset_vector become to 0xfffffff. YH

1 0

Another V2 question
by Richard Smith 24 Jan '05

24 Jan '05

> probably because the cmos checksum is wrong. You need to use cmos_util > (from LNXI ftp site) to set up the cmos with good params and checksum. >the docs I could find. My cmos is now fixed up, and I'm getting in to >my normal image. Hmmmm... Our board dosent have CMOS. Well dosen't have any retainable cmos that is. There isn't a battery hooked up to the southbridge. Guess this means that I'll never come out of fallback? Of course I'm stll a long ways off from that now.... -- Richard A. Smith

4 22

Dependency problem
by Richard Smith 24 Jan '05

24 Jan '05

Something is messed up with my dependencys. After I edit auto.c and do a make in my top level config directory. I get nothing to be done for 'all' after playing with it more I can go into the fallback direcory and delete all the .o's and .inc's and lots of other files but as long as I don't mess with ./fallback/linuxbios.rom it won't rebuild. I looked through the makefile and my INIT-OBJECTS is blank. But if this were really the case I don't see how I would be building a working image. Any ideas on what I should look at? -- Richard A. Smith

1 0

It booted
by Gin 24 Jan '05

24 Jan '05

I just want to tell everyone that my board now booted SMP/non-SMP kernel ok. The problem is the setting of IOAPIC in ICH3. Thanks all for helping. gin

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot January 2005