users

users@lists.genode.org

2352 discussions

multiple devices, single driver
by Joel Nider 26 Oct '18

26 Oct '18

Hi, I have been looking at several drivers in Genode, and they all seem to have static data - specifically a Heap object and Root object. I am wondering with this kind of setup, is it possible to manage more than one device with a single driver? Thanks, Joel

3 7

Re: users Digest, Vol 6, Issue 15
by A Noor 25 Oct '18

25 Oct '18

I want to run Genode-ARM on android system. Thank you. Regards, Ayesha On Thu, 25 Oct 2018 at 15:30, <users-request(a)lists.genode.org> wrote: > Send users mailing list submissions to > users(a)lists.genode.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.genode.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.genode.org > > You can reach the person managing the list at > users-owner(a)lists.genode.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Genode on Secure Tablet (Christian Helmuth) > 2. Re: multiple devices, single driver (Alexander Boettcher) > 3. Re: multiple devices, single driver (Joel Nider) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 24 Oct 2018 15:19:24 +0200 > From: Christian Helmuth <christian.helmuth(a)genode-labs.com> > To: users(a)lists.genode.org > Subject: Re: Genode on Secure Tablet > Message-ID: <20181024131924.GC4718(a)genode-labs.com> > Content-Type: text/plain; charset=utf-8 > > Hello Ayesha, > > On Wed, Oct 24, 2018 at 01:34:51PM +0530, A Noor wrote: > > I have successfully emulated ARM-Genode in Bionic beaver. I need to run > the > > genode on the secure tablet now. > > Can anyone pls help me out through this process. A small help also > > accountable. > > congrats for mastering the first step to run Genode on your secure > tablet. Now as you really like to use the hardware, it is the best > time to tell us which hardware platform you're addressing. Otherwise > I'm afraid nobody will emerge for helping you. > > Regards > -- > Christian Helmuth > Genode Labs > > https://www.genode-labs.com/ · https://genode.org/ > https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ > > Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > > > > ------------------------------ > > Message: 2 > Date: Thu, 25 Oct 2018 08:08:04 +0200 > From: Alexander Boettcher <alexander.boettcher(a)genode-labs.com> > To: Genode users mailing list <users(a)lists.genode.org>, Joel Nider > <JOELN(a)il.ibm.com> > Subject: Re: multiple devices, single driver > Message-ID: <8e5c2053-d5b3-6942-083b-e53931ddd885(a)genode-labs.com> > Content-Type: text/plain; charset=utf-8 > > Hello, > > On 23.10.18 14:50, Joel Nider wrote: > > I have been looking at several drivers in Genode, and they all seem to > > have static data - specifically a Heap object and Root object. I am > > wondering with this kind of setup, is it possible to manage more than > one > > device with a single driver? > > of course. As described in the Genode book [0] in chapter 3.2.3, the > root object provides the implementation just of the interface. Whenever > a client connects to a service (like a driver for nic, ahci, nvme, usb > etc.) a session is established via this interface. The driver may > associate (typically does so depending on your specified policy) one > specific device it drives to this session - as done e.g. for drivers > handling multiple devices, e.g. ahci, nvme, usb. > > A driver may provide also different services, e.g. our old usb driver > provides Nic, Block, Input (so several root interfaces). > > Cheers, > > Alex. > > [0] https://www.genode.org/documentation/genode-foundations-18-05.pdf > > -- > Alexander Boettcher > Genode Labs > > https://www.genode-labs.com - https://www.genode.org > > Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > > > > ------------------------------ > > Message: 3 > Date: Thu, 25 Oct 2018 10:38:08 +0300 > From: "Joel Nider" <JOELN(a)il.ibm.com> > To: Alexander Boettcher <alexander.boettcher(a)genode-labs.com> > Cc: Genode users mailing list <users(a)lists.genode.org> > Subject: Re: multiple devices, single driver > Message-ID: > < > OFE542A872.7CA6CBCD-ONC2258331.0026D25E-C2258331.0029F1A3(a)notes.na.collabserv.com > > > > Content-Type: text/plain; charset="US-ASCII" > > Hi Alex, > > > On 23.10.18 14:50, Joel Nider wrote: > > > I have been looking at several drivers in Genode, and they all seem to > > > > have static data - specifically a Heap object and Root object. I am > > > wondering with this kind of setup, is it possible to manage more than > one > > > device with a single driver? > > > > of course. As described in the Genode book [0] in chapter 3.2.3, the > > root object provides the implementation just of the interface. Whenever > > a client connects to a service (like a driver for nic, ahci, nvme, usb > > etc.) a session is established via this interface. The driver may > > associate (typically does so depending on your specified policy) one > > specific device it drives to this session - as done e.g. for drivers > > handling multiple devices, e.g. ahci, nvme, usb. > > I will give you my situation as a specific example. I am writing a driver > for a PCIe attached NIC (x86 platform). Let us say that I have 2 physical > NICs in my machine with the same device ID and vendor ID. I have specified > in my config file that I have a driver called "nic_drv", without > specifying the PCIe address (copied from the example in > repos/os/run/ping.run). > > When the driver starts, I can enumerate the PCIe devices through the > Platform::Connection object that is instantiated from the 'env' object. I > see all PCIe devices of class 'NET' (even other NICs that I don't want my > driver to handle). So far so good. I can filter through the devices by > requesting the capability (with Platform::Device_client) and I can read > the device ID and vendor ID and pick the devices I want to handle. > > Now I have a list of several devices that I want my driver handle. If I > understand you correctly, I should have only one Root object (and one Heap > object). That implies I should also only call parent().announce() once. > But then how do I instantiate my Nic::Session_component once per device? > What is happening so far, is that some time after I call > parent().announce(), my Nic::Session_component derived class gets > instantiated, and the constructor is called. But I have no way of knowing > which device it is meant to handle, since there is no mechanism for > passing the device capability to Nic::Session_component. In addition, I > only see this constructor being called once. I expected to see one > constructor per PCIe device. This causes further problems such as not > being able to map the mmio region since the size and base address are not > known until I query the PCIe BAR, and there is no 'new' operator > available, which means to me I'm doing something fundamentally wrong. > > So what is the correct way to build the driver such that I get an object > per device (and the object knows the device)? > > Thanks, > Joel > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > users mailing list > users(a)lists.genode.org > https://lists.genode.org/listinfo/users > > ------------------------------ > > End of users Digest, Vol 6, Issue 15 > ************************************ >

1 0

Genode on Secure Tablet
by A Noor 24 Oct '18

24 Oct '18

I have successfully emulated ARM-Genode in Bionic beaver. I need to run the genode on the secure tablet now. Can anyone pls help me out through this process. A small help also accountable. Regards, Ayesha.

2 1

Problem building src archive for component using Qt
by Duss Pirmin 23 Oct '18

23 Oct '18

Hello Genodeans I have a component that uses QToolButton. When I build it in my run script, the build works well. When I want to build my src package I get the following error message: button.o:(.data.rel.ro._ZTIN14Launcher_slice6ButtonE[_ZTIN14Launcher_slice6ButtonE]+0x10): undefined reference to `typeinfo for QToolButton' I have an other component that uses QPushButton where I can build the src archive. If I replace QPusButton with QToolButton in this component, I get the same error. I have tried to find out what might be the cause of it, but was not successful so far. Both of this buttons are in the library qt5_widgets (listed in the file repos/libports/lib/mk/qt5_widgets_generated.inc) Best regards, Pirmin

4 5

First steps with Sculpt on Dell XPS 13
by Roman Iten 17 Oct '18

17 Oct '18

Hi, for some time now I've been thinking about upgrading:) my day-to-day operating system from bare metal Linux to Sculpt. My Dell XPS 13 (9350) doesn't boot out of the box and I didn't had the time to investigate. Now the cool new report_dump gives me a chance to easily spot problems when using Sculpt on my laptop. So I prepared "Sculpt as a hardware-probing instrument" as described in the release notes [1]. But it seems like the XPS doesn't boot far enough as no reports are dumped... I suspected there's probably an issue related to the XPS' display resolution of 3200 x 1800. After all it's clearly been declared in Sculpts hardware requirements [2], that displays with a higher resolution than 2560 x 1440 "are not expected to work". I tried to artificially restrict the resolution to FHD [3]. The internal display still doesn't work, but when an external monitor is connected via an USB-C dock or adapter (!), the Leitzentrale is displayed and the report_dump subsystem dumps reports to the flash memory. Using Leitzentrale, I then updated config/fb_drv to enable the internal display with it's native resolution. All screens go blank, but now I have a log to share [4] (the reconfiguration of the fb_drv happens after line 500) So far my very first experiences with Sculpt on the Dell XPS 13. And here some related questions: 1. What do you think about the idea to generally restrict the resolution of the initial fb_drv configuration to the maximum resolution supported by Sculpt (instead of that of the connected display(s), which may break Sculpt), similar to [3]? This would also help if, for example, an external 4K TV is connected during boot. 2. On Sculpt, most/all? internal displays report only their native resolution. On the XPS this is 3200 x 1800 and I can't force a lower resolution. Although under Linux, xrandr reports a bunch of supported resolutions from 3200 x 1800 down to 640 x 360. Does the intel_fb_drv under Genode intentionally reports and supports only the native resolution? 3. Should I create an issue regarding [4] on GitHub? 4. Instead of installing Sculpt directly on my current laptop I consider to buy a new XPS 13 (9370). It has a Killer 1435 wireless module featuring a Qualcomm Atheros QCA6174A chip which seems to be supported on Linux by the ath10k module... Has someone any experience (or assumptions) whether there's a chance that it will work on Sculpt (right now or in the near future)? Cheers, Roman [1] https://genode.org/documentation/release-notes/18.08 [2] https://genode.org/documentation/articles/sculpt-tc [3] https://github.com/rite/genode/commit/ba65d4307e892320b791b52cdccca1d421694… [4] https://gist.github.com/rite/1e5602c9ed55a810fe9306475e3962c0#file-log-L501

10 19

Hardware Compatibility List
by baconicsynergy＠protonmail.ch 17 Oct '18

17 Oct '18

Hello friends, Is there a list of hardware that Genode is known to function properly on? What laptop(s) does Genode run on the best? I can't find any on genode.org :3

2 1

measure execution time
by lzSun 16 Oct '18

16 Oct '18

Hello all, I have implemented a service in genode os which is based on tz_vmm demo on i.mx53-qsb board. Now I want to measure the execution time of the service. I measure the execution time both in linux and genode,but find a incredible result: 1. In linux, I record the start time t1 and end time t2 ,then I use t2-t1 to measure the execution time. 2. In genode, I get a timer use : Timer::Connection _timer(_env), and use _timer.elapsed_ms() to get the start and the end of the service time and use end-start to calculate the execution time. However, the result of the two world are far from each other. In linux, it's about 45 seconds, but in genode it's only about 11 seconds. I know, in linux side, it will first open the help module in kernel space and issue smc to switch to secure world and switch back when service is done. But I think it won't take such a long time.And actually, I think the execution is about 45 seconds which I observed from the start and end message. So I doubt there's problem with my measurement in genode. My settings: 1. In tz_vmm.run: add targets {drivers/timer} add <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> add boot_modules {timer} 2. In service file , server.cc: add #include <trace/timestamp.h> in funcion add: Timer::Connection _timer(_env); start=_timer.elapsed_ms(); Any help will be grateful, thanks! ------------------ Best wishes

1 0

FOSDEM 2019 - Microkernels developer room - CfP
by Sebastian Sumpf 11 Oct '18

11 Oct '18

FOSDEM 2019 - Microkernels and Component-based OSes devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2019 [1] in Brussels, Belgium and will share a developer room on Sunday February 03, 2019 [2]. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-, unikernel-, and componenent-based operating systems. Possible topics include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * enabling support for hardware (architectures, device drivers) * used languages and tools * maintenance and testing * security and robustness * trends and challenges * use cases, experiences, lessons learned and demos Please use the Pentabarf [3] system to submit your proposals. You do not need to create a new account if you already have one. When in doubt, please use the devroom mailing list [4]. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the mailing list. The deadline for your proposal is on December the 1st 2018. Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract (one or two paragraphs) * duration of your talk (please, at least 25 and no longer than 55 min) The official devroom schedule (along with the accepted talks) will be announced on December the 15th on the devroom's mailing list and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. About the devroom Since the first Microkernel devroom in 2012 this devroom has been part of each following FOSDEM. By now it has become a somewhat institutionalized tradition for the micro kernel community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the Microkernel devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in Brussels. The year 2019 will not be any different, so there is going to be a microkernel family dinner on Saturday night. We try place a reservation, so we will inform you about the exact location and time later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. Important dates recap * 01.12.2018: Deadline for submissions * 15.12.2018: Schedule published and speakers notified of acceptance * 03.02.2019: The devroom takes places Links [1] http://fosdem.org [2] https://fosdem.org/2019/practical/transportation [3] https://penta.fosdem.org/submission/FOSDEM19 [4] https://lists.fosdem.org/listinfo/microkernel-devroom See you all at FOSDEM!

1 0

VirtualBox Guest Additions
by John J. Karcher 04 Oct '18

04 Oct '18

Hello Everyone, One of the top items on my personal Genode wish list is the VirtualBox Guest Additions. I have never ported a serious software project across platforms (and am not a Genode expert - yet), so I am not the best person for the job. But it is a personal "itch", so I will dig in and do my best if no one else is already working on it. Below I will briefly share what I have discovered in my limited research. Any advice or insight would be greatly appreciated. To make a long story short, I have only found 3 useful sources of information about porting the Guest Additions: 1. The source code from the VirtualBox project itself [1] 2. A page on the OSDev wiki [2] 3. An e-mail on the VBox-Dev mailing list [3] If anyone is aware of any more info, please let me know. To make a long story short, the interface to the VirtualBox host is through a virtual PCI device (using IRQ and MMIO). Once this interface is in place, the various pieces (e.g. time sync, shared folders, etc.) can be added individually. There are several ports of the Guest Additions in the VirtualBox source tree, and they share a lot of common code, but there doesn't seem to be a common skeleton among the OS-specific parts of the code. On the other hand, the OSDev page takes a minimalist, low-level approach. This is probably the general path I will follow, at least to start. [1] https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions [2] https://wiki.osdev.org/VirtualBox_Guest_Additions [3] https://www.virtualbox.org/pipermail/vbox-dev/2007-July/005860.html Wish me luck! -- John J. Karcher devuser(a)alternateapproach.com

1 0

Sculpt VC Depot Configuration
by John J. Karcher 02 Oct '18

02 Oct '18

Hello Everyone, I may be missing something obvious, but I can't find where to add a new depot to a Sculpt VC instance (for run-time installation). Can this be configured at run-time? Thanks! -- John J. Karcher devuser(a)alternateapproach.com

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users