users March 2012

users@lists.genode.org

10 participants
14 discussions

Has anyone had success with GCC SVN/4.7
by Taru Karttunen 04 Sep '12

04 Sep '12

Hello I was hacking around gccgo (go implementation in gcc) and I can get the runtime and the compiler compiled when using gcc-4.7-RC-20120314. But the issue becomes rest of Genode not liking a newer gcc. Has anyone else had success with either GCC 4.7 or a SVN version of GCC? My current issue is: Library libc MERGE libc.lib.so fd_alloc.o: In function `Libc::file_descriptor_allocator()': /home/taruti/genohack/genode/libports/src/lib/libc/fd_alloc.cc:26: undefined reference to `__dso_handle' /usr/local/genode-gcc/bin/genode-x86-ld: fd_alloc.o: relocation R_X86_64_PC32 against undefined hidden symbol `__dso_handle' can not be used when making a shared object Has anyone got an idea how to solve this? ps. if someone is trying this, one has to compile libsupc++ explicitely with -fPIC to get cxx working. - Taru Karttunen

3 9

Further questions
by Peter Nguyen 30 Mar '12

30 Mar '12

Hi, Thanks you very much for that. I now have it running. I have another question about Genode. More specifically, I was wondering whether any of the Iguana services at all. I ask this given that the weaver.xml file refers to memsections and pds (i'm assuming that means protection domains). Peter ----- Forwarded message from Norman Feske <norman.feske@...1...> ----- Date: Tue, 05 Jan 2010 08:43:36 +0100 From: Norman Feske <norman.feske@...1...> Reply-To: Genode OS Framework Mailing List <genode-main(a)lists.sourceforge.net> Subject: Re: Broken assertion To: Genode OS Framework Mailing List <genode-main(a)lists.sourceforge.net> Hi Peter, this is a different error as the one mentioned in the Wiki. It actually tells you what's wrong. ;-) In the 'weaver.xml' file, there is a memsection referring to a file called 'config'. This is the configuration file of Genode's init process. You can use a copy of the template provided at 'os/config/demo'. You can either specify this file as filename for the 'config' module entry in 'weaver.xml' or copy it to your '<builddir>/bin/' directory (and of course rename it to 'config'). This bit was missing in the Wiki. So I added it to the Wiki page. Thank you for pointing it out. Norman Peter Nguyen wrote: > Hi, > > In the wiki describing how to build Genode on OKL4, does the bug alert refer to > following message: An error occurred: [Errno 2] No such file or directory: > 'config'? > > I've followed the build instructions, and i've changed the value as suggested as > the quick fix, but I still get this error. > > As usual, any help would be greatly appreciated. > > Peter ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Genode-main mailing list Genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main ----- End forwarded message -----

3 4

AHCI example not working
by Taru Karttunen 24 Mar '12

24 Mar '12

Hello The AHCI-example seems to fail at least on x86-64 + Fiasco.OC. make run/ahci ... int main(): --- create local services --- int main(): --- start init --- int main(): transferred 43 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open file "ld.lib.so" [init -> ahci] --- AHCI driver started --- [init -> test-ahci] --- AHCI block driver test --- Quota exceeded! amount=4096, size=4096, consumed=4096 [init -> ahci] upgrade quota donation for SIGNAL session Quota exceeded: acpi -> pci_drv memory for slab: 1024 used quota: 357728 ds_size: 32768 sizeof(Ram_session_component): 352 quota_limit: 385024 [init -> acpi] could not expand dataspace pool Error: Test execution timed out make: *** [run/ahci] Error 254 Making the various quantums larger does not seem to help. - Taru Karttunen

2 3

Local network between l4linux and genode application
by Ivan Loskutov 23 Mar '12

23 Mar '12

Hello. How to make network connection betwen server in l4linux and genode application (for example Arora)? Has Genode implementation for this case?

2 5

Linux GUI application on Nitpicker
by Ivan Loskutov 22 Mar '12

22 Mar '12

Hello. Norman Feske showed demo on FOSDEM where GUI application from linux was displayed on Nitpicker. Is demo specific to OKLinux or can be implemented on l4linux too? I can't find an example for this in sources.

3 3

Live CD planning
by Norman Feske 22 Mar '12

22 Mar '12

Hello everyone, according to our road map, we intend to release another Genode Live CD in the not-too-distant future. The live CD should not be just an update of the current one - that would be rather boring. Instead, the goal behind the new live system is to provide a glimpse of our vision to use Genode as OS for doing productive work. Even though it will still have the character of a tech demo rather than a productive system, its presentation and content will be mainly focused on topics important to (at least our personal notion of) general-purpose computing. The previous live CD was designed to be easily approachable and relatively simple. The new system should be attractive to people who enjoy tinkering with a command-line interface. I propose the following demo setups to be included on the live system: 1. Self hosting - running the GNU tool chain on Genode The setup should showcase the use of Noux to run the GNU userland natively to accomplish everyday tasks such as editing and compiling source code. The most distinctive concept of Noux compared to traditional Unix systems is that each working topic can be executed in a specially tailored instance. So I would like to present one Noux instance with only VIM and coreutils (read-only) and the Genode source code (read/writable). This is for doing editing work. A second instance includes coreutils, make, GCC, binutils, findutils, the Genode source code (all read-only), and the build directory (read/writable). This is for compiling. By separating the editing from compiling, we can make sure that no bug in the build system or tool chain may affect the source code. A third Noux instance should allow us to execute the resulting binary and look at its output. This instance won't be able to access anything besides the actual binary. 2. On-target debugging - use GDB to debug a subsystem With GDB monitor, we are able to debug Genode processes over a serial line or a TCP connection. Using Noux, we could principally run GDB on the system as well and simply connect it via the terminal-session interface to GDB monitor. This would allow us to execute most steps of our GDB tutorial directly on the machine. As a nice side effect, people who explore this setup will learn how to use GDB. .-) 3. L4Android Running L4Android on Genode is merely a feature demo but flavoured with a bit of hackability. Besides showing the Android framebuffer output, I would like to show the Linux kernel output and the Genode LOG output side-by-side (using small fonts). The remaining part of the screen should be used for a console with access to the Android debugger. This way, users can dive right inside the running Android OS. 4. Media replay This setup should present how Qt4, audio output, and video decoding are running together. In addition, I'd like to enhance the setup with (some kind of) a real-time demonstration that facilitates Nitpicker and our Qt4 plugin mechanism. Using this mechanism it is possible to provide a data path for pixels originating from the video component to the screen but bypassing Qt4. Thereby, we can run the real-time critical video processing at a higher static priority than Qt4, yet still present Qt4 and the video component tightly integrated in one GUI. Overall presentation I propose to let the user run each of the setups exclusively by selecting a menu entry from a small area at the top of the screen (similar to how tabs work). By not allowing the concurrent use of multiple setups, we simplify the UI and guide the attention of the user to only one topic at a time. The main part of the screen will be used by fixed-positioned windows (maybe except for the media setup). The left side (maybe 25% of the screen width) will always present a PDF file (MuPDF in action!) with a brief description of what to see and what to do (e.g., explaining the GDB commands to use in the GDB demo). The middle and right portions of the screen will be used for displaying the actual demo and, depending on the demo, will be further subdivided. Technical qualities and limitations The previous live CD could only be started from CD-ROM, which is kind of old-fashioned. The new system should be bootable from both CD-ROM and USB stick. For the latter, we need to work on the USB stack because our existing USB driver (on linux_drivers) is outdated to a point where it does not work with most current-generation hardware. For the screen output, we will still use our VESA driver with a fixed video mode of 1024x768. Obviously, this is quite behind the times but there are several reasons to have it this way. First, it works nicely - no additional work is needed. Second, most people will try out the live CD on VirtualBox or a similar VM. Here, a lower resolution than the host system does not hurt. Third, when giving presentations, 1024x768 have proven to work well with most data projectors. Last but not least, fixing the resolution allows us to design the graphical presentation pretty easily. In contrast, if we supported varying resolutions, static placement and sizing of screen portions would no longer be feasible. This screams for a tiled window manager, which we don't have yet. The live CD will use the Fiasco.OC kernel as this is the only kernel where L4Android and GDB are featured. Working topics I am current busy with getting Noux into shape for realizing the self-hosting and GDB setups. Once this is finished I will take care of the graphical touches, editing, and overall conceptual work. Stefan will take care of the Android setup, which comes mostly down to integrating existing components. The media setup is mainly worked on by Christian Prochaska. Sebastian is looking into the new USB stack. Of course, we will need to do comprehensive stability testing before releasing the live CD. Fortunately, each of the setups can be developed and tested independently. This enables us to pre-release each setup as a different ISO image for everyone to test. I will certainly do so for my work. This way, we can start testing way before the final integration phase. Release date? There is no definitive release date yet. Given the rather ambitioned plan outlined above and our past experiences with the substantial testing effort needed for such an undertaking, I think that the release in the first half of May is feasible. But that is just a rough estimation from my side. Do you have further ideas for setups to feature on the live CD or remarks on the current plan? Please don't hesitate to share them with us. Or maybe you interested in lending a helping hand for any of the topics? 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

Joint GSoC topic with HelenOS
by Norman Feske 19 Mar '12

19 Mar '12

Hello, despite of our unsuccessful attempt to apply to Google's Summer of Code, there are some very good news: The HelenOS project has been accepted as mentoring organization and has prepared a joint topic with Genode. If you are a student interested in advanced OS-level development in the context of Genode, please have a look at the following description: HelenOS as a Genode platform http://trac.helenos.org/ticket/419 Because of the advanced level of this topic, you will be working in close collaboration with the main developers of both projects HelenOS and Genode. The mentoring role on the Genode side will be filled by Stefan Kalkowski and me. On the HelenOS side, Martin Decky and Jakub Jermar have shown interest in mentoring this work. I would be excited about a student brave enough to dive into this realm and about the opportunity to bring both projects more closely together. If you are interested, please let us know! 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

Issue #122: Design and implement hack'n'hike event for the Genode crowd
by Norman Feske 19 Mar '12

19 Mar '12

Hi Folks, let me point you to the following issue in our issue tracker: https://github.com/genodelabs/genode/issues/122 For those who are not following the issue tracker closely, we have just fixed the date and location of the first Genode Hack'n Hike event, which is all about hacking and relaxing in the wonderful surrounding of the Saxon Switzerland. Counting the definitive attendees so far, there is still a bit of space left in our accommodation. So if you are interested, please make yourself known and join the discussion of the issue #122. 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

Fwd: [Genode Labs] Your organization application has been rejected.
by Norman Feske 16 Mar '12

16 Mar '12

FYI, no GSoC fun for Genode this year. -------- Original Message -------- Subject: [Genode Labs] Your organization application has been rejected. Date: Fri, 16 Mar 2012 17:45:19 +0000 From: no-reply@...105... To: norman.feske@...1... Thank you for submitting "Genode Labs" organization application to Google Summer of Code 2012. Unfortunately, we were unable to accept your organization's application at this time. We received many more applications for the program than we are able to accommodate, and we would encourage you to reapply for future instances of the program. Best regards, Google Open Source Programs

1 0

Building Genode for Gumstix Overo platform
by Ivan Loskutov 12 Mar '12

12 Mar '12

*Hello Genodians! I tried to build Genode for Gumstix Overo platform. I added new build target foc_overo and implemented framebuffer and touchscreen drivers. I added my changes to my fork on Github https://github.com/iloskutov/genode First question about core. Core for Fiasco.OC used LD_TEXT_ADDR = 0x140000 in base-foc/src/core/target.inc. In Overo memory locations starting at 0x80000000. I think, I need to set LD_TEXT_ADDR = 0x80140000. I added it to base-foc/src/core/arm/target.inc but it applied for all ARM targets. How can I set it for my Overo target only? In our project we use Chestnut43 board for prototype. This board has 4.3” LCD 480x272 pixels. I get display configuration for this LCD from Linux driver. Display work, picture is drawing, colors are correct. But sometimes window drawn with distortion (normal drawing http://dl.dropbox.com/u/8558928/pic_1.jpg , distorted: http://dl.dropbox.com/u/8558928/pic_2.jpg http://dl.dropbox.com/u/8558928/pic_3.jpg ). I can’t solve this yet. Maybe I have wrong configuration for display controller. Touchscreen based on ADS7846 chip. I wrote simple driver. How can I do calibration implementation? I see several solutions: 1. Create new input event for touchscreen. Then driver can to send raw data to Nitpicker. Nitpicker translate this data to screen coordinates use calibration constants which must be loaded from some application. 2. Calibration data must be loaded to the touchscreen driver. But how make it correct? Maybe you can to offer best solution? Drivers implementation are simple. I don’t write drivers for GPIO and McSPI as independent part yet. For test platform I wrote simple Qt application. I don’t understand how to work resolution dependency. Where need I write all dependencies for automatic build my target. I used qt4/run/qt4.run as base for my run target. Execution “make run/qt_test” failed with error “cannot stat `bin/ dejavusans.lib.so'”. Not all libraries was built. If I execute “make run/qt4” previously then my qt_test built without error.*

6 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users March 2012