users

users@lists.genode.org

6 participants
2306 discussions

memory size in tz_vmm
by lzSun 01 Nov '18

01 Nov '18

Hello, I am very interested in genode and I am working on tz_vmm demo using i.mx53-qsb board now. After the tz_vmm start, I find a boot message like this: " Genode 18.05 <local changes> 211 MiB RAM and 64535 caps assigned to init " To my understanding, it's present that the available memory that the genode os in secure world is 211MB. And After the system boot up, I use Top command to observe the memroy that normal world have which gives me like this: " Mem: 37956K used, 49444K free, 0K shrd, 68K buff, 26456K cached " This shows that the total memory the linux in the normal world can use is less than 150MB. And I have some questions about this: 1. Can this memory size be increased? For example, I want to increase the memory size that genode can use. To my understanding, this memory distribution between two worlds(secure and normal) can be configured. So I wonder whether I can determine this memory distribution. If it's indeed configurable, where I can find the source file to configure this and whether this configuration can be changed dynamically when the system is running. 2. As far as I know, the i.mx53-qsb have 1GB, but from the situation above, the total memory size is about 400MB which is far less than 1GB. So why can this situation happened? Thanks, Best wishes

2 1

Genode over RPI
by Moh 30 Oct '18

30 Oct '18

Hi Genode, it has been long time since i played with Genode. In the past, I was able to run Genode over a RPI Model B+ V1.2. nowadays, I am trying to run the same code, so i got another RPI with the same version (i.e. Model B+ V1.2 ) but Genode was not able to boot. ACT light keeps lighting on. The PI which is working has a SOC SAMSUNG 431 K4P4G324EG- RGC2 while the other RPI has ELPIDA b4432bbPA-10-F. What i should change to get it work in the second RPI. best,

2 1

use hard float in Genode
by lzSun 30 Oct '18

30 Oct '18

Hello, I wonder whether I can use hard float in Genode. I am now using Genode 18.05 and was working on tz_vmm demo. I add "-CC_OPT += -mfloat-abi=hard -mfpu=vfp" in "/repos/base/mk/global.mk" file. It seems Genode tool chain can recognize this arguments,but print error message like this: "/usr/local/genode-gcc/bin/genode-arm-ld: error: supc++.o.tmp uses VFP register arguments, /usr/local/genode-gcc/bin/../lib/gcc/arm-none-eabi/6.3.0/../../../../arm-none-eabi/lib/libsupc++.a(class_type_info.o) does not" Form the error message, I guess it can't use hard float in genode because some static library in genode tool chain are build by soft float.Am I right? Any help will be OK, thanks. ------------------ Best wishes

2 1

HPET description not found when using UEFI boot with Nova
by Parfait Tokponnon 28 Oct '18

28 Oct '18

Hello all, We would like to test the UEFI framebuffer driver on Nova but the booting hangs just after this log on serial output : NOVA Microhypervisor v8-b156131 (x86_64): Oct 24 2018 16:04:18 [gcc 6.3.0] [MBI2] Command: $make run/demo KERNEL=nova with QEMU_RUN_OPT := --include power_on/qemu --include log/qemu --include image/uefi. QEMU emulator version 2.12.92 (v3.0.0-rc2-1-ga0c7f2c-dirty) This is a fresh Genode directory, just cloned from github. Actually, the booting hangs in function acpi::setup() because the HPET signature is not found when parsing the RSDT acpi table. Here is the list of signatures found in the acpi table : {FACP, APIC, SSDT, BGRT}. It is worth precising that it works fine when using the default (non-uefi) configuration. In this case, the acpi signatures list is {FACP, APIC, HPET, MCFG}. How can I fix this?

2 2

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users