On 06/27/2017 12:21 PM, rijure...@mpi-sws.org wrote:
> In base-hw/src/core/spec/arm_v7/trustzone/mode_transition.s,
> _nonsecure_kernel_entry:, where we go in the monitor handler after a DABT,
> we have
> mov r1, #0
> mcr p15, 0, r1, c1, c1, 0 //sets SCR all 0s
> cps #SVC_MODE //changes proce
On 06/26/2017 06:55 PM, rijure...@mpi-sws.org wrote:
> In base-hw/src/core/include/spec/imx53/trustzone/csu.h, SECURE = 0x33.
>
> So SECURE_UART = 1 in
> base-hw/src/core/include/spec/imx53_qsb/trustzone/csu_config.h should
> initialize UART as RD+WR for secure user and spvr models as given in
Hi,
On 06/26/2017 06:14 PM, rijure...@mpi-sws.org wrote:
> In os/src/server/tz_vmm/spec/imx53/main.cc, added the following enums
> (1) UART_BASE = 0x53FBC000,
> (2) UART_SIZE = 0x43FFF
>
> In os/src/server/tz_vmm/include/vm_base.h
> In Vm_base constructor, added
> (3)_ram_iomem_uart(uart_base, ua
Hi David,
On 06/29/2017 03:08 PM, David Werner wrote:
> Hi Stefan,
>
>>> As being said, this specific IRQ object is part of the SIGNAL session
>>> and its client state. I'm not sure how your restore mechanism works
>>> exactly, but if work is done within the component that gets restored,
>>> you
Hi,
Christian, thanks a lot for your speedy refactoring of the OpenVPN port to run
the OpenVPN code in the main thread. The OpenVPN code no longer blocks on
opening a socket and now tries to setup a VPN connection with the configured
server. Unfortunately we are now stumbling upon two new probl
Hi Stefan,
As being said, this specific IRQ object is part of the SIGNAL session
and its client state. I'm not sure how your restore mechanism works
exactly, but if work is done within the component that gets restored,
you can do the re-attachment there. Otherwise, you would need to change
the r
