#########################################################################
#########################################################################
-ALL += $(obj)u-boot.srec $(obj)u-boot.bin $(obj)System.map $(U_BOOT_NAND)
+ALL += $(obj)u-boot.srec $(obj)u-boot.bin $(obj)System.map $(U_BOOT_NAND) $(U_BOOT_ONENAND)
+ ifeq ($(ARCH),blackfin)
+ ALL += $(obj)u-boot.ldr
+ endif
all: $(ALL)
thus the compiler cannot perform type checks on these assignments.
2. The pointer to the jump table is passed to the application in a
- machine-dependent way. PowerPC, ARM and MIPS architectures use a
- dedicated register to hold the pointer to the 'global_data'
- structure: r2 on PowerPC, r8 on ARM and k0 on MIPS. The x86
- architecture does not use such a register; instead, the pointer to
- the 'global_data' structure is passed as 'argv[-1]' pointer.
+ machine-dependent way. PowerPC, ARM, MIPS and Blackfin architectures
+ use a dedicated register to hold the pointer to the 'global_data'
- structure: r29 on PowerPC, r8 on ARM, k0 on MIPS, and P5 on Blackfin.
- The x86 architecture does not use such a register; instead, the pointer
- to the 'global_data' structure is passed as 'argv[-1]' pointer.
++ structure: r2 on PowerPC, r8 on ARM, k0 on MIPS, and P5 on Blackfin.
++ The x86 architecture does not use such a register; instead, the
++ pointer to the 'global_data' structure is passed as 'argv[-1]'
++ pointer.
The application can access the 'global_data' structure in the same
way as U-Boot does: