* Pali Rohár <pali.rohar@xxxxxxxxx> [150117 09:32]: > On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote: > > * Pali Rohár <pali.rohar@xxxxxxxxx> [150117 01:21]: > > > Hello, after playing with aes and non-aes version of > > > bootloaders I found out that code which configure L3 > > > firewall must be in signed X-Loader part. So probably we > > > cannot change configuration at runtime... > > > > > > Tony, > > > any idea how to dump L3_PM_ADDR_MATCH_* registers from > > > userspace or from kernel? Now I have configured one N900 > > > with original Nokia X-Loader (where loading omap aes driver > > > cause kernel crash) and one N900 with aes X-Loader (where > > > loading omap aes driver is working). > > > > Hmm maybe give the omapconf too a try? It's at: > > > > https://github.com/omapconf/omapconf > > > > That uses /dev/mem from userspace, then you can just ioremap > > them in the kernel code if you need to do something during > > runtime. Probably best to access them with a syscon mapping > > from the aes driver. > > > > Regards, > > > > Tony > > https://github.com/omapconf/omapconf/wiki > > Legacy TI OMAP platforms (OMAP[1-2-3]) are not supported. Oh OK. Well at least you can look at the code if you want to do it from the user space :) Regards, Tony -- 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
