u-boot/board/siemens/common
Wolfgang Denk 54841ab50c Make sure that argv[] argument pointers are not modified.
The hush shell dynamically allocates (and re-allocates) memory for the
argument strings in the "char *argv[]" argument vector passed to
commands.  Any code that modifies these pointers will cause serious
corruption of the malloc data structures and crash U-Boot, so make
sure the compiler can check that no such modifications are being done
by changing the code into "char * const argv[]".

This modification is the result of debugging a strange crash caused
after adding a new command, which used the following argument
processing code which has been working perfectly fine in all Unix
systems since version 6 - but not so in U-Boot:

int main (int argc, char **argv)
{
	while (--argc > 0 && **++argv == '-') {
/* ====> */	while (*++*argv) {
			switch (**argv) {
			case 'd':
				debug++;
				break;
			...
			default:
				usage ();
			}
		}
	}
	...
}

The line marked "====>" will corrupt the malloc data structures and
usually cause U-Boot to crash when the next command gets executed by
the shell.  With the modification, the compiler will prevent this with
an
	error: increment of read-only location '*argv'

N.B.: The code above can be trivially rewritten like this:

	while (--argc > 0 && **++argv == '-') {
		char *arg = *argv;
		while (*++arg) {
			switch (*arg) {
			...

Signed-off-by: Wolfgang Denk <wd@denx.de>
Acked-by: Mike Frysinger <vapier@gentoo.org>
2010-07-04 23:55:42 +02:00
..
fpga.c Make sure that argv[] argument pointers are not modified. 2010-07-04 23:55:42 +02:00
fpga.h Initial revision 2002-06-10 16:09:10 +00:00
README Change all '$(...)' variable references into '${...}' 2005-11-20 21:40:11 +01:00

CCM/SCM-Ergaenzungen fuer U-Boot und Linux:
-------------------------------------------

Es gibt nun ein gemeinsames Kommando zum Laden der FPGAs:

  => help fpga
  fpga fpga status [name] - print FPGA status
  fpga reset  [name] - reset FPGA
  fpga load [name] addr - load FPGA configuration data

Der Name kann beim CCM-Module auch weggelassen werden.
Die Laengenangabe und damit "puma_len" ist nicht mehr
noetig:

  => fpga load puma 40600000
  FPGA load PUMA: addr 40600000: (00000005)... done

Die MTD-Partitionierung kann nun mittels "bootargs" ueber-
geben werden:

  => printenv addmtd
  addmtd=setenv bootargs ${bootargs}
    mtdparts=0:256k(U-Boot)ro,768k(Kernel),-(Rest)\;1:-(myJFFS2)

Die Portierung auf SMC ist natuerlich noch nicht getestet.

Wolfgang Grandegger (04.06.2002)