Dear "aneesh.bansal@freescale.com",
In message 680c371d651d49a08b33ddd4d01fb3bd@DM2PR03MB415.namprd03.prod.outlook.com you wrote:
In case of secure boot, boot from NAND is ramboot. It was removed by some other commit. So defining it again.
In case of not-secure-boot, it's not ramboot.
What user of CONFIG_SYS_RAMBOOT are you concerned about? Many of them look like this:
#elif !defined(CONFIG_SYS_RAMBOOT) && defined(CONFIG_SECURE_BOOT)
...which doesn't make sense if secure boot is always considered ramboot.
-Scott
CONFIG_SYS_RAMBOOT is for secure boot from NAND, SPI and SD.
This is a misuse of the variable. The established meaning does NOT include booding from standard boot media like NAND, SPI and SD. It refers to booting from RAM "directly", after the image has been placed into RAM by "external" means, say by a JTAG debugger, or by copying it to a PCI card's memory.
Please avoid such misleading usage.
Best regards,
Wolfgang Denk