I've been trying to debug Genode's interrupt issues on my desktop computer
on and off for a few years now, and I've recently gathered more information
by testing some different devices and configurations that I hadn't before.
I'd already found that both usb_drv and ahci_drv waited for interrupts t
Thanks, Josef (and Sebastian). Given your reluctance to reactive
rump cgd, what better alternatives would you suggest adopting or
developing for disk and/or file-system encryption in Genode?
dm_crypt, Veracrypt, CryFS, ... ? It would be nice to have a
light-weight solution; maybe something could b
Hi,
On Tue, Sep 11, 2018 at 05:01:02PM +0800, lzSun wrote:
> Hello,
> I am using genode 18.05 and I am trying the TZ_VMM demo on imx53-qsb board. I
> encountered problem when the system is booting. The error like this:
>
>
> [init -> tz_vmm] Start virtual machine ...
Hi,
On Mon, Sep 10, 2018 at 04:44:14PM +0800, lzSun wrote:
> Hello,
> I am new to Genode and the version I am using is 18.05. I am trying to boot
> genode on the secure world and linux on normal world on i.MX53-QSB board. I
> follow steps in this link:
> https://sourceforge.net/p/genode/mailma
On 09/11/2018 12:30 AM, Steven Harp wrote:
>
> Is rump_cgd (block encrypted devices introduced ~14.05) still
> supported/operational in Genode 18.x? Issue #2224 mentions
> "not converted" in transition to new base API [1], and #2778 seems
> to have removed the 'tool/rump' script (which was handy
Hello,
I am using genode 18.05 and I am trying the TZ_VMM demo on imx53-qsb board. I
encountered problem when the system is booting. The error like this:
[init -> tz_vmm] Start virtual machine ...
[init -> tz_vmm] Error:
Hello Steven,
* Steven Harp [2018-09-10 17:30:14 -0500]:
> Is rump_cgd (block encrypted devices introduced ~14.05) still
> supported/operational in Genode 18.x? Issue #2224 mentions
> "not converted" in transition to new base API [1], and #2778 seems
> to have removed the 'tool/rump' script (whi
I've had issues with interrupts on Genode on my desktop computer with an
AMD chipset. In particular, the USB and AHCI drivers both get stuck waiting
for interrupts. However, the VESA framebuffer driver works fine. I have
tried using ACPICA to solve my issues, but with no success.
I recently bought
