users

users@lists.genode.org

6 participants
2306 discussions

create_uboot for wand_quad
by Pirmin Duss 24 Jan '19

24 Jan '19

Hello Genodeans I'm currently porting Genode to the Apalis iMX6 board of Toradex. As a starting point I used the wand_quad. Currently I'm able to build run/log for both base-hw and base-sel4. My problem arises when I run tool/create_uboot I get the following error: In file included from /var/cache/genode_contrib/uboot/include/linux/compiler.h:54:0, from /var/cache/genode_contrib/uboot/include/linux/byteorder/little_endian.h:12, from /var/cache/genode_contrib/uboot/arch/arm/include/asm/byteorder.h:29, from /var/cache/genode_contrib/uboot/include/compiler.h:125, from /var/cache/genode_contrib/uboot/include/image.h:19, from /var/cache/genode_contrib/uboot/include/common.h:82: /var/cache/genode_contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory #include gcc_header(__GNUC__) ^ I have a work around, for compiling Uboot. By using the uboot tree provided by Toradex (see: https://github.com/trimpim/genode/blob/apalis_imx6/tool/create_uboot) the Image is created. Does Martin's uboot tree do some special configuration things? the only change I see is that it adds an empty file. Best regards, Pirmin

2 1

This year's Genode Hack'n'Hike
by Norman Feske 23 Jan '19

23 Jan '19

Hello, there will be another Genode Hack'n'Hike this year! Besides FOSDEM, this annual event is certainly one the Genode highlights of the year. It is a small gathering of around 10 to 20 developers and enthusiasts of Genode and provides a healthy mix of daylight outdoor activities and candlelight hacking activities. The informal character of the Hack'n'Hike presents a great opportunity for newcomers to get acquainted with the people behind Genode. This year, it will take place during May 10 to 13 in Königstein nearby Dresden/Germany. The event is sponsored by Genode Labs. There is no registration fee. If you like to participate, please register by commenting at the corresponding topic on our issue tracker linked below. There you can also find the most up-to-date information about traveling arrangements and the exact location: https://github.com/genodelabs/genode/issues/2841 Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Error: hammer ABI contains Genode-internal symbol '__bss_start'
by Guido Witmond 18 Jan '19

18 Jan '19

Dear Genodians, I'm back at learning how to do packaging. By following the developer-resources/porting_libraries guide, I ported the Hammer parser combinator library into a Genode port [1]. It builds and runs a simple test. (commit 665e71d). Now I want to make it a depot package. I copied the structure from libports/expat and adapted it. I have a recipes/{api,src}/content.mk (commit XXXXXX) I created the lib/symbols/hammer file by ! tool/abi_symbols bin/hammer.lib.so Then I run the build: ! ~/genode/tool/depot/create guido/bin/x86_64/hammer UPDATE_VERSIONS=1 FORCE=1 KEEP_BUILD_DIR=1 It starts good: ! created guido/api/base/2018-11-23 ! created guido/api/hammer/2019-01-08 ! created guido/api/libc/2018-11-26 ! created guido/src/hammer/2019-01-08-a However, I get this error during the compile of hammer. ! MERGE hammer.lib.so ! Error: hammer ABI contains Genode-internal symbol '__bss_start', ! Error: hammer ABI contains Genode-internal symbol '__eh_frame_start__' all from the symbol_blacklist defined in check_abi. It ends with this error: recipe for target 'hammer.lib.checked' failed So where did I go wrong? (Maybe this is an item for the list of missing documentation). 1: https://github.com/gwitmond/genode-hammer-library

3 7

I would like you to intergrate my work in bt2hmda in Genode
by Unidef 16 Jan '19

16 Jan '19

Bt2hmda stands for binary trees to high multidimensional arrays Sample code is at https://GitHub.com/unidef/quantum It doesn’t have to be large arrays, it can be like twenty arrays of 5 I still need to write how to move in neural space, but I failed calculus so I plum gave up You’ll need a revolving dma to properly adequate it to modern pc’s, but my dream is to make it into a small sql library that can hold exobytes through md threading and buffering Sent from my iPhone

1 0

Roadmap 2019
by Norman Feske 15 Jan '19

15 Jan '19

Hallo everyone, hereby, I'd like to follow up on our tradition to discuss Genode's road map on the mailing list. Let's take the turn of the year to recapture the events of 2018 and make plans for the next twelve months. Please feel welcome to chime in! By mid of January, I'll finalize Genode's official road map and would like to take your input into account. In the following, let me share my personal reflections and goals. The Year of Sculpt When I declared 2018 as Genode's Year of Sculpt, I had no concrete idea how Sculpt OS would shape up. I was convinced that we had - functionality-wise - all building blocks of a general-purpose OS in place. But it was rather unclear how to best put them together to attain a practical system. The unconquered design space seemed vast, which was both exciting but also - at times - a bit paralyzing. I ultimately had to bang a few nails into the wall, taking decisions with uncertain outcome. The Year of Sculpt was - more than anything - a design-space exploration, not an up-front planned activity. In the process, I came up with many half-baked thoughts and had the fortune of having our team at Genode Labs scrutinizing my ideas while also taking me seriously. Whenever an idea was indefensible, we jointly came up with a better one. Whenever uncertain about a proposed solution, I went forward with implementing it and took our team as guinea pigs. Whenever an idea was blocked by a limitation of an existing component, I could count on the support of the others to lend a helping hand with tweaking the components as needed. Unsurprisingly, many topics of the past year had a direct connection to Sculpt, e.g., the NIC router, the huge device-driver efforts, the GUI-stack improvements, and the work on the file-system and networks stacks. For me personally, this ride was certainly the most rewarding period in Genode's history so far. Now, when looking at the result, I am overwhelmed about what we achieved together! Whenever I have the chance to showing off Sculpt running on my laptop, Sculpt doesn't fail to impress. That said, during the course of the year, this positive sense of achievement eventually blended with the rather dull feeling that our hard work remains largely unnoticed outside the inner circle of Genode enthusiasts. The public at large remains quite indifferent (e.g., I was unable to capture the interest of FOSDEM to feature a talk about Sculpt OS on their main track). For a long time, I tricked myself into believing that once we overcome all technical road blocks, Genode will eventually become widely recognized automatically. There was always a technical challenge to take on. With Sculpt, we have reached a point where this excuse doesn't hold anymore. There is no technical piece missing. This leaves me with the question of how to make Genode relevant at a larger scale? Since this is not a technical question, I admittedly struggle to find a good answer. When thinking of the overall leitmotif for 2019, I always come back to this question. Plan for 2019 I see three directions to help Genode to become more widely recognized. 1) Widening the audience of Sculpt OS 2) Fostering the community spirit around our project 3) Marketing of Genode-based products Let me outline my thoughts behind each point. 1) Widening the audience of Sculpt OS Sculpt works well, but it is arguably still too hard to use for non-technical users and it lacks a lot of software that users take for granted today. Consequently, we should improve its ease of use. In particular, I'd love to explore the more consequent use of Sculpt's component graph as an intuitive user interface for both the composition and the configuration of components. The ultimate goal would be to eliminate the need for editing any text files. With respect to software availability, I have high hopes in the Genode SDK that we introduced in Genode 18.11. Let's follow this route further. 2) Fostering the community spirit around our project Our project enjoys a healthy community of users and contributors. But the community is rather scattered and the various groups work pretty much in isolation. As a result, the work of one group is often invisible to the others, not to speak of any public visibility. Could we possibly establish an instrument that would help each participant to gain more visibility and thereby help the community at large to become more relevant? I'll come up with a concrete proposal for such an instrument soon. One technical element may be a feature of Sculpt that would allow the user to browse the software depots provided by various community members and install/deploy packages by just a few clicks. This would vastly ease the discoverability of the available software and highlight the roles of the respective developers. A non-technical element may be a dissemination of Genode-related news at a higher rate than the current release announcements. 3) Marketing of Genode-based products Let's build Genode-based solutions to real-world problems and talk about them. The more diverse the solutions, the better. Be it server appliances, network equipment, controlling devices, or other forms of embedded systems, there are so many opportunities. One important trait of such products is the trustworthiness of Genode. So we constantly need to reinforce the confidence in Genode's quality. We should continue and expand our quality-assurance and software-hardening activities. For example, I see a huge potential in cultivating the use of Ada/SPARK for certain security-critical components. These are my high-level thoughts about the direction of the project. I deliberately left out a list of technical items from this initial posting. Let's fill in the technical substance together. :-) Please don't hesitate to share your thoughts. You may consider the following questions: * What are your ambitions for 2018? * Which areas of Genode would you like to see improved? How would you possibly contribute to these improvements? * Which technical topics do you find tempting? * If you imagine a Genode-based system one year in the future, how would it look like? * Do you have further ideas that would help making Genode relevant at a larger scale than today? Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

12 27

Re: Roadmap 2019
by ttcoder＠netcourrier.com 14 Jan '19

14 Jan '19

Thank you for the encouragement Norman. That gives me determination to deliver on the 'hype' I posted.. and be useful to the community this coming year. Now that I'm aware of the upcoming "genodians.org" it seems I should have waited before registering at neocities.org Anyway here's the micro-blog as it is now: https://tts-genode.neocities.org/genode.html Will migrate the entries in there to genodians.org when is ready -- looking forward to it yes. More entries are queued up to help "prime the pump" if need be. > We ultimately should strive for a agreed-upon official way. Right now, > however, I feel that it's still too early to take informed decisions. So > may we take 2019 as the year for desktop experimentation? I'll try to do my part, fueled by feedback as well. 'Experimentation' is an interesting perspective: One key ingredient/catalyzer, I believe, is ease of programming: when things take a lot of time and energy, developers get 'shy', overly cautious, think twice before coding.. Discussions heat up as there is more at stake. When it's easy to come up with an (at least partial) implementation however, the discussion is less abstract as it moves forward supported by quickly-put together concrete examples. Over time my 'library' of code and framework have reached a point where I can write GUI code very easily and quickly.. Meaning any given project does not have me too worried about it possibly ending up in the trash later. (as the Jam/MR guys say, "make simple things simple, make complex things manageable") We'll see how that factors in! > Indeed. However, we have a rough plan to enable features like > screenshots and screen recording. Maybe, these are worth considering for > the road map? Considering the conflicting imperatives -- prioritizing security on the one hand, and some quote-unquote "urgency" to enable developers to "show off" on the other hand... Maybe it would make sense to prioritize implementing (a rough version of) the feature, but keep it hidden behind a compile-time flag? There would be a prominent comment near the if-def, "leave this commented out in production!" Just a thought. I can use a digital camera to shoot the screen in the meantime. Cedric

3 3

Genode on i.mx6 with TrustZone
by lzSun 08 Jan '19

08 Jan '19

Hello, I have a i.mx6q sabre SD board and I want to try it with genode and TrustZone feature. I found there's a related issue: https://sourceforge.net/p/genode/mailman/genode-main/thread/5535FB27.109060…, I tried it with Genode as secure world (https://github.com/iitmadras/genode/tree/hw_sabrelite_tz_support) and met the same problem that it stuck at : Starting Kernel .... And the solution mentioned it was about the UART configuration difference with sabre Lite and sabre SD board. However, I am little confused with it. First, the sabre Lite and sabre SD board are both equiped with 4 i.MX6 processor, so I think the UART address are same which can be found in "i.MX 6Dual/6Quad Applications Processor Reference Manual", so I can not understand where is the UART configration difference. Also, I have tried to modify the UART_1_MMIO_BASE in [1] to all the UART address in "i.MX 6Dual/6Quad Applications Processor Reference Manual", but the problem still exist. Second, when I create the build dir with: ./tool/creat_builddir hw_sabrelite and try it with run/printf, it can successfully print the message. But when I create the build dir with: ./too/creat_builddir hw_sabrelite_tz and try it with run/printf, it stuck at "starting kernel ..." . In other words , I cannot get the print message successfully with TrustZone. Please give me advice to fix this problem. By the way, I want to know if there's any newer version that I can try genode with TrustZone on i.mx6. Thanks a lot. ------------------ Best wishes

1 0

Hack'n'Hike 2019
by Martin Stein 07 Jan '19

07 Jan '19

Hi guys! The Hack'n'Hike has become a fun tradition amongst the Genode enthusiasts. Every year around May we gather in a cozy accommodation somewhere in the beautiful nature of Saxony/Germany and mix relaxed hacking all around Genode with refreshing outdoor activities. This year it will be the 10th to the 13th May in Ferdinands Homestay, Königsstein in the Saxony Switzerland. For more details and news please see the corresponding Github issue [1]. If you have questions or suggestions, feel free to answer this mail. If you like to join us, please let us know before the end of February! Cheers, Martin [1] https://github.com/genodelabs/genode/issues/2841

1 0

Depot Archive Creation
by Edward Sandberg 03 Jan '19

03 Jan '19

Hello all, I am trying to create a depot archive that is my own custom version of a port available in the main distribution. I modeled my recipe files after the ones found in libports/recipes. Section 5.5.1 of the genode foundations book seems to indicate that adding /<date> would be enough to distinguish between archives with the same name so my files look like this: # cat repos/adventium/recipes/src/libssl/api libssl/2019-01-02 # cat repos/adventium/recipes/src/libssl/used_apis libc libcrypto/2019-01-02 so # cat repos/adventium/recipes/src/libcrypto/api libcrypto/2019-01-02 but when I try to run ./tool/depot/create I get the following error: # ./tool/depot/create adventium/src/libssl/2019-01-02 Error: recipe for 'libcrypto' is ambiguous, candidates are: /home/esandberg/genode/repos/adventium/recipes/api/libcrypto /home/esandberg/genode/repos/libports/recipes/api/libcrypto make[3]: *** [/home/esandberg/genode/tool/depot/mk/extract.inc:33: checked_recipe_is_unique] Error 1 make[2]: *** [/home/esandberg/genode/depot/var/extract.mk:44: adventium/api/libcrypto/2019-01-02] Error 2 make[1]: *** [/home/esandberg/genode/tool/depot/extract:175: execute_generated_extract_mk_file] Error 2 make: *** [tool/depot/create:41: extract] Error 2 Is it not possible to have more than one archive with the same name or am I just missing a step? -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

2 1

Experiences with Sculpt VC
by Guido Witmond 19 Dec '18

19 Dec '18

Hi Genodians, I've been playing with Sculpt VC again. Doing so thought me a lot more about routing. This time I succeeded in creating a VM with partitions on two SATA disks. It runs Nixos inside with the /home partition on an encrypted ZFS mirror. (and the root partition on a virtual disk, just like the Debian VM). When I want to start the VM and the ahci-1.part_blk is not running, the Runtime manager reports with a diagnostic stating vm-nixos needs ahci-1.part_blk. To start my vm, I inspect a different partition on that disk. That starts the part_blk and Runtime starts my VM. So far so good. The problems start here: 1. When the VM runs and I stop inspecting that partition, the Runtime manager kills my VM. The manager was happy to start my VM when the resource came available but does not keep the part_blk alive when the inspector stops. 2. When the VM runs (and has a session to the part_blk for that partition, I can format that partition from the Storage component. I get data corruption errors in ZFS on that disk. (But ZFS lives on and repairs it from the other mirror). That seems to be in violation of The Book para 4.5.8: """The part-block component requests a single block session, parses a partition table, and hands out each partition as a separate block session to its clients. There can be one client for each partition. """ I would expect that the formatter would get an error because it should not get a session to that partition. Could someone shine a light on what's going on? The log file is here: https://paste.wtmnd.nl/xfNMa3yY I wrote a full write-up of my sculpting here: https://paste.wtmnd.nl/WKUQowg2 -- I intend to make it a blog post for others to learn from, hence the writing style. Regards, Guido.

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users