mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-13 23:02:59 +00:00
385cbe298a
As of Linux 4.16, a multiplatform AArch64 kernel with our distro config takes 26M. The current space reservation leaves only 17M for the kernel and if it goes over it, the initrd gets overwritten when loading the kernel from the filesystem. A similar problem happens on ARMv7 with the DTBs taken from the downstream Raspberry Pi foundation kernel. I guess they compile them with DT overlay support enabled which grows them just enough. Fix both of these problems by rewriting the memory map, which now allows kernels to be up to 36M and DTBs up to 1M. Also the comment block was kind of obsolete ever since the introduction of AArch64 support and the firmware-loaded DTB doesn't get placed at 0x100 anymore either, so that is fixed as well. Signed-off-by: Tuomas Tynkkynen <tuomas@tuxera.com> Signed-off-by: Alexander Graf <agraf@suse.de>
157 lines
5.3 KiB
C
157 lines
5.3 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
* (C) Copyright 2012-2016 Stephen Warren
|
|
*/
|
|
|
|
#ifndef __CONFIG_H
|
|
#define __CONFIG_H
|
|
|
|
#include <linux/sizes.h>
|
|
#include <asm/arch/timer.h>
|
|
|
|
#if defined(CONFIG_TARGET_RPI_2) || defined(CONFIG_TARGET_RPI_3_32B)
|
|
#define CONFIG_SKIP_LOWLEVEL_INIT
|
|
#endif
|
|
|
|
/* Architecture, CPU, etc.*/
|
|
#define CONFIG_ARCH_CPU_INIT
|
|
|
|
/* Use SoC timer for AArch32, but architected timer for AArch64 */
|
|
#ifndef CONFIG_ARM64
|
|
#define CONFIG_SYS_TIMER_RATE 1000000
|
|
#define CONFIG_SYS_TIMER_COUNTER \
|
|
(&((struct bcm2835_timer_regs *)BCM2835_TIMER_PHYSADDR)->clo)
|
|
#endif
|
|
|
|
/*
|
|
* 2835 is a SKU in a series for which the 2708 is the first or primary SoC,
|
|
* so 2708 has historically been used rather than a dedicated 2835 ID.
|
|
*
|
|
* We don't define a machine type for bcm2709/bcm2836 since the RPi Foundation
|
|
* chose to use someone else's previously registered machine ID (3139, MX51_GGC)
|
|
* rather than obtaining a valid ID:-/
|
|
*
|
|
* For the bcm2837, hopefully a machine type is not needed, since everything
|
|
* is DT.
|
|
*/
|
|
#ifdef CONFIG_BCM2835
|
|
#define CONFIG_MACH_TYPE MACH_TYPE_BCM2708
|
|
#endif
|
|
|
|
/* Memory layout */
|
|
#define CONFIG_NR_DRAM_BANKS 1
|
|
#define CONFIG_SYS_SDRAM_BASE 0x00000000
|
|
#define CONFIG_SYS_UBOOT_BASE CONFIG_SYS_TEXT_BASE
|
|
/*
|
|
* The board really has 256M. However, the VC (VideoCore co-processor) shares
|
|
* the RAM, and uses a configurable portion at the top. We tell U-Boot that a
|
|
* smaller amount of RAM is present in order to avoid stomping on the area
|
|
* the VC uses.
|
|
*/
|
|
#define CONFIG_SYS_SDRAM_SIZE SZ_128M
|
|
#define CONFIG_SYS_INIT_SP_ADDR (CONFIG_SYS_SDRAM_BASE + \
|
|
CONFIG_SYS_SDRAM_SIZE - \
|
|
GENERATED_GBL_DATA_SIZE)
|
|
#define CONFIG_SYS_MALLOC_LEN SZ_4M
|
|
#define CONFIG_SYS_MEMTEST_START 0x00100000
|
|
#define CONFIG_SYS_MEMTEST_END 0x00200000
|
|
#define CONFIG_LOADADDR 0x00200000
|
|
|
|
/* Devices */
|
|
/* GPIO */
|
|
#define CONFIG_BCM2835_GPIO
|
|
/* LCD */
|
|
#define CONFIG_LCD_DT_SIMPLEFB
|
|
#define CONFIG_VIDEO_BCM2835
|
|
|
|
#ifdef CONFIG_CMD_USB
|
|
#define CONFIG_TFTP_TSIZE
|
|
#define CONFIG_MISC_INIT_R
|
|
#endif
|
|
|
|
/* Console configuration */
|
|
#define CONFIG_SYS_CBSIZE 1024
|
|
|
|
/* Environment */
|
|
#define CONFIG_ENV_SIZE SZ_16K
|
|
#define CONFIG_SYS_LOAD_ADDR 0x1000000
|
|
#define CONFIG_PREBOOT "usb start"
|
|
|
|
/* Shell */
|
|
|
|
/* ATAGs support for bootm/bootz */
|
|
#define CONFIG_SETUP_MEMORY_TAGS
|
|
#define CONFIG_CMDLINE_TAG
|
|
#define CONFIG_INITRD_TAG
|
|
|
|
/* Environment */
|
|
#define ENV_DEVICE_SETTINGS \
|
|
"stdin=serial,usbkbd\0" \
|
|
"stdout=serial,vidconsole\0" \
|
|
"stderr=serial,vidconsole\0"
|
|
|
|
/*
|
|
* Memory layout for where various images get loaded by boot scripts:
|
|
*
|
|
* I suspect address 0 is used as the SMP pen on the RPi2, so avoid this.
|
|
*
|
|
* Older versions of the boot firmware place the firmware-loaded DTB at 0x100,
|
|
* newer versions place it in high memory. So prevent U-Boot from doing its own
|
|
* DTB + initrd relocation so that we won't accidentally relocate the initrd
|
|
* over the firmware-loaded DTB and generally try to lay out things starting
|
|
* from the bottom of RAM.
|
|
*
|
|
* kernel_addr_r has different constraints on ARM and Aarch64. For 32-bit ARM,
|
|
* it must be within the first 128M of RAM in order for the kernel's
|
|
* CONFIG_AUTO_ZRELADDR option to work. The kernel itself will be decompressed
|
|
* to 0x8000 but the decompressor clobbers 0x4000-0x8000 as well. The
|
|
* decompressor also likes to relocate itself to right past the end of the
|
|
* decompressed kernel, so in total the sum of the compressed and and
|
|
* decompressed kernel needs to be reserved.
|
|
*
|
|
* For Aarch64, the kernel image is uncompressed and must be loaded at
|
|
* text_offset bytes (specified in the header of the Image) into a 2MB
|
|
* boundary. The 'booti' command relocates the image if necessary. Linux uses
|
|
* a default text_offset of 0x80000. In summary, loading at 0x80000
|
|
* satisfies all these constraints and reserving memory up to 0x02400000
|
|
* permits fairly large (roughly 36M) kernels.
|
|
*
|
|
* scriptaddr and pxefile_addr_r can be pretty much anywhere that doesn't
|
|
* conflict with something else. Reserving 1M for each of them at
|
|
* 0x02400000-0x02500000 and 0x02500000-0x02600000 should be plenty.
|
|
*
|
|
* On ARM, both the DTB and any possible initrd must be loaded such that they
|
|
* fit inside the lowmem mapping in Linux. In practice, this usually means not
|
|
* more than ~700M away from the start of the kernel image but this number can
|
|
* be larger OR smaller depending on e.g. the 'vmalloc=xxxM' command line
|
|
* parameter given to the kernel. So reserving memory from low to high
|
|
* satisfies this constraint again. Reserving 1M at 0x02600000-0x02700000 for
|
|
* the DTB leaves rest of the free RAM to the initrd starting at 0x02700000.
|
|
* Even with the smallest possible CPU-GPU memory split of the CPU getting
|
|
* only 64M, the remaining 25M starting at 0x02700000 should allow quite
|
|
* large initrds before they start colliding with U-Boot.
|
|
*/
|
|
#define ENV_MEM_LAYOUT_SETTINGS \
|
|
"fdt_high=ffffffff\0" \
|
|
"initrd_high=ffffffff\0" \
|
|
"kernel_addr_r=0x00080000\0" \
|
|
"scriptaddr=0x02400000\0" \
|
|
"pxefile_addr_r=0x02500000\0" \
|
|
"fdt_addr_r=0x02600000\0" \
|
|
"ramdisk_addr_r=0x02700000\0"
|
|
|
|
#define BOOT_TARGET_DEVICES(func) \
|
|
func(MMC, mmc, 0) \
|
|
func(USB, usb, 0) \
|
|
func(PXE, pxe, na) \
|
|
func(DHCP, dhcp, na)
|
|
#include <config_distro_bootcmd.h>
|
|
|
|
#define CONFIG_EXTRA_ENV_SETTINGS \
|
|
"dhcpuboot=usb start; dhcp u-boot.uimg; bootm\0" \
|
|
ENV_DEVICE_SETTINGS \
|
|
ENV_MEM_LAYOUT_SETTINGS \
|
|
BOOTENV
|
|
|
|
|
|
#endif
|