u-boot.git/doc, branch v2010.12

barco: drop unsupported board configuration

2010-11-26T21:08:18+00:00

The barco board appears to be unmaintained since it was added about 5
years ago. The environment location has probably never been correct.
Drop it.

Signed-off-by: Wolfgang Denk 
Cc: Marc Leeman 
Acked-by: Stefan Roese

ERIC: drop unsupported board configuration

2010-11-26T21:08:17+00:00

The ERIC board appears to be unmaintained for more than 9 years. The
environment location has probably never been correct, and has been
definitely broken since for at least a year.  Drop it.

Signed-off-by: Wolfgang Denk 
Cc: Stefan Roese 
Cc: Swen Anderson 
Acked-by: Stefan Roese

DA850 EVM: passing maximum clock rate information to kernel

2010-11-19T21:29:11+00:00

The TI DA850/OMAP-L138/AM18x EVM can be populated with devices
having different maximum allowed CPU clock rating.

The maximum clock the chip can support can only be determined from
the label on the package (not software readable).

Introduce a method to pass the maximum allowed clock rate information
to kernel using ATAG_REVISION. The kernel uses this information to
determine the maximum cpu clock rate reachable using cpufreq.

Note that U-Boot itself does not set the CPU clock rate. The CPU
clock is setup by a primary bootloader ("UBL"). The rate setup by
UBL could be different from the maximum clock rate supported by the
device.

Signed-off-by: Sekhar Nori 
Signed-off-by: Sandeep Paulraj

DA850 EVM: add information regarding DA850 in README.davinci

2010-11-19T21:29:06+00:00

The README.davinci in documentation folder is missing information
regarding DA850 which is a supported DaVinci device.

Add this information.

Signed-off-by: Sekhar Nori 
Signed-off-by: Sandeep Paulraj

Drop support for CONFIG_SYS_ARM_WITHOUT_RELOC

2010-10-29T19:39:59+00:00

When this define was introduced, the idea was to provide a soft
migration path for ARM boards to get adapted to the new relocation
support.  However, other recent changes led to a different
implementation (ELF relocation), where this no longer works.  By now
CONFIG_SYS_ARM_WITHOUT_RELOC does not only not help any more, but it
actually hurts because it obfuscates the actual code by sprinkling it
with lots of dead and non-working debris.

So let's make a clean cut and drop CONFIG_SYS_ARM_WITHOUT_RELOC.

Signed-off-by: Wolfgang Denk 
Tested-by: Heiko Schocher 
Tested-by: Reinhard Meyer

Replace CONFIG_RELOC_FIXUP_WORKS by CONFIG_NEEDS_MANUAL_RELOC

2010-10-29T19:32:07+00:00

By now, the majority of architectures have working relocation
support, so the few remaining architectures have become exceptions.
To make this more obvious, we make working relocation now the default
case, and flag the remaining cases with CONFIG_NEEDS_MANUAL_RELOC.

Signed-off-by: Wolfgang Denk 
Tested-by: Heiko Schocher 
Tested-by: Reinhard Meyer

Coding Style cleanup

2010-10-27T20:48:30+00:00

Signed-off-by: Wolfgang Denk

VoVPN-GW_100MHz: drop unsupported board configuration

2010-10-24T13:46:08+00:00

The 100MHz configuation of the VoVPN-GW has never been supported, so
drop it now.

Signed-off-by: Wolfgang Denk

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

2010-10-23T19:59:42+00:00

post/i2c: Add ability to ignore I2C devices

2010-10-22T07:19:14+00:00

Add the ability to not report an I2C POST error for a set of given I2C
addresses on bootup.  This is useful for cases when a device may or may
not be present, and neither case is considered an error.  For example:

- Some form factors such as XMC and Compact PCI Express have an I2C
  EEPROM whose address changes based on geographical address.  Eg
  installed in one slot its EEPROM address is, 0x50, in another its
  0x51, etc.  This allows multiple devices to have their EEPROMs present
  on the same I2C bus.  Thus the I2C devices present for an XMC or
  CPCIe card depend on if and where other cards are installed in the
  same system.

- Some cards have optional I2C devices.  Eg one hardware build
  configuration has different I2C devices than another and software
  can't determine if the optional device should be present or not.

- Some cards have optional daughtercards with I2C devices on them.

- I2C EEPROMs address range depends on their size.  Its possible to
  support differently size EEPROMs by only probing the EEPROM's base
  address and ignoring the other addresses that are impacted by its
  size.

A new CONFIG_SYS_POST_I2C_IGNORES define has been added which specifies
a list of I2C addresses for the I2C POST to ignore.

Signed-off-by: Peter Tyser 
Acked-by: Heiko Schocher 
Acked-by: Wolfgang Denk 
Signed-off-by: Kumar Gala