users

users@lists.genode.org

1 participants
2310 discussions

Changing the Genode directory layout regarding aSPECts
by Stefan Kalkowski 08 Sep '15

08 Sep '15

Hello, as discussed in the issue "Apply SPEC approach consequently to all repositories" [1], I have changed the directory layout of Genode's source tree accordingly [2]. The commit will probably enter the staging branch soon. Therefore, the question for all Genode developers arises, what needs to be taken into account. First, when you rebase to to the new directory layout, it is strongly recommended to fully clean your build directories before compiling again. Moreover, the top-level Makefile within the build-directories has changed. This should be no issue, as it is normally just a symbolic link to the Makefile within your Genode's source tree. After the change, when you add new code with aspect-dependent parts, which means parts of the headers and compilation units are chosen using SPEC-variables (e.g.: 32bit vs. 64bit, or arm vs. x86), that code should reside in a 'spec/<SPEC-VARIABLE-NAME>/' subdirectory from now on. I hope you are all fine with those changes. Until now, it didn't hit the staging or master branches. So if there are any strong concerns against it, feel free to express them now. [1] https://github.com/genodelabs/genode/issues/1673 [2] https://github.com/skalk/genode/tree/issue%231673 -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

Xpra port?
by Jookia 08 Sep '15

08 Sep '15

Hey there, After disappearing and thinking for a while about how to have some kind of support for GNU/Linux sandboxes with seamless integration to the window manager. I've thought a lot about how the Qubes approach does it using shared memory and Xorg messages but this doesn't work over the network, so I'm starting to wonder if it'd be better to just use something like Xpra. I'm not sure how big the TCB of it is versus just passing X messages, but it shouldn't really be that bad if you only give it access to files shared with the sandboxed system, meaning it'd be counterproductive to break in to Xpra. Xpra also plans a Wayland port which might map well. Thoughts? Jookia.

2 2

Porting YSE5250 to base-foc
by Waldo Paz Rodriguez 08 Sep '15

08 Sep '15

Hello Genode comunity, I'm trying port the yse5250 board to base-foc. I follow the guide proposed by Norman Feske and test the printf scenario, as shown in the serial output Fiasco.OC and servers run correctly, but when I try to run Genode throws an error. L4 Bootstrapper Build: #3 vie sep 4 09:10:02 CDT 2015, 4.9.2 Scanning up to 2047 MB RAM Memory size is 2047MB (40000000 - bfefffff) RAM: 0000000040000000 - 00000000bfefffff: 2096128kB Total RAM: 2047MB mod05: 41144000-41174530: genode/test-printf mod04: 410ff000-41143c70: genode/init mod03: 410fe000-410fe110: genode/config mod02: 41094000-410fddec: genode/core mod01: 41082000-41093368: sigma0 mod00: 41015000-4108195c: /home/waldo/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco Moving up to 6 modules behind 41100000 moving module 00 { 41015000-4108195b } -> { 41260000-412cc95b } [444764] moving module 01 { 41082000-41093367 } -> { 412cd000-412de367 } [70504] moving module 02 { 41094000-410fddeb } -> { 412df000-41348deb } [433644] moving module 03 { 410fe000-410fe10f } -> { 41175000-4117510f } [272] moving module 04 { 410ff000-41143c6f } -> { 41176000-411bac6f } [281712] moving module 05 { 41144000-4117452f } -> { 41100000-4113052f } [197936] moving module 03 { 41175000-4117510f } -> { 41131000-4113110f } [272] moving module 04 { 41176000-411bac6f } -> { 41132000-41176c6f } [281712] Scanning /home/waldo/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco -serial_esc Scanning sigma0 Scanning genode/core Relocated mbi to [0x4100e000-0x4100e148] Loading o/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco Loading sigma0 Loading genode/core find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40001000, 40001a3f] { a40} Kern o/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco [ 40002000, 4007afff] { 79000} Kern o/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco [ 400a0000, 400a5fdf] { 5fe0} Sigma0 sigma0 [ 400b0000, 400b617b] { 617c} Sigma0 sigma0 [ 41000000, 410143f7] { 143f8} Boot bootstrap [ 4100e000, 4100e245] { 246} Root Multiboot info [ 41100000, 41176c6f] { 76c70} Root Module [ 80100000, 8024b63b] { 14b63c} Root genode/core API Version: (87) experimental Sigma0 config ip:400a0100 sp:41013de4 Roottask config ip:80100000 sp:00000000 Starting kernel o/genode-15-08/build/foc_yse5250/kernel/fiasco.oc/fiasco at 4000121c Hello from Startup::stage2 Number of IRQs available at this GIC: 160 Cache config: ON ID_PFR[01]: 00001031 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 Watchdog initialized SERIAL ESC: allocated IRQ 84 for serial uart Not using serial hack in slow timer handler. \0x1b[1;32mWelcome to Fiasco.OC (arm)! \0x1b[0;32mL4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: 7870838 compiled with gcc 4.9.2 for Samsung Exynos [] Build: #3 vie sep 4 09:09:57 CDT 2015 \0x1b[0m Timer for CPU0 is at IRQ 152 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 40002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:40000000;40000fff] [0:4007b000;4009ffff] [0:400a6000;400affff] [0:400b7000;4100dfff] [4:4100e000;4100efff] [0:4100f000;410fffff] [4:41100000;41176fff] [0:41177000;800fffff] [4:80100000;8024bfff] [0:8024c000;beefffff] IOMEM:---------------------- [0:0;3fffffff] [0:bff00000;ffffffff] KIP @ 40002000 magic: 4be6344c version: 87024444 sigma0 esp: 41013de4 eip: 400a0100 sigma1 esp: 00000000 eip: 00000000 root esp: 00000000 eip: 80100000 MBI @ 4100e000 mod[3] [41131000,41131110) config mod[4] [41132000,41176c70) init mod[5] [41100000,41130530) test-printf :ram_alloc: Allocator 8023aec0 dump: Block: [40000000,40001000) size=00001000 avail=00001000 max_avail=00001000 Block: [4007b000,400a0000) size=00025000 avail=00025000 max_avail=00025000 Block: [400a6000,400a601c) size=0000001c avail=00000000 max_avail=00025000 Block: [400a601c,400a6038) size=0000001c avail=00000000 max_avail=00000000 Block: [400a6038,400a6054) size=0000001c avail=00000000 max_avail=00009fac Block: [400a6054,400b0000) size=00009fac avail=00009fac max_avail=00009fac Block: [400b7000,400b701c) size=0000001c avail=00000000 max_avail=3ef89000 Block: [400b701c,4100e000) size=00f56fe4 avail=00f56fe4 max_avail=00f56fe4 Block: [4100f000,41100000) size=000f1000 avail=000f1000 max_avail=3ef89000 Block: [41177000,80100000) size=3ef89000 avail=3ef89000 max_avail=3ef89000 Block: [8024c000,bef00000) size=3ecb4000 avail=3ecb4000 max_avail=3ecb4000 => mem_size=2127253504 (2028 MB) / mem_avail=2127253392 (2028 MB) :region_alloc: Allocator 8023c030 dump: Block: [00001000,20000000) size=1ffff000 avail=1ffff000 max_avail=1ffff000 Block: [30000000,40000000) size=10000000 avail=10000000 max_avail=1ffff000 Block: [40001000,40002000) size=00001000 avail=00001000 max_avail=1ffff000 Block: [40003000,4007b000) size=00078000 avail=00078000 max_avail=00078000 Block: [400a0000,400a6000) size=00006000 avail=00006000 max_avail=1ffff000 Block: [400b0000,400b7000) size=00007000 avail=00007000 max_avail=010f0000 Block: [bef00000,bfff0000) size=010f0000 avail=010f0000 max_avail=010f0000 => mem_size=823611392 (785 MB) / mem_avail=823611392 (785 MB) :io_mem: Allocator 8023b31c dump: Block: [00000000,40000000) size=40000000 avail=40000000 max_avail=40000000 Block: [40001000,40002000) size=00001000 avail=00001000 max_avail=40000000 Block: [40003000,4007b000) size=00078000 avail=00078000 max_avail=00078000 Block: [400a0000,400a6000) size=00006000 avail=00006000 max_avail=00078000 Block: [400b0000,400b7000) size=00007000 avail=00007000 max_avail=410fffff Block: [bef00000,ffffffff) size=410fffff avail=410fffff max_avail=410fffff => mem_size=2165858303 (2065 MB) / mem_avail=2165858303 (2065 MB) :io_port: Allocator 8023b778 dump: :irq: Allocator 8023bbd4 dump: Block: [00000000,00000298) size=00000298 avail=00000298 max_avail=00000298 => mem_size=664 (0 MB) / mem_avail=664 (0 MB) :rom_fs: Rom_fs 8023c8e4 dump: Rom: [41132000,41176c70) init Rom: [41131000,41131110) config Rom: [40002000,40003000) l4v2_kip Rom: [40002000,40003000) kip Rom: [41100000,41130530) test-printf :core ranges: Allocator 8023f240 dump: Block: [40000000,40001000) size=00001000 avail=00001000 max_avail=00001000 Block: [4007b000,400a0000) size=00025000 avail=00025000 max_avail=00025000 Block: [400a6000,400b0000) size=0000a000 avail=0000a000 max_avail=7def1000 Block: [400b7000,4100e000) size=00f57000 avail=00f57000 max_avail=7def1000 Block: [4100f000,bef00000) size=7def1000 avail=7def1000 max_avail=7def1000 => mem_size=2129100800 (2030 MB) / mem_avail=2129100800 (2030 MB) \0x1b[32mGenode 15.08 <local changes>\0x1b[0m int main(): \0x1b[33m--- create local services ---\0x1b[0m int main(): \0x1b[33m--- start init ---\0x1b[0m \0x1b[34mReceived something different than a pagefault, ignoring ...\0x1b[0m Best Regards, waldo

2 1

Re: Uboot creation script fails
by Mark Albers 07 Sep '15

07 Sep '15

Hi Martin, i'm on version 15.08 now and have created a new build directory. The error is still the same. I added the hello_tutorial repository, yes. Here is the output of genode-arm-readelf --version: GNU readelf (GNU Binutils) 2.25 Copyright (C) 2014 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) any later version. This program has absolutely no warranty. I used the pbxa9 platform only for test purposes, the problem is the same with another platform. Regard, Mark

1 0

More small questions
by Jookia 05 Sep '15

05 Sep '15

Hey again, Sorry for the single word titles. I don't have Genode installed at the moment, but I'm curious about some minor things happening in the Genode space. >From what I've seen it doesn't really have a proper command line shell that can administer the system interactively. Is this the case, how would one handle doing tasks like managing daemons, file systems, launching applications in a system tree? For instance in the future, if I wanted to use a web browser over Tor I'd somehow have to launch a Tor network service and then have a web browser use that network service. How would I accomplish that? In future I'd imagine having a system configuration file specifying a tree like this for my machine showing services, applications, file systems that are available to services, GUI launchers, etc to build up a compartmentalized system. How hard would it get Fiasco.OC to run a rich GNU/Linux system through trustzone? I've heard it's possible, but I'm not sure how it'd work in Genode. I'd really like to have something like to run slow virtual L4Linux systems for 'secure' applications and an untrusted rich system elsewhere. Though perhaps this is a bad idea, and if it's not doable base-hw will have to do. Cheers, Jookia.

1 0

Qt in file manager?
by Nobody III 05 Sep '15

05 Sep '15

I'm hoping to find time to write a file manager for Genode. Do you think I'm safe to use Qt? I'm not planning on showing previews at first, and if I decide to add previews, they will be rendered in a separate process, so the only untrusted data I see are the filenames. In this case, I think it's safe to say that Qt won't be able to be compromised by rendering plain text. What do you think?

1 0

Testing the SD Card Driver for Raspberry Pi Model B
by Waldo Paz Rodriguez 04 Sep '15

04 Sep '15

Hello Genode comunity, I 'm testing the SD Card driver for Raspberry Pi model B, essentially I execute the sd_card.run scenario. The test fail when the reading process is called. This is the serial output: Genode 15.05-150-g4bc5872 <local changes> int main(): --- create local services --- int main(): --- start init --- int main(): transferred 249 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open ROM session for module "ld.lib.so" [init -> platform_drv] --- Raspberry Pi platform driver --- [init -> sd_card_drv] --- SD card driver --- [init -> platform_drv] Input message: [init -> platform_drv] 00000018 00000000 00020001 00000008 00000004 00000000 00000000 [init -> platform_drv] Output message: [init -> platform_drv] 00000018 80000001 00020001 00000008 80000008 00000000 00000001 [init -> sd_card_drv] -> index=0x00000000, arg=0x00000000, rsp_type=0 [init -> sd_card_drv] -> index=0x00000008, arg=0x000001aa, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000029, arg=0x40018000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000029, arg=0x40018000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000002, arg=0x00000000, rsp_type=1 [init -> sd_card_drv] CID: 0x1b534d30 0x30303030 0x100702ac 0x1200cc00 [init -> sd_card_drv] -> index=0x00000003, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] RCA: 0x59b4 [init -> sd_card_drv] -> index=0x00000009, arg=0x59b40000, rsp_type=1 [init -> sd_card_drv] -> index=0x00000007, arg=0x59b40000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x59b40000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000006, arg=0x00000002, rsp_type=2 [init -> sd_card_drv] SD card detected [init -> sd_card_drv] capacity: 7523 MiB [init -> test-blk-cli] block device with block size 512 sector count 15407104 (testing 131072 sectors) [init -> sd_card_drv] -> index=0x00000000, arg=0x00000000, rsp_type=0 [init -> sd_card_drv] -> index=0x00000008, arg=0x000001aa, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000029, arg=0x40018000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000029, arg=0x40018000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000002, arg=0x00000000, rsp_type=1 [init -> sd_card_drv] CID: 0x1b534d30 0x30303030 0x100702ac 0x1200cc00 [init -> sd_card_drv] -> index=0x00000003, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] RCA: 0x59b4 [init -> sd_card_drv] -> index=0x00000009, arg=0x59b40000, rsp_type=1 [init -> sd_card_drv] -> index=0x00000007, arg=0x59b40000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000037, arg=0x59b40000, rsp_type=2 [init -> sd_card_drv] -> index=0x00000006, arg=0x00000002, rsp_type=2 [init -> sd_card_drv] SD card detected [init -> sd_card_drv] capacity: 7523 MiB [init -> test-blk-cli] reading block 0 - 131071, 246 per request [init -> sd_card_drv] -> index=0x00000012, arg=0x00000000, rsp_type=2 [init -> sd_card_drv] command timed out [init -> sd_card_drv] Read_multiple_block failed, Status: 0x01ff0207 [init -> test-blk-cli] Test failed! [init -> test-blk-cli] couldn't read block 0 - 246 [init] virtual void Genode::Child_policy::exit(int): child "test-blk-cli" exited with exit value -2 Regards waldo

2 3

seL4: does X server require Linux; hardware for VMs
by John Lee 04 Sep '15

04 Sep '15

Hi I'd like to try running Genode on seL4. I wasn't expecting this to get into a release this soon so I'm very pleased to see it. Two questions, one re software, one re hardware: Software: For applications like firefox I read that it's currently necessary to run an X server. Does that X instance (and firefox) need to run on a Linux VM? Hardware: I read on the seL4 FAQ that to "run Linux on top of SeL4", I need: 1. Intel VT-x with EPT (standard by now I guess?) 2. an HPET [1] that supports MSI delivery [2] Re 2.: is all this integrated in Haswell processors? If yes, does Haswell support this? If no, does anybody know how to verify a motherboard supports it? [1] https://en.wikipedia.org/wiki/High_Precision_Event_Timer [2] https://en.wikipedia.org/wiki/Message_Signaled_Interrupts John

3 3

Gmane mirror?
by John Lee 04 Sep '15

04 Sep '15

Does anybody (in particular the list administrators of course) object if I request that gmane.org carries this mailing list? Thanks John

2 2

Build Target linux-arm: Wrong Compiler?
by Krefft, Daniel 03 Sep '15

03 Sep '15

Hello, we want to build Genode on top of Linux for an ARM-based platform (beagle bone black). Therefore, we choose the 'linux_arm' as build target. With Genode's ARM-Toolchain and x86-Toolchain in place, the compilation works without any problems. But, the resulting program is build for the x86_64 architecture. So, we have the following two questions: 1. Is it possible to build the linux_arm target for ARM (as suspected)? 2. Where can we change the compiler option pointing to e.g. arm-none-eabi? Best regards, Daniel -- ***************************************************************** * Daniel Krefft M.Sc. * * T: +49-89-289-18791 * * * Technische Universitaet Muenchen * Fakultaet fuer Informatik - F13 (Prof. Baumgarten) * Boltzmannstr. 3 * D-85748 Garching bei Muenchen * Germany *****************************************************************

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users