i.MX28: Reformat the DRAM memory configuration data

[karo-tx-uboot.git] / README

diff --git a/README b/README
index 89646725a0b884c5b8b10e4262a1682478788a29..b69a3b6f6edc96c58491249d0f6665d07ea31987 100644 (file)
--- a/README
+++ b/README
@@ -644,23 +644,6 @@ The following options need to be configured:
                'Sane' compilers will generate smaller code if
                CONFIG_PRE_CON_BUF_SZ is a power of 2
 
-- Pre-console putc():
-               Prior to the console being initialised, console output is
-               normally silently discarded. This can be annoying if a
-               panic() happens in this time.
-
-               If the CONFIG_PRE_CONSOLE_PUTC option is defined, then
-               U-Boot will call board_pre_console_putc() for each output
-               character in this case, This function should try to output
-               the character if possible, perhaps on all available UARTs
-               (it will need to do this directly, since the console code
-               is not functional yet). Note that if the panic happens
-               early enough, then it is possible that board_init_f()
-               (or even arch_cpu_init() on ARM) has not been called yet.
-               You should init all clocks, GPIOs, etc. that are needed
-               to get the character out. Baud rates will need to default
-               to something sensible.
-
 - Safe printf() functions
                Define CONFIG_SYS_VSNPRINTF to compile in safe versions of
                the printf() functions. These are defined in
@@ -2261,6 +2244,31 @@ The following options need to be configured:
                example, some LED's) on your board. At the moment,
                the following checkpoints are implemented:
 
+- Detailed boot stage timing
+               CONFIG_BOOTSTAGE
+               Define this option to get detailed timing of each stage
+               of the boot process.
+
+               CONFIG_BOOTSTAGE_USER_COUNT
+               This is the number of available user bootstage records.
+               Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
+               a new ID will be allocated from this stash. If you exceed
+               the limit, recording will stop.
+
+               CONFIG_BOOTSTAGE_REPORT
+               Define this to print a report before boot, similar to this:
+
+               Timer summary in microseconds:
+                      Mark    Elapsed  Stage
+                         0          0  reset
+                 3,575,678  3,575,678  board_init_f start
+                 3,575,695         17  arch_cpu_init A9
+                 3,575,777         82  arch_cpu_init done
+                 3,659,598     83,821  board_init_r start
+                 3,910,375    250,777  main_loop
+                29,916,167 26,005,792  bootm_start
+                30,361,327    445,160  start_kernel
+
 Legacy uImage format:
 
   Arg  Where                   When