1. 30 7月, 2013 7 次提交
  2. 27 7月, 2013 3 次提交
  3. 27 6月, 2013 1 次提交
  4. 21 6月, 2013 1 次提交
  5. 18 6月, 2013 1 次提交
  6. 08 6月, 2013 1 次提交
    • P
      am335x: enable falcon boot mode for mmc (raw and fat) and nand · 12d7a474
      Peter Korsgaard 提交于
      Jump into full u-boot mode if a 'c' character is received on the uart.
      
      We need to adjust the spl bss/malloc area to not overlap with the
      loadaddr of the kernel (sdram + 32k), so move it past u-boot instead.
      
      For raw mmc, we store the kernel parameter area in the free space after
      the MBR (if used). For nand, we use the last sector of the partition
      reserved for u-boot.
      
      This also enables the spl command in the full u-boot so the kernel
      parameter area snapshot can be created.
      Signed-off-by: NPeter Korsgaard <peter.korsgaard@barco.com>
      12d7a474
  7. 06 6月, 2013 1 次提交
    • T
      am33xx/omap4+: Move SRAM_SCRATCH_SPACE_ADDR to <asm/arch/omap.h> · edfcf85a
      Tom Rini 提交于
      The location of valid scratch space is dependent on SoC, so move that
      there.  On OMAP4+ we continue to use SRAM_SCRATCH_SPACE_ADDR.  On
      am33xx/ti814x we want to use what the ROM defines as "public stack"
      which is the area after our defined download image space.  Correct the
      comment about and location of CONFIG_SPL_TEXT_BASE.
      Signed-off-by: NTom Rini <trini@ti.com>
      edfcf85a
  8. 05 6月, 2013 1 次提交
    • T
      am33xx: Correct NON_SECURE_SRAM_START/END · 320d9746
      Tom Rini 提交于
      Prior to Sricharan's cleanup of the boot parameter saving code, we
      did not make use of NON_SECURE_SRAM_START on am33xx, so it wasn't a
      problem that the address was pointing to the middle of our running SPL.
      Correct to point to the base location of the download image area.
      Increase CONFIG_SPL_TEXT_BASE to account for this scratch area being
      used.  As part of correcting these tests, make use of the fact that
      we've always been placing our stack outside of the download image area
      (which is fine, once the downloaded image is run, ROM is gone) so
      correct the max size test to be the ROM defined top of the download area
      to where we link/load at.
      Signed-off-by: NTom Rini <trini@ti.com>
      
      ---
      Changes in v2:
      - Fix typo noted by Peter Korsgaard
      320d9746
  9. 10 5月, 2013 3 次提交
  10. 10 4月, 2013 3 次提交
  11. 08 4月, 2013 1 次提交
    • B
      musb: am335x: disable bulk split-combine feature · 4de602f2
      Bin Liu 提交于
      On TI AM335x devices, MUSB has bulk split/combine feature enabled
      in the ConfigData register, but the current MUSB driver does not
      support it yet. Therefore, disable the feature for now, until the
      driver adds the support.
      
      One usecase which is broken because of this feature is that Ether
      gadget stops working in Fullspeed mode (by un-defining
      CONFIG_USB_GADGET_DUALSPEED)
      
      After desabled this feature, MUSB driver send packets in proper size
      (no more than 64 bytes) in Fullspeed mode.
      
      This has been validated with Ether gadget in Fullspeed mode on AM335x
      EVM.
      Signed-off-by: NBin Liu <b-liu@ti.com>
      4de602f2
  12. 25 3月, 2013 1 次提交
    • T
      am33xx: Add required includes to some omap/am33xx code · 98f92001
      Tom Rini 提交于
      - In arch/arm/cpu/armv7/omap-common/timer.c,
        drivers/mtd/nand/omap_gpmc.c and drivers/net/cpsw.c add #include files
        that the driver needs but had been relying on <config.h> to bring in.
      - In arch/arm/cpu/armv7/omap-common/lowlevel_init.S add <config.h>
      - In am335x_evm.h and pcm051.h don't globally include
        <asm/arch/hardware.h> and <asm/arch/cpu.h> but just <asm/arch/omap.h>
        as that is the only include which defines things the config uses.
      
      Cc: Lars Poeschel <poeschel@lemonage.de>
      Signed-off-by: NTom Rini <trini@ti.com>
      98f92001
  13. 22 3月, 2013 3 次提交
  14. 13 3月, 2013 1 次提交
  15. 11 3月, 2013 1 次提交
  16. 09 3月, 2013 2 次提交
  17. 19 2月, 2013 5 次提交
  18. 07 2月, 2013 1 次提交
    • H
      AM335X: Set fdt_high for AM335X devices to enable booting with Device Tree · f170899f
      hvaibhav@ti.com 提交于
      For AM335X boards, such as the EVM and Bone Linux kernel fails to
      locate the device tree blob on boot. The reason being is that
      u-boot is copying the DT blob to the upper part of RAM when booting
      the kernel and the kernel is unable to access the blob.
      By setting the fdt_high variable to 0xffffffff (to prevent the copy)
      the kernel is able to locate the DT blob and boot.
      
      This patch is tested on BeagleBone platform.
      Signed-off-by: NVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Tom Rini <trini@ti.com>
      f170899f
  19. 10 12月, 2012 3 次提交