diff options
author | Wolfgang Denk <wd@denx.de> | 2011-09-11 21:24:09 +0200 |
---|---|---|
committer | Wolfgang Denk <wd@denx.de> | 2011-09-11 21:24:09 +0200 |
commit | 04e5ae793153e74d682f2d0e297e58fd75366c8f (patch) | |
tree | 2a94d2ea7897d12a9600a5d378cfd3f810ee29fc /doc | |
parent | 3b7175524939ffc73af2b8eb1ee5166838d3f260 (diff) | |
download | u-boot-imx-04e5ae793153e74d682f2d0e297e58fd75366c8f.zip u-boot-imx-04e5ae793153e74d682f2d0e297e58fd75366c8f.tar.gz u-boot-imx-04e5ae793153e74d682f2d0e297e58fd75366c8f.tar.bz2 |
Minor coding style cleanup.
Signed-off-by: Wolfgang Denk <wd@denx.de>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/README.SPL | 2 | ||||
-rw-r--r-- | doc/README.at91-soc | 1 | ||||
-rw-r--r-- | doc/README.ublimage | 22 | ||||
-rw-r--r-- | doc/README.usb | 18 |
4 files changed, 21 insertions, 22 deletions
diff --git a/doc/README.SPL b/doc/README.SPL index ce8e19f..30624a5 100644 --- a/doc/README.SPL +++ b/doc/README.SPL @@ -34,7 +34,7 @@ endif COBJS-$(CONFIG_SPL_BUILD) += foo.o #ifdef CONFIG_SPL_BUILD - foo(); + foo(); #endif diff --git a/doc/README.at91-soc b/doc/README.at91-soc index ed6e76a..bed035c 100644 --- a/doc/README.at91-soc +++ b/doc/README.at91-soc @@ -39,4 +39,3 @@ The method for updating 3. add new structures for SoC access 4. Convert arch, driver and boards file to new SoC 5. remove legacy code, if all boards and drives are ready - diff --git a/doc/README.ublimage b/doc/README.ublimage index add24d6..ab25b26 100644 --- a/doc/README.ublimage +++ b/doc/README.ublimage @@ -101,22 +101,22 @@ This steps are done automagically if you do a "make all" Structure of this binary (Example for the cam_enc_4xx board with a NAND page size = 0x800): -offset : 0x00000 | 0x800 | 0x3800 -content: UBL | nand_spl | u-boot code - Header | code | +offset : 0x00000 | 0x800 | 0x3800 +content: UBL | nand_spl | u-boot code + Header | code | The NAND layout looks for example like this: (Example for the cam_enc_4xx board with a NAND page size = 0x800, block size = 0x20000 and CONFIG_SYS_NROF_UBL_HEADER 5): -offset : 0x80000 | 0xa0000 | 0xa3000 -content: UBL | nand_spl | u-boot code - Header | code | - ^ ^ - ^ 0xa0000 = CONFIG_SYS_NROF_UBL_HEADER * 0x20000 - ^ - 0x80000 = Block 4 * 0x20000 +offset : 0x80000 | 0xa0000 | 0xa3000 +content: UBL | nand_spl | u-boot code + Header | code | + ^ ^ + ^ 0xa0000 = CONFIG_SYS_NROF_UBL_HEADER * 0x20000 + ^ + 0x80000 = Block 4 * 0x20000 If the cpu starts in NAND boot mode, it checks the UBL descriptor starting with block 1 (page 0). When a valid UBL signature is found, @@ -132,7 +132,7 @@ read and processed. Once the user-specified start-up conditions are set, the RBL copies the nand_spl into ARM internal RAM, starting at address 0x0000: 0020. - ^^^^ + ^^^^ The nand_spl code itself now does necessary intializations, and at least, copies the u-boot code from NAND into RAM, and jumps to it ... diff --git a/doc/README.usb b/doc/README.usb index a8a4058..0771c71 100644 --- a/doc/README.usb +++ b/doc/README.usb @@ -116,7 +116,7 @@ Bus 002 Device 010: ID 0b95:7720 ASIX Electronics Corp. AX88772 If you look at drivers/usb/eth/asix.c you will see this line within the supported device list, so we know this adapter is supported. - { 0x0b95, 0x7720 }, /* Trendnet TU2-ET100 V3.0R */ + { 0x0b95, 0x7720 }, /* Trendnet TU2-ET100 V3.0R */ If your adapter is not listed there is a still a chance that it will work. Try looking up the manufacturer of the chip inside your adapter. @@ -144,8 +144,8 @@ To enable USB Host Ethernet in U-Boot, your platform must of course support USB with CONFIG_CMD_USB enabled and working. You will need to add some config settings to your board header file: -#define CONFIG_USB_HOST_ETHER /* Enable USB Ethernet adapters */ -#define CONFIG_USB_ETHER_ASIX /* Asix, or whatever driver(s) you want */ +#define CONFIG_USB_HOST_ETHER /* Enable USB Ethernet adapters */ +#define CONFIG_USB_ETHER_ASIX /* Asix, or whatever driver(s) you want */ As with built-in networking, you will also want to enable some network commands, for example: @@ -168,9 +168,9 @@ You can also set the default IP address of your board and the server as well as the default file to load when a 'bootp' command is issued. All of these can be obtained from the bootp server if not set. -#define CONFIG_IPADDR 10.0.0.2 (replace with your value) -#define CONFIG_SERVERIP 10.0.0.1 (replace with your value) -#define CONFIG_BOOTFILE uImage +#define CONFIG_IPADDR 10.0.0.2 (replace with your value) +#define CONFIG_SERVERIP 10.0.0.1 (replace with your value) +#define CONFIG_BOOTFILE uImage The 'usb start' command should identify the adapter something like this: @@ -200,9 +200,9 @@ TFTP from server 172.22.72.144; our IP address is 172.22.73.81 Filename '/tftpboot/uImage-sjg-seaboard-261347'. Load address: 0x40c000 Loading: ################################################################# - ################################################################# - ################################################################# - ################################################ + ################################################################# + ################################################################# + ################################################ done Bytes transferred = 3557464 (364858 hex) CrOS> |