users

users@lists.genode.org

1 participants
2310 discussions

[GSoC] Rust bindings for the Genode API
by Saurav Sachidanand 03 Mar '17

03 Mar '17

Hello Genode, I'm Saurav Sachidanand, and I'm a CS sophomore studying in India. For more than year I've been programming in Rust and have published some personal projects in it (few involving the Rust-C FFI) and have contributed a few patches to Servo (github.com/saurvs). I've also played around a bit with kernel modules in NetBSD. I'm interested in working on Rust bindings for the Genode API. I'm also completely new to Genode, and so I'll spend time reading the extensive documentation and the Genode Foundations book, and building and running Genode, and will do independent research on the project. I'd greatly appreciate any guidance and pointers regarding this project. I'd also like to ask if a scripting language has been ported to Genode. If not, I'd like to suggest working on porting Lua since it is widely used as embeddable and extensible language, and has a manageably-sized codebase so that it can be one half of a two part GSoC project. Thanks, Saurav

2 1

Zynq-7000 HDMI driver status
by Johannes Schlatow 02 Mar '17

02 Mar '17

Hello everyone, earlier this year I mentioned that I have been working on an HDMI driver for the zynq-based boards. Unfortunately, I have only very limited time to work on this and it already ended up on a very low priority in my to-do list. The good news is, however, that the main parts have already been implemented but require some more debugging. In case anyone is interested in getting her/his hands dirty, I'll gladly provide assistance. You can find the code on github: https://github.com/ValiValpas/genode-world/tree/zynq_hdmi The run script I used for development is `adv7511.run`. The last thing I noticed was that the axi-clkgen driver is not working properly. Cheers Johannes

1 0

GSoC 2017: Isochronous USB devices, guidance needed
by Tyler Jones 02 Mar '17

02 Mar '17

Hello everyone, I am a Computer Science student in the US, and I am interested in the USB device work in Genode. I have experience with linux kernel USB device drivers, and am interested in the challenge of widening that knowledge with a separate and unique environment. I have spent some time trying to familiarise myself with the Genode code base and reading sections of the book, so I comfortable with how the OS operates at a high level. However, I am uncertain with the most appropriate direction in tackling the problem. Any help with this would be greatly appreciated. Thank you, in advance, for anyone willing to help guide me in a correct direction. I look forward to contributing to this project in any way that I am able! Thanks again, Tyler Jones

2 1

Google Summer of Code
by Norman Feske 01 Mar '17

01 Mar '17

Hello everyone, apparently, Zhongze Liu was quicker than me to announce Genode's participation in this year's Google Summer of Code (GSoC) program. ;-) Please find our official announcement on the genode.org website: http://genode.org/news/google-summer-of-code 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

Genode OS Framework version 17.02 released
by Norman Feske 28 Feb '17

28 Feb '17

I am happy to announce the release of Genode 17.02. Among the highlights of the new version are the introduction of Genode's ABI, init's new ability to the change a running subsystem on the fly, and a greatly improved VFS infrastructure that has been in the works for more than a year. As usual, all those topics are covered in full detail in the release documentation: https://genode.org/documentation/release-notes/17.02 For a brief summary: - Genode application binary interface (ABI) - Enhanced infrastructure for virtual file systes (VFS) - VFS support for synchronous I/O and reconfiguration - Rump-kernel-based file systems as VFS plugin - Linux TCP/IP stack as VFS plugin - New execution model of the C runtime - Dynamically reconfigurable init component - Generic user-input-processing component - Improved SD-card drivers, added support for i.MX6 - Muen separation kernel updated to version 0.8 I hope you'll enjoy the new version! 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

linux uart driver
by Prashanth Mundkur 16 Feb '17

16 Feb '17

Hi, I'm exploring writing a simple uart driver for linux in order to get terminal_mux working on linux. When I disable the linux spec check in terminal_mux.run, the build always picks up: Program drivers/uart/spec/x86/uart_drv even though I created a drivers/uart/spec/linux/ and changed drivers/uart/spec/linux/target.mk to read REQUIRES = linux and the etc/specs.conf in the build directory to read: SPECS += linux x86_64 I'd like to know how I can get the build to say Program drivers/uart/spec/linux/uart_drv Thanks, --prashanth

2 2

Q2 - build demo error
by Philip Rhoades 14 Feb '17

14 Feb '17

People, Using Fedora 25 x86_64 I get: Program drivers/framebuffer/spec/sdl/fb_sdl COMPILE fb_sdl.o COMPILE input.o LINK fb_sdl /usr/bin/ld: cannot find -lsupc++ collect2: error: ld returned 1 exit status /root/genode/repos/base/mk/prg.mk:174: recipe for target 'fb_sdl' failed make[3]: *** [fb_sdl] Error 1 var/libdeps:375: recipe for target 'fb_sdl.prg' failed make[2]: *** [fb_sdl.prg] Error 2 Makefile:270: recipe for target 'gen_deps_and_build_targets' failed make[1]: *** [gen_deps_and_build_targets] Error 2 make[1]: Leaving directory '/root/genode/build.lx' Error: Genode build failed Makefile:307: recipe for target 'run/demo' failed make: *** [run/demo] Error 252 The only relevant Google result taslked about static linking . . but I thought it better to ask here first . . Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@...479...

2 1

Smallest supported OS ?
by Philip Rhoades 14 Feb '17

14 Feb '17

People, I have only just signed up - I was led to Genode by a post on the MaidSAFE forum and so I am quite interested in the prospects for Genode and I want to get involved. First question - from searching the archives I can't see any info on one of things I am interested in - what is the smallest bootable OS that can be set up with Genode? - could it be small enough to fit on a floppy disk? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@...479...

2 2

Re: USB storage detachment / reattachment
by Boris Mulder 13 Feb '17

13 Feb '17

Dear Genode developers, Following Martijn's mail at the end of last year, which stated: >> As a way to support detachment / reattachment of USB storage I’m >> thinking about placing the rump_fs and part_blk components in a child >> subtree of the CLI component that is spawned on demand and cleaned-up >> after use. But this seems a bit like overkill. > That's exactly the right solution. I don't think that it's overkill > either. Spawning up rump_fs and part_blk dynamically is certainly quick > enough. Memory-wise, it does not take more resources that a static > scenario either. By letting your CLI component implement the protocol > outlined above, you have full control over chain of events. Also the > aborting rump_fs is nothing fatal anymore but can be gracefully handled > by the CLI component. As another benefit, the solution does not need us > to supplement the notion of hot-plugging to the file-system and block > session interfaces, which would otherwise inflate the complexity of > these interfaces (and thereby all the clients that rely on them). Martijn and I have been thinking of a way to implement this, and came to the conclusion that instead of spawning the stack as children of the CLI component, it might be better to use a new management component in-between. As Josef said earlier: > A custom runtime/management component could monitor the > usb_drv device report and spawn the whole stack if it detects a USB > storage device. The usb_drv's device report does not contain the device > class so far though but adding that to the report is easy. This is exactly what we're trying to do now. We want to create a custom component called "media" that monitors usb devices by reading the report. It provides a service to other components through which they can request a filesystem session in order to read-write from/to the usb-stick. For this, it spawns the part_blk and rump_fs components as children if the usb is plugged in, and kills them once the usb is plugged out. It roughly looks like this: rump_fs part_blk | | CLI media USB_drv | | | init But this raises a few questions. First, the filesystem interface needs to be presented to the client somehow. To avoid adding another layer of indirection into media, essentially duplicating rump_fs's entire API, we would like the client (in this case CLI) to be directly connected to rump_fs. The client can then ask media if the USB is connected before calling a function from rump_fs. However, this means that rump_fs provides a service, announces it to its parent (media), and media has to decide what to do with that announce. It can implement rump_fs as a slave, but that way the entire API needs to be copied into media so media can present it as its own service to the client. So we would like media to announce the filesystem service to its parent (in this case init), so any client can use this service. In the same way, any session request will be passed from CLI to its parent (init), init has to pass it to media, and media passes it to rump_fs. However, the current implementation and specification of genode does not allow services of any server to exist in any level above the server's parent. Services can only be provided to direct parents, and to other components in the parent's subtree. Therefore, copying the API from the child to the parent seems unavoidable. Another problem that pops up is that media has to spawn all these subcomponents as children. In order to route block session requests from rump-fs to part-blk, media needs to implement some routing policy and effectively serves the same role for these two components as init serves for the system. So we could: 1. Copy all necessary code for routing from init to media (which is almost all code if we want to be generic). 2. Let media spawn another init child component (let's call it sub-init for now) which in turn spawns rump-fs and part-blk and does the routing. To us, the second option seems much more clean as it involves no code-copying. However, services announced by rump-fs can not be used by other components that are not children of the new init, and are kind of useless. Their announcements can not be passed on to the parents, leaving us with the same problem as we had with rump_fs but with the additional problem that even if there would be a custom way to forward service announces and requests to the parent/child respectively, sub-init has no such policy, and this functionality has to be included in sub-init's code as well, adding a lot of complexity. Eventually both cases bottle down to the same problem: service announcements to a parent cannot automatically be forwarded to that parent's parent, and likewise, service requests need to be able to be delegated to children of children without a lot of hassle. The only option if I'm correct is implementing this functionality manually, but this does not work if the parent is an existing component that does not support it. Is there a reason this is never done? For init it is clear that it would never pass an announce to its parent (usually core) or receive session requests from it. But how about the general case? And how should we solve cases such as the above scenario? kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

4 10

Volume names of partitions
by Boris Mulder 10 Feb '17

10 Feb '17

Hi, Many file system formats support a name tag. Is there any way in Genode to read or write this "volume name"? -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users