users

users@lists.genode.org

3 participants
2323 discussions

genode-manual make error
by Bob Stewart 23 Jan '15

23 Jan '15

Hi, I tried to execute make in the manual directory after getting gosh and the texlive stuff and got an error on a chapter_tag: bob@...297...:/Work/genode-manual/manual$ make gosh --style manual.gosh manual.txt > misc.tmp.tex can't read "chapter_tag": no such variable while executing "printline "\\$chapter_tag[section_env_latex $title]"" (procedure "process_chapter_latex" line 9) invoked from within "process_chapter_latex {{20 Introduction} {21 ############} {22 {}} {23 {}} {24 {Universal truths}} {25 ================} {26 {}} {27 {| TODO}} {28 {}}..." ("eval" body line 1) invoked from within "eval "$spec_function [list $content]"" (procedure "handle_txtblock" line 18) invoked from within "handle_txtblock documentmain $txtcontent" (file "/usr/bin/gosh" line 1177) make: *** [manual.pdf] Error 1 Thanks for any help.

3 2

SMC in tz_vmm
by chirag garg 23 Jan '15

23 Jan '15

Hi all, I have some doubts in Genode Flow, ARM provides the smc instruction to enter in the monitor-mode which performs the world switch between normal world and secure world. As tz_vmm script is also successfully achieving the above objective of world switch from the secure world to the normal world. But i am not able to figure out flow which will which execute a call of smc instruction in the run of tz_vmm script. Can anyone explain me the flow ? Thanks in advance. Regards Chirag Garg IIT Madras , Rise Lab

3 3

1st Microkernel Stammtisch 2015
by Julian Stecklina 23 Jan '15

23 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Microkernel Hackers in and around Dresden, let's meet for a drink and trade stories! Where: Campus, HÃ¼bnerstr. 13, Dresden, Germany When: Thursday, Jan 29th, 2015 @ 20:00 CET Please leave an entry in this doodle, if you plan to join, so we can reserve a sufficiently large table: http://doodle.com/ktv4nrn5wutg569w Feel free to forward this mail, Julian -----BEGIN PGP SIGNATURE----- Version: OpenKeychain v3.1.2 iGcEAREIACcgHEp1bGlhbiBTdGVja2xpbmEgPGpzQGFsaWVuOC5kZT4FAlTCHuIA CgkQ2EtjUdW3H9kobACfSvmrOIxq/sOggHb78yVTzuKbGi4AoOxiBKy7UUBP/WbY XP3xTD4Trk3q =4V+q -----END PGP SIGNATURE-----

1 0

make run/rump_ext2 fails
by Adrian 22 Jan '15

22 Jan '15

Hello, I am trying to explore the rump_fs facilities. I followed the repos/dde_rump/README and failed when executing make run/rump_ext2. Following is a pasted-in terminal output. Any help would be appreciated. adrian@...295...:~/genode-14.11/build/build.fs$ make run/rump_ext2 using run script /home/adrian/genode-14.11/repos/base-nova/run/env using run script /home/adrian/genode-14.11/repos/dde_rump/run/rump_ext2.run building targets: core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs spawn make core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs make[1]: Betrete Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: target 'test/libc_vfs' does not exist make[1]: *** [error_missing_targets] Fehler 1 make[1]: Verlasse Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: Genode build failed make: *** [run/rump_ext2] Fehler 252 adrian@...295...:~/genode-14.11/build/build.fs$ Regards, Adrian Schuur

3 2

[HEADS UP] Refactored run tool on staging
by Josef Söntgen 22 Jan '15

22 Jan '15

Hello, tl;dr we merged the modularized version of our run tool to the staging branch. This version requires changes in the build directory, e.g., changes to 'etc/build.conf' and it is therefore advised to remake all used build directories if one uses the current staging branch. There is also 'tool/run/README', which explains the usage and the architecture in more detail. In addition you can take a look at the corresponding issue [1]. The run tool served us well over the years and by continously extending its functionality it met our daily requirements. The way it was extended up to now, however, was in an ad-hoc fashion that made future changes and maintaining more time-consuming. We addressed these problems by refactoring the run tool: * Modularizing the run tool: each step (building/loading components, execution scenarios and so) is now implemented by a module. All of the common use cases, that were handled by the old run tool, are now covered by combining these modules. This makes the actual run tool more managable and makes future extensions easier. * Unifying the argument handling of the run tool: each module is configured explicitly in the same fashion. That makes configuration failures more visible. To just give an example on how the interface of the run tool changed, here is a comparison of the old way and the new way to handle a common use case: In this case, we want to reset the target system and caputure the LOG output via AMT. The target system loads all files it needs to execute the scenario via TFTP: * Old (changes in nova_x86_64/etc/build.conf): RUN_OPT = --target amt --tftp-absolute export AMT_TEST_MACHINE_IP = 10.23.42.51 export AMT_TEST_MACHINE_PWD = secret export PXE_TFTP_DIR_BASE = /var/lib/tftpboot export PXE_TFTP_DIR_OFFSET = /x86 * New (changes in nova_x86_64/etc/build.conf): RUN_OPT = --include boot_dir/nova AMT_HOST = 10.23.42.51 AMT_PASSWORD = secret RUN_OPT += --include power_on/amt \ --power-on-amt-host $(AMT_HOST) \ --power-on-amt-password $(AMT_PASSWORD) RUN_OPT += --include log/amt \ --log-amt-host $(AMT_HOST) \ --log-amt-password $(AMT_PASSWORD) RUN_OPT += --include load/tftp \ --load-tftp-base-dir /var/lib/tftpboot \ --load-tftp-offset-dir /x86 --load-tftp-absolute The new way is arguably more verbose but also makes the configuration more clear, which is more important in our opinion. In addition, it is possible to capture the LOG output, i.e., via an USB-serial adapter by replacing 'log/amt' with 'log/serial'. That is something, that was more difficult to achieve with the old tool. When creating a new build dir, a default RUN_OPT configuration is added to the generated 'build.conf'. In most cases this means creating an ISO image and starting the scenario in Qemu like the old tool did in the default configuration. As I have said before, there is a README file, that hopefully provides all information that is needed to get you started with the new tool. If you think there is something that is missing from this documentation, please drop a note either via E-Mail or github. Cheers Josef [1] https://github.com/genodelabs/genode/issues/1355

1 0

Run script issue
by chirag garg 20 Jan '15

20 Jan '15

Hi all, I created one run script "switch" which gives me the following error at compilation at the last stage. make[1]: Leaving directory `/home/chirag/genode-ns/build6' cp: cannot stat `bin/switch': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $binaries" (procedure "build_boot_image" line 16) invoked from within "build_boot_image "core init switch"" (file "/home/chirag/genode-ns/repos/os/run/switch.run" line 37) invoked from within "source $include_name" ("foreach" body line 3) invoked from within "foreach include_name [get_cmd_arg --include ""] { puts "using run script $include_name" source $include_name }" (file "/home/chirag/genode-ns/tool/run" line 1004) make: *** [run/switch] Error 1 Like error message says that it is not able to copy switch file from the bin folder because it is not there. WHY this script is failed to create the bin/switch file ? Please let me know the all possible reason behind it. I am attaching switch.run script in the mail. Thanks in advance. Regards Chirag Garg IIT Madras , Rise Lab

3 4

Network Performance in Genode
by Mohammad Hamad 18 Jan '15

18 Jan '15

HI, I am studying the network performance (with lwip) of Genode with different kernels such as linux and base_hw. Genode ported netperf as tool to measure the performance with many tests ( TCP_RR , TCP_STREAM and etc). there is run file (netperf_lwip) working with linux kernel . I made some changes to make it run for Raspberry bi but i still have some questions . - is netpperf ported to genode for measuring the performance on the linux kernel or it is accepted tools for Raspberry bi too, can I trust it with Raspberry? - each time i run the TCP_RR test I get different results . while it is almost stable when i run the same test between two linux machines . - should i accept the result for one test or i should calculate the average of many tests for the same parameters best, Mohammad

1 0

Juno Development Platform and Genode
by Stefan Brenner 15 Jan '15

15 Jan '15

Hi guys, just a short question, are there any experiences to run Genode on top of the Juno ARM Development Platform (http://www.arm.com/products/tools/development-boards/versatile-express/juno… Best, Stefan

1 0

Genode at FOSDEM 2015
by Norman Feske 14 Jan '15

14 Jan '15

Hello again, I am happy to announce that there will be three Genode-related talks at FOSDEM this year: "Genode - OS security by design" Sunday 12:00 - 12:25 Security devroom (AW1.120) "Transplantation of VirtualBox to the NOVA microhypervisor" Sunday 14:20 - 15:00 Virtualization devroom (UD2.120) "Introducing a radically componentized GUI architecture" Sunday 15:30 - 16:15 Microkernel devroom (K.3.201) More information about the talks (including abstracts) are available at the FOSDEM website: https://fosdem.org/2015/schedule/speaker/norman_feske/ Cheers 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

1 0

Exploring Genode
by Norman Feske 14 Jan '15

14 Jan '15

[my third attempt to post this message on the mailing list...] Thanks Tim, for featuring Genode on your blog! http://thenewsh.blogspot.de/2015/01/exploring-genode.html I think that your assessment of our project is fairly accurate. Cheers Norman

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users