Re: Porting i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821)

Hi, Am 29.10.2015 um 14:42 schrieb Mahdi Aichouch: Hello, Starting from a previous work [1] , I ported the i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821). There is no compilation error, but when I tested on the Freescale i.MX6 Sabre SDB, it seems that L4Linux does

Re: Sharing one ethernet network device between two L4Linux instances

Am 23.10.2015 um 10:48 schrieb Mahdi Aichouch: Regarding the use of the "cons multiplexer", if I understood correctly I should use it instead of "l4shmns" service, right? If yes, do I have to disable the support of "l4shmns" option in L4Linux and remove all configuration from my Lua

Re: Sharing one ethernet network device between two L4Linux instances

Am 22.10.2015 um 10:28 schrieb Matthias Lange: Hi, On 10/21/2015 02:34 PM, Mahdi Aichouch wrote: Hello, I was able to run two L4linux instances on top of L4 Fiasco OC using a Qemu emulator of a versatile express-a9 board . I would like to make these two instances share one ethernet network

Re: BSP support - UART

Am 14.10.2015 um 00:39 schrieb ba_f: Hello Hackers, I have a custom board with Zynq processor. Unfortunately, it uses UART0 which produces only garbage. (A lot of white spaces or tabs and single freak characters, if this is any help.) My ZedBoard uses UART1 and Fiasco runs successfully on

Re: make uimage error

Am 12.09.2015 um 00:34 schrieb Adam Lackorzynski: On Fri Sep 11, 2015 at 18:01:25 +, Shabnam Engineer wrote: I have another question that I want to see output in the monitor, does Fiasco support hdmi driver? No. if no, how can i see that it works well? By connecting to the UART.

Re: make uimage error

Am 12.09.2015 um 00:34 schrieb Adam Lackorzynski: On Fri Sep 11, 2015 at 18:01:25 +, Shabnam Engineer wrote: I have another question that I want to see output in the monitor, does Fiasco support hdmi driver? No. if no, how can i see that it works well? By connecting to the UART.

Re: Disable log color

Hi, $ fgrep -r \033[37m * src/l4/pkg/plr/server/src/log:#define WHITE \033[37m so changing WHITE to should do the job. Martin Am 10.03.2015 um 16:07 schrieb teclis High Elf: thanks Matthias, It still is inserting the control codes for white: \033[37m This is my cfg file:

Re: [Out-Of-Topic]How to Access Input GPIO of OMAP4460 without L4Re (direct access)

Am 27.01.2015 um 16:19 schrieb Erry Pradana Darajati: Hi L4 Hackers, My subject seems out of topic, but i don't know where i can ask this kind of thing, and i think there are many people have a knowledge about this subject. I have a problem. I want to directly access GPIO140 (in GPIO5 ball) as

Re: strange Bug

Am 26.11.2014 um 23:24 schrieb Björn Döbel: The fact that your PC has a value that is also valid in Moe does *not* imply that the code comes from Moe. Those are two completely distinct binaries executing in different address spaces. But is it possible in JDB to display memory of a certain

Re: strange Bug

Am 24.11.2014 um 23:37 schrieb ba_f: Hi Martin, thank you, but i'm afraid, i haven't learnt the full lesson, yet. Hi ba_f, blx r7 is a false alarm, it cannot cause this type of write page fault. Even the instruction itself makes no sense since r7 has a value of 1. Could you do the

Re: strange Bug

Am 22.11.2014 um 15:37 schrieb ba_f: Hello, well i guess we're stuck here. Because i can't find no 15c7a8 nor e12fff37 in myClient. I also checked the one shared lib myClient uses, without success. Maybe i do objdump the wrong files? arm-linux-gnueabihf-objdump -Dlx

Re: Run and debug Fiasco.OC kernel and L4Re using a DSTREAM JTAG device and the ARM DS-5 IDE

Am 18.11.2014 um 18:55 schrieb Mahdi Aichouch: Hello Adam, I used this command line to compile the fiasco kernel and l4re. $ make -j 4 BOOTSTRAP_NO_STRIP=y PLATFORM_TYPE=imx6 PLATFORM_UART_NR=1 I also added all these options to the src/l4/conf/Makeconf.boot But when I debug

Re: l4linux shutdown cleanup

Hi Ramya, Am 08.10.2014 um 16:18 schrieb Masti Ramya Jayaram: Dear all, I would like to perform some cleanup operations after l4linux shuts down..such as zero out all the memory it used and re-encrypt the original vmlinux image. I would like to know how I could do this from sigma0 preferably

Re: Using IO-Server

. Best regards, Martin. Am 10.09.2014 um 15:33 schrieb Martin Schröder: Hi Korbinian, Am 10.09.2014 um 14:24 schrieb Korbinian Ederer: Hello Community, I'm relative new to l4RE. My Goal is to get access to an Hardware Device which is Build in the Processor. After some research i came

Re: Using IO-Server

Hi Korbinian, Am 10.09.2014 um 14:24 schrieb Korbinian Ederer: Hello Community, I'm relative new to l4RE. My Goal is to get access to an Hardware Device which is Build in the Processor. After some research i came to the conclusion that the IO-Server is the thing I need, but i have no clue how

Re: Physical memory allocation to L4linux

Hi Ramya, Am 09.09.2014 um 11:39 schrieb Masti Ramya Jayaram: Hi all, I start l4linux by specifying 64M on memory in its configuration file. I would like this memory to be a fixed range of physical memory and I was wondering if there is a way to do it. MYRAM = new Device() { .hid=

Re: Minimal requirements to run L4linux using only a serial console

Hi Ramya, Am 29.08.2014 um 14:29 schrieb Masti Ramya Jayaram: Hi Martin, Thanks for checking that. I also see that my build works provided I don't apply a special patch meant for my board (Intel SCC). The patch essentially only alters the frequency and disables the PIC. If you disable the

Re: Minimal requirements to run L4linux using only a serial console

Sent: 29 August 2014 15:55 To: Martin Schröder; l4-hackers@os.inf.tu-dresden.de Subject: RE: Minimal requirements to run L4linux using only a serial console Hey Martin, Back on the list ;-) Ok, I can confirm that when I busy loop during fiasco init, I can actually see the character that I typed

Re: Minimal requirements to run L4linux using only a serial console

-table as input I noticed)? Or is there more to it? Thanks for your patience, ramya From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroe...@openlimit.com] Sent: 29 August 2014 16:29 To: l4-hackers

Re: Minimal requirements to run L4linux using only a serial console

of printing Hello world prints ello World :) What could the reason be? Thanks, Ramya From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroe...@openlimit.com] Sent: 29 August 2014 17:35 To: l4-hackers@os.inf.tu

Re: Minimal requirements to run L4linux using only a serial console

Hi Masti, I just applied your config, replaced drops-rd.rd by ramdisk-x86.rd and everything (command prompt, debugger) runs fine as expected in Qemu. Maybe you ran into a similar problem as described in this thread: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/thread.html#5165 Best

Re: Minimal requirements to run L4linux using only a serial console

From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroe...@openlimit.com] Sent: 27 August 2014 16:28 To: l4-hackers@os.inf.tu-dresden.de Subject: Re: Minimal requirements to run L4linux using only a serial console Hi Masti, I just applied your

Re: Device Tree Blob support in l4linux

Hi Adam, Am 21.08.2014 um 23:03 schrieb Adam Lackorzynski: I have some still hacky code on my disk which I think handles this. I have to check and clean this up to commit it. sounds promising! Even a dirty patch would help me a lot. Best regards, Martin

Re: How can a thread map memory to itself

Am 21.08.2014 um 23:50 schrieb Adam Lackorzynski: Just some side note: Ctrl-C also works for leaving insert mode... ... at the cost of Qemu terminating ;-) Martin ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de

Re: How can a thread map memory to itself

Am 22.08.2014 um 18:05 schrieb Matthias Lange: On Fri, Aug 22, 2014 at 01:37:24PM +0200, Martin Schröder wrote: Am 21.08.2014 um 23:50 schrieb Adam Lackorzynski: Just some side note: Ctrl-C also works for leaving insert mode... ... at the cost of Qemu terminating ;-) You can use -serial

Re: How can a thread map memory to itself

Hi, Am 20.08.2014 um 22:15 schrieb Björn Döbel: Fiasco has a kernel debugger which you can enter by pressing ESC at runtime. Pressing h will give you a list of commands. the invocation of jdb by pressing ESC is IMHO not the very best choice since it makes l4linux virtually impossible to use.

Re: Device Tree Blob support in l4linux

Hi Adam, Am 19.08.2014 um 00:13 schrieb Adam Lackorzynski: I am using the imx28-evk.dts where I replaced the model and compatible line by what I found in simple.dts. Ok, that's one thing to do. Does Linux say that it uses a DT? Like: [0.00] Machine model: L4Linux (DT) Yes it does:

Re: Device Tree Blob support in l4linux

Hi Adam, I tracked the problem down to l4linux/arch/l4/kernel/arch-arm/setup.c: In static customize_machine(void) either machine_desc-init_machine() is called and the static/generic platform devices are added (and the DT disregarded). If init_machine is not set the DT is parsed instead by

Re: Device Tree Blob support in l4linux

Am 13.08.2014 um 22:40 schrieb Adam Lackorzynski: So it worked before using DTBs? Some config/setting issue? Yes, both network of my imx28 worked withou DTB. I is some config issue: After searching a while, I am sure that the Device Tree is not used in my configuration at all. As I wrote

Re: Device Tree Blob support in l4linux

Hi Adam, Am 11.08.2014 um 23:41 schrieb Adam Lackorzynski: So l4x_load_dtb(main.c) is fine, but then something else in setup_arch goes wrong. The dtb s stolen from some other linux build, so maybe the dtb is wrong. Hmm, you need to tune the DT a bit I think. Did you take out the GIC, timer

Re: Device Tree Blob support in l4linux

Hi Adam, Am 05.08.2014 um 22:44 schrieb Adam Lackorzynski: Appending the DTB won't work with L4Linux. However, you can just use l4x_dtb=rom/your.dtb on the cmdline. it does not work for me. With a provided dtb it stops here: l4linux | l4x_register_pointer_section: addr = 0200 size =

Re: how to get or initialize clock in L4Linux

Hi Yunchuan, Am 08.08.2014 um 10:49 schrieb Yunchuan Geng: Hi, L4hackers, I am implementing I2C drivers from native linux to L4Linux. I am using Freescale iMX6Q SD board. Kernel version 3.14 in ./drivers/i2c/busses/i2c-imx.c, function i2c_imx_probe(), devm_clk_get() is called. And fails at

Device Tree Blob support in l4linux

a native linux build) and added it to moe but without any success. Unfortunately I did not find any references nor any examples how someone can provide a Device Tree Blob to l4linux. Has anybody ever managed to get l4linux running with DTB support? Best regards Martin Schröder

Re: User space filesystems for L4Linux

Hi, Am 11.07.2014 18:33, schrieb Uwe Geuder: After doing the comparison if found http://pokecraft.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO , which taught me that the compression level has major effect. I had run everything with -9 wrongly assuming that

Re: How to enable scheduling time in one-shot model

Hi Yuxin, Am 14.07.2014 17:09, Yuxin Ren schrieb: I know in previous Fiasco kernel, there is a kernel option to use scheduling timer in one-shot model. But I cannot find this option in the latest Fiasco kernel. So now how can I enable this feature? In addition, where is the code for timer

Re: Who uses memory originally from IO device

Am 07.07.2014 23:54, schrieb Adam Lackorzynski: After some debugging it am convinced that MOE is not using or blocking this OCRAM at address 0x0. But what is the reason that io cannot allocate the requested memory and maps instead something of the same size? There's some unfortunate behavior

Re: Delay::measure function

Hello Xavier, Am 04.07.2014 11:18, schrieb Xavier LEBARS: Hello, Thanks for the answer, we can display Hello World only once. (I resend my message because I forgot to add the L4 mailing list ...) the Hello World example calls sleep(1) which causes the kernel to suspend the task for one

Re: Who uses memory originally from IO device

Am 03.07.2014 18:21, schrieb Martin Schröder: My board is equipped with 128MB external DRAM: L4 Bootstrapper Build: #1234 Do 3. Jul 17:34:17 CEST 2014, 4.6.2 Scanning up to 128 MB RAM Memory size is 128MB (4000 - 47ff) RAM: 4000 - 47ff: 131072kB Total

Re: Fwd: Problems using qemu devices from l4re

Hi Maria, Am 02.07.2014 16:38, schrieb Maria Soler: - vbus = l:new_channel(); -- Start io l:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0), icu = L4.Env.icu, input

MOE uses memory originally from IO device

My board is equipped with 128MB external DRAM: L4 Bootstrapper Build: #1234 Do 3. Jul 17:34:17 CEST 2014, 4.6.2 Scanning up to 128 MB RAM Memory size is 128MB (4000 - 47ff) RAM: 4000 - 47ff: 131072kB Total RAM: 128MB In addition the CPU has 128kb

Re: Delay::measure function

Hi Xavier, Am 01.07.2014 17:04, schrieb Xavier LEBARS: Hi everyone, I’m currently trying to port Fiasco + L4re with the « Hello World » application on a Zedboard which has a Xilinx Zynq z7020 processor (ARM Cortex A9 MPCore). We already configure UART and Timer for the microkernel but boot

Re: IO configuration language

Am 24.06.2014 23:27, schrieb Adam Lackorzynski: So setting the name is possible. It should work like this: client0 = Io.Vi.System_bus(function () _self[x.y] = wrap(...); end), with table style it looks a bit cleaner: client0 = Io.Vi.System_bus{

Re: IO configuration language

Am 23.06.2014 12:49, schrieb Martin Schröder: Am 22.06.2014 23:25, schrieb Adam Lackorzynski: 1) How can I use the device in the example if the hid is not unique? I even tried wrap(hw:device(NIC0)) but this does not work eiher. wrap(hw.NIC0) should do it. I just made the hid string unique

Re: IO configuration language

Am 24.06.2014 14:32, schrieb Martin Schröder: I don't think this is easily possible with the new syntax. Do you need that type of name? Yes. Just double checked with the old style syntax: l4linux depends on that type of name in the platform_device_callbacks. Btw, the arm-rv.io

Re: IO configuration language

Am 22.06.2014 23:25, schrieb Adam Lackorzynski: 1) How can I use the device in the example if the hid is not unique? I even tried wrap(hw:device(NIC0)) but this does not work eiher. wrap(hw.NIC0) should do it. this fails here: io | rom/foo.io: error executing lua config: Wrong

Re: Doubts about File Systems on FIASCO on ARM (Cortex-A15)

Am 19.06.2014 18:06, schrieb Jorge Ventura: This is a good direction. I forgot that, in reality we need two drivers, one for a block device and another one for the filesystem itself. The two drivers are not sufficient if the underlying hardware is some sort of bare flash devices (NOR, NAND)

IO configuration language

IO supports two configuration formats. The (legacy format ?) IO configuration language and a (newer ?) lua based one. Except for some examples and the syntax file ioconfig.vim I could not find much documentation. But anyway I am running into trouble when using the lua based one instead of my

Re: page fault on virtual bus

Am 28.05.2014 00:46, schrieb Adam Lackorzynski: An example is for example in l4/conf/examples/x86-fb.cfg. btw, in the example l4/conf/examples/io_example.io (https://os.inf.tu-dresden.de/L4Re/doc/io.html) the two lines beginning with dev = wrap(hw:match( ... should be replaced by dev

Re: page fault on virtual bus

two lines should be adjusted slightly: local loader = L4.default_loader; local io_buses = { vbus1 = loader:new_channel(); }; - loader:start({ caps = { client1 = vbus1:svr(), + loader:start({ caps = { client1 = io_buses.vbus1:svr(), icu= L4.Env.icu,

Re: About DMA mem and IO Server

This warning does not hurt anyway, but does anybody know what this warning is about and how to avoide it? Martin Am 12.05.2014 11:51, schrieb Martin Schröder: I don't know the reason. But I also get the same WARNING (also twice) for each DMAMEM on my board - of course the beginning-end

Re: About DMA mem and IO Server

Am 12.05.2014 09:34, schrieb Taeung: Thanks Martin :-) Referencing website link which you give me , I'm trying to secure Ethernet on L4Linux. I've got eth0 and configure ip address, netmask , etc. But if I do 'ping 8.8.8.8' for test, error occur such as 'Error connecting: Network is

Re: [Resend] Why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ?

Hi Taeung, the FEC Ethernet Driver has no out-of-the-box support for L4 but it is possible to get it running with l4linux. For example in the Kconfig both config NET_VENTOR_FRESCALE and if NET_VENDOR_FREESCALE needs the depends on trailed with || L4 so it will show in linux menuconfig. But

Re: Network Server Ankh

Am 08.02.2014 18:01, schrieb Ajith Whowe: Dear Martin, These commands indicate that the link is always down with the NO-CARRIER“ flag. Please kindly refer to the outputs given below. This flag is set by the function „update_carrier“, which checks 3 conditions, namely the i) priv-remote_attached

Re: Network Server Ankh

Hi, Am 07.02.2014 15:22, schrieb Ajith Whowe: Dear Adam, Thank You very much for the response. Do You mean that the l4shmnet can be used as a communication channel between two (or more ?) instances of l4linux over TCP/IP? Yes, never tried with more, but two instances are working fine. By

Re: Network Server Ankh

Hi Ajith, Am 07.02.2014 17:58, schrieb Ajith Whowe: Dear Martin, Thanks a lot. It did the job. I have the network interfaces on both sides. Nevertheless I can not ping one another. The strange thing is the ping request clearly does invoke any of the net_device_ops: static const struct

Re: nothing after make for snapshot

Hi, Am 30.01.2014 19:12, schrieb Emanuel Berg: I have not been able to install from l4re-snapshot-2013123021.tar.bz2 The toolchain test says everything is fine (though I had to install dialog and doxygen from the repos as well). With 'make setup' I get the dialog, and I can pick between

l4linux signals SIGSEGV instead of SIGILL and others

Hi, I have a piece of code running fine on native Linux, but terminating unexpected with SIGSEGV while running on l4linux on the same piece of hardware. The relevant code is in _armv7_neon_probe vorr q15,q15,q15 (undefined instruction on ARMv5) which normally would throw SIGILL and thus

Re: Snapshot 2013123012 possible broken for ARM9 l4linux?

Hi, I just tested it on freescale i.MX28 EVK and it's working fine again. Thank you for fixing! Martin ___ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

Re: Snapshot 2013123012 possible broken for ARM9 l4linux?

Hi, earlyprintk=1 did not change much, but with showpfexc=2 a few more lines are shown l4linux | == L4Linux starting... l4linux | Linux version 3.12.0-l4 (mschroeder@vm-ms) (gcc version 4.6.2 (OSELAS.Toolchain-2011.11.3) ) #12 Wed Jan 15 16:21:26 CET 2014 l4linux | Binary name:

Snapshot 2013123012 possible broken for ARM9 l4linux?

When I compile the latest l4re-snapshot-2013123021 for ARM Platform (arm-rv-arm9 / Realview ARM9) and run it on qemu (or a real hardware), it stops here: l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t:1) offs=8000 vaddr=0200 vend=02362f1c l4linux |

Writing to TTBCR on ARM9 causes fault

I am trying to get L4 running on the freescale i.MX28 EVK. During startup it stops with a fault at fiasco/src/kern/arm/bootstrap.cpp:236 asm volatile(mcr p15, 0, %[ttbcr], c2, c0, 2 // TTBCR : : [ttbcr] r (Page::Ttbcr_bits)); Unlike ARM11, the ARM9 does not know about TTBCR.