diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.ARM-memory-map | 4 | ||||
| -rw-r--r-- | doc/README.COBRA5272 | 8 | ||||
| -rw-r--r-- | doc/README.LED_display | 27 | ||||
| -rw-r--r-- | doc/README.arm-relocation | 12 | ||||
| -rw-r--r-- | doc/README.korat | 6 | ||||
| -rw-r--r-- | doc/README.m68k | 4 | ||||
| -rw-r--r-- | doc/README.phytec.pcm030 | 4 |
7 files changed, 46 insertions, 19 deletions
diff --git a/doc/README.ARM-memory-map b/doc/README.ARM-memory-map index e2c4e16..1b120ac 100644 --- a/doc/README.ARM-memory-map +++ b/doc/README.ARM-memory-map @@ -9,8 +9,8 @@ To: Wolfgang Denk <wd@denx.de> > >How are they (should they be) set in your memory map above? -_armboot_start contains the value of TEXT_BASE (0xA07E0000); it seems -TEXT_BASE and _armboot_start are both used for the same purpose in +_armboot_start contains the value of CONFIG_SYS_TEXT_BASE (0xA07E0000); it seems +CONFIG_SYS_TEXT_BASE and _armboot_start are both used for the same purpose in different parts of the (ARM) code. Furthermore, the startup code (cpu/<arm>/start.S) internally uses another variable (_TEXT_BASE) with the same content as _armboot_start. diff --git a/doc/README.COBRA5272 b/doc/README.COBRA5272 index 2d3f706..ae0f148 100644 --- a/doc/README.COBRA5272 +++ b/doc/README.COBRA5272 @@ -89,9 +89,9 @@ please first check: => u-boot as single bootloader starting from flash - in board/cobra5272/config.mk TEXT_BASE should be + in board/cobra5272/config.mk CONFIG_SYS_TEXT_BASE should be - TEXT_BASE = 0xffe00000 + CONFIG_SYS_TEXT_BASE = 0xffe00000 => linking address for u-boot as single bootloader stored in flash @@ -128,9 +128,9 @@ please modify the settings: => u-boot as RAM version, chainloaded by another bootloader or using bdm cable - in board/cobra5272/config.mk TEXT_BASE should be + in board/cobra5272/config.mk CONFIG_SYS_TEXT_BASE should be - TEXT_BASE = 0x00020000 + CONFIG_SYS_TEXT_BASE = 0x00020000 => target linking address for RAM diff --git a/doc/README.LED_display b/doc/README.LED_display new file mode 100644 index 0000000..521746e --- /dev/null +++ b/doc/README.LED_display @@ -0,0 +1,27 @@ +LED display internal API +======================================= + +This README describes the LED display API. + +The API is defined by the include file include/led-display.h + +The first step in to define CONFIG_CMD_DISPLAY in the board config file. +Then you need to provide the following functions to access LED display: + +void display_set(int cmd); + +This function should control the state of the LED display. Argument is +an ORed combination of the following values: + DISPLAY_CLEAR -- clear the display + DISPLAY_HOME -- set the position to the beginning of display + DISPLAY_MARK -- enable mark (decimal point), if implemented + +int display_putc(char c); + +This function should display it's parameter on the LED display in the +current position. Returns the displayed character on success or -1 in +case of failure. + +With this functions defined 'display' command will display it's +arguments on the LED display (or clear the display if called without +arguments). diff --git a/doc/README.arm-relocation b/doc/README.arm-relocation index b46347b..8d328e0 100644 --- a/doc/README.arm-relocation +++ b/doc/README.arm-relocation @@ -49,7 +49,7 @@ disappear and boards which have to migrated to relocation will disappear too. ----------------------------------------------------------------------------- For boards which boot from nand_spl, it is possible to save one copy -if TEXT_BASE == relocation address! This prevents that uboot code +if CONFIG_SYS_TEXT_BASE == relocation address! This prevents that uboot code is copied again in relocate_code(). example for the tx25 board: @@ -66,7 +66,7 @@ e) there it copy u-boot to CONFIG_SYS_NAND_U_BOOT_DST and f) u-boot code steps through board_init_f() and calculates the relocation address and copy itself to it -If TEXT_BASE == relocation address, the copying of u-boot +If CONFIG_SYS_TEXT_BASE == relocation address, the copying of u-boot in f) could be saved. ----------------------------------------------------------------------------- @@ -76,10 +76,10 @@ TODO - fill in bd_t infos (check) - adapt all boards -- maybe adapt TEXT_BASE (this must be checked from board maintainers) +- maybe adapt CONFIG_SYS_TEXT_BASE (this must be checked from board maintainers) This *must* be done for boards, which boot from NOR flash - on other boards if TEXT_BASE = relocation baseaddr, this saves + on other boards if CONFIG_SYS_TEXT_BASE = relocation baseaddr, this saves one copying from u-boot code. - new function dram_init_banksize() is actual board specific. Maybe @@ -93,13 +93,13 @@ Relocation with NAND_SPL (example for the tx25): and start with code execution on this address. - The First page contains u-boot code from u-boot:nand_spl/nand_boot_fsl_nfc.c - which inits the dram, cpu registers, reloacte itself to TEXT_BASE and loads + which inits the dram, cpu registers, reloacte itself to CONFIG_SYS_TEXT_BASE and loads the "real" u-boot to CONFIG_SYS_NAND_U_BOOT_DST and starts execution @CONFIG_SYS_NAND_U_BOOT_START - This u-boot does no ram int, nor cpu register setup. Just looks where it have to relocate and relocate itself to this address. - If relocate address = TEXT_BASE(not the same, as the TEXT_BASE + If relocate address = CONFIG_SYS_TEXT_BASE(not the same, as the TEXT_BASE from the nand_spl code), no need to copy, just go on with bss clear and jump to board_init_r. diff --git a/doc/README.korat b/doc/README.korat index a753f84..e059f78 100644 --- a/doc/README.korat +++ b/doc/README.korat @@ -36,8 +36,8 @@ sufficient that the upgradable U-Boot can be started by a branch to 0xF7FBFFFC. The build sequence: - make korat_config - make all perm=1 + make korat_perm_config + make all builds the permanent U-Boot by selecting loader file "u-boot.lds" and defining preprocessor symbol "CONFIG_KORAT_PERMANENT". The default build: @@ -45,7 +45,7 @@ preprocessor symbol "CONFIG_KORAT_PERMANENT". The default build: make korat_config make all -creates the upgradable U-Boot but selecting loader file "u-boot-F7FC.lds" and +creates the upgradable U-Boot by selecting loader file "u-boot-F7FC.lds" and leaving preprocessor symbol "CONFIG_KORAT_PERMANENT" undefined. 2008-02-22, Larry Johnson <lrj@acm.org> diff --git a/doc/README.m68k b/doc/README.m68k index a00ab69..3766b33 100644 --- a/doc/README.m68k +++ b/doc/README.m68k @@ -72,7 +72,7 @@ For the preloader, please see http://mailman.uclinux.org/pipermail/uclinux-dev/2003-December/023384.html U-boot is configured to run at 0x20000 at default. This can be configured by -change TEXT_BASE in board/m5282evb/config.mk and CONFIG_SYS_MONITOR_BASE in +change CONFIG_SYS_TEXT_BASE in board/m5282evb/config.mk and CONFIG_SYS_MONITOR_BASE in include/configs/M5282EVB.h. 3.2 BuS EB+MCF-EV123 @@ -96,7 +96,7 @@ CONFIG_MONITOR_IS_IN_RAM must be defined. If it is defined the initial vector table and basic processor initialization will not be compiled in. The start address of u-boot must be adjusted in the boards config header file (CONFIG_SYS_MONITOR_BASE) and Makefile -(TEXT_BASE) to the load address. +(CONFIG_SYS_TEXT_BASE) to the load address. 4.1 MCF5272 specific Options/Settings ------------------------------------- diff --git a/doc/README.phytec.pcm030 b/doc/README.phytec.pcm030 index 29b7637..05faab6 100644 --- a/doc/README.phytec.pcm030 +++ b/doc/README.phytec.pcm030 @@ -5,11 +5,11 @@ pcm030_RAMBOOT_config \ pcm030_LOWBOOT_config: unconfig @ >include/config.h @[ -z "$(findstring LOWBOOT_,$@)" ] || \ - { echo "TEXT_BASE = 0xFF000000" >board/phytec/pcm030/config.tmp ; \ + { echo "CONFIG_SYS_TEXT_BASE = 0xFF000000" >board/phytec/pcm030/config.tmp ; \ echo "... with LOWBOOT configuration" ; \ } @[ -z "$(findstring RAMBOOT_,$@)" ] || \ - { echo "TEXT_BASE = 0x00100000" >board/phycore_mpc5200b_tiny/\ + { echo "CONFIG_SYS_TEXT_BASE = 0x00100000" >board/phycore_mpc5200b_tiny/\ config.tmp ; \ echo "... with RAMBOOT configuration" ; \ echo "... remember to make sure that MBAR is already \ |