users

users@lists.genode.org

2285 discussions

catching Socketfs Inaccessible exceptions
by Steven Harp 04 Oct '17

04 Oct '17

Experimenting with the VFS socket plugin, I'm tripping over an exception that I'm not sure how to handle. This is demonstrated in the "netty_tcp" test, which launches two echo servers, one listening on port 80, and another on port 8080. Both servers launch and become operational on about 25% of runs (under x86_64, nova kernel, QEMU, user network); on the remaining starts, one of the servers succeeds, but the other fails like this: #+BEGIN_EXAMPLE [init -> netty-server-8080] initialize server [init -> netty-server-80] initialize server [init -> netty-server-8080] sd=0 [init -> netty-server-8080] config: port=8080 read_write=0 nonblock=0 [init -> netty-server-8080] setsockopt: SO_REUSEADDR not yet implemented - always true [init -> netty-server-80] sd=0 [init -> netty-server-80] config: port=80 read_write=0 nonblock=1 [init -> netty-server-80] setsockopt: SO_REUSEADDR not yet implemented - always true [init -> netty-server-80] Error: plugin()->open("/socket/tcp/2/listen") failed [init -> netty-server-80] Error: _fd_for_type: listen file not accessible [init -> netty-server-8080] test in blocking mode [init -> netty-server-80] Error: Uncaught exception of type 'Socket_fs::Context::Inaccessible' [init -> netty-server-80] Warning: abort called - thread: ep [init] child "netty-server-80" exited with exit value 1 #+END_EXAMPLE Empirically, it appears that the server that gets past "setsockopt:..." first will become operational--the other server usually will not. The order seems to be non-deterministic. Its not clear how to catch the 'Socket_fs::Context::Inaccessible' exception in the netty server code, or even if that is an appropriate response. Suggestions? - Steve Harp

2 1

UEFI support for x86
by Edward Sandberg 02 Oct '17

02 Oct '17

Hello, I sent the following email to the sel4 mailing list but this may be a better fit. I built Genode 17.08 with run option "image/uefi" and platform option "sel4_x86_32". I have tried booting the resulting image on a variety of machines but am not getting the behavior I expect. The machines I have tried are: * Up board (a Windows compatible Atom-based system) * Dell M3800 laptop * Dell Latitude 7280 laptop * HP ProLiant DL380 Gen9 Server * Dell Optoplex 990 * Asus P9X79 WS Motherboard with Intel Core i7-3930K The furthest I have gotten was on the UP board, which only supports UEFI boot: https://www.intel.com/content/www/us/en/support/emerging-technologies/intel… I saw serial output but no graphical output (see below). The other machines I tried to boot on didn't even give me serial output. The serial output seems to indicate that an attempt to create a framebuffer failed. Is this the correct build procedure? What hardware have you used to test UEFI boot? Does the trace below suggest any experiments to try? ***************************************************************** WARNING: no console will be available to OS Bender: Hello World. Boot config: parsing cmdline '' Boot config: console_port = 0x3f8 Boot config: debug_port = 0x3f8 Boot config: disable_iommu = false Boot config: parsing cmdline 'sel4 disable_iommu' Boot config: console_port = 0x3f8 Boot config: debug_port = 0x3f8 Boot config: disable_iommu = true module #0: start=0xeaba000 end=0xf0ff968 size=0x645968 name='image.elf' Physical Memory Region from 0 size 8f000 type 1 Physical Memory Region from 8f000 size 1000 type 4 Physical Memory Region from 90000 size e000 type 1 Physical Memory Region from 9e000 size 2000 type 2 Physical Memory Region from 100000 size 1ef00000 type 1 Adding physical memory region 0x100000-0x1f000000 Physical Memory Region from 1f000000 size 1200000 type 2 Physical Memory Region from 20200000 size 3af29000 type 1 Physical Memory Region from 5b129000 size 30000 type 2 Physical Memory Region from 5b159000 size 25000 type 3 Physical Memory Region from 5b17e000 size 5d2000 type 4 Physical Memory Region from 5b750000 size 2b9000 type 2 Physical Memory Region from 5ba09000 size 79000 type 20 Physical Memory Region from 5ba82000 size 57e000 type 1 Physical Memory Region from e0000000 size 4000000 type 2 Physical Memory Region from fea00000 size 100000 type 2 Physical Memory Region from fec00000 size 1000 type 2 Physical Memory Region from fed01000 size 1000 type 2 Physical Memory Region from fed03000 size 1000 type 2 Physical Memory Region from fed06000 size 1000 type 2 Physical Memory Region from fed08000 size 2000 type 2 Physical Memory Region from fed1c000 size 1000 type 2 Physical Memory Region from fed80000 size 40000 type 2 Physical Memory Region from fee00000 size 1000 type 2 Physical Memory Region from ffc00000 size 400000 type 2 Kernel loaded to: start=0x200000 end=0x281000 size=0x81000 entry=0x20007e ACPI: RSDP paddr=0x3c490 ACPI: RSDP vaddr=0xdfc3c490 ACPI: RSDT paddr=0x5b161028 ACPI: RSDT vaddr=0xdfd61028 ACPI: FADT paddr=0x5b1611a8 ACPI: FADT vaddr=0xdfd611a8 ACPI: FADT flags=0x421 ACPI: MADT paddr=0x5b177380 ACPI: MADT vaddr=0xdfd77380 ACPI: MADT apic_addr=0xfee00000 ACPI: MADT flags=0x1 ACPI: MADT_APIC apic_id=0x0 ACPI: MADT_APIC apic_id=0x2 ACPI: MADT_APIC apic_id=0x4 ACPI: MADT_APIC apic_id=0x6 ACPI: MADT_IOAPIC ioapic_id=1 ioapic_addr=0xfec00000 gsib=0 ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x0 ACPI: MADT_ISO bus=0 source=9 gsi=9 flags=0xd ACPI: 4 CPU(s) detected Detected 1 boot module(s): ELF-loading userland images from boot modules: size=0xd87000 v_entry=0x2000000 v_start=0x2000000 v_end=0x2d87000 p_start=0xf100000 p_end=0xfe87000 Moving loaded userland images to final location: from=0xf100000 to=0x281000 size=0xd87000 Starting node #0 with APIC ID 0 Starting node #1 with APIC ID 2 Starting node #2 with APIC ID 4 Starting node #3 with APIC ID 6 Booting all finished, dropped to user space virtual address layout of core: overall [00002000,c0000000) core image [02000000,02d87000) ipc buffer [02d87000,02d88000) boot_info [02d88000,02d8a000) stack area [40000000,50000000) Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet :phys_alloc: Allocator 0x2800df8 dump: Block: [00200000,00201000) size=4K avail=0 max_avail=0 Block: [00201000,00202000) size=4K avail=0 max_avail=0 Block: [00202000,00203000) size=4K avail=0 max_avail=0 Block: [00203000,00204000) size=4K avail=0 max_avail=0 Block: [00204000,00205000) size=4K avail=0 max_avail=0 Block: [00205000,00206000) size=4K avail=0 max_avail=0 Block: [00206000,00207000) size=4K avail=0 max_avail=0 Block: [00207000,00208000) size=4K avail=0 max_avail=0 Block: [00208000,00209000) size=4K avail=0 max_avail=0 Block: [00209000,0020a000) size=4K avail=0 max_avail=0 Block: [0020a000,0020b000) size=4K avail=0 max_avail=0 Block: [0020b000,0020c000) size=4K avail=0 max_avail=0 Block: [0020c000,0020d000) size=4K avail=0 max_avail=0 Block: [01008000,01009000) size=4K avail=0 max_avail=0 Block: [01009000,0100a000) size=4K avail=0 max_avail=0 Block: [0100a000,0100b000) size=4K avail=0 max_avail=0 Block: [0100b000,0100c000) size=4K avail=0 max_avail=0 Block: [0100c000,0100d000) size=4K avail=0 max_avail=0 Block: [0100d000,0100e000) size=4K avail=0 max_avail=0 Block: [0100e000,0100f000) size=4K avail=0 max_avail=0 Block: [0100f000,01010000) size=4K avail=0 max_avail=0 Block: [01010000,01011000) size=4K avail=0 max_avail=0 Block: [01011000,01012000) size=4K avail=0 max_avail=0 Block: [01012000,01013000) size=4K avail=0 max_avail=0 Block: [01013000,01014000) size=4K avail=0 max_avail=0 Block: [01014000,01015000) size=4K avail=0 max_avail=0 Block: [01015000,01016000) size=4K avail=0 max_avail=0 Block: [01016000,01017000) size=4K avail=0 max_avail=0 Block: [01017000,01018000) size=4K avail=0 max_avail=0 Block: [01018000,01019000) size=4K avail=0 max_avail=0 Block: [01019000,0101a000) size=4K avail=0 max_avail=0 Block: [0101a000,0101b000) size=4K avail=0 max_avail=0 Block: [0101b000,0101c000) size=4K avail=0 max_avail=0 Block: [0101c000,0101d000) size=4K avail=0 max_avail=0 Block: [0101d000,0101e000) size=4K avail=0 max_avail=0 Block: [0101e000,0101f000) size=4K avail=0 max_avail=0 Block: [0101f000,01020000) size=4K avail=0 max_avail=0 Block: [01020000,01021000) size=4K avail=0 max_avail=0 Block: [01021000,01022000) size=4K avail=0 max_avail=0 Block: [01022000,01023000) size=4K avail=0 max_avail=0 Block: [01023000,01024000) size=4K avail=0 max_avail=0 Block: [01024000,01025000) size=4K avail=0 max_avail=0 Block: [01025000,01026000) size=4K avail=0 max_avail=0 Block: [01026000,01027000) size=4K avail=0 max_avail=0 Block: [01027000,01028000) size=4K avail=0 max_avail=0 Block: [01028000,01029000) size=4K avail=0 max_avail=0 Block: [01029000,0102a000) size=4K avail=0 max_avail=0 Block: [0102a000,0102b000) size=4K avail=0 max_avail=0 Block: [0102b000,0102c000) size=4K avail=0 max_avail=0 Block: [0102c000,0102d000) size=4K avail=0 max_avail=400M Block: [0102d000,0102e000) size=4K avail=0 max_avail=0 Block: [0102e000,0102f000) size=4K avail=0 max_avail=0 Block: [0102f000,01030000) size=4K avail=0 max_avail=0 Block: [01030000,01031000) size=4K avail=0 max_avail=0 Block: [01031000,01032000) size=4K avail=0 max_avail=0 Block: [01032000,01033000) size=4K avail=0 max_avail=0 Block: [01033000,01034000) size=4K avail=0 max_avail=0 Block: [01034000,01035000) size=4K avail=0 max_avail=0 Block: [01035000,01036000) size=4K avail=0 max_avail=0 Block: [01036000,01037000) size=4K avail=0 max_avail=0 Block: [01037000,01038000) size=4K avail=0 max_avail=0 Block: [01038000,01039000) size=4K avail=0 max_avail=0 Block: [01039000,0103a000) size=4K avail=0 max_avail=0 Block: [0103a000,0103b000) size=4K avail=0 max_avail=0 Block: [0103b000,0103c000) size=4K avail=0 max_avail=0 Block: [0103c000,0103d000) size=4K avail=0 max_avail=0 Block: [0103d000,0103e000) size=4K avail=0 max_avail=0 Block: [0103e000,0103f000) size=4K avail=0 max_avail=0 Block: [0103f000,01040000) size=4K avail=0 max_avail=0 Block: [01040000,01041000) size=4K avail=0 max_avail=0 Block: [01041000,01042000) size=4K avail=0 max_avail=0 Block: [01042000,01043000) size=4K avail=0 max_avail=0 Block: [01043000,01044000) size=4K avail=0 max_avail=0 Block: [01044000,01045000) size=4K avail=0 max_avail=400M Block: [01045000,01046000) size=4K avail=0 max_avail=0 Block: [01046000,01047000) size=4K avail=0 max_avail=0 Block: [01047000,01048000) size=4K avail=0 max_avail=0 Block: [01048000,01049000) size=4K avail=0 max_avail=0 Block: [01049000,0104a000) size=4K avail=0 max_avail=0 Block: [0104a000,0104b000) size=4K avail=0 max_avail=0 Block: [0104b000,0104c000) size=4K avail=0 max_avail=0 Block: [0104c000,0104d000) size=4K avail=0 max_avail=0 Block: [0104d000,0104e000) size=4K avail=0 max_avail=0 Block: [0104e000,0104f000) size=4K avail=0 max_avail=0 Block: [0104f000,01050000) size=4K avail=0 max_avail=0 Block: [01050000,01051000) size=4K avail=0 max_avail=400M Block: [01051000,01052000) size=4K avail=0 max_avail=0 Block: [01052000,01053000) size=4K avail=0 max_avail=3756K Block: [01053000,01054000) size=4K avail=0 max_avail=0 Block: [01054000,01055000) size=4K avail=0 max_avail=3756K Block: [01055000,01400000) size=3756K avail=3756K max_avail=3756K Block: [01800000,01801000) size=4K avail=0 max_avail=400M Block: [01801000,02000000) size=8188K avail=8188K max_avail=8188K Block: [03000000,1c000000) size=400M avail=400M max_avail=400M Block: [1e000000,1ebe0000) size=12160K avail=12160K max_avail=12160K => mem_size=444485632 (423 MB) / mem_avail=444112896 (423 MB) :unused_phys_alloc:Allocator 0x28063b8 dump: Block: [00100000,00200000) size=1M avail=1M max_avail=1M Block: [0020d000,01008000) size=14316K avail=14316K max_avail=14316K Block: [01400000,01800000) size=4M avail=4M max_avail=4M Block: [02000000,03000000) size=16M avail=16M max_avail=32M Block: [1c000000,1e000000) size=32M avail=32M max_avail=32M Block: [1ebe0000,1f000000) size=4224K avail=4224K max_avail=32M Block: [fec00000,fec01000) size=4K avail=4K max_avail=4K Block: [fee00000,fee01000) size=4K avail=4K max_avail=64K Block: [ffff0000,ffffffff] size=64K avail=64K max_avail=64K => mem_size=74633216 (71 MB) / mem_avail=74633216 (71 MB) :unused_virt_alloc:Allocator 0x2807424 dump: Block: [00002000,02000000) size=32760K avail=32760K max_avail=32760K Block: [02d8a000,04d8a000) size=32M avail=0 max_avail=0 Block: [04d8a000,40000000) size=969176K avail=969176K max_avail=1792M Block: [50000000,c0000000) size=1792M avail=1792M max_avail=1792M => mem_size=2938585088 (2802 MB) / mem_avail=2905030656 (2770 MB) :virt_alloc: Allocator 0x2801e64 dump: Block: [0283e000,0283f000) size=4K avail=0 max_avail=0 Block: [0283f000,02840000) size=4K avail=0 max_avail=0 Block: [02840000,02841000) size=4K avail=0 max_avail=32M Block: [02841000,02842000) size=4K avail=0 max_avail=0 Block: [02842000,02d87000) size=5396K avail=5396K max_avail=32M Block: [02d8a000,04d8a000) size=32M avail=32M max_avail=32M => mem_size=39096320 (37 MB) / mem_avail=39079936 (37 MB) :io_mem_alloc: Allocator 0x2802edc dump: Block: [00000000,00100000) size=1M avail=1M max_avail=1M Block: [1f000000,fec00000) size=3580M avail=3580M max_avail=3580M Block: [fec01000,fee00000) size=2044K avail=2044K max_avail=18364K Block: [fee01000,ffff0000) size=18364K avail=18364K max_avail=18364K => mem_size=3775848448 (3600 MB) / mem_avail=3775848448 (3600 MB) boot module 'acpi_drv' (96740 bytes) boot module 'fb_drv' (305596 bytes) boot module 'status_bar' (114120 bytes) boot module 'init' (254488 bytes) boot module 'platform_drv' (289772 bytes) boot module 'ps2_drv' (110324 bytes) boot module 'testnit' (84060 bytes) boot module 'config' (6549 bytes) boot module 'launchpad.config' (594 bytes) boot module 'ld.lib.so' (702684 bytes) boot module 'rom_filter' (86348 bytes) boot module 'timer' (89704 bytes) boot module 'xray_trigger' (112640 bytes) boot module 'pointer' (71144 bytes) boot module 'report_rom' (101328 bytes) boot module 'nitpicker' (265900 bytes) boot module 'scout' (1703896 bytes) boot module 'liquid_fb' (248988 bytes) boot module 'launchpad' (740624 bytes) boot module 'nitlog' (124736 bytes) Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Genode 17.08 423 MiB RAM and 261142 caps assigned to init Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x1 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x2 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x4 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x8 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x10 [init] child "nitpicker_config" announces service "ROM" [init] child "acpi_report_rom" announces service "Report" [init] child "report_rom" announces service "Report" [init] child "acpi_report_rom" announces service "ROM" [init] child "report_rom" announces service "ROM" [init] child "timer" announces service "Timer" Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x20 [init -> nitpicker_config] Warning: top-level node <xray> missing in input ROM xray [init -> nitpicker_config] Warning: could not obtain input value for input xray_enabled [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 13 [init -> acpi_drv] Found MCFG [init -> acpi_drv] MCFG BASE 0xe0000000 seg 0x0 bus 0x0-0xff Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x40 Warning: unmapping of managed dataspaces not yet supported Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x80 [init] child "platform_drv" announces service "Platform" [init -> fb_drv] Found PCI VGA at 00:02.0 [init -> fb_drv] fb mapped to 0x2000 [init] child "fb_drv" announces service "Framebuffer" [init -> fb_drv] Warning: VBE Bios not present [init -> fb_drv] Warning: Could not set vesa mode 0x0@...64... [init -> ps2_drv] Error: no data available [init -> nitpicker] Error: Framebuffer-session creation failed (ram_quota=8192, cap_quota=3) [init -> nitpicker] Error: __cxa_guard_abort called Kernel: Thread 'ep' died because of an uncaught exception [init -> nitpicker] Error: Uncaught exception of type 'Genode::Service_denied' [init -> nitpicker] Warning: abort called - thread: ep [init] child "nitpicker" exited with exit value 1 [init -> ps2_drv] Error: no data available [init -> ps2_drv] i8042: self test failed (0x23) [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Warning: scan code setting not supported [init -> ps2_drv] Using keyboard with scan code set 1 [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Warning: could not reset mouse (missing ack) [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Warning: could not reset mouse (unexpected response) [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Warning: could not enable stream [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Error: failed to read from port [init -> ps2_drv] Error: failed to read from port [init -> platform_drv] PS2 uses IRQ, vector 0x1 [init -> platform_drv] PS2 uses IRQ, vector 0xc [init] child "ps2_drv" announces service "Input"

2 1

ahci_drv default writeable?
by Steven Harp 27 Sep '17

27 Sep '17

Noticed that in 17.08 (and 17.05) these examples failed w. x86/nova - run/libc_vfs_fs_fat - run/libc_vfs_fat apparently because: [init -> ahci_drv] read-only session opened at device 0 for 'test-libc_vfs -> 0' so e.g., mkdir fails with EPERM. Hacking libports/run/libc_vfs_filesystem_test.inc to add writeable="yes" to the "ahci_drv" component configuration: <config> <policy label_prefix="test-libc_vfs" device="0" writeable="yes"/> <policy label_prefix="vfs" device="0" writeable="yes" /> </config> suffices, but maybe this is not appropriate. Was the default policy intended to be writeable="yes" for this driver? // Steve Harp

2 1

VirtualBox with Networking
by Chris Rothrock 26 Sep '17

26 Sep '17

I have been able to make a working environment with Genode/NOVA/VirtualBox a single VM running TinyCore with networking enabled and can communicate across the network. So far, only on VirtualBox 4, 5 still has issues that I am still trying to work out that I will get into at a later time but my goal is multiple VMs with networking. With VirtualBox 4, I have successfully made two VM environments and both VMs see eth0, I can assign an IP address to each but neither VM can communicate outside their own VM. Unlike with the single VM, I was unsuccessful to get an IP via DHCP (hence why I used a static IP), they could not ping the other VM, they could not ping anything on the network to which they were attached. Is there a setting in the test.vbox file different than for a single VM mode that I need to make to make the bridge work for this? -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

3 5

config syntax in hw_gpio_drv?
by Steven Harp 25 Sep '17

25 Sep '17

In Genode 17.08 (master) on rpi platform with hw (or foc) base, run/lxip_udp_echo seems to generate config XML that doesn't quite pass the syntax check: * * * genode build completed var/run/lxip_udp_echo/genode/config:31: parser error : AttValue: " or ' expected <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:31: parser error : attributes construct error <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:31: parser error : Couldn't find end of Start Tag resource line 31 <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:32: parser error : AttValue: " or ' expected <provides><service name=\"Gpio\"/></provides> ^ var/run/lxip_udp_echo/genode/config:32: parser error : attributes construct error <provides><service name=\"Gpio\"/></provides> ^ var/run/lxip_udp_echo/genode/config:32: parser error : Couldn't find end of Start Tag service line 32 <provides><service name=\"Gpio\"/></provides> ^ Error: Invalid XML syntax in var/run/lxip_udp_echo/genode/config Makefile:309: recipe for target 'run/lxip_udp_echo' failed * * * The extraneous reversed virgules in the attribute values appear only for hw_gpio_drv: <start name="hw_gpio_drv"> <resource name=\"RAM\" quantum=\"4M\"/> <provides><service name=\"Gpio\"/></provides> <config/> </start> 1. Suggestions? 2. Is it reasonable to suppose this should run okay on RPI-version (v1,2,3?) hardware? // Steve Harp

2 2

Porting third-party code to Genode
by Jörg-Christian Böhme 25 Sep '17

25 Sep '17

My setup/environment: - Source: Branch: master commit 0adbd1ce2428dadffc61664d93ec394d5b0e6722 Date: Wed Aug 30 12:42:42 2017 +0200 - Target-genode-System: nova x86_64 - Host-System: genode-x86-gcc (GCC) 6.3.0 Ubuntu 17.04 QEMU emulator version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.3) Hi, I read the documentation about Native Genode port of a library from the gnode website[1]. It looks very easy to "create a port" of a library for genode. I started to port a library and I have realized what is meant by Chapter "Creating the build Makefile". This Chapter says, that I should create a build (Makefile) for the third party source code ? I was expected that the port mechanism from genode will execute the configure script (Cross compiling) of the third party just as the "source based" Linux/UNIX (FreeBSD/Arch Linux) systems does. I investigate for example how libssh is ported and I see that in genode/repos/libports/lib/mk/libssh.mk every source file are added. For such a small lib it is easy but for a bigger lib like Qt5, I see there are helper scripts to generate the port mk for genode ? I didn't use "Makefiles" in my projects. I'm a cmake user :-). So my knowledge about Makefiles are very poor. Maybe I missed something. My question: It is not possible to execute the "third party build system" to cross compile it for genode? My port idea/work: I didn't see any information about boost on the "Future Challenges of the Genode project"[2] or "Genode Porting Wishlist"[3] site, so I try to port boost to genode. Maybe somebody is also working on this? Cheers Jörg [1] http://genode.org/documentation/developer-resources/porting_libraries [2] https://genode.org/about/challenges [3] http://usr.sysret.de/jws/genode/porting_wishlist.html

3 2

SDIO Interface for SDCard
by George Joseph 25 Sep '17

25 Sep '17

Hi, I was trying to understand the sdio interfacing. Then I looked into the sdcard driver written for imx6. I was able to successfully built and run it on the platform. When I looked deeper into the code I see the sd host controller interface is written part of sd card driver. I was confused ,shouldn't the sdio driver including the DMA support be a independent service than coupled with a user space sd card service? Since sdio can be used for interfacing other modules like wireless,audio,etc, I believe it should be part of the core modules. I may be wrong about this. I would like to do the whole the sdio interfacing in Genode.More help will be appriciated. :) Thanks for the help Regards George +91-7674068356

1 0

Custom InputMethod for QtVirtualKeyboard
by Johannes Kliemann 21 Sep '17

21 Sep '17

Hi Christian, I tried to implement a custom InputMethod for the QtVirtualKeyboard. But I couldn't find any useful information on how to do this. Beside the Technical Guide [1] for the keyboard there seems to be no documentation on how to do this. I have implemented my custom InputMethod class in QML (based on the example) but I failed to find any useful information on how to activate it. The part Activating an Input Method [2] is not helpful at all since it only links to the class references of the InputEngine (which neither explain where or how to use the custom class). Do you have any idea? Regards, Johannes [1]: https://doc.qt.io/qt-5/technical-guide.html [2]: https://doc.qt.io/qt-5/technical-guide.html#activating-an-input-method

2 1

i.MX6 Wand-Quad drivers
by Steven Harp 15 Sep '17

15 Sep '17

Hello: What is the current scope of driver support in Genode 17.08 for the peripheral devices on the Wand-Quad board? - Ethernet (Atheros)? - USB controllers? - Wi-Fi (Broadcom)? - Bluetooth (Broadcom)? - Vivante GPUs / framebuffer? - SDIO? - GPIO? Anybody currently working on these?

2 1

cli_monitor vs launcher vs launchpad
by Jörg-Christian Böhme 08 Sep '17

08 Sep '17

My setup/environment: - Source: Branch: staging commit 17f3b559735027bcbde233ebacbb1f9d173a566c Date: Thu Aug 3 09:44:17 2017 -0500 - Target-genode-System: nova x86_64 - Host-System: genode-x86-gcc (GCC) 6.3.0 Ubuntu 17.04 QEMU emulator version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.3) Hi, I try to understand the difference between cli_monitor, launcher, launchpad and qt-launchpad. I looked into the source code and I understand following: - app/cli_monitor is the command line version to start child processes. It exists in the low-level OS components repo. - app/launcher is the UI version of cli_monitor and uses some headers from cli_monitor. It exists in the gems repo. - app/launchpad is the UI version to start child processes. Launchpad is not using the cli_monitor headers. It exists in the demo repo. - app/qt5/qt_launchpad is the Qt version of launchpad. It uses lib/launchpad from demo repo. It exists in the libports repo. Both cli_monitor headers and lib/launchpad using the Genode::Child and Genode::Child_policy API to managed the child compoments as described in section 8.17.2. Child management [1]. What I see between the cli_monitor/launcher and launchpad approach, that the configuration of the subsystems is different. But is there even more differences ? May I asked, what are the future plans of these "launchers"? Cli_monitor is in the OS repo and sounds like the API is what I should use to implement some "own" launchers. Launch app in gems repo, as what I understand from the email from Norman (see Friday, 4. August 2017 11:56:38 CEST from Norman Feske) this is outdated. Launchpad is in the demo repo and what I see in the git commit history, this is also the older approach to "launch" subsystems in genode, or? Here some background information, why I asked... I will use genode as a desktop system and for such a use case I need something to launch applications. I notice, that genode is currently implementing a package management and it sounds like for me, in the future I need a launcher that are flexible enough to start an application after I installed a package in genode :-) ... but step by step. I'm a C++ developer and using STL/boost etc. but for UI I use Qt/QML. The idea, I will try to develope a launcher in Qt/QML (I know there is a launchpad in Qt ... but not in QML). I still try to find out, which approach is the best: Use the lib/launchpad or cli_monitor API or develope from scratch as described in section 8.17.2. Child management [1]. Maybe I will still using the current aprroaches (launchpad etc.), it depends on the email reply :-) Cheers, Jörg [1] http://genode.org/documentation/genode-foundations-17-05.pdf

4 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users