[oe] [PATCH] remove duplicated code from linux.inc

[Graham Gower]

2009/7/31 Marcin Juszkiewicz <marcin at juszkiewicz.com.pl>:
> Dnia piątek, 31 lipca 2009 o 14:35:19 Graham Gower napisał(a):
>> And for those playing at home, the value to assign to UBOOT_ENTRYSYM

Of course, that should have read UBOOT_ENTRYSYMBOL.

>> for a given arch can be found by grepping
>> linux/arch/${ARCH}/kernel/vmlinux.lds.S for 'ENTRY'.
>
> So according to your post for ARM it will be 'stext':
>
> 15:10 hrw at home:linux-2.6.30$ grep ^ENTRY arch/arm/kernel/vmlinux.lds.S
> ENTRY(stext)
>
> For AT91SAM9263-EK we get:
>
> 15:10 hrw at home:linux-2.6.30$ arm-angstrom-linux-gnueabi-nm vmlinux|grep
> stext
> c0008000 T _stext
> c0008000 T stext
>
> But when I boot this device I have:
>
> ## Booting kernel from Legacy Image at 22200000 ...
>   Image Name:   Angstrom/2.6.30/at91sam9263ek
>   Image Type:   ARM Linux Kernel Image (uncompressed)
>   Data Size:    2074384 Bytes =  2 MB
>   Load Address: 20008000
>   Entry Point:  20008000
>   Verifying Checksum ... OK
>   Loading Kernel Image ... OK
>
> So entry point is different.

Yes, the linux kernel links to a virtual address. If u-boot leaves the
MMU disabled on your platform then you will need to use a physical
address. I haven't checked u-boot to see if this is common or not.

Does the resulting uImage with entry point c0008000 boot for you?

-Graham