1. 07 12月, 2011 2 次提交
  2. 16 11月, 2011 2 次提交
    • S
      omap4/5: Add support for booting with CH. · 78f455c0
      Sricharan 提交于
      Configuration header(CH) is 512 byte header attached to an OMAP
      boot image that will help ROM code to initialize clocks, SDRAM
      etc and copy U-Boot directly into SDRAM. CH can help us in
      by-passing SPL and directly boot U-boot, hence it's an alternative
      for SPL. However, we intend to support both CH and SPL for OMAP4/5.
      
      Initialization done through CH is limited and is not equivalent
      to that done by SPL. So U-Boot has to distinguish between the
      two cases and handle them accordingly. This patch takes care
      of doing this.
      Signed-off-by: Nsricharan <r.sricharan@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      78f455c0
    • S
      omap5: Add minimal support for omap5430. · 508a58fa
      Sricharan 提交于
      This patch adds the minimal support for OMAP5. The platform and machine
      specific headers and sources updated for OMAP5430.
      
      OMAP5430 is Texas Instrument's SOC based on ARM Cortex-A15 SMP architecture.
      It's a dual core SOC with GIC used for interrupt handling and SCU for cache
      coherency.
      
      Also moved some part of code from the basic platform support that can be made
      common for OMAP4/5. Rest is kept out seperately. The same approach is followed
      for clocks and emif support in the subsequent patches.
      Signed-off-by: Nsricharan <r.sricharan@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      508a58fa
  3. 28 10月, 2011 1 次提交
  4. 01 10月, 2011 2 次提交
  5. 03 8月, 2011 4 次提交
    • A
      omap: add MMC and FAT support to SPL · 8cf686e1
      Aneesh V 提交于
      - Add MMC raw and FAT mode boot support for OMAP
      - Provide a means by which parameters passed by ROM-code
        can be saved in u-boot.
      - Save boot mode related information passed by OMAP4 ROM-code
        and use it to determine where to load the u-boot from
      - Assumes that the image has a mkimage header. Gets the
        payload size and load address from this header. If the
        header is not detected assume u-boot.bin as payload
      Signed-off-by: NAneesh V <aneesh@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      8cf686e1
    • A
      omap: add basic SPL support · bcae7211
      Aneesh V 提交于
      - Provide alternate implementations of board_init_f()
        board_init_r() for OMAP spl.
      - Provide linker script
      - Initialize global data
      - Add serial console support
      - Update CONFIG_SYS_TEXT_BASE to allow for SPL's bss and move
        it to board config header from config.mk
      Signed-off-by: NAneesh V <aneesh@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      bcae7211
    • A
      omap4: add clock support · 3776801d
      Aneesh V 提交于
      Add support for:
      1. DPLL locking
      2. Initialization of clock domains and clock modules
      3. Setting up the right voltage on voltage rails
      
      This work draws upon previous work done for x-loader by:
      	Santosh Shilimkar <santosh.shilimkar@ti.com>
      	Rajendra Nayak <rnayak@ti.com>
      Signed-off-by: NAneesh V <aneesh@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      3776801d
    • A
      omap4: utility function to identify the context of hw init · d2f18c27
      Aneesh V 提交于
      The basic hardware init of OMAP4(s_init()) can happen in 4
      different contexts:
       1. SPL running from SRAM
       2. U-Boot running from FLASH
       3. Non-XIP U-Boot loaded to SDRAM by SPL
       4. Non-XIP U-Boot loaded to SDRAM by ROM code using the
          Configuration Header feature
      
      What level of hw initialization gets done depends on this
      context. Add a utility function to find this context.
      Signed-off-by: NAneesh V <aneesh@ti.com>
      Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>
      d2f18c27
  6. 20 5月, 2011 1 次提交
  7. 28 4月, 2011 1 次提交
  8. 20 1月, 2011 1 次提交
  9. 14 1月, 2011 6 次提交
  10. 12 11月, 2010 2 次提交
  11. 19 10月, 2010 1 次提交
  12. 02 8月, 2010 1 次提交
  13. 13 4月, 2010 1 次提交
  14. 13 2月, 2010 1 次提交
    • J
      prepare joining at91rm9200 into at91 · 98250e8e
      Jens Scharsig 提交于
      * prepare joining at91 and at91rm9200
       * add modified copy of soc files to cpu/arm920t/at91 to make
         possible to compile at91rm9200 boards in at91 tree instead
         of at91rm9200
       * add header files with c structure defs for AT91 MC, ST and TC
       * the new cpu files are using at91 c structure soc access
       * please read README.soc-at91 for details
      Signed-off-by: NJens Scharsig <js_at_ng@scharsoft.de>
      98250e8e
  15. 31 10月, 2008 1 次提交
  16. 24 10月, 2008 1 次提交