users

users@lists.genode.org

2317 discussions

Rust Project Ideas
by nsf＠ksu.edu 22 Feb '24

22 Feb '24

Hello Genodians, I am new to Genode and am looking into projects I might be able to do to help get practice with Genode and get a better understanding of rust. On the last rust update, it seemed like the Genode team determined one of the next steps would be to explore rust on top of native Genode framework. Would there be a project that would be able to help achieve this goal? I thought of working with the Gnode api to create a transition layer so that components written in rust can directly work with the api. Would this be a project be helpful or would something else be more appropriate? Thanks in advance for the help, and if I am off base, please let me know! Sincerely, Nathan

4 4

Testing pc_linux image
by Pirmin Duss 16 Feb '24

16 Feb '24

Hello Genodians I'm back to working on the integration of the Intel IGC driver in to the pc_nic_drv. I have rebased my work tree to latest master. I can run the driver and it starts up. The log output is as follows: [init -> nic_drv_igc] NR_IRQS: 4352, nr_irqs: 4352, preallocated irqs: 256 [init -> nic_drv_igc] time-clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns [init -> nic_drv_igc] time-clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [init -> nic_drv_igc] time-clocksource: Switched to clocksource dde_counter [init -> nic_drv_igc] e1000-e1000_main: Intel(R) PRO/1000 Network Driver [init -> nic_drv_igc] e1000-e1000_main: Copyright (c) 1999-2006 Intel Corporation. [init -> nic_drv_igc] e1000e-netdev: Intel(R) PRO/1000 Network Driver [init -> nic_drv_igc] e1000e-netdev: Copyright(c) 1999 - 2015 Intel Corporation. [init -> nic_drv_igc] Intel(R) 2.5G Ethernet Linux Driver [init -> nic_drv_igc] Copyright(c) 2018 Intel Corporation. [init -> nic_drv_igc] igc 04:00.0: PCIe PTM not supported by PCIe bus/controller [init -> nic_drv_igc] igc 04:00.0 eth0: MAC: d8:bb:c1:5b:3a:18 [init -> nic_drv_igc] sched_clock: Marking stable (144026000, 246486000)->(405777000, -15265000) [init -> mac_report_rom] report 'nic_drv_igc -> devices' [init -> mac_report_rom] <devices> [init -> mac_report_rom] <nic name="eth0" mac_address="d8:bb:c1:5b:3a:18"/> [init -> mac_report_rom] </devices> [init -> nic_drv_igc] igc 04:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [init -> nic_drv_igc] create uplink for net device eth0 [init -> nic_router] [uplink_igc] NIC sessions: 1 [init -> nic_router] [uplink_igc] snd ETH d8:bb:c1:5b:3a:18 > ff:ff:ff:ff:ff:ff IPV4 0.0.0.0 > 255.255.255.255 UDP 68 > 67 DHCP DISCOVER d8:bb:c1:5b:3a:18 > 0.0.0.0 [init -> nic_router] [uplink_igc] rcv ETH b4:2e:99:f9:18:72 > d8:bb:c1:5b:3a:18 IPV4 0.0.0.0 > 0.0.0.0 The last two lines get repeated. In Wireshark I see that the DHCP server offers an IP to the MAC of the Intel IGC, but nic_router doesn't see that. To be sure, that nothing is missing from the binary I would like to test the Linux kernel Image that get built by run make pc_linux. From what I understand, this wouldn't even need a root filesystem, as the kernel can do DHCP on its own. Before I start piecing something together, I'd like to ask, if someone does have a ready solution which allows to boot that image via iPXE? Regards, Pirmin

2 2

Genode::Registry blocking(?) on for_each call
by Zachary Zollers 15 Feb '24

15 Feb '24

Hello Genodians, I am attempting to familiarize myself with some of the provided data structures. When playing around with the Registry class, I encountered an interesting error. [1] is a GitHub gist containing the code I am running. I am wanting to use the Registry class to keep track of services announced by children on a parent component. When looking though the Genode repository, this seemed to be the accepted way to do this (please correct me if I am misunderstanding). When I run this code, I get the following output: Genode 23.11 87 MiB RAM and 63252 caps assigned to init [init -> parent] Child requested session: 'PD' Error: illegal READ at address 0x4 by pager_object: pd='init -> parent' thread='ep' ip=0x7acf4 I would like to pass a reference to the Registry to each instance of Child_policy so I can use services announced by other children. As an additional experiment however, I tried creating a new Registry as a class member for each Child_policy (see the comment at the top of the Tutorial::Child class). This resulted in the following output: Genode 23.11 87 MiB RAM and 63252 caps assigned to init [init -> parent] Child requested session: 'PD' To me, this indicates that the for_each call is blocking. I cannot see, however, what would be holding the mutex before I get to this point. Any pointers in the right direction would be greatly appreciated :) [1] https://gist.github.com/zgzollers/48181fbc2dac6e51015602c6329593f9 Thanks, Zachary Zollers

3 3

open/ close/ read
by Michael Grunditz 14 Feb '24

14 Feb '24

Hi Is open() read() close() supposed to work? For me they doesn’t. It works sometimes but not all times. It also doesn’t read the file it just reads the first bytes or kbytes if large file. fopen fread fclose is ok and stat. Michael

3 7

Child Component Not Starting
by Zachary Zollers 13 Feb '24

13 Feb '24

Hello Genodians, I am attempting to create my first Genode system scenario from scratch. After following some of the available tutorials, I feel like I have a foundational understanding of the client/server interfaces. I am now attempting to create a system that utilizes the parent/child interfaces. I am intentionally using the more bare-bones Child interface over the Sandbox API for educational purposes. [1] is a link to a GitHub gist containing my parent component and runscript. The child is the simple hello world program provided at the beginning of the Genode Foundations book. At present, everything seems to start without errors, but the output from the child is not displayed. After a couple of days of fumbling around, I have not been able to get this to work properly. Any suggestions you may have are greatly appreciated. As I said previously, this is my first attempt at creating a Genode system from scratch. Any feedback you may have is greatly appreciated (even if it is not directly related to the issue at hand). [1] https://gist.github.com/zgzollers/397f56b66179f3276e048be8a8a7a543 Thanks in advance, Zachary Zollers

3 3

link state with the new usb_net driver
by Pirmin Duss 02 Feb '24

02 Feb '24

Hello Genodians While testing my changed usb_net driver that supports SMSC95XX on arm_v8a I discovered, that the link state isn't propagated to the connected nic_router as it has been with the old version. With the old driver the log output of nic_router was as follows when the cable was connected/disconnected: <connect cable> [init -> nic_router] [secondary_nic] NIC sessions: 1 [init -> nic_router] [secondary_nic] dynamic IP config: interface 10.10.10.10/16, ... <disconnect cable> [init -> nic_router] [secondary_nic] dynamic IP config: none [init -> nic_router] [secondary_nic] NIC sessions: 0 With the new driver nic_router always reports: [init -> nic_router] [secondary_nic] NIC sessions: 1 As I do not have any other devices that need the usb_net driver, I'm not sure, if this only happens for my driver or if this is consistent with all other device types. Could someone with an other usb_net driven device give me feedback, if other devices show the same log outputs? Regards, Pirmin

2 2

using tool/dde_linux/ scripts for usb_net driver
by Pirmin Duss 30 Jan '24

30 Jan '24

Hello Genodians While upgrading to Genode 23.11 I noticed, that the new usb_net_drv no longer supports the smsc95xx which is in our IoT gateway. The source file for this was used by the old driver but isn't in the sources.list of the new driver. I started by adding the missing source file. After fixing a missing include path I have a number of unresolved symbols. To use tool/dde_linux/create_dummies some variables need to be set - TARGET -> drivers/usb_net - DUMMY_FILE -> /tmp/generated_dummies.c - ARCH -> x86_64 - BUILD_DIR -> build/x86_64 - LINUX_KERNEL_DIR -> build/x86_64/pc_linux/x86_64 This generates a file that contains the missing functions and variables. If I change the following: - ARCH -> arm_v8a - BUILD_DIR -> build/arm_v8a - LINUX_KERNEL_DIR -> build/arm_v8a/imx_linux/arm_v8a The generated file only contains the header. Is it save to copy the functions generated in the x86_64 run in to the generated_dummies.c for the arm_64 spec? Regards, Pirmin

2 2

Getting screen coordinate of a window
by Michael Grunditz 28 Jan '24

28 Jan '24

Hello! Can I get screen coordinates of a window? I would like to be able to caputure absolute mouse events and convert them to the window coordinate system. I don't want to have relative mouse movement like I see in many examples. In my context it doesn't work very well. BTW the handle_relative_motion never seems to return anything. Is there a configuration that I need? Would be terific if I could by some function get window internal coordinates, but handle_relative_motion might not be something for that? I also want to know if there are routines better suited than memcpy for ploting large buffers? I have noticed that if I put something in a loop without a little delay the system crawls. Is the Gui not preemptive? As little as 10ns is enough. I plot 640x480x4. It acts a bit strange. Each second a frame takes less than 1/60 seconds. There are 3 frames that runs slower and back to quick. I have nano sleep that is based on that timing. /Michael

4 8

Roadmap 2024
by Norman Feske 19 Jan '24

19 Jan '24

Hello everyone, in his most recent posting, Credric already noted that now is the time of year again to reflect on our achievements of this year and to anticipate topics to pursue next year. To keep up with this fine tradition, let me kick off our road-map discussion with my personal perspective. Reflections of 2023 As indicated by the overarching theme of the last roadmap "Rocking the platforms we support!", Genode's four releases of 2023 had a strong focus on low-level platform work. This has been especially visible on modern PC platforms like the Gen12 Framework laptop I have under my fingertips right now. At the beginning of 2023, Sculpt OS was in principle working on this machine, but with compromises that spoiled the user experience: fan noise, an erratic touchpad (using the firmware's PS/2 emulation), Fn key having no effect, strange issues when re-plugging an external display, and no indication of the battery state. In the meantime, not only are all these rough edges gone, but we even gained the ability to exercise precise control over the machine' performance/frequency/temperature/power characteristics using an interactive GUI. I think it's fair so say that Genode advanced far beyond the state of "working" and has entered the territory of "rocking". I wish to name four further personal highlights of the year: First, we got the mobile version of Sculpt OS into the hands of a pilot group of users who provided instructive feedback to us. From my perspective, the system-update mechanism that I created for this purpose turned out to be an almost pivotal point in the evolution of Sculpt OS because it reduces the effort and risk of test-driving experimental versions to almost zero. It was a pleasure to see how e.g., Johannes leveraged this new way of gathering feedback for his IOMMU line of work. Providing system images for testing has become a second nature. Second, the road map for 2023 envisioned Sculpt OS running on our custom base-hw kernel on the PC. We identified DMA protection and virtualization support as the two remaining showstoppers. With much excitement, I followed how both of these deeply technical topics got covered over the course of the year. Third, Goa finally emerged from a personal project of mine to an official Genode project led by Johannes. I'm stunned how much the project benefited from this change. All of the remaining backlog of my vague plans - I'm thinking of the index-project support or bash completion - got eventually realized in a way true to the spirit of the project. The fate of the Goa tool makes me immensely happy. Fourth, during the first half of the year, I found myself intensively working on Genode's new debug-monitor component, pursuing the idea to implement a debugging instrument as a specialized version of init augmented with the GDB protocol. This engagement was pretty much motivated by a customer. The result of my initial work then seamlessly transitioned into the hands of Christian Prochaska who did a marvelous job with steadily advancing this line of work towards our joint vision of on-target debugging on Sculpt OS. The technical feats notwithstanding, I found the frictionless way of collaborating a pure joy. Besides the highlights above, one topic close to my heart was the creation of the dialog API that I designed as necessity to make the code of Sculpt's administrative user interface maintainable and easy to extend in the longer run. Plans for 2024 After concentrating so intensively on topics below the surface, I now long for reaping user-visible rewards. Speaking of the dialog API just mentioned, I see potential in using this new infrastructure for Genode-native applications and immediately think of the file manager that I already wanted to tackle this year. But I also have plenty of ideas to make Sculpt OS more user friendly. What about presenting the README files of software packages directly in the GUI? Making the component graph scrollable? Allowing the user to select an arbitrary directory as a file system to a component? Buttons for saving the current deployment or the settings? Beyond Sculpt's administrative user interface, I'd also like to attend the GUI stack. I think of refining the GUI-session interface to remove tearing artifacts, to better support desktop-UI-paradigms like drag'n'drop, and to explore the opportunity of using nitpicker's mechanisms at the application-level, not only at the window-composition level. Hence, I'd condense my ambition for the next year to "Sculpt OS usability". Device-wise, I'm going to continue my engagement with the PinePhone and look forward to the upcoming MNT PocketReform laptop. Above I presented my personal view. How about your's? I would very much appreciate you sharing your feedback, ideas, concerns, and plans regarding Genode. How are your interests aligned with the perspective shared above? Do you see specific pain points that deserve the attention of Genode's core developer team? What is your perspective on Genode's past year's accomplishments? Can you share your ambitions or even concrete plans? How and where would you like to see Genode at the end of 2024? 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

18 39

Re: Random Thoughts / Questions (inspired by Roadmap discussion)
by ttcoder＠netcourrier.com 19 Jan '24

19 Jan '24

Hi John, > Cedric, your HoG screenshot looks great! Please keep us informed - I > hope your TuneTracker transition goes smoothly! I might get in touch off-list to take you up on your "beta testing" offer (from a while back!), my current tester has network-card issues and it might be good to broaden the test base, try out different hardware with different Nic adapters. > Depot Package Discoverability: > Several people have mentioned that it is difficult to discover which > Sculpt depot packages are available, and from where. > > I am going to try to put a temporary solution in place for this, until > someone develops something better. No promises on timing, but I want to > bring the badly neglected "Genode Corner" [1] up to date, then add a > front-end for listing / searching Depot packages. > > This will probably take the form of a daily process to pull in the depot > indexes, add a search page, and maybe an RSS feed system. If anyone has > any implementation advice or feature requests, please let me know. > > [1] https://www.alternateapproach.com/computing/genode/genode_corner/ Well if it was my project (or if I was part of the implementing team ^^) I'd probably try to write the back-end script in V, as I suspect it would really fly for that kind of job : downloading/parsing an XML file and generating server-side data. The trouble is, I'm not sure how it would interact with the front-end, since it's a compiled langage (and I have extremly limited front-end experience). Cedric

2 1

← Newer
1
...
8
9
10
11
12
13
14
...
232
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users