Re: runtime check for omap-aes bus access permission (was: Re: 3.13-rc3 (commit 7ce93f3) breaks Nokia N900 DT boot)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

-- 
Pali Rohár
pali.rohar@xxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux