Dear George,
Actually r8a7796 and r8a7795 are different chips with different
peripherals, so you should adjust your r8a7796-xxx.dtb.
I'm not really sure what the problem is with XEN 4.6, but the
crash point you are stepped in with 4.8 is commented as following
/*
* Currently, to ensure hypervisor safety, when we received a
* guest-generated vSerror/vAbort, we just crash the guest to
protect
* the hypervisor. In future we can better handle this by
injecting
* a vSerror/vAbort to the guest.
*/
So I guess you see the abort on access to a peripheral missing on
r8a7796 but described in a device tree for r8a7795.
--
Andrii Anisov
Lead
Systems Engineer
Office: +380
44 390 5457 x 66766
Cell: +380 50
5738852 Email: andrii_anisov@xxxxxxxx
Kyiv, Ukraine (GMT+3) epam.com
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s)
or entity(ies) to which it is addressed and contains
information that is legally privileged and confidential. If
you are not the intended recipient, or the person responsible
for delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. All
unintended recipients are obliged to delete this message and
destroy any printed copies.
