Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 09 8月, 2010 1 次提交
  3. 25 7月, 2010 1 次提交
  5. 13 7月, 2010 2 次提交
    • S
      NAND: formatting cleanups from env.oob support · 53504a27
      由 Scott Wood 提交于 
      Change if (ok) {
	bunch of stuff
} else {
	error
}

to

if (error) {
	get out
}

proceed with bunch of stuff

Plus a few whitespace cleanups.
Signed-off-by: NScott Wood <scottwood@freescale.com>
      53504a27
    • B
      NAND: environment offset in OOB (CONFIG_ENV_OFFSET_OOB) · c9f7351b
      由 Ben Gardiner 提交于 
      This is a re-submission of the patch by Harald Welte
<laforge@openmoko.org> with minor modifications for rebase and changes
as suggested by Scott Wood <scottwood@freescale.com> [1] [2].

This patch enables the environment partition to have a run-time dynamic
location (offset) in the NAND flash.  The reason for this is simply that
all NAND flashes have factory-default bad blocks, and a fixed compile
time offset would mean that sometimes the environment partition would
live inside factory bad blocks. Since the number of factory default
blocks can be quite high (easily 1.3MBytes in current standard
components), it is not economic to keep that many spare blocks inside
the environment partition.

With this patch and CONFIG_ENV_OFFSET_OOB enabled, the location of the
environment partition is stored in the out-of-band (OOB) data of the
first block in flash. Since the first block is where most systems boot
from, the vendors guarantee that the first block is not a factory
default block.

This patch introduces the 'nand env.oob' command, which can be called
from the u-boot command line. 'nand env.oob get' reads the address of
the environment partition from the OOB data, 'nand env.oob set
{offset,partition-name}' allows the setting of the marker by specifying
a numeric offset or a partition name.

[1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/43916
[2] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/79195Signed-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
Acked-by: NHarald Welte <laforge@gnumonks.org>
      c9f7351b
  7. 05 7月, 2010 1 次提交
    • W
      Make sure that argv[] argument pointers are not modified. · 54841ab5
      由 Wolfgang Denk 提交于 
      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: NWolfgang Denk <wd@denx.de>
Acked-by: NMike Frysinger <vapier@gentoo.org>
      54841ab5
  9. 22 5月, 2010 1 次提交
  11. 24 3月, 2010 1 次提交
  13. 14 11月, 2009 2 次提交
  15. 17 7月, 2009 1 次提交
    • S
      Remove legacy NAND and disk on chip code. · be33b046
      由 Scott Wood 提交于 
      Legacy NAND had been scheduled for removal.  Any boards that use this
were already not building in the previous release due to an #error.

The disk on chip code in common/cmd_doc.c relies on legacy NAND,
and it has also been removed.  There is newer disk on chip code
in drivers/mtd/nand; someone with access to hardware and sufficient
time and motivation can try to get that working, but for now disk
on chip is not supported.
Signed-off-by: NScott Wood <scottwood@freescale.com>
      be33b046
  17. 08 7月, 2009 1 次提交
  19. 13 6月, 2009 1 次提交
    • W
      General help message cleanup · a89c33db
      由 Wolfgang Denk 提交于 
      Many of the help messages were not really helpful; for example, many
commands that take no arguments would not print a correct synopsis
line, but "No additional help available." which is not exactly wrong,
but not helpful either.

Commit ``Make "usage" messages more helpful.'' changed this
partially. But it also became clear that lots of "Usage" and "Help"
messages (fields "usage" and "help" in struct cmd_tbl_s respective)
were actually redundant.

This patch cleans this up - for example:

Before:
	=> help dtt
	dtt - Digital Thermometer and Thermostat

	Usage:
	dtt         - Read temperature from digital thermometer and thermostat.

After:
	=> help dtt
	dtt - Read temperature from Digital Thermometer and Thermostat

	Usage:
	dtt
Signed-off-by: NWolfgang Denk <wd@denx.de>
      a89c33db
  21. 28 4月, 2009 1 次提交
    • L
      Separate mtdparts command from jffs2 · 0c8a8491
      由 Ladislav Michl 提交于 
      On Thu, Mar 19, 2009 at 01:30:36PM +0100, Stefan Roese wrote:
> Currently the mtdparts commands are included in the jffs2 command support.
> This doesn't make sense anymore since other commands (e.g. UBI) use this
> infrastructure as well now. This patch separates the mtdparts commands from
> the jffs2 commands making it possible to only select mtdparts when no JFFS2
> support is needed.

One more leftover... Let nboot command know about partitions even if JFFS2
support is not enabled.
Signed-off-by: NLadislav Michl <ladis@linux-mips.org>
Acked-by: NStefan Roese <sr@denx.de>
      0c8a8491
  23. 17 4月, 2009 1 次提交
  25. 24 3月, 2009 1 次提交
  27. 21 3月, 2009 1 次提交
  29. 18 3月, 2009 2 次提交
  31. 28 1月, 2009 2 次提交
  33. 24 1月, 2009 3 次提交
  35. 29 10月, 2008 1 次提交
  37. 19 10月, 2008 1 次提交
  39. 14 8月, 2008 1 次提交
  41. 13 8月, 2008 9 次提交
  43. 11 7月, 2008 1 次提交
  45. 10 7月, 2008 1 次提交
  47. 01 7月, 2008 1 次提交
  49. 29 5月, 2008 1 次提交
  51. 14 5月, 2008 1 次提交