* Sebastian Reichel <sre@xxxxxxxx> [131207 10:51]: > On Sat, Dec 07, 2013 at 08:51:04AM -0800, Tony Lindgren wrote: > > * Pali Rohár <pali.rohar@xxxxxxxxx> [131207 05:58]: > > > On Saturday 07 December 2013 14:48:20 Sebastian Reichel wrote: > > > > On Sat, Dec 07, 2013 at 09:18:32AM +0100, Pali Rohár wrote: > > > > > On Saturday 07 December 2013 01:00:27 Sebastian Reichel > > > wrote: > > > > > > On Fri, Dec 06, 2013 at 02:27:25PM -0800, Tony Lindgren > > > wrote: > > > > > > > * Sebastian Reichel <sre@xxxxxxxxxx> [131206 13:37]: > > > > > > > > Nokia N900 DT boot breaks for me using 3.13-rc3. You > > > > > > > > can see the relevant kernel output below. Disabling > > > > > > > > the AES module in the omap3-n900.dts with status = > > > > > > > > "disabled" fixed the boot for me. > > > > > > > > > > > > > > OK thanks for letting me know. How about the following > > > > > > > patch to fix it? > > > > > > > > > > > > That's basically what I did to fix the problem. > > > > > > > > > > > > I guess the proper fix would be a runtime check if the > > > > > > device can be accessed (if that's possible). AFAIK it is > > > > > > possible to use the AES module on the N900 if the > > > > > > bootloader is slightly patched. > > > > > > > > > > > > Pali, can you elaborate more about this? I've seen, that > > > > > > you added a section about this on [0]. > > > > > > > > > > > > [0] http://elinux.org/N900#M-Shield > > > > > > > > > > > > -- Sebastian > > > > > > > > > > Yes, if you want to use M-Shield on Nokia N900, you need to > > > > > use new version of signed Nokia X-Loader which enable > > > > > M-Shield usage outside secure world. > > > > > > > > > > Because this updated X-Loader is not official and I think > > > > > nobody has it in n900, please disable using these M-Shield > > > > > crypto modules on n900. > > > > > > > > Is the updated X-Loader available somewhere? > > > > > > > > > > It was on mediafire server linked from this thread: > > > http://maemo.org/community/maemo-developers/n900_aes_and_sha1-md5_hw_acceleration_drivers/ > > > > > > Now it is deleted from that server, but I have copy on my HDD. > > > > Hmm OK let's hope there's some working link still around for those. > > It seems like we should eventually cover both options, but for > > the -rc cycle, we need to just disable those hardware modules in > > the .dtsi files. > > Yes. I think for -rc cycle disabling the AES module is the right > way. It has been disabled before anyway. I will test your patch > later. OK thanks. > > I think we can check the configuration from the L3 registers. > > Looks like we no longer have those defined after purging the > > unused defines a while back, but I think the registers for the > > configuration are L3_PM_READ_PERMISSION etc registers. > > I asked Pali to send me his copy of the updated NOLO bootloader, > so that I can test this. I just checked the omap documentation > (I only have access to the public one) and crypto related stuff > is not documented for the L3_PM_READ_PERMISSION register. There > are a couple of reserved bits, which may be used for this, though. > > I also CC'd Joel Fernandes, since he worked on the driver before and > may have access to the documentation. Looks like at least the 36xx public version referenced here has them: http://www.spinics.net/lists/linux-omap/msg21857.html I'd assume the registers are the same for 34xx since we don't have them defined separately in the kernel. 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
