Re: exploring Mesa in Genode

Hi Jamey! Welcome to Genode. I'm also interested in 3D and GPU architecture, though not doing much Genode hacking recently. I suggest that you use the NOVA or Fiasco.OC kernels because they're the primary platforms. Could you elaborate on what you mean by a multi-process 3D? >From the architectur

Re: ahci + network

On Tue, Mar 11, 2014 at 8:52 PM, Sartakov A. Vasily wrote: > Ok, let I check again, because nothing happened and I still stuck in QEMU Try using the "q35" machine in qemu which emulates ICH9 intel chipset, it has fixed some ACPI interrupts in the past. Though back then we used Fiasco.OC which onl

Re: Bringing up Genode run/nested_init on a Beaglebone.

On Sun, Aug 25, 2013 at 8:18 PM, Bob Stewart wrote: > I'm try to get a basic Genode setup working on a Beaglebone Black (TI > AM335x processor). I'm using a version of u-boot specifically built for the > Beaglebone Black from Robert Nelson's eewiki pages. The only modification I > made was to all

Re: Genode Source building

On Tue, Aug 20, 2013 at 3:15 PM, Venkada Ramanujam < venkadaramanu...@gmail.com> wrote: > > Hi, > > Complete building and installation for Genode source code is not > available. So can i follow below steps. will it work ? > > 1.Extracting available genode.iso > 2.compile only particular code

Re: issue while running l4linux on fiasco_x86_32

Hi! Could you please explain why Genode freezes silently in this case instead of throwing a runtime config parsing error? 2013/5/24 Stefan Kalkowski > Hi Raja, > > to me it seems you've hit a recent bug, have a look at issue #744: > > https://github.com/genodelabs/genode/issues/744 > > On Gen

Re: Nic Driver performance

2013/5/18 Norman Feske > Hi Alexander, > > Hello Norman! Thank you for your comprehensive email which answered many questions I had about Genode current state! > > In short, the system executes a CPU-bounded workload spends a lot of > time in the idle thread, which is a contradiction. On CPU-bo

Re: failing in getting ipxe souce

2013/5/17 Raja Sekhar > > Hi, Raja Sekhar! As for ipxe, check your internet connection, because for me, ipxe.org opens fine. For qoost,download its source code manually (google it) and put the tarball where it is expected if you need it. Otherwise, do a "touch contrib/qoost-ce3d328928" It's a

Nic Driver performance

Hi, Genode hackers! I've been debugging the performance of the network under Genode. I am using Genode on X86 with the dde_ipxe nic driver. So far, I have figured out the following: 1. Memcpy and malloc calls in the nic driver take a negligible amount of time. I'm using X86 rdtsc to measure tick

Re: how to install Genode on PC machine

2013/4/15 Ivan Loskutov > I've upload ipxe to github > https://github.com/Ksys-labs/ipxe/tree/boot_l4linux > > First you need build ipxe. > Go to ipxe source folder. If you would like to have autoboot you need > embedd start script for ipxe. Create script boot.ipxe with context like > this: > #!

Re: Using C++11 by default

2013/3/23 Norman Feske : > Hello, > > I would like to go with the times and switch Genode to use C++11 by > default. This will enable us to solve a number of problems in a more > elegant way, e.g., by using variadic templates for the RPC framework, we > can possibly get rid of the current limit of

Re: Interrupts in L4Linux

2013/3/18 Sebastian Sumpf : > Hi Alexander, > > On 03/18/2013 04:51 PM, Alexander Tarasikov wrote: >> Hello, Genode Hackers! >> >> I'm currently implementing an X86 PCI bus driver for L4Linux as a >> temporary solution for >> getting USB support i

Re: omap4 gpiomux driver

2013/1/24 Norman Feske > Hi Alexander, > > thanks for sharing your work. > > Hi Norman, Thank you for your response > > I would like to receive the following comments: > > * does it make sense to make separate MUX drivers for each SoC given how > > specific they are > > or do we make it pa

omap4 gpiomux driver

Hi, Genode hackers! I'm just letting you know I've written the initial implementation of the GPIO pinmux driver for omap4. So that if someone needs it, you don't have to start from scratch. The driver is in our 'tuna-hacks' branch. Currently, it's quite dirty (even the extra file from u-boot got

Re: Trouble porting linux driver to DDE Kit

> This may have something to do with > https://github.com/genodelabs/genode/issues/332 which is still not > completely fixed, there is a race between the interrupt thread creation > in dde-kit and the driver. Can you try if the attached patch changes > anything? > > Hi! Thanks for the reply, but un

Re: Trouble porting linux driver to DDE Kit

Hi again! I've now have another kind of a problem. While you can clearly see that we now have the control endpoint working and the device (with the zero gadget) is detected by the host. However, it seems like non-control endpoints are still malfunctioning. Take a look at the log. To me, endpoint