u-boot.git, branch v2013.01-rc3

Prepare v2013.01-rc3

2013-01-10T21:44:40+00:00

Signed-off-by: Tom Rini

bootm: relocate names of sub-command table for archs with CONFIG_NEEDS_MANUAL_RELOC

2013-01-10T21:35:12+00:00

To make bootm sub-command feature working on archs with CONFIG_NEEDS_MANUAL_RELOC,
the name pointers in the sub-command table need to be relocated.

Signed-off-by: Daniel Schwierzeck

cfi_flash: Report Advanced Sector Protection (PPB) with flinfo cmd

2013-01-10T13:40:00+00:00

Report the usage of the Advanced Sector Protection (PPB) to the user
upon 'flinfo' command. E.g:

Bank # 1: CFI conformant flash (16 x 16)  Size: 64 MB in 512 Sectors
  AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E2301
  Advanced Sector Protection (PPB) enabled
  Erase timeout: 16384 ms, write timeout: 2 ms
  Buffer write timeout: 5 ms, buffer size: 32 bytes

  Sector Start Addresses:
  FC000000 E      FC020000 E RO   FC040000 E      FC060000 E      FC080000 E
  ...

Signed-off-by: Stefan Roese 
Cc: Anatolij Gustschin 
Cc: Holger Brunck 
Tested-by: Holger Brunck

cfi_flash: Enable PPB protection for all AMD cmdset flash chips

2013-01-10T13:39:54+00:00

Not only Spansion supports the Persistent Protection Bits (PPB) locking.
Other devices like the Micron JS28F512M29EWx also support this type
of locking/unlocking. Detection of support is done in the same way as
done for the Spansion chips - via the 0x49 CFI word.

This patch enables this PPB protection mechanism for all AMD type
(AMD commandset) chips.

Signed-off-by: Stefan Roese 
Cc: Anatolij Gustschin 
Cc: Holger Brunck 
Tested-by: Holger Brunck

cfi_flash: Read PPB sector protection from device for AMD/Spansion chips

2013-01-10T13:39:48+00:00

Patch 66863b05 [cfi_flash: add support for Spansion flash PPB sector
protection] introduced the PPB (Persistent Protection Bit) locking for
Spansion chips. But right now the sector protection status (locked vs
unlocked) is set to unlocked for all sectors upon bootup. The real
sector protection status is ignored.

This patch now reads the current sector protection status and uses
it for these AMD/Spansion flash chips.

Signed-off-by: Stefan Roese 
Cc: Anatolij Gustschin 
Cc: Holger Brunck 
Tested-by: Holger Brunck

cfi_flash: Add manufact_match helper function

2013-01-10T13:39:30+00:00

Consolidate manufacturer matching into the function manufact_match()
and use it.

Signed-off-by: Stefan Roese 
Tested-by: Holger Brunck

mtd/cfi: add support for SST 4KB sector granularity

2013-01-10T13:39:13+00:00

Add support for SST 4KB sector granularity.

Many recent SST flashes, i.e. SST39VF3201B and similar of this family
are declared CFI-conformant from SST. They support CFI query, but implement
2 different sector sizes in the same memory: a 64KB sector (they call it
"block", std AMD erase cmd=0x30), and a 4KB sector (they call it "sector",
erase cmd=0x50). Also, CFI query on these chips, reading from address 0x2dh
of cfi query struct, detects a number of secotrs for the 4KB granularity
(flinfo shows it).

For all other aspects, they are CFI compliant, so, as Linux do, i think
it's a good idea to handle these chips in the CFI driver, with a fixup
to allow 4KB granularity, as should be expected, instead of 64KB.

Signed-off-by: Angelo Dureghello 
Signed-off-by: Stefan Rose

Merge branch 'master' of git://git.denx.de/u-boot-arm

2013-01-09T15:13:22+00:00

Fix SPL build for non-ARM targets

2013-01-09T13:34:40+00:00

Signed-off-by: Albert ARIBAUD

Merge branch 'master' of git://git.denx.de/u-boot-arm

2013-01-08T21:26:42+00:00