
20 Jan
2014
20 Jan
'14
11:04 p.m.
On Mon, 2014-01-20 at 14:55 +0530, Aneesh Bansal 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