u-boot.git/board/esd, branch v2010.09

at91: Enabeling USB host on meesc board

2010-08-20T14:17:52Z

There was an redesign, so USB is available now. Signed-off-by: Daniel Gorsulowski Signed-off-by: Reinhard Meyer

at91: Update meesc board to new SoC access

2010-08-20T14:17:48Z

* convert meesc board to use c stucture SoC access * change gpio access to at91_gpio syntax * moved CONFIG_SYS_HZ below board and cpu defines (purely cosmetic) Signed-off-by: Daniel Gorsulowski Signed-off-by: Reinhard Meyer

ppc4xx: Fix building of PMC440 board

2010-08-09T14:05:07Z

Update image size and default environment after addition of new environment handling. Signed-off-by: Matthias Fuchs Signed-off-by: Stefan Roese

ppc4xx: Fix building of CANBT board

2010-08-09T14:05:03Z

Update image size after addition of new environment handling. Signed-off-by: Matthias Fuchs Signed-off-by: Stefan Roese

ppc4xx: Fix building of AR405 board

2010-08-09T14:04:59Z

Update image size after addition of new environment handling. Signed-off-by: Matthias Fuchs Signed-off-by: Stefan Roese

Rename getenv_r() into getenv_f()

2010-08-03T22:45:36Z

While running from flash, i. e. before relocation, we have only a limited C runtime environment without writable data segment. In this phase, some configurations (for example with environment in EEPROM) must not use the normal getenv(), but a special function. This function had been called getenv_r(), with the idea that the "_r" suffix would mean the same as in the _r_eentrant versions of some of the C library functions (for example getdate vs. getdate_r, getgrent vs. getgrent_r, etc.). Unfortunately this was a misleading name, as in U-Boot the "_r" generally means "running from RAM", i. e. _after_ relocation. To avoid confusion, rename into getenv_f() [as "running from flash"] Signed-off-by: Wolfgang Denk Acked-by: Detlev Zundel

cmd_usage(): simplify return code handling

2010-07-24T18:43:57Z

Lots of code use this construct: cmd_usage(cmdtp); return 1; Change cmd_usage() let it return 1 - then we can replace all these ocurrances by return cmd_usage(cmdtp); This fixes a few places with incorrect return code handling, too. Signed-off-by: Wolfgang Denk

83xx/85xx/86xx: LBC register cleanup

2010-07-16T15:55:09Z

Currently, 83xx, 86xx, and 85xx have a lot of duplicated code dedicated to defining and manipulating the LBC registers. Merge this into a single spot. To do this, we have to decide on a common name for the data structure that holds the lbc registers - it will now be known as fsl_lbc_t, and we adopt a common name for the immap layouts that include the lbc - this was previously known as either im_lbc or lbus; use the former. In addition, create accessors for the BR/OR regs that use in/out_be32 and use those instead of the mismash of access methods currently in play. I have done a successful ppc build all and tested a board or two from each processor family. Signed-off-by: Becky Bruce Acked-by: Kim Phillips Signed-off-by: Kumar Gala

Make sure that argv[] argument pointers are not modified.

2010-07-04T21:55:42Z

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 Acked-by: Mike Frysinger

ppc4xx: Fix building PLU405 board

2010-05-17T09:00:42Z

Due to some overlapping sections it's time to update TEXT_BASE for this board. Signed-off-by: Matthias Fuchs Signed-off-by: Stefan Roese