1. 28 9月, 2016 1 次提交
  2. 26 9月, 2016 1 次提交
  3. 24 9月, 2016 2 次提交
  4. 15 9月, 2016 11 次提交
  5. 07 9月, 2016 8 次提交
  6. 27 8月, 2016 1 次提交
  7. 03 8月, 2016 1 次提交
  8. 28 7月, 2016 2 次提交
  9. 27 7月, 2016 6 次提交
  10. 22 7月, 2016 2 次提交
    • S
      powerpc/mpc85xx: T104x: Add nand secure boot target · aa36c84e
      Sumit Garg 提交于
      For mpc85xx SoCs, the core begins execution from address 0xFFFFFFFC.
      In non-secure boot scenario from NAND, this address will map to CPC
      configured as SRAM. But in case of secure boot, this default address
      always maps to IBR (Internal Boot ROM).
      The IBR code requires that the bootloader(U-boot) must lie in 0 to 3.5G
      address space i.e. 0x0 - 0xDFFFFFFF.
      
      For secure boot target from NAND, the text base for SPL is kept same as
      non-secure boot target i.e. 0xFFFx_xxxx but the SPL U-boot binary will
      be copied to CPC configured as SRAM with address in 0-3.5G(0xBFFC_0000)
      As a the virtual and physical address of CPC would be different. The
      virtual address 0xFFFx_xxxx needs to be mapped to physical address
      0xBFFx_xxxx.
      
      Create a new PBI file to configure CPC as SRAM with address 0xBFFC0000
      and update DCFG SCRTACH1 register with location of Header required for
      secure boot.
      
      The changes are similar to
      commit 467a40df
          powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041
      
      While P3041 has a 1MB CPC and does not require SPL. On T104x, CPC
      is only 256K and thus SPL framework is used.
      The changes are only applicable for SPL U-Boot running out of CPC SRAM
      and not the next level U-Boot loaded on DDR.
      Reviewed-by: NRuchika Gupta <ruchika.gupta@nxp.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NAneesh Bansal <aneesh.bansal@nxp.com>
      Signed-off-by: NSumit Garg <sumit.garg@nxp.com>
      Reviewed-by: NYork Sun <york.sun@nxp.com>
      aa36c84e
    • S
      powerpc/mpc85xx: SECURE BOOT- Enable chain of trust in SPL · 8f01397b
      Sumit Garg 提交于
      As part of Chain of Trust for Secure boot, the SPL U-Boot will validate
      the next level U-boot image. Add a new function spl_validate_uboot to
      perform the validation.
      
      Enable hardware crypto operations in SPL using SEC block.
      In case of Secure Boot, PAMU is not bypassed. For allowing SEC block
      access to CPC configured as SRAM, configure PAMU.
      Reviewed-by: NRuchika Gupta <ruchika.gupta@nxp.com>
      Signed-off-by: NAneesh Bansal <aneesh.bansal@nxp.com>
      Signed-off-by: NSumit Garg <sumit.garg@nxp.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Reviewed-by: NYork Sun <york.sun@nxp.com>
      8f01397b
  11. 20 7月, 2016 1 次提交
  12. 16 7月, 2016 1 次提交
  13. 12 7月, 2016 3 次提交