Genode 17.05 dde_rump ISO filesystem

Hi: While evaluating file system alternatives, I ran some tests of the dde_rump file system code (Genode 17.05 master/HEAD on Ubuntu 16.04 / x86_64). The EXT2 and FAT file system tests work as expected (although the latter benefited from a ). The ISO file system however left me a puzzle (trace

Re: Networking Support in VirtualBox

The top entry from git log: commit 5e3e8073467628cd2a88fc1025be9a157f976e57 Author: Christian Helmuth Date: Wed May 31 16:05:53 2017 +0200 version: 17.05 This is the version pulled when I started with a fresh environment with the command: git clone

Re: Networking Support in VirtualBox

Chris, On Tue, Jul 25, 2017 at 09:46:52AM -0400, Chris Rothrock wrote: > The run recipe I am using is virtualbox.run. In this recipe there is no > indications that the ACPI has any configurable components. These > capabilities must be set in another file that this recipe is calling - > please

Re: Networking Support in VirtualBox

There was no arbitrary concatenation at all - this was the entirety of the log as it was transmitted across the serial port from the moment the Genode boot started with the NOVA kernel. If any concat was done, it was due to the unmodified code provided with the source. The 32 bit scenario was

Re: Using Genode 17.05 with Fiasco.OC

Hi Jörg, thank you for introducing yourself and for your interest in Genode! > I started a month ago with Gnode hello tutorial and play around with them. > Therefore, I call myself a newbie :-) > But at the end, I will use Genode on my laptop (like turmvilla example) and > start to develop some

Re: Blocking wait for interrupt

Hi Johannes, On 07/25/2017 08:54 AM, Johannes Kliemann wrote: > Hi, > > I'm currently writing a dde_linux driver that requires to wait for an > interrupt to be handled. > It basically initializes the hardware and then waits for an event to > occur. This event is usually triggered by the

Re: Networking Support in VirtualBox

Hello Chris, your log is very hard to read as it seems to arbitrarily concatenate several logs or multiple copies of the same log. I suggest you store one log file per boot of the test machine and attach the resulting file to your email in the future. I'll add some comments about what I read in

Blocking wait for interrupt

Hi, I'm currently writing a dde_linux driver that requires to wait for an interrupt to be handled. It basically initializes the hardware and then waits for an event to occur. This event is usually triggered by the interrupt (respectively its handler) which occurs after hardware initialization. My