[coreboot] [commit] r5330 - in trunk: . src/arch/i386

Arne Georg Gleditsch arne.gleditsch at numascale.com
Fri Apr 9 13:21:07 CEST 2010


Myles Watson <mylesgw at gmail.com> writes:
> On Tue, Mar 30, 2010 at 2:32 PM, repository service <svn at coreboot.org> wrote:
>
>     Author: stepan
>     Date: Tue Mar 30 22:32:01 2010
>     New Revision: 5330
>     URL: https://tracker.coreboot.org/trac/coreboot/changeset/5330
>
>     Log:
>     make crt0s and ldscripts evaluate late, so the chipset_* variables are
>     there at
>     the time they are finally used. This should solve the Problem Myles was
>     seeing
>     earlier today. 
>
> It does.

Hm, this only seems to be effective if CONFIG_BIG_BOOTBLOCK is set.  Not
sure why?  The s2912_fam10 mainboard had TINY_BOOTBLOCK set, and stopped
working when I updated today.  I'm not sure why that is, either, but I
see both the serengeti_fam10 and mahogany_fam10 mainboards have it set
as well.

I made a quick attempt at fixing this, but ran into linker script
problems like:

.../crossgcc/xgcc/bin/../lib/gcc/i386-elf/4.4.2/../../../../i386-elf/bin/ld: section .id loaded at [00000000ffffff61,00000000ffffff7f] overlaps section .rom loaded at [00000000ffff0000,0000000100000cdf]                                                                                     
.../crossgcc/xgcc/bin/../lib/gcc/i386-elf/4.4.2/../../../../i386-elf/bin/ld: build/coreboot: section .id vma 0xffffff61 overlaps previous sections
.../crossgcc/xgcc/bin/../lib/gcc/i386-elf/4.4.2/../../../../i386-elf/bin/ld: build/coreboot: section .romstrap vma 0xffffffa0 overlaps previous sections
.../crossgcc/xgcc/bin/../lib/gcc/i386-elf/4.4.2/../../../../i386-elf/bin/ld: build/coreboot: section .reset vma 0xfffffff0 overlaps previous sections
.../crossgcc/xgcc/bin/../lib/gcc/i386-elf/4.4.2/../../../../i386-elf/bin/ld: build/coreboot: section .text vma 0x100000d00 overlaps previous sections
collect2: ld returned 1 exit status

which I didn't really have the time to pursue.  I'm reverting my local
checkout for now.  If anyone has pointers regarding how to resolve this,
I'd be happy to hear them.

-- 
							Arne.




More information about the coreboot mailing list