u-boot.git/cpu/arm926ejs/Makefile, branch v2009.01 Unnamed repository; edit this file 'description' to name the repository. ARM926EJ-S: relocate OMAP specific 'cpuinfo.c' into OMAP directory 2008-11-04T22:40:05+00:00 Roman Mashak romez777@gmail.com 2008-10-22T20:00:26+00:00 e352495318d8056a00faa21b633b3e4374bfbf52 OMAP identification is implemented in 'cpuinfo.c' and located in ARM926EJ-S directory. It makes sense to place this file in OMAP specific subdirectory, i.e. cpu/arm926ejs/omap Signed-off-by: Roman Mashak <romez777@gmail.com> 
OMAP identification is implemented in 'cpuinfo.c' and located in ARM926EJ-S directory.
It makes sense to place this file in OMAP specific subdirectory, i.e. cpu/arm926ejs/omap

Signed-off-by: Roman Mashak <romez777@gmail.com>
Move "ar" flags to config.mk to allow for silent "make -s" 2006-10-08T23:02:05+00:00 Wolfgang Denk wd@atlas.denx.de 2006-10-08T23:02:05+00:00 2b208f5308ae0c72a6840180e59ed1ab4f9b69fc Based on patch by Mike Frysinger, 20 Jun 2006 
Based on patch by Mike Frysinger, 20 Jun 2006
Add support for a saving build objects in a separate directory. 2006-09-01T17:49:50+00:00 Marian Balakowicz m8@semihalf.com 2006-09-01T17:49:50+00:00 f93286397ed2a7084efb0362a43ee09f11702349 Modifications are based on the linux kernel approach and support two use cases: 1) Add O= to the make command line 'make O=/tmp/build all' 2) Set environement variable BUILD_DIR to point to the desired location 'export BUILD_DIR=/tmp/build' 'make' The second approach can also be used with a MAKEALL script 'export BUILD_DIR=/tmp/build' './MAKEALL' Command line 'O=' setting overrides BUILD_DIR environent variable. When none of the above methods is used the local build is performed and the object files are placed in the source directory. 
Modifications are based on the linux kernel approach and
support two use cases:

  1) Add O= to the make command line
  'make O=/tmp/build all'

  2) Set environement variable BUILD_DIR to point to the desired location
  'export BUILD_DIR=/tmp/build'
  'make'

The second approach can also be used with a MAKEALL script
'export BUILD_DIR=/tmp/build'
'./MAKEALL'

Command line 'O=' setting overrides BUILD_DIR environent variable.

When none of the above methods is used the local build is performed and
the object files are placed in the source directory.
Update omap5912osk board support 2006-05-10T08:55:16+00:00 Stefan Roese sr@denx.de 2006-05-10T08:55:16+00:00 6080a0eb63dacc85ba703dca90271be866112da6 - Fix OMAP support that omap5912osk compiles in current source tree - Update with code from "http://omap.spectrumdigital.com/osk5912" to fix problems with DDR initialization - Fix timer setup - Use CFI flash driver and support complete 32MB of onboard flash - Add "print_cpuinfo()" and "checkboard()" functions to display CPU (with frequency) and Board infos Patch by Stefan Roese, 10 May 2006 
  - Fix OMAP support that omap5912osk compiles in current source tree
  - Update with code from "http://omap.spectrumdigital.com/osk5912"
    to fix problems with DDR initialization
  - Fix timer setup
  - Use CFI flash driver and support complete 32MB of onboard flash
  - Add "print_cpuinfo()" and "checkboard()" functions to display
    CPU (with frequency) and Board infos
Patch by Stefan Roese, 10 May 2006
* Patch by George G. Davis, 19 Aug 2003: 2003-08-29T22:00:43+00:00 wdenk wdenk 2003-08-29T22:00:43+00:00 6f21347d49b1741e4b8247f5e2d3fa83ef169c25 fix TI Innovator/OMAP1510 pin configs * Patches by Kshitij, 18 Aug 2003 - add support for arm926ejs cpu core - add support for TI OMAP 1610 Innovator Board 
  fix TI Innovator/OMAP1510 pin configs

* Patches by Kshitij, 18 Aug 2003
  - add support for arm926ejs cpu core
  - add support for TI OMAP 1610 Innovator Board