Lines Matching refs:up

79 - clean up code
221 This is the intended start-up flow for boards. This should apply for both
246 	- must not set up SDRAM or use console
253 	- purpose: set up the machine ready for running board_init_r():
261 	- dram_init() is called to set up DRAM. If already done in SPL this
268 	- should set up SDRAM, and anything needed to make the UART work
411 		supported, core will start to execute uboot when wakes up.
706 		boot command (on start-up) it will call board_run_command()
732 		is then picked up in board_init_f() and made available through
863 		support disks up to 2.1TB.
1437 		ping) and therefore take up to a few hundred milliseconds to
1444 		cache. The default is to keep IDs for up to four outstanding
1502 		Fix-up device tree with MAC addresses fetched sequentially from
2046 		before giving up the operation. If not defined, a
2465 		it is set up by spl_init() and before that, the simple malloc()
2687 		fixing up gd->ram_size the Linux kernel should gets passed
2940 	Builds up envcrc with the target environment so that external utils
2998 		when U-Boot starts up. The board function checkboard() is called
3248 		low level initializations (like setting up the memory
4384 	drivers, set up the MMU, etc. - this means, that you cannot
4400 	one, all aligned on "uint32_t" boundaries (size rounded up to
4468 Here, a CPM timer is set up to generate an interrupt every second.
4596 	require any physical RAM backing up the cache. The cleverness
4783 initial stack is set up in the internal Dual Ported RAM (in case CPUs
4805 pages, and the final stack is set up.