Simon Glass 983c72f479 Clarify bootm OS arguments ... At present the arguments to bootm are processed in a somewhat confusing way. Sub-functions must know how many arguments their calling functions have processed, and the OS boot function must also have this information. Also it isn't obvious that 'bootm' and 'bootm start' provide arguments in the same way. Adjust the code so that arguments are removed from the list before calling a sub-function. This means that all functions can know that argv[0] is the first argument of which they need to take notice. Signed-off-by: Simon Glass <sjg@chromium.org>		2013-06-26 10:16:41 -04:00
..
board.c	lib: consolidate hang()	2013-05-01 16:41:08 -04:00
bootm.c	Clarify bootm OS arguments	2013-06-26 10:16:41 -04:00
Makefile	microblaze: Add muldi3.c which contains routines for _muldi3	2013-02-04 12:07:09 +01:00
muldi3.c	microblaze: Add muldi3.c which contains routines for _muldi3	2013-02-04 12:07:09 +01:00
time.c	microblaze: Move __udelay implementation	2012-07-10 11:54:06 +02:00