users

users@lists.genode.org

2285 discussions

Building for Raspberry Pi Ubuntu
by buzz heavyyear 30 Nov '13

30 Nov '13

Greetings, I'm trying to build the Pi platform. Running: gcc-arm-linux-gnueabi --version gives:arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 I've created the build.rpi directory with platform as hw_rpi. I then do a 'make run/demo' which results in : using run script /home/nick/genode-13.08/base-hw/run/envusing run script /home/nick/genode-13.08/os/run/demo.runspawn make core init drivers/timer server/nitpicker server/liquid_framebuffer app/launchpad app/scout test/nitpicker server/nitlog drivers/framebuffer drivers/pci drivers/inputmake[1]: Entering directory `/home/nick/genode-13.08/build.rpi'checking library dependencies...Skip target core/arndale because it requires platform_arndaleSkip target core/imx31 because it requires platform_imx31Skip target core/imx53 because it requires platform_imx53Skip target core/panda because it requires platform_pandaSkip target core/pbxa9 because it requires platform_pbxa9Skip target core/vea9x4/no_trustzone because it requires platform_vea9x4Skip target core/vea9x4/trustzone because it requires platform_vea9x4 trustzoneSkip target drivers/framebuffer/imx53 because it requires imx53Skip target drivers/framebuffer/omap4 because it requires omap4Skip target drivers/framebuffer/pl11x/pbxa9 because it requires pl11x platform_pbxa9Skip target drivers/framebuffer/pl11x/vea9x4 because it requires pl11x platform_vea9x4Skip target drivers/framebuffer/pl11x/vpb926 because it requires pl11x platform_vpb926Skip target drivers/framebuffer/sdl because it requires linux sdlSkip target drivers/input/fiasco_ux because it requires fiasco x86Skip target drivers/input/imx53 because it requires imx53Skip target drivers/input/ps2/pl050 because it requires pl050Skip target drivers/input/ps2/x86 because it requires x86 ps2Skip target drivers/pci/device_pd because it requires novaSkip target drivers/pci/x86 because it requires x86 Library platform MERGE platform.lib.a Library mini_c COMPILE abort.o COMPILE atol.o COMPILE malloc_free.o COMPILE memcmp.o COMPILE memset.o COMPILE mini_c.o COMPILE printf.o COMPILE snprintf.o COMPILE strlen.o COMPILE strtod.o COMPILE strtol.o COMPILE vsnprintf.o MERGE mini_c.lib.a Library libz_static COMPILE adler32.o COMPILE compress.o COMPILE crc32.o COMPILE deflate.o COMPILE gzio.o COMPILE infback.o COMPILE inffast.o COMPILE inflate.o COMPILE inftrees.o COMPILE trees.o COMPILE uncompr.o COMPILE zutil.o MERGE libz_static.lib.a Library libpng_static COMPILE png.o COMPILE pngerror.o COMPILE pngget.o COMPILE pngmem.o COMPILE pngpread.o COMPILE pngread.o COMPILE pngrio.o COMPILE pngrtran.o COMPILE pngrutil.o COMPILE pngset.o COMPILE pngtrans.o COMPILE pngwio.o COMPILE pngwrite.o COMPILE pngwtran.o COMPILE pngwutil.o MERGE libpng_static.lib.a Library cxx COMPILE exception.o COMPILE guard.o COMPILE malloc_free.o COMPILE misc.o COMPILE new_delete.o COMPILE unwind.o MERGE supc++.o CONVERT supc++.o MERGE cxx.lib.a Library syscall COMPILE syscall.o MERGE syscall.lib.a Library base-common COMPILE allocator/allocator_avl.o COMPILE allocator/slab.o COMPILE avl_tree/avl_tree.o COMPILE child/child.o COMPILE console/console.o COMPILE elf/elf_binary.o COMPILE heap/heap.o COMPILE heap/sliced_heap.o COMPILE ipc.o COMPILE ipc/ipc_marshal_cap.o COMPILE lock/lock.o COMPILE process/process.o COMPILE server/common.o COMPILE server/server.o COMPILE signal/common.o COMPILE signal/signal.o COMPILE thread/thread_bootstrap.o COMPILE thread/trace.o MERGE base-common.lib.a Library startup COMPILE _main.o ASSEMBLE crt0.o MERGE startup.lib.a Library base COMPILE console/log_console.o COMPILE env/context_area.o COMPILE env/env.o COMPILE env/reload_parent_cap.o COMPILE thread/thread.o COMPILE thread_support.o MERGE base.lib.a Library launchpad COMPILE launchpad.o MERGE launchpad.lib.a Library blit COMPILE blit.o MERGE blit.lib.a Library scout_widgets CONVERT binary_closed_icon.rgba.o CONVERT binary_downarrow.rgba.o CONVERT binary_kill_icon.rgba.o CONVERT binary_loadbar.rgba.o CONVERT binary_mono16.tff.o CONVERT binary_opened_icon.rgba.o CONVERT binary_redbar.rgba.o CONVERT binary_sizer.rgba.o CONVERT binary_slider.rgba.o CONVERT binary_titlebar.rgba.o CONVERT binary_uparrow.rgba.o CONVERT binary_vera16.tff.o CONVERT binary_vera18.tff.o CONVERT binary_vera20.tff.o CONVERT binary_vera24.tff.o CONVERT binary_verabi10.tff.o CONVERT binary_verai16.tff.o CONVERT binary_whitebar.rgba.o COMPILE elements.o COMPILE platform_genode.o COMPILE refracted_icon.o COMPILE scrollbar.o COMPILE sky_texture.o COMPILE startup.o COMPILE tick.o COMPILE widgets.o MERGE scout_widgets.lib.a Program app/scout/genode/scout COMPILE about.o CONVERT binary_about.rgba.o CONVERT binary_backward.rgba.o CONVERT binary_cover.rgba.o CONVERT binary_forward.rgba.o CONVERT binary_genode_logo.png.o CONVERT binary_home.rgba.o CONVERT binary_index.rgba.o CONVERT binary_ior.map.o CONVERT binary_launchpad.png.o CONVERT binary_liquid_fb_small.png.o CONVERT binary_nav_next.rgba.o CONVERT binary_nav_prev.rgba.o CONVERT binary_pointer.rgba.o CONVERT binary_setup.png.o CONVERT binary_x-ray_small.png.o COMPILE browser_window.o COMPILE doc.o COMPILE launcher.o COMPILE main.o COMPILE navbar.o COMPILE png_image.o LINK scout Program core/rpi/core COMPILE _main.occ1plus: error: unrecognized command line option ‘-std=gnu++11’make[3]: *** [_main.o] Error 1make[2]: *** [core.prg] Error 2make[1]: *** [gen_deps_and_build_targets] Error 2make[1]: Leaving directory `/home/nick/genode-13.08/build.rpi'Error: Genode build failedmake: *** [run/demo] Error 255 Any ideas on how to proceed? Best regardsNick

4 11

Deploy genode on arndale
by Claudio L. 29 Nov '13

29 Nov '13

Hello, I'm new to genode but not new to develoment. I'd like to port genode to my dev board (Odroid-XU). To begin, I built the foc_arndale target successfully following the instructions. What I couldn't find anywhere is instructions on how to build a boot image for u-boot, which files are needed in the image, entry point, etc. Where can I find that information? An explanation or a link would be helpful. As a constructive critic to the Genode project: Documentation is fantastic, but there's nothing on how to create a partition, put all the files and boot on x86, or for other platforms as well (at least something generic, saying that we need to load the kernel image (where to find it in the path), the 'core' executable, drivers, build an image, etc. The description on the website begins with how to configure the 'init' process, which says it is loaded by 'core', which is the first task started by the kernel. So how do we put it all together in an image? I think we'd need an image with the kernel, core, init, the uart driver, and perhaps an sd/mmc driver, so that init reads the rest of the services from the sd card. I noticed the build directory has a large file, fiasco.image (15 MB?), what does it contain? I have too many questions, please bear with me. Once I learn all this, I can write some tutorials for other people like me. Thanks, Claudio

3 7

Announcement: Genode OS Framework version 13.11 released
by Christian Helmuth 28 Nov '13

28 Nov '13

Today we are happy to announce a fresh release of Genode, which is the 22nd release of the framework since the first version in August 2008. In the box this time is a good deal of new features and changes ranging from the base framework over platform support to applications and libraries: - Base framework - Dynamic resource balancing - C++11 enabled by default - Improved event tracing - Low-level OS infrastructure - Gigabit networking using the Linux TCP/IP stack - Improved nitpicker GUI server - New terminal services - New file-system server for hybrid Genode/Linux systems - New C-runtime plugin for accessing block devices - Device drivers - Graphics and USB HID for Raspberry Pi - HDMI for Samsung Exynos 5 - Applications and libraries - Qt5 with support for OpenGL and QML - New file systems based on FUSE - Port of DosBox - Runtime environments - Advanced GNU debugger features - ARM TrustZone support on Freescale i.MX53 - Platforms - Base-HW enabled for dynamic workloads - Lifetime management for kernel object on NOVA - Ballooning support for L4Linux running on Fiasco.OC Extensive information is available in the release documentation: http://genode.org/documentation/release-notes/13.11 Best regards and have fun with Genode -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://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

1 0

FOSDEM microkernel devroom submission deadline nears (Dec 1st)
by Julian Stecklina 27 Nov '13

27 Nov '13

Hello fellow microkernel hackers, the deadline for submitting talks to our devroom in Brussels is December 1st. If you haven't already, consider submitting a talk. Details are in the original CfP mail: https://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006068.html Submissions are done via FOSDEM's Pentabarf: https://penta.fosdem.org/submission/ If Pentabarf doesn't work for you, please send your proposal or any other questions regarding the devroom to: microkernel-devroom@...86... See you in Brussels, Julian

1 0

thread cpu utilization
by Jilong Kuang - SISA 26 Nov '13

26 Nov '13

Hello, I'm wondering if there is a way to get thread CPU utilization info for Fiasco.OC kernel in Genode. Best regards, Jilong -- Jilong Kuang Ph.D. | Samsung Research America - Silicon Valley (SRA-SV) Senior Research Engineer, Computer Science Lab t: 408-544-2705 c: 951-318-2995 jilong.kuang@...60...<mailto:jilong.kuang@...60...> Please consider the environment before printing this email. This message is intended only for the named recipient(s) above and may contain confidential or privileged information or protected attorney work product. If you are not the intended recipient, any review, dissemination, distribution or copying is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this message and its attachments from your computer and dispose of all other copies or printouts. Thank you.

3 2

base-hw ,,, What is CACHE_LINE_SIZE_LOG2?
by bob 19 Nov '13

19 Nov '13

Hi, Is CACHE_LINE_SIZE_LOG2 the line length in 32 bit words of the L2 Instruction or Data caches? That's the only cache line length I see in the board spec of the am335x in its TRM. I'm having a problem the initial start of the kernel, which appear to hang when the MMU is switched on in init_virt_kernel function. The tlb should set up correctly as I've defined the boards physical ram and MMIO regions in the Core_tbl class. The CACHE_LINE_SIZE_LOG2 parameter appears to be used as the stride length for walking the tlb. It is currently set at 2 only because that's the value used in the Panda and imx53 boards board_base.h. If that's not the problem, I'm at a loss as to what the issue could be since the CPU object is straight cortex-a8 from the arm_v7 architecture. Any pointers to how to diagnose the issue would be a great help. Thanks, Bob Stewart

6 14

NOVA : Intel IO ports and Guest Unrestricted mode.
by avinash singh 13 Nov '13

13 Nov '13

Hello Guys, I am experimenting with NOVA Microkernel and trying to run some code in guest mode. I am attaching test program which usage NOVA syscall binding interface to create test program. Objective of this test program to run cpuid and outb instruction in guest mode on intel machine. Here, I am launching intel vcpu in real mode paging disable with all necessary register setup properly in vcpu startup portal handler. Once you download this code, run make and modify run.sh to point NOVA hypervisor. I want to discuss two problem. Problem -1: This test program runs (guest mode code) cpuid instruction but outb/inb instruction never runs in guest mode. I see that for outb instruction gives IO portal invoked again and again. First, I delegate IO ports from Kernel in root pd. My vcpu execution context is created in root pd. I believe that IO ports should be accessible from guest mode after delegating IO ports from kernel to guest. Secondly, same code for AMD runs if I set proper AMD vcpu registers in startup handler. Problem -2 As Intel process supports unrestricted guest mode; Advantage of that, I can run real mode instruction in vCPU context with paging disable without doing any instruction interpretations. I set Unrestricted guest mode control bit in VMCS control registers, though intel vCPU never runs guest in unrestricted mode. But When I experiments this with KVM it works. My question is, does NOVA kernel supports to run intel cpu in unrestricted guest mode? or is there any trick to do that so. Please help me if I am missing something. Any help regarding these two issues would be very helpful. Regards Avinash Singh

3 6

Re: Writing Pin-muxing registers in an am3359.
by Bob Stewart 05 Nov '13

05 Nov '13

Christian, Thanks for your thoughtful reply. I've been looking at an extension to IO memory services in the kernel to access a restricted region, and adding parametric enabling of it is a good idea. My thinking was that setting the pin-mux registers should be done a driver separate from the gpio driver and that driver should read a config file to get the settings, then exit. All the use cases I'm dealing with require an initial set up then the applications execute using those settings without changing them. I'm currently using foc but I intend to go the base-hw route shortly. If time permits, I'll look into using the handle_slow_trap Thread method as learning exercise. Again, thanks for the reply. Bob Sent with AquaMail for Android http://www.aqua-mail.com

1 0

Writing Pin-muxing registers in an am3359.
by Bob Stewart 05 Nov '13

05 Nov '13

On a TI am3359 processor (Beaglebone Black) I'm attempting to attempting to control the GPIO pin-muxing through the Control subsystem registers which start at 0x4e100000. I can read and write to the GPIO0 through GPIO3 registers correctly through MMIO after attaching the device memory, but when I try to write to any of the pin mux registers nothing is written and no errors are output. The code I've written to set up pin muxing resides in a gpio driver which is a modified version of an am 33xx gpio driver I pulled from the ksyslabs.org repository. With verbosity turned on, I see the that the pin mux registers are attached to local memory: /Genode::Io_mem_session_component::Dataspace_attr Genode::Io_mem_session_component::_prepare_io_mem(const char*, Genode::Range_allocator*): I/O mem [44e10000,44e11000)// //[init -> gpio_drv] GPIO_control base is 0x44e10000 local is 0x4000/ I write a value of 5 to the register offset 0x800 into the Control dataspace: /[init -> gpio_drv] mmio write 0x4800: 0x00000005// //[init -> gpio_drv] void Omap_driver::set_pin_controls(int, int, int): B=1, P=0, Mode=5, Input=0, Offset=0/ In jdb I see that the value at 0x4800 has not changed after apparently writing 5 to it. I believe I've set up the IO memory mapping correctly, the values read from the pin muxing registers look correct, and the GPIO subsystem appears to be set up correctly as I can turn on and off some LEDs. Is there something I need to do to enable writing to the memory region containing the Control registers? Thanks for any help. Bob Stewart

2 6

Choosing a Kernel
by Neal H. Walfield 05 Nov '13

05 Nov '13

Hi, I'm looking to run Genode on an ARM Cortex A8. I'm primarily interested in the security properties of the resulting system. I'm explicitly not interested in running multiple OS personalities or doing virtualization. What I do want is as pure an object capability system as possible and as small an attack surface as possible. This seems to suggest Fiasco.OC or OKL4, but perhaps the bare hardware kernel is better. I think NOVA doesn't come into question, because it only runs on x86. I couldn't find much information about the bare hardware kernel. I'd appreciate any pointers. Thanks! :) Neal

5 16

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users