On Wed, 2012-09-05 at 14:00 +0100, Dave Martin wrote: > On Wed, Sep 05, 2012 at 04:32:01PM +0800, Guodong Xu wrote: > > Turn on CCI snoops. Data abort exception is captured and handled > > for implementations where CCI is not integrated. > > This may work for now, but it's potentially fragile. We may get > platform variants where there is some different peripheral at 0x2c090000. I agree with the 'potentially fragile' assessment, however experimentation by Guodong and me showed that the CCI must be enabled on all cores and done before the bootwrapper drops into non-secure mode. I.e. before we get the chance to enter the C code and easily parse device-tree. Perhaps there is something we need to do to get access to CCI in non secure mode? -- Tixy _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm