1. 23 Aug, 2012 2 commits
    • Liu Gang's avatar
      powerpc/corenet_ds: Get rid of the CONFIG_SRIOBOOT_SLAVE_PORTx macro · 81fa73ba
      Liu Gang authored
      When compile the slave image for boot from SRIO, no longer need to
      specify which SRIO port it will boot from. The code will get this
      information from RCW and then finishes corresponding configurations.
      
      This has the following advantages:
      	1. No longer need to rebuild an image when change the SRIO port for
      	   boot from SRIO, just rewrite the new RCW with selected port,
      	   then the code will get the port information by reading new RCW.
      	2. It will be easier to support other boot location options, for
      	   example, boot from PCIE.
      Signed-off-by: default avatarLiu Gang <Gang.Liu@freescale.com>
      Signed-off-by: default avatarAndy Fleming <afleming@freescale.com>
      81fa73ba
    • Liu Gang's avatar
      powerpc/corenet_ds: Get rid of the SRIOBOOT_MASTER build target · ff65f126
      Liu Gang authored
      Get rid of the SRIOBOOT_MASTER build target, and to support for serving as
      a SRIO boot master via environment variable. Set the environment variable
      "bootmaster" to "SRIO1" or "SRIO2" using the following command:
      
      		setenv bootmaster SRIO1
      		saveenv
      
      The "bootmaster" will enable the function of the SRIO boot master, and
      this has the following advantages compared with SRIOBOOT_MASTER build
      configuration:
      	1. Reduce a build configuration item in boards.cfg file.
      	   No longer need to build a special image for master, just use a
      	   normal target image and set the "bootmaster" variable.
      	2. No longer need to rebuild an image when change the SRIO port for
      	   boot from SRIO, just set the corresponding value to "bootmaster"
      	   based on the using SRIO port.
      Signed-off-by: default avatarLiu Gang <Gang.Liu@freescale.com>
      Signed-off-by: default avatarAndy Fleming <afleming@freescale.com>
      ff65f126
  2. 13 Aug, 2012 2 commits
  3. 09 Aug, 2012 6 commits
  4. 08 Aug, 2012 4 commits
  5. 31 Jul, 2012 9 commits
  6. 30 Jul, 2012 1 commit
  7. 20 Jul, 2012 1 commit
    • Marek Vasut's avatar
      common.h: Remove include compiler.h · 546910f8
      Marek Vasut authored
      Remove this as including it on global scale breaks a lot of things.
      This was reported by:
      Matthew McClintock <B29882@freescale.com>
      
      Fix found by:
      Tom Rini <trini@ti.com>
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Tom Rini <trini@ti.com>
      546910f8
  8. 18 Jul, 2012 2 commits
  9. 16 Jul, 2012 1 commit
  10. 11 Jul, 2012 4 commits
  11. 10 Jul, 2012 4 commits
  12. 09 Jul, 2012 4 commits
    • Stephen Warren's avatar
      tegra: define fdt_load/fdt_high variables · 63905f16
      Stephen Warren authored
      These variables act like loadaddr, but for a device tree image. Defining
      them in the environment allows boot scripts to be identical on Tegra20 and
      Tegra30, which have different memory base addresses, and hence need
      different values for these variables.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      63905f16
    • Stephen Warren's avatar
      tegra: enable bootz command · dd8ab953
      Stephen Warren authored
      bootz is just like bootm, except that it can boot a raw zImage, without
      requiring it to be wrapped inside a uImage.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      dd8ab953
    • Stephen Warren's avatar
      tegra: bootcmd: start USB only when needed · f78d348c
      Stephen Warren authored
      Instead of initializing USB as soon as bootcmd is executed, defer it
      until the first boot device that (potentially in the case of network)
      uses USB is scanned. This avoids initializing USB when booting from MMC,
      so speeds that up.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      f78d348c
    • Stephen Warren's avatar
      tegra: bootcmd enhancements · 03cddf28
      Stephen Warren authored
      Place the list of searched boot devices, file-system types, boot file
      locations/prefixes, and boot script names into variables. This allows
      the user to override them directly (e.g. to change boot order, or select
      the specific values they use) without having to edit the main bootcmd
      and script_boot variables.
      
      The default boot order is changed from USB, MMC, DHCP to MMC, USB, DHCP.
      This speeds up the typical MMC boot case. People who want USB boot can
      now edit variable boot_targets appropriately.
      
      Also, reformat BOOTCMDS_COMMON to fit within 80 columns.
      
      Potential future enhancements might be:
      * Allow boards to specify which of bootcmd_mmc0/... should be defined,
        based on the HW they contain.
      * Allow boards to influence the order that the boot targets are added
        into the boot_targets variable.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      03cddf28