Hi John, On 14.07.2016 15:23, john stokes wrote: > thank you for your suggestion. but my basic aim to see the l4android > running so i am concentrating on that nitpicker is a GUI component > hence i can correct it later.
in your scenario, nitpicker is the only component that accesses the physical framebuffer (provided by the VESA driver). L4Android merely accesses a virtual framebuffer. The framebuffer and input sessions of L4Android are routed to a nit_fb instance called "android_fb". This nit_fb component, in turn, tries to open a nitpicker session to display the virtual tramebuffer on screen. Since you left nitpicker unconfigured, it won't display anything from "android_fb" on screen. Regards Norman -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
