X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=README;h=82224f75e4964a21d92a425eb12e9de6508b5a5a;hb=122d805fd4bd478bb83536348291d34ae648364b;hp=b662eb983615c1f855c366a83c7cf9f55bc605cb;hpb=604c7d4a5a3cf70949f6e6094bf0d52ee3b4804d;p=u-boot

diff --git a/README b/README
index b662eb9836..82224f75e4 100644
--- a/README
+++ b/README
@@ -3086,17 +3086,6 @@ CBFS (Coreboot Filesystem) support
 		memories can be connected with a given cs line.
 		Currently Xilinx Zynq qspi supports these type of connections.
 
-		CONFIG_SYS_SPI_ST_ENABLE_WP_PIN
-		enable the W#/Vpp signal to disable writing to the status
-		register on ST MICRON flashes like the N25Q128.
-		The status register write enable/disable bit, combined with
-		the W#/VPP signal provides hardware data protection for the
-		device as follows: When the enable/disable bit is set to 1,
-		and the W#/VPP signal is driven LOW, the status register
-		nonvolatile bits become read-only and the WRITE STATUS REGISTER
-		operation will not execute. The only way to exit this
-		hardware-protected mode is to drive W#/VPP HIGH.
-
 - SystemACE Support:
 		CONFIG_SYSTEMACE
 
@@ -3218,55 +3207,6 @@ CBFS (Coreboot Filesystem) support
 		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
-
-		CONFIG_CMD_BOOTSTAGE
-		Add a 'bootstage' command which supports printing a report
-		and un/stashing of bootstage data.
-
-		CONFIG_BOOTSTAGE_FDT
-		Stash the bootstage information in the FDT. A root 'bootstage'
-		node is created with each bootstage id as a child. Each child
-		has a 'name' property and either 'mark' containing the
-		mark time in microsecond, or 'accum' containing the
-		accumulated time for that bootstage id in microseconds.
-		For example:
-
-		bootstage {
-			154 {
-				name = "board_init_f";
-				mark = <3575678>;
-			};
-			170 {
-				name = "lcd";
-				accum = <33482>;
-			};
-		};
-
-		Code in the Linux kernel can find this in /proc/devicetree.
 
 Legacy uImage format:
 
@@ -3360,9 +3300,9 @@ Legacy uImage format:
    65	net/eth.c		Ethernet found.
 
   -80	common/cmd_net.c	usage wrong
-   80	common/cmd_net.c	before calling NetLoop()
-  -81	common/cmd_net.c	some error in NetLoop() occurred
-   81	common/cmd_net.c	NetLoop() back without error
+   80	common/cmd_net.c	before calling net_loop()
+  -81	common/cmd_net.c	some error in net_loop() occurred
+   81	common/cmd_net.c	net_loop() back without error
   -82	common/cmd_net.c	size == 0 (File with size 0 loaded)
    82	common/cmd_net.c	trying automatic boot
    83	common/cmd_net.c	running "source" command