On Thu, 2015-01-15 at 16:49 -0700, Stephen Warren wrote: > On 01/13/2015 12:45 PM, Ian Campbell wrote: > > In this case the secure code lives in RAM, and hence needs to be reserved, > > but > > it has been relocated, so the reservation of __secure_start does not apply. > > > > Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to reserve such a > > region. > > > > This will be used in a subsequent patch for Jetson-TK1 > > It's rather hard to review this without any documentation in the README, > of the new symbol, or any of the existing: > > CONFIG_ARMV7_NONSEC > CONFIG_ARMV7_VIRT > CONFIG_ARMV7_PSCI > > It'd be nice to have a description of what those do exactly, and how > they interact or conflict.
Anyone got any opinions in the new Kconfig-world regarding whether it is more or less appropriate to use the help section of the Kconfig file vs. the README file? ...and only now do I notice that the first two of the three options mentioned above are already documented in the Kconfig and the third (PSCI) isn't a Kconfig option (yet?) so there's no ambiguity about where it should be put. I also just noticed that the README says "Later we will add a configuration tool - probably similar to or even identical to what's used for the Linux kernel". Ian. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
