diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.at91 | 84 | ||||
| -rw-r--r-- | doc/README.b4860qds | 4 | ||||
| -rw-r--r-- | doc/README.fdt-control | 9 | ||||
| -rw-r--r-- | doc/README.scrapyard | 8 | ||||
| -rw-r--r-- | doc/README.t4240qds | 26 | ||||
| -rw-r--r-- | doc/README.ubi | 80 | ||||
| -rw-r--r-- | doc/README.watchdog | 3 | ||||
| -rw-r--r-- | doc/SPL/README.am335x-network | 2 | ||||
| -rw-r--r-- | doc/device-tree-bindings/exynos/dwmmc.txt | 54 | ||||
| -rw-r--r-- | doc/driver-model/UDM-pci.txt | 6 | 
10 files changed, 246 insertions, 30 deletions
| diff --git a/doc/README.at91 b/doc/README.at91 index b51df00da..67412136e 100644 --- a/doc/README.at91 +++ b/doc/README.at91 @@ -1,6 +1,9 @@  Atmel AT91 Evaluation kits -http://atmel.com/dyn/products/tools.asp?family_id=605#1443 +Index +  - I. Board mapping & boot media +  - II. NAND partition table +  - III. watchdog support  I. Board mapping & boot media  ------------------------------------------------------------------------------ @@ -10,7 +13,7 @@ AT91SAM9260EK, AT91SAM9G20EK & AT91SAM9XEEK  Memory map  	0x20000000 - 23FFFFFF	SDRAM (64 MB)  	0xC0000000 - Cxxxxxxx	Atmel Dataflash card (J13) -	0xD0000000 - Dxxxxxxx	Soldered Atmel Dataflash +	0xD0000000 - D07FFFFF	Soldered Atmel Dataflash (AT45DB642)  Environment variables @@ -20,7 +23,6 @@ Environment variables  		- Nand flash.  	You can choose your storage location at config step (here for at91sam9260ek) : -		make at91sam9260ek_config		- use data flash (spi cs1) (default)  		make at91sam9260ek_nandflash_config	- use nand flash  		make at91sam9260ek_dataflash_cs0_config	- use data flash (spi cs0)  		make at91sam9260ek_dataflash_cs1_config	- use data flash (spi cs1) @@ -32,7 +34,7 @@ AT91SAM9261EK, AT91SAM9G10EK  Memory map  	0x20000000 - 23FFFFFF	SDRAM (64 MB) -	0xC0000000 - Cxxxxxxx	Soldered Atmel Dataflash +	0xC0000000 - C07FFFFF	Soldered Atmel Dataflash (AT45DB642)  	0xD0000000 - Dxxxxxxx	Atmel Dataflash card (J22)  Environment variables @@ -43,7 +45,6 @@ Environment variables  		- Nand flash.  	You can choose your storage location at config step (here for at91sam9260ek) : -		make at91sam9261ek_config		- use data flash (spi cs0) (default)  		make at91sam9261ek_nandflash_config	- use nand flash  		make at91sam9261ek_dataflash_cs0_config	- use data flash (spi cs0)  		make at91sam9261ek_dataflash_cs3_config	- use data flash (spi cs3) @@ -65,7 +66,6 @@ Environment variables  		- Nor flash (not populate by default)  	You can choose your storage location at config step (here for at91sam9260ek) : -		make at91sam9263ek_config		- use data flash (spi cs0) (default)  		make at91sam9263ek_nandflash_config	- use nand flash  		make at91sam9263ek_dataflash_cs0_config	- use data flash (spi cs0)  		make at91sam9263ek_norflash_config	- use nor flash @@ -79,19 +79,15 @@ AT91SAM9M10G45EK  ------------------------------------------------------------------------------  Memory map -	0x20000000 - 23FFFFFF	SDRAM (64 MB) -	0xC0000000 - Cxxxxxxx	Atmel Dataflash card (J12) +	0x70000000 - 77FFFFFF	SDRAM (128 MB)  Environment variables  	U-Boot environment variables can be stored at different places: -		- Dataflash on SPI chip select 0 (dataflash card)  		- Nand flash.  	You can choose your storage location at config step (here for at91sam9m10g45ek) : -		make at91sam9m10g45ek_config			- use data flash (spi cs0) (default)  		make at91sam9m10g45ek_nandflash_config		- use nand flash -		make at91sam9m10g45ek_dataflash_cs0_config	- use data flash (spi cs0)  ------------------------------------------------------------------------------ @@ -100,7 +96,7 @@ AT91SAM9RLEK  Memory map  	0x20000000 - 23FFFFFF	SDRAM (64 MB) -	0xC0000000 - Cxxxxxxx	Soldered Atmel Dataflash +	0xC0000000 - C07FFFFF   Soldered Atmel Dataflash (AT45DB642)  Environment variables @@ -108,12 +104,66 @@ Environment variables  		- Dataflash on SPI chip select 0  		- Nand flash. -	You can choose your storage location at config step (here for at91sam9260ek) : -		make at91sam9263ek_config		- use data flash (spi cs0) (default) -		make at91sam9263ek_nandflash_config	- use nand flash -		make at91sam9263ek_dataflash_cs0_config	- use data flash (spi cs0) +	You can choose your storage location at config step (here for at91sam9rlek) : +		make at91sam9rlek_nandflash_config	- use nand flash + + +------------------------------------------------------------------------------ +AT91SAM9N12EK, AT91SAM9X5EK +------------------------------------------------------------------------------ + +Memory map +	0x20000000 - 27FFFFFF	SDRAM (128 MB) + +Environment variables + +	U-Boot environment variables can be stored at different places: +		- Nand flash. +		- SD/MMC card +		- Serialflash/Dataflash on SPI chip select 0 + +	You can choose your storage location at config step (here for at91sam9x5ek) : +		make at91sam9x5ek_dataflash_config	- use data flash +		make at91sam9x5ek_mmc_config		- use sd/mmc card +		make at91sam9x5ek_nandflash_config	- use nand flash +		make at91sam9x5ek_spiflash_config	- use serial flash + + +------------------------------------------------------------------------------ +SAMA5D3XEK +------------------------------------------------------------------------------ + +Memory map +	0x20000000 - 3FFFFFFF	SDRAM (512 MB) + +Environment variables + +	U-Boot environment variables can be stored at different places: +		- Nand flash. +		- SD/MMC card +		- Serialflash on SPI chip select 0 + +	You can choose your storage location at config step (here for sama5d3xek) : +		make sama5d3xek_mmc_config		- use SD/MMC card +		make sama5d3xek_nandflash_config	- use nand flash +		make sama5d3xek_serialflash_config	- use serial flash + + +II. NAND partition table + +	All the board support boot from NAND flash will use the following NAND +	partition table + +		0x00000000 - 0x0003FFFF	bootstrap	(256 KiB) +		0x00040000 - 0x000BFFFF u-boot		(512 KiB) +		0x000C0000 - 0x000FFFFF env		(256 KiB) +		0x00100000 - 0x0013FFFF env_redundant	(256 KiB) +		0x00140000 - 0x0017FFFF spare		(256 KiB) +		0x00180000 - 0x001FFFFF dtb		(512 KiB) +		0x00200000 - 0x007FFFFF kernel		(6 MiB) +		0x00800000 - 0xxxxxxxxx rootfs		(All left) -II. Watchdog support +III. Watchdog support  	For security reasons, the at91 watchdog is running at boot time and,  	if deactivated, cannot be used anymore. diff --git a/doc/README.b4860qds b/doc/README.b4860qds index f6c5ff8e9..bd10a6df0 100644 --- a/doc/README.b4860qds +++ b/doc/README.b4860qds @@ -185,7 +185,7 @@ Start Address	End Address	Description	Size  0xF_A0C0_0000 	0xF_DFFF_FFFF	Free		1012 MB  0xF_A000_0000 	0xF_A0BF_FFFF	MAPLE0/1/2	12 MB  0xF_0040_0000 	0xF_9FFF_FFFF	Free		12 GB -0xF_0000_0000 	0xF_003F_FFFF	DCSR		4 MB +0xF_0000_0000 	0xF_01FF_FFFF	DCSR		32 MB  0xC_4000_0000 	0xE_FFFF_FFFF	Free		11 GB  0xC_3000_0000 	0xC_3FFF_FFFF	sRIO-2 I/O 	256 MB  0xC_2000_0000 	0xC_2FFF_FFFF	sRIO-1 I/O  	256 MB @@ -215,7 +215,7 @@ Start Address	End Address	Description	Size  0xF_A0C0_0000 	0xF_DFFF_FFFF	Free		1012 MB  0xF_A000_0000 	0xF_A0BF_FFFF	MAPLE0/1/2	12 MB  0xF_0040_0000 	0xF_9FFF_FFFF	Free		12 GB -0xF_0000_0000 	0xF_003F_FFFF	DCSR		4 MB +0xF_0000_0000 	0xF_01FF_FFFF	DCSR		32 MB  0xC_4000_0000 	0xE_FFFF_FFFF	Free		11 GB  0xC_3000_0000 	0xC_3FFF_FFFF	sRIO-2 I/O 	256 MB  0xC_2000_0000 	0xC_2FFF_FFFF	sRIO-1 I/O  	256 MB diff --git a/doc/README.fdt-control b/doc/README.fdt-control index 5963f78e9..95a88a7c7 100644 --- a/doc/README.fdt-control +++ b/doc/README.fdt-control @@ -49,6 +49,12 @@ the features of each board in the device tree file, and have a single  generic source base.  To enable this feature, add CONFIG_OF_CONTROL to your board config file. +It is currently supported on ARM, x86 and Microblaze - other architectures +will need to add code to their arch/xxx/lib/board.c file to locate the +FDT. Alternatively you can enable generic board support on your board +(with CONFIG_SYS_GENERIC_BOARD) if this is available (as it is for +PowerPC). For ARM, Tegra and Exynos5 have device trees available for +common devices.  What is a Flat Device Tree? @@ -99,7 +105,8 @@ Then run the compiler (your version will vary):  	*   Bad configuration:	0  	* Strange test result:	0 -You will also find a useful ftdump utility for decoding a binary file. +You will also find a useful fdtdump utility for decoding a binary file, as +well as fdtget/fdtput for reading and writing properties in a binary file.  Where do I get an fdt file for my board? diff --git a/doc/README.scrapyard b/doc/README.scrapyard index 2cdb8a9dc..a0f1fa30f 100644 --- a/doc/README.scrapyard +++ b/doc/README.scrapyard @@ -11,8 +11,11 @@ easily if here is something they might want to dig for...  Board            Arch        CPU            Commit      Removed     Last known maintainer/contact  ================================================================================================= -smdk6400         arm         arm1176        -           -           Zhong Hongbo <bocui107@gmail.com> -ns9750dev        arm         arm926ejs      -           -           Markus Pietrek <mpietrek@fsforth.de> +Alaska8220       powerpc     mpc8220        -           - +Yukon8220        powerpc     mpc8220        -           - +sorcery          powerpc     mpc8220        -           - +smdk6400         arm         arm1176        52587f1	2013-04-12  Zhong Hongbo <bocui107@gmail.com> +ns9750dev        arm         arm926ejs      4cfc611	2013-02-28  Markus Pietrek <mpietrek@fsforth.de>  AMX860           powerpc     mpc860         1b0757e     2012-10-28  Wolfgang Denk <wd@denx.de>  c2mon            powerpc     mpc855         1b0757e     2012-10-28  Wolfgang Denk <wd@denx.de>  ETX094           powerpc     mpc850         1b0757e     2012-10-28  Wolfgang Denk <wd@denx.de> @@ -93,3 +96,4 @@ R5200            ColdFire    -              48ead7a     2008-03-31  Zachary P. L  CPCI440          powerpc     440GP          b568fd2     2007-12-27  Matthias Fuchs <matthias.fuchs@esd-electronics.com>  PCIPPC2          powerpc     MPC740/MPC750  7c9e89b     2013-02-07  Wolfgang Denk <wd@denx.de>  PCIPPC6	powerpc	MPC740/MPC750 -	  -		Wolfgang Denk <wd@denx.de> +omap2420h4       arm         omap24xx       -           2013-06-04  Richard Woodruff <r-woodruff2@ti.com> diff --git a/doc/README.t4240qds b/doc/README.t4240qds index 677d120a8..a9841fb5f 100644 --- a/doc/README.t4240qds +++ b/doc/README.t4240qds @@ -86,7 +86,7 @@ The addresses in brackets are physical addresses.  0x0_0000_0000 (0x0_0000_0000) - 0x0_7fff_ffff   2GB DDR (more than 2GB is initialized but not mapped under with TLB)  0x0_8000_0000 (0xc_0000_0000) - 0x0_dfff_ffff 1.5GB PCIE memory -0x0_f000_0000 (0xf_0000_0000) - 0x0_f03f_ffff  4MB  DCSR +0x0_f000_0000 (0xf_0000_0000) - 0x0_f1ff_ffff  32MB DCSR (includes trace buffers)  0x0_f400_0000 (0xf_f400_0000) - 0x0_f5ff_ffff  32MB BMan  0x0_f600_0000 (0xf_f600_0000) - 0x0_f7ff_ffff  32MB QMan  0x0_f800_0000 (0xf_f800_0000) - 0x0_f803_ffff 256KB PCIE IO @@ -96,3 +96,27 @@ The addresses in brackets are physical addresses.  0x0_ffff_f000 (0x0_7fff_fff0) - 0x0_ffff_ffff   4KB Boot page translation for secondary cores  The physical address of the last (boot page translation) varies with the actual DDR size. + +Voltage ID and VDD override +-------------------- +T4240 has a VID feature. U-boot reads the VID efuses and adjust the voltage +accordingly. The voltage can also be override by command vdd_override. The +syntax is + +vdd_override <voltage in mV>, eg. 1050 is for 1.050v. + +Upon success, the actual voltage will be read back. The value is checked +for safety and any invalid value will not adjust the voltage. + +Another way to override VDD is to use environmental variable, in case of using +command is too late for some debugging. The syntax is + +setenv t4240qds_vdd_mv <voltage in mV> +saveenv +reset + +The override voltage takes effect when booting. + +Note: voltage adjustment needs to be done step by step. Changing voltage too +rapidly may cause current surge. The voltage stepping is done by software. +Users can set the final voltage directly. diff --git a/doc/README.ubi b/doc/README.ubi index da2dfac50..3cf4ef232 100644 --- a/doc/README.ubi +++ b/doc/README.ubi @@ -2,7 +2,8 @@  UBI usage in U-Boot  ------------------- -Here the list of the currently implemented UBI commands: +UBI support in U-Boot is broken down into five separate commands. +The first is the ubi command, which has six subcommands:  => help ubi  ubi - ubi commands @@ -142,3 +143,80 @@ read 524288 bytes from volume 0 to 900000(buf address)  => cmp.b 800000 900000 80000  Total of 524288 bytes were the same + + +Next, the ubifsmount command allows you to access filesystems on the +UBI partition which has been attached with the ubi part command: + +=> help ubifsmount +ubifsmount - mount UBIFS volume + +Usage: +ubifsmount <volume-name> +    - mount 'volume-name' volume + +For example: + +=> ubifsmount ubi0:recovery +UBIFS: mounted UBI device 0, volume 0, name "recovery" +UBIFS: mounted read-only +UBIFS: file system size:   46473216 bytes (45384 KiB, 44 MiB, 366 LEBs) +UBIFS: journal size:       6348800 bytes (6200 KiB, 6 MiB, 50 LEBs) +UBIFS: media format:       w4/r0 (latest is w4/r0) +UBIFS: default compressor: LZO +UBIFS: reserved for root:  0 bytes (0 KiB) + +Note that unlike Linux, U-Boot can only have one active UBI partition +at a time, which can be referred to as ubi0, and must be supplied along +with the name of the filesystem you are mounting. + + +Once a UBI filesystem has been mounted, the ubifsls command allows you +to list the contents of a directory in the filesystem: + + +=> help ubifsls +ubifsls - list files in a directory + +Usage: +ubifsls [directory] +    - list files in a 'directory' (default '/') + +For example: + +=> ubifsls +            17442  Thu Jan 01 02:57:38 1970  imx28-evk.dtb +          2998146  Thu Jan 01 02:57:43 1970  zImage + + +And the ubifsload command allows you to load a file from a UBI +filesystem: + + +=> help ubifsload +ubifsload - load file from an UBIFS filesystem + +Usage: +ubifsload <addr> <filename> [bytes] +    - load file 'filename' to address 'addr' + +For example: + +=> ubifsload ${loadaddr} zImage +Loading file 'zImage' to addr 0x42000000 with size 2998146 (0x002dbf82)... +Done + + +Finally, you can unmount the UBI filesystem with the ubifsumount +command: + +=> help ubifsumount +ubifsumount - unmount UBIFS volume + +Usage: +ubifsumount     - unmount current volume + +For example: + +=> ubifsumount +Unmounting UBIFS volume recovery! diff --git a/doc/README.watchdog b/doc/README.watchdog index 33f31c214..59f306b85 100644 --- a/doc/README.watchdog +++ b/doc/README.watchdog @@ -30,3 +30,6 @@ CONFIG_IMX_WATCHDOG  CONFIG_XILINX_TB_WATCHDOG  	Available for Xilinx Axi platforms to service timebase watchdog timer. + +CONFIG_BFIN_WATCHDOG +	Available for bf5xx and bf6xx to service the watchdog. diff --git a/doc/SPL/README.am335x-network b/doc/SPL/README.am335x-network index e5a198f49..9b63791ad 100644 --- a/doc/SPL/README.am335x-network +++ b/doc/SPL/README.am335x-network @@ -7,7 +7,7 @@ NAND and bricked (empty) board with only a network cable.   I. Building the required images    1. You have to enable generic SPL configuration options (see -docs/README.SPL) as well as CONFIG_SPL_NET_SUPPORT, +doc/README.SPL) as well as CONFIG_SPL_NET_SUPPORT,  CONFIG_ETH_SUPPORT, CONFIG_SPL_LIBGENERIC_SUPPORT and  CONFIG_SPL_LIBCOMMON_SUPPORT in your board configuration file to build  SPL with support for booting over the network. Also you have to enable diff --git a/doc/device-tree-bindings/exynos/dwmmc.txt b/doc/device-tree-bindings/exynos/dwmmc.txt new file mode 100644 index 000000000..566da3b63 --- /dev/null +++ b/doc/device-tree-bindings/exynos/dwmmc.txt @@ -0,0 +1,54 @@ +* Exynos 5250 DWC_mobile_storage + +The Exynos 5250 provides DWC_mobile_storage interface which supports +. Embedded Multimedia Cards (EMMC-version 4.5) +. Secure Digital memory (SD mem-version 2.0) +. Secure Digital I/O (SDIO-version 3.0) +. Consumer Electronics Advanced Transport Architecture (CE-ATA-version 1.1) + +The Exynos 5250 DWC_mobile_storage provides four channels. +SOC specific and Board specific properties are channel specific. + +Required SoC Specific Properties: + +- compatible: should be +	- samsung,exynos5250-dwmmc: for exynos5250 platforms + +- reg: physical base address of the controller and length of memory mapped +	region. + +- interrupts: The interrupt number to the cpu. + +Required Board Specific Properties: + +- #address-cells: should be 1. +- #size-cells: should be 0. +- samsung,bus-width: The width of the bus used to interface the devices +	supported by DWC_mobile_storage (SD-MMC/EMMC/SDIO). +	. Typically the bus width is 4 or 8. +- samsung,timing: The timing values to be written into the +	Drv/sample clock selection register of corresponding channel. +	. It is comprised of 3 values corresponding to the 3 fileds +	  'SelClk_sample', 'SelClk_drv' and 'DIVRATIO' of CLKSEL register. +	. SelClk_sample: Select sample clock among 8 shifted clocks. +	. SelClk_drv: Select drv clock among 8 shifted clocks. +	. DIVRATIO: Clock Divide ratio select. +	. The above 3 values are used by the clock phase shifter. + +Example: + +mmc@12200000 { +	samsung,bus-width = <8>; +	samsung,timing = <1 3 3>; +	samsung,removable = <1>; +} +In the above example, +	. The bus width is 8 +	. Timing is comprised of 3 values as explained below +		1 - SelClk_sample +		3 - SelClk_drv +		3 - DIVRATIO +	. The 'removable' flag indicates whether the the particilar device +	  cannot be removed (always present) or it is a removable device. +		1 - Indicates that the device is removable. +		0 - Indicates that the device cannot be removed. diff --git a/doc/driver-model/UDM-pci.txt b/doc/driver-model/UDM-pci.txt index c2cf2d5a6..6a592b336 100644 --- a/doc/driver-model/UDM-pci.txt +++ b/doc/driver-model/UDM-pci.txt @@ -201,11 +201,7 @@ III) Analysis of in-tree drivers      -----------------------------        Standard driver, uses indirect functions. -    12) powerpc/cpu/mpc8220/pci.c -    ----------------------------- -      Standard driver, specifies all read/write functions separately. - -    13) powerpc/cpu/mpc85xx/pci.c +    12) powerpc/cpu/mpc85xx/pci.c      -----------------------------        Standard driver, uses indirect functions, has two busses. |