On 01/29/2016 12:54 PM, Marc Zyngier wrote:
By the look of it, you're trying to use a GICv3 firmware, and pass a GICv2 DT to the kernel. Do not do that. Either you use a GICv2 firmware (having spoken to the ATF guys, there is a GICv2 driver in there that should work for your case) and pass a GICv2 DT, or you go GICv3 all the way. A mix of the two things is completely unsupported on the model, and solidly places you in the UNPREDICTABLE category when running that on actual HW...
Once we upgrade to ATF 1.2 we will remove all of our GICv2 stuff and see if everything works smoothly; till then, at least, we seem to have a workaround in place for development that will let us keep moving forward. From the ATF docs it does seem that using a v3 GIC in v2 compatibility mode should be supported, but it's not pressing from our side to drill any deeper to try to see why it's not actually working correctly for us (though I'd be happy to try any further testing in this configuration if that's helpful). Thanks! -- Chris Metcalf, EZChip Semiconductor http://www.ezchip.com _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
