users

users@lists.genode.org

1 participants
2310 discussions

how to pass event to l4linux
by unknown＠example.com 08 May '13

08 May '13

Hi! i implement touch screen driver in os\src\input\ft5406,and can get the coordinate x, y,then i use: _ev_queue.add(Input::Event(Input::Event::MOTION, 0, _abs_x, _abs_y, 0, 0)); _ev_queue.add(Input::Event(Input::Event::PRESS, Input::BTN_TOUCH, _abs_x, _abs_y, 0, 0)); _ev_queue.add(Input::Event(Input::Event::RELEASE, Input::BTN_TOUCH, _abs_x, _abs_y, 0, 0)); to add the event to the event queue. now the question is how can i pass the events to linux. the bot modules are: set boot_modules { core init timer omap4_gpio_drv omap4_i2c_drv omap4_fb_drv input_ft5406_drv sd_card_drv usb_drv nic_bridge nitpicker nit_fb part_blk terminal terminal_log l4android root-ginger.gz } thank you very much!!!

2 2

Cap index quota
by Daniel Waddington 03 May '13

03 May '13

Hi, I have a Ram_connection which is running out of cap indexes - "cap index allocation failed". How do I increase the quota for these? I understand I can construct my own cap session, but its not clear how to get the Ram_connection to use it. Context is Genode on Fiasco.OC/amd64. Thanks Daniel

2 1

part_blk on fiasco.oc
by yuqing wang 02 May '13

02 May '13

Hi, I used the foc_x86_32 platform to try part_blk run script ,there was a error. [init -> atapi_drv] 5 and below: yes enabled: yes [init -> atapi_drv] PRD base at 002f9000 (physical) at 00002000 (virtual) [init -> atapi_drv] Device initialized! Enabling interrupts ... Error: Test execution timed out make: *** [run/part_blk] Error 254 I try to find where is wrong and I get it I add some print function in file : genodedir/os/src/drivers/atapi/ata_device.cc void Ata::Device::read_capacity() { _block_start = 0; _block_size = 512; enum { CMD_NATIVE_MAX_ADDRESS = 0xf8 }; if (_lba48) { PERR("_LBA48 TRUE"); //PERR("dev_num= %c\n",dev_num()); PERR("dev_num= %d\n",dev_num()); if (!reg_non_data_lba48(dev_num(), CMD_NATIVE_MAX_ADDRESS, 0, 1, 0UL, 0UL)) { PERR("reg in"); _block_end = _pio->inb(CB_SN); /* 0 - 7 */ _block_end |= _pio->inb(CB_CL) << 8; /* 8 - 15 */ _block_end |= _pio->inb(CB_CH) << 16; /* 16 - 23 */ _block_end |= _pio->inb(CB_DH) << 24; /* 24 - 31 */ } PERR("reg out"); } else { ... and log message like this [init -> atapi_drv] Bus master interface base addr: 0000c040 (I/O) secondary (no) (supported) [init -> atapi_drv] LBA48 [init -> atapi_drv] UDMA Modes supported: [init -> atapi_drv] 0 and below: yes enabled: no [init -> atapi_drv] 1 and below: yes enabled: no [init -> atapi_drv] 2 and below: yes enabled: no [init -> atapi_drv] 3 and below: yes enabled: no [init -> atapi_drv] 4 and below: yes enabled: no [init -> atapi_drv] 5 and below: yes enabled: yes [init -> atapi_drv] PRD base at 002f9000 (physical) at 00002000 (virtual) [init -> atapi_drv] Device initialized! Enabling interrupts ... [init -> atapi_drv] _LBA48 TRUE [init -> atapi_drv] dev_num= 0 Error: Test execution timed out make: *** [run/part_blk] Error 254 I think the dev_num =0 is the reason to cause my issue , but i can not solve it . Any help is appreciated. Regards Yuqing Wang

3 4

Splitting Dataspaces
by Daniel Waddington 30 Apr '13

30 Apr '13

Hi, If a process P has a dataspace (RAM) which it acquired from 'core', is there a way for it to split the dataspace so it can give some part to dataspace P2? Daniel

2 5

use ahci_drv on real hardware
by yuqing wang 30 Apr '13

30 Apr '13

Hi, I tried to add ahci_drv to l4linux to make my hard disk available. I modified the l4linux run script and tried ,found that there was something wrong during booting . The script and log file is attached . Is my script wrong,or I should change some config of l4linux? Regards Yuqing Wang

2 1

Support variable length blobs in RPC
by Daniel Waddington 27 Apr '13

27 Apr '13

Hi, What's the best way to create RPC types for variable length data (assuming a maximum size of that will fit in the UTCB). I looked at Rpc_in_buffer, but this seems to only support strings, and using as an out param seems awkward. For the moment I am using a statically sized structure, but I fear there is needless copying going on. BTW, this RPC is for one-off control - of course shared memory is better for streaming. Daniel

2 1

debug nic_drv
by Keqin Sun 26 Apr '13

26 Apr '13

Hi, I want to debug nic_drv on a real machine using gdb_monitor. But gdb showed this: (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... and my run srcript is: # # Build # build { core init drivers/timer drivers/pci app/gdb_monitor drivers/uart drivers/nic } create_boot_directory # # Generate config # install_config { <config verbose="yes"> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> <service name="SIGNAL"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides> <service name="Timer"/> </provides> </start> <start name="uart_drv"> <resource name="RAM" quantum="2M"/> <provides> <service name="Terminal"/> </provides> #is that service name "Terminal" should be "/dev/ttyS0" ? <config> <policy label="gdb_monitor" uart="1"/> </config> </start> <start name="pci_drv"> <resource name="RAM" quantum="2M"/> <provides><service name="PCI"/></provides> </start> <start name="gdb_monitor"> <resource name="RAM" quantum="5M"/> <provides><service name="Nic" /></provides> <config> <target name="nic_drv"/> <preserve name="RAM" quantum="2M"/> </config> </start> </config>} # # Boot image # build_boot_image { core init timer ld.lib.so libc.lib.so libc_log.lib.so libc_lock_pipe.lib.so libc_terminal.lib.so uart_drv pci_drv gdb_monitor nic_drv } set local_port 5555 #append qemu_args " -nographic " append qemu_args " -m 128 -nographic " # connect comport 0 to stdio append qemu_args " -net nic,model=e1000 -net user " append qemu_args " -serial mon:stdio " # connect comport 1 with TCP port $local_port append qemu_args " -serial chardev:uart " append qemu_args " -chardev socket,id=uart,port=$local_port,host=localhost,server,nowait " #run_genode_until forever run_genode_until {.*Remote debugging using /dev/ttyS0.*} 30 #run_genode_until {.*Remote debugging using /dev/terminal.*} 30 #exec [terminal] -e "[gdb] bin/nic_drv -ex \"target remote localhost:$local_port\" " & #exec [terminal] -e "[gdb] bin/nic_drv -ex \"target remote localhost:$local_port\" " & interact Is that correct? Maybe the serial was occupied by the system output? keqin

3 12

"Could not allocate metadata" error msg
by Jilong Kuang - SISA 23 Apr '13

23 Apr '13

Hi all, Can anyone give me a hint on how to get rid of the "Could not allocate metadata" error msg? Or, how can I effectively increase the quota for that? I already gave sufficiently large (way more than the process needs) RAM quota in the run script (config file). I also tried putting a line like this at the beginning of the main() function "Genode::env()->parent()->upgrade(Genode::env()->ram_session_cap(), "ram_quota=64M");" But it doesn't help much. Thank you for your help! Best regards, Jilong

2 3

Re: debug nic_drv
by Keqin Sun 22 Apr '13

22 Apr '13

Hi Norman, Thanks for your reply, and it is really helpful. I was totally lost in that issue and you pulled me out. I will give it a try following your guide. Regards Keqin On ÐÇÆÚÁù, ËÄÔÂ 20, 2013 6:39 pm, Norman Feske wrote: ----------------------------------------------------------------------------------- Hi Keqin, I suspect that you are mixing up the UART interfaces. The run script relies on two UARTs to be present. UART 0 is used for printing Genode's LOG messages and the kernel messages. The GDB monitor requires a separate channel of communication to the remote GDB. The run script uses UART 1 via the 'uart_drv' for that. UART 1 is then translated by qemu to a TCP connection. When executing the script on real hardware, you need two UARTs as well. I suspect that you have connected only a single one. Connecting GDB to the UART 0 of the Genode system makes no sense because this one is unrelated to the GDB monitor. > <start name="uart_drv"> > <resource name="RAM" quantum="2M"/> > <provides> <service name="Terminal"/> </provides> > #is that service name "Terminal" should be "/dev/ttyS0" ? The service name denotes the type of the session. The UART driver provides sessions of type "Terminal" and "Uart". (the "Uart" type is a specialized kind of "Terminal", not important here) In the Genode world "/dev/ttyS0" has no meaning. > <config> > <policy label="gdb_monitor" uart="1"/> > </config> > </start> This configuration tells the UART driver to hand out the second UART (UART 1) to the gdb_monitor client. The numbering starts at 0. UART 0 is typically used by the kernel and Genode's core. > Is that correct? Does the run script works as intended on Qemu? > Maybe the serial was occupied by the system output? I guess, you are putting your finger exactly on the issue. Do you have a way to connect a second UART to your PC? If you consider using a PCI card with additional comports, you will need to make sure that the UART driver uses the I/O ports of the card. (by modifying the function 'io_port_base' in 'os/src/drivers/uart/i8250/main.cc'. You may determine the right values by booting Linux once and executing 'lspci'. I admit, that sounds a bit awkward and complicated. Normally, you could use the TCP terminal ('gems/src/server/tcp_terminal') as an alternative to an UART interface when using GDB monitor. So there would be no need for multiple UART interfaces. (the TCP terminal provides the "Terminal" interface but works over TCP) Unfortunately, that's not possible when debugging the NIC driver because TCP terminal requires a NIC driver to work. 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 ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Genode-main mailing list Genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main -----------------------------------------------------------------------------------

1 0

how to solve issue#593
by yuqing wang 19 Apr '13

19 Apr '13

Hi, I want to run l4linux on real machine ,but there is someting wrong. [init -> nic_drv] number of devices: 1 [init -> nic_drv] --- init rx_callbacks [init -> nic_drv] --- get MAC address [init -> nic_drv] 00:0e:04:00:03:16 [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) [init -> nic_drv] mmemory allocation failed in alloc_memblock (size=2048, align=800, offset=0) PC hardware motherboard : DELL OptiPlex 330 CPU : Intel Pentium dual e2180 @ 2.00GHz Ethernet : intel 82541pi RAM : 2G the log is attached as log1 . I know it is discussed before as issue#593, https://github.com/genodelabs/genode/issues/593 , and I find chelmuth tried to solve this issue .Later,I find a branch about issue#593 https://github.com/chelmuth/genode/tree/issue593. I download the branch,find l4linux.run script have error running in qemu. [init -> nic_drv] snprintf not implemented [init -> nic_drv] void {anonymous}::Backing_store::_grow(): size=0 + chunk=8000 [init -> nic_drv] memory allocation failed in alloc_memblock (size=256, align=100, offset=0) [init -> nic_drv] dde_ipxe_nic_init(): opening device 00:03.0 failed [init -> nic_drv] number of devices: 0 [init -> nic_drv] --- init rx_callbacks I also tried issue593.run script ,have the same error. the log is attached as log2. Any help is appreciated. Regards. Yuqing Wang

3 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users