10 Jun, 2013

21 commits


08 Jun, 2013

1 commit


07 Jun, 2013

1 commit

  • The non-SPL build of U-Boot on Tegra only runs on a single CPU, and
    hence there is no need to enable the SCU when running U-Boot. If an
    SMP OS is booted, and it needs the SCU enabled, it will enable the SCU
    itself. U-Boot doing so is redundant.

    The one exception is Tegra20, where an enabled SCU is required for some
    aspects of PCIe to work correctly.

    Some Tegra SoCs contain CPUs without a software-controlled SCU. In this
    case, attempting to turn it on actively causes problems. This is the case
    for Tegra114. For example, when running Linux, the first (or at least
    some very early) user-space process will trigger the following kernel
    message:

    Unhandled fault: imprecise external abort (0x406) at 0x00000000

    This is typically accompanied by that process receving a fatal signal,
    and exiting. Since this process is usually pid 1, this causes total
    system boot failure.

    Signed-off-by: Tom Warren
    [swarren, fleshed out description, ported to upstream chipid APIs]
    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Tom Warren
     

06 Jun, 2013

2 commits

  • No need to use the 'status' variable, so just remove it.

    Signed-off-by: Fabio Estevam
    Reviewed-by: Otavio Salvador

    Fabio Estevam
     
  • When running the "save" command several times on a mx6qsabresd we see:

    U-Boot > save
    Saving Environment to MMC...
    Writing to MMC(1)... done
    U-Boot > save
    Saving Environment to MMC...
    MMC partition switch failed
    U-Boot > save
    Saving Environment to MMC...
    Writing to MMC(1)... done
    U-Boot > save
    Saving Environment to MMC...
    MMC partition switch failed
    U-Boot > save
    Saving Environment to MMC...
    Writing to MMC(1)... done
    U-Boot > save
    Saving Environment to MMC...
    MMC partition switch failed

    This issue is caused by the incorrect usage of CONFIG_SYS_MMC_ENV_PART.

    CONFIG_SYS_MMC_ENV_PART should be used to specify the mmc partition that stores
    the environment variables.

    On some imx boards it is been incorrectly used to pass the partition of kernel
    and dtb files for the 'mmcpart' script variable.

    Remove the CONFIG_SYS_MMC_ENV_PART usage and configure the 'mmcpart' variable
    directly.

    Reported-by: Jason Liu
    Signed-off-by: Fabio Estevam
    Acked-by: Jason Liu

    Fabio Estevam
     

05 Jun, 2013

3 commits

  • We need to call the save_omap_boot_params function on am33xx/ti81xx and
    other newer TI SoCs, so move the function to boot-common. Only OMAP4+
    has the omap_hw_init_context function so add ifdefs to not call it on
    am33xx/ti81xx. Call save_omap_boot_params from s_init on am33xx/ti81xx
    boards.

    Reviewed-by: R Sricharan
    Signed-off-by: Tom Rini

    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: Tom Rini

    ---
    Changes in v2:
    - Fix typo noted by Peter Korsgaard

    Tom Rini
     
  • Only called in this file, mark as static.

    Signed-off-by: Tom Rini

    Tom Rini
     

04 Jun, 2013

1 commit


03 Jun, 2013

11 commits