Change Armada XP kernel load address to the u-boot's end address

Loading kernel to 0xf00000 has no practical reason.
Starting it from the u-boot's highest possible end address
(2MB counting from 0x0) makes more sense.

Tested by:	kevlo
This commit is contained in:
Zbigniew Bodek
2013-10-28 21:37:45 +00:00
parent 67c3c19d0a
commit d7b0107591
+6 -6
View File
@@ -1,16 +1,16 @@
# $FreeBSD$ # $FreeBSD$
# kernel gets loaded at 0x00f00000 by the loader, but runs at virtual address # kernel gets loaded at 0x00200000 by the loader, but runs at virtual address
# 0xc0f00000. RAM starts at 0. We put the pagetable at a reasonable place # 0xc0200000. RAM starts at 0. We put the pagetable at a reasonable place
# in memory, but may need to bounce it higher if there's a problem with this. # in memory, but may need to bounce it higher if there's a problem with this.
# We could paper over this by loading the kernel at 0xc0000000 virtual, but # We could paper over this by loading the kernel at 0xc0000000 virtual, but
# that leads to other complications, so we'll just reclaim the lower region of # that leads to other complications, so we'll just reclaim the lower region of
# ram after we're loaded. Put the page tables for startup at 1MB. # ram after we're loaded. Put the page tables for startup at 1MB.
makeoptions KERNPHYSADDR=0x00f00000 makeoptions KERNPHYSADDR=0x00200000
makeoptions KERNVIRTADDR=0xc0f00000 makeoptions KERNVIRTADDR=0xc0200000
options KERNPHYSADDR=0x00f00000 options KERNPHYSADDR=0x00200000
options KERNVIRTADDR=0xc0f00000 options KERNVIRTADDR=0xc0200000
options PHYSADDR=0x00000000 options PHYSADDR=0x00000000
options STARTUP_PAGETABLE_ADDR=0x00100000 options STARTUP_PAGETABLE_ADDR=0x00100000