Catalin Marinas <catalin.marinas@xxxxxxx> writes: > On Thu, Nov 15, 2012 at 12:41:43PM +0000, Siarhei Siamashka wrote: >> BTW, I always wondered about what could be preventing TI and the other >> silicon vendors from using something like an SMC API based on >> asymmetric cryptography? My understanding is that for OMAP4 GP chips, >> ROM code switches to non-secure mode before passing control to the >> bootloader and there is simply no way to workaround bugs like this. > > AFAIK, there are some SMCs to the OMAP secure firmware that allow such > bits to be set (see omap4_l2x0_set_debug() for example). I'm not sure > they are documented. The trouble with OMAP is that the secure ROM API only allows access to a tiny subset of the registers we'd need. In part this can be explained by the important OMAP customers all using the HS chips with full access to secure mode. -- Måns Rullgård mans@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
