- l4-hackers - example.com Site

25 Sep '14

Hello l4-hackers, I get an error when trying to compile, respectively linking my program. /opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-ld: cannot find -lld-l4 make[3]: *** [myProg] Fehler 1 My Program does not include this lib. It comes from the L4-make process (prog.mk). I have already compiled smaller programs, without problems. BTW before that missing lib error, i get a lot of "multiple definition of...". Any ideas? I use Debian 7 32bit. Thanks

3 4

Does unmap() flush tlb on other cores
by Yuxin Ren 23 Sep '14

23 Sep '14

Hi All, I have question about tlb flush. When a memory page is unmaped, do we always flush tlb of all other cores? Or do we have some way to track which core to flush? If so, how do we track that information? And it would be better if some one can show the code in the kernel to do that. Thanks a lot. Yuxin

2 2

Re: std::cin in Fiasco/L4Re (with 'make qemu')
by Stark, Josef 23 Sep '14

23 Sep '14

Hi, >I'm not sure where you enter this. >For me, the following works quite fine: > >#include <stdio.h> > >int main(void) >{ > printf("Press some key: "); > char c = getchar(); > printf("\nYour input: %c (%d)\n", c, c); > > printf("Enter a number: "); > int number; > scanf("%x", &number); > printf("Your number: %d\n", number); > > return 0; >} If I copy this code into the hello example, and change the Makefile accordingly: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = hello SRC_C = main.c REQUIRES_LIBS = libc_be_file_stdin include $(L4DIR)/mk/prog.mk I can successfully run it IF moe runs hello directly (without Ned and a config, as a "make qemu E=hello" does). If, however, hello is run through a config file and therefore Ned, as in hello-cfg, it doesn't work. Execution does not halt and outputs invalid values: MOE: Starting: rom/ned rom/hello.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/hello.cfg' hello | Press some key: hello | Your input: � (-1) hello | Enter a number: Your number: -2147450972 How to make it work? Pass a certain capability to hello? Josef

2 1

l4/sys/syscalls.h: No such file or directory
by Valentin Hauner 18 Sep '14

18 Sep '14

Hi, I'm using the following example provided by Michael Hohmuth in 2000 to create new tasks and threads: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2000/000384.html I've placed the code in a copy of the hello example, but added > REQUIRES_LIBS = l4sys to the Makefile. The directory structure is located at './l4/pkg/taskcreat'. Nevertheless, compilation is terminated due to a fatal error: > ./l4/pkg/taskcreat/server/src/main.c:5:29: fatal error: l4/sys/syscalls.h: No such file or directory Why is syscalls.h missing here? Best regards, Valentin

4 52

How to debug Fiasco Kernel
by cem akpolat 18 Sep '14

18 Sep '14

Dear all, I was searching how to debug the fiasco kernel through JDB. The following link gives a good approach how to it through minicom. http://os.inf.tu-dresden.de/l4env/doc/html/dev-overview/ However, even if I see the messages on the screen, is it possible to interact with JDB without having an exception? I looked at also the "Fiasco Kernel Debugger Manual", however, I couldn't figure out how to exactly interact with JDB. Until now I could only interact with JDB in case of any exception occurrence. Thanks in advance. Sincerely, Cem Akpolat

3 3

Trimming uclibc in l4
by Masti Ramya Jayaram 18 Sep '14

18 Sep '14

Dear all, I would like to extract the minimal subset of uclibc required by bootstrap, sigma and their dependencies only. My idea is to have these modules use the smaller libc while retain the usual uclibc build for the other packages. I intend to go about this by copying uclibc (say into uclibc_min) and then modifying the contrib_files_all.lst and contrib_files_x86.lst. Is this the correct way to do this? Also, I extracted all the package dependencies of bootstrap and sigma from the control files (below) bootstrap: drivers_uart drivers_of libc l4util cxx_io drivers-frst:libc l4util: crtn libc crtn: l4sys l4sys: ldscripts l4util: crtn libc cxx: l4sys l4util ulibc: l4sys sigma0: crtn l4sys l4util libsigma0 cxx_io libsigma0: l4sys Is this the correct way to do this as well? Thanks, Ramya

3 6

Physical memory allocation to L4linux
by Masti Ramya Jayaram 16 Sep '14

16 Sep '14

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. I understand from my earlier posts that the image of l4linux is in the same location everytime because the boot loader puts it there. I am not referring to this memory. I am concerned with the 64M that will potentially get allocated to l4linux. Thanks in advance, ramya

3 13

Question about dec_lock_cnt method in Context class
by Yuxin Ren 16 Sep '14

16 Sep '14

Hi All, I have a question about the dec_lock_cnt method in Context class under multiple processor. In its implementation, it checks if thread's home cpu is equal to current cpu. If not, it does not unset "_running_under_lock" variable, even if the _lock_cnt is 0. Why does it check if home cpu is equal to current cpu? Consider the following case: Thread A is running on core 1 holding a helping lock, but is preempted by another high priority thread. Thread B is running on core 2, and tries to take the same helping lock. It finds the lock is held by A, so it helps A to run by migrating A to core 2. When A releases its lock, finding the current cpu is not its home cpu, so it does not set "_running_under_lock" to false. Then A continues to run on core 1 and tries to take that lock again. But now it can never take the lock, as the implementation of helping lock. PRIVATE inline bool NO_INSTRUMENT Switch_lock::set_lock_owner(Context *o) { bool have_no_locks = o->_lock_cnt < 1; if (have_no_locks) { assert_kdb (current_cpu() == o->home_cpu()); for (;;) { if (EXPECT_FALSE(access_once(&o->_running_under_lock))) continue; if (EXPECT_TRUE(mp_cas(&o->_running_under_lock, Mword(false), Mword(true)))) break; } } ... } Do I misunderstand anything here? Thank you very much. Best, Yuxin

2 8

Re: Using IO-Server
by Martin Schröder 12 Sep '14

12 Sep '14

Hi Korbinian, Am 12.09.2014 um 13:44 schrieb Korbinian Ederer: > Hi, > Thanks for the resources. > The given Documents are describing the use of th *.io and *.cfg files, this is also documented in L4 Doc. > My question now is how to access the configured Device in Server Code. then continue with this example: /src/l4linux/arch/l4/kernel/arch-arm/mach_setup.c In copy_platform_device you can see how the IO resources (IRQ, MEM, IO) are enumerated. Also search for the functions l4io_lookup_resource and l4io_request_iomem to see how this is mapped in your address. The rest is up to your driver. 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 to the conclusion that the IO-Server is the thing I need, but i have no clue how to invoke it. >>> It would be great if someone could supply a short example >> >> Try this: >> https://os.inf.tu-dresden.de/L4Re/doc/io.html >> /src/l4/conf/examples/*.io, *.cfg >> https://fooprotected.wordpress.com/2012/04/12/l4linux-patch-for-mv643xx-eth… >> >> >> Best regards, >> Martin.

1 0

Does Fiasco have yield system call or something similar
by Yuxin Ren 10 Sep '14

10 Sep '14

Hi All, Does Fiasco support yield system call? Or other mechanism one thread can switch to another one without IPC? Thank you very much. Yuxin

2 1

Using IO-Server
by Korbinian Ederer 10 Sep '14

10 Sep '14

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 to invoke it. It would be great if someone could supply a short example Thanks Korbinian

2 1

Aborted L4linux due to CLI/STI
by Masti Ramya Jayaram 10 Sep '14

10 Sep '14

Dear all, I get an error during L4linux boot when I enter the debugger (using ESC) and resume: Aborted L4linux due to CLI/STI at 0x534911. When I disassemble this using gdb: (gdb) disassemble 0x534911 Dump of assembler code for function cmpxchg8b_emu: 0x00534910 <+0>: pushf 0x00534911 <+1>: cli 0x00534912 <+2>: cmp (%esi),%eax 0x00534914 <+4>: jne 0x534922 <cmpxchg8b_emu+18> 0x00534916 <+6>: cmp 0x4(%esi),%edx 0x00534919 <+9>: jne 0x534924 <half_same> 0x0053491b <+11>: mov %ebx,(%esi) 0x0053491d <+13>: mov %ecx,0x4(%esi) 0x00534920 <+16>: popf 0x00534921 <+17>: ret 0x00534922 <+18>: mov (%esi),%eax 0x00534924 <+0>: mov 0x4(%esi),%edx 0x00534927 <+3>: popf 0x00534928 <+4>: ret When I built l4linux, I had to disable CONFIG_X86_CMPXCHG, CONFIG_CMPXCHG_LOCAL and CONFIG_X86_CMPXCHG64 despite building for the Pentium because my processor does not support PAE (which is the option that enables this). I am guessing This is the reason it tries to emulate the CMPXCHG instructions. What is the correct l4linux configuration to use for a machine that does not support any of the atomic instructions like CMPXCHG8, ATOMIC, etc.? Thanks, ramya

2 5

GCC 4.9
by Stefan Wallentowitz 09 Sep '14

09 Sep '14

Dear L4 hackers, we recently started porting FIASCO to OpenRISC and our cross-compiler is GCC 4.9. I added the required libraries to our project mirror at github: https://github.com/TUM-LIS/optimsoc-fiasco/tree/for-upstream-gcc4.9 Are you interested in this? Do you want me to submit a patch for the latest public svn tree? Regards, Stefan

2 1

Preventing access to a part of the address space from Sigma0
by Masti Ramya Jayaram 09 Sep '14

09 Sep '14

Dear all, I would like to prevent access to a part of the address space from sigma0 for security reasons on my board. For example, I would like to prevent even sigma from accessing say 0xc0000000 - 0xffffffff of memory. What is the best way to accomplish this and test it? Thanks, ramya

2 1

Checking executables before running them in L4re/fiasco
by Masti Ramya Jayaram 09 Sep '14

09 Sep '14

Dear all, I am using fiasco/l4re to run applications (say hello world) and L4linux. The module list in the two cases looks like this: entry hello-cfg kernel fiasco -serial_esc -freq=533000 roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello entry l4linux kernel fiasco -serial_esc -freq=533000 roottask moe rom/l4linux.cfg module l4re module ned module l4linux.cfg module io module vmlinuz module ramdisk-x86.rd I would like to add some functionality that performs a few checks on hello and vmlinuz before they are executed. In this context, I have the following questions: a. Where is it best to implement such functionality - moe or ned? Or should I implement a separate server and do this? b. I need access to an special range of IO memory when I perform the checks. i guess I could always use the io module and do "l4io_request_iomem()" . Would that be the right way to do it from moe/ned? c. Is there a way to allocate/reserve a dedicated range of physical memory to these applications (hello/vmlinuz) so that they get allocated the same chunk everytime (of physical memory)? Thanks in advance, ramya

2 12

Adding a custom library to l4/pkg/bootstrap
by Masti Ramya Jayaram 05 Sep '14

05 Sep '14

Hi all, I have managed to compile a custom C library (libscc-sec) as part of the l4 packages. Now I would like to use it in the bootstrap package (make a call to a function in the library). I did the following: a. Added the library as a requirement in pkg/bootstrap/Control requires: drivers_uart drivers_of libc l4util cxx_io libscc-sec b. Modified the pkg/bootstrap/server/src/Make.rules so that it also looks for libscc-sec by: L4_LIBS = -static -nostdlib $(DRV_LIBS) -lcxx_base -lcxx_io -llibscc-sec But on compiling, I get an error that says that -llibscc-sec not found The package is getting compiled and I can see the library libscc-sec.a in the build folder. What am I missing? Thanks, ramya

3 6

Compiling the Fiasco.OC +L4Re for Raspberry PI
by Waldo Paz Rodriguez 03 Sep '14

03 Sep '14

hello hanzel, I have seen in l4hacker list that you have compiled fiasco.oc + l4re for Raspberry PI whithout problems. Iá¸¿ trying to compile it for rpi. I follow the next steps> 1- Compile Fiasco.OC for Broadcom2835 2- Compile L4Re for RaspberryPI model B with MODULE_SEARCH_PATH pointing to FOC builddir 3- Generate the hello example ELF image I have transformed it into a binary using: /usr/local/genode-gcc/bin/genode-arm-objcopy -Obinary bootstrap.elf l4.img I have used the three elf image and have used to the linaro and genode toolchain (both). When I have put the binary on the PI only can see the colored screen. I am using the Fiasco.OC +L4Re from 2014022815 snapshot. I am doing something wrong? Can you help me?

2 1

Passing data to a thread
by Valentin Hauner 03 Sep '14

03 Sep '14

Hi, I'm trying to pass some data to a newly created thread. Since l4_thread_ex_regs only accepts an instruction pointer, but no data pointer, it seems impossible to me to use a parameterized function such as: > thread1_func(void *data) { /* Read the data ... */ } So far, my efforts are: 1. I've tried filling the stack allocated to each newly created thread with > thread_stack = malloc(8 << 10); > thread_stack[0] = my_data; but then I'm not able to pop the data from the stack in thread1_func. 2. I've tried using IPC: The main thread which is creating the new threads sends the data to the destination thread. I'm using l4_ipc_send in the main thread and l4_ipc_receive in thread1_func just like in your utcb-ipc example. It works great, but unfortunately the call of l4_ipc_send leads to an _immediate_ execution of thread1_func (timeouts: L4_IPC_NEVER), so my scheduling policy is not respected. So how can I pass data to a thread in a way that is equivalent to passing arguments to functions? Best regards, Valentin

2 2

Fault in function writev (ulibc)
by Masti Ramya Jayaram 02 Sep '14

02 Sep '14

Dear all, I am running a custom application package on fiasco using a serial line (no keyboard/screen) and I intermittently get faults caused by printf. I notice that on disassembling the code around the error that the function is called writev in ulibc. Has anyone experienced something similar before? Thanks, ramya

2 2

New package linking fails
by Masti Ramya Jayaram 01 Sep '14

01 Sep '14

Dear all, I am trying to create a new package under l4/pkg. The linking of the package fails and it has to do with the linker path but I am not sure how to fix it. Here are the details. Package structure: (relevant parts) l4/pkg/test/server/src/main.cc l4/pkg/test/server/src/folder1/test1.c l4/pkg/test/include/test1.h l4/pkg/test/server/src/Makefile PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = $(PKGNAME) # list requirements of your program here REQUIRES_LIBS = libsigma0 libirq l4util l4re_c-util # list your .c or .cc files here SRC_C = folder1/test1.c SRC_CC = main.cc include $(L4DIR)/mk/prog.mk The compilation of the package fails with an undefined reference in main.cc to a function in test1.c (defined through test1.h). All the object files are generated and I checked under build. What do you think is the issue? Thanks, ramya

2 3

lwip and C++ compilation/linking issue
by Stark, Josef 01 Sep '14

01 Sep '14

Hello, I want to use TCP/IP (and therefore ankh and lwip) inside a C++ application. The unmodified lwip example (src/l4/pkg/ankh/examples/lwip) compiles fine (and also works without DHCP and with a little tweaking), but it is written and configured as C and not C++. So if I change the filename of main.c to main.cc and the Makefile accordingly, unfortunately it doesn't compile. Following error: ---------------- ... Compiling main.o In file included from /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/contrib/lwip/contrib/src/include/lwip/arch.h:46:0, from /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/contrib/lwip/contrib/src/include/lwip/debug.h:35, from /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/contrib/lwip/contrib/src/include/lwip/opt.h:46, from /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/contrib/lwip/contrib/src/include/lwip/tcpip.h:35, from /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/l4/ankh/lwip-ankh.h:3, from /home/josef/Desktop/test/main.cc:10: /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/contrib/lwip/arch/cc.h:48:13: error: previous declaration of ‘int* __h_errno_location()’ with ‘C++’ linkage extern int *__h_errno_location (void) __THROW __attribute__ ((__const__)); ^ In file included from /home/josef/Desktop/test/main.cc:19:0: /home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/include/uclibc/netdb.h:61:73: error: conflicts with new declaration with ‘C’ linkage extern int *__h_errno_location (void) __THROW __attribute__ ((__const__)); ^ make[1]: *** [main.o] Error 1 make: *** [/home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/ext-pkg/home/josef/Desktop/test/OBJ-x86_586-l4f] Error 2 ----------------- Alright, so I tried surrounding the offending include with 'extern "C" ' (as well as moving it above #include <l4/ankh/lwip-ankh.h> since this file also includes it): extern "C" { #include "arch/cc.h" } I think that it solved the problem, because the error went away, but another error appeared (see below), so I also tried doing the same only to the offending line inside arch/cc.h instead: extern "C" { extern int *__h_errno_location (void) __THROW __attribute__ ((__const__)); } Both approaches led to the same linker error: ------------------ main.o: In function `main': main.cc:(.text.startup+0x11c): undefined reference to `ankhif_init(netif*)' make[1]: *** [test] Error 1 make: *** [/home/josef/Desktop/l4re-snapshot-2014053111/obj/l4/x86/ext-pkg/home/josef/Desktop/test/OBJ-x86_586-l4f] Error 2 ------------------ This is the Makefile (only the line SRC_CC is different to the original example Makefile) ------------------ PKGDIR ?= . L4DIR ?= $(PKGDIR)/../l4re-snapshot-2014053111/src/l4 TARGET = test SRC_CC = main.cc SYSTEMS = x86-l4f arm-l4f REQUIRES_LIBS = lwip libc_be_socket_lwip liblwip_netif_ankh libc_support_misc include $(L4DIR)/mk/prog.mk ------------------ Which library is missing here, or what else could be going wrong? Cheers, Josef

1 1

Minimal requirements to run L4linux using only a serial console
by Masti Ramya Jayaram 30 Aug '14

30 Aug '14

Dear all, I am trying to run L4linux on fiasco/l4re but with the keyboard and VGA disabled. I can get all the way to the command prompt (of the shell) in the initramfs but then, on pressing a key, I get a page fault and I cannot debug the system anymore using the serial_esc. I suspect it is my configuration which I have provided below. I was wondering what the minimal packages are to achieve this. modules.list: entry l4linux kernel fiasco -serial_esc -freq=533000 roottask moe rom/l4linux.cfg module l4re module ned module l4linux.cfg module io module vmlinuz module drops-rd.rd I have disabled the framebuffer and input server in the L4linux stub drivers configuration and enabled the serial console. l4linux.cfg: --vim:set ft=lua: L4.default_loader:start({ caps = { log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/io -vvvv rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk$ I also specify a custom frequency for my board to fiasco.oc, do I have to make similar modifications to l4linux (e.g., Timer frequency)? Thanks, Ramya

3 14

RE: Minimal requirements to run L4linux using only a serial console
by Masti Ramya Jayaram 29 Aug '14

29 Aug '14

Hi Martin, That was a very useful tip. I simply changed the default value in kernel/fiasco/src/kern/config.cpp from SERIAL_ESC_IRQ to SERIAL_ESC_NOIRQ which leads to polling (I am guessing) and voila! It works! I even tried on the actual SCC and it works! I can break into the debugger as well as input to l4linux. Thanks a lot for your help for your help. Best, Ramya ________________________________________ From: Masti Ramya Jayaram Sent: 29 August 2014 17:48 To: Martin Schröder; l4-hackers(a)os.inf.tu-dresden.de Subject: RE: Minimal requirements to run L4linux using only a serial console Also with acpi on, it does enter the debugger in qemu. Best, Ramya ________________________________________ From: Masti Ramya Jayaram Sent: 29 August 2014 17:45 To: Martin Schröder; l4-hackers(a)os.inf.tu-dresden.de Subject: RE: Minimal requirements to run L4linux using only a serial console Hey Martin, No I just realized that ESC does not break into the debugger. But I can clearly see that the process instead of printing "Hello world" prints "ello World" :) What could the reason be? Thanks, Ramya ________________________________________ From: l4-hackers [l4-hackers-bounces(a)os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroeder(a)openlimit.com] Sent: 29 August 2014 17:35 To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Minimal requirements to run L4linux using only a serial console Hi Ramya, a: No, its not a must. The UART could also be polled (by a timer) to see if something arrived. b: At least regarding l4linux there is nothing more to it - afaik. But let's go back to the hello word example on the SCC. What happens if you press the <ESC> key? Does it break into the JDB debugger? Best regards, Martin Am 29.08.2014 um 16:56 schrieb Masti Ramya Jayaram: > Hey Martin, > > I am trying to run l4linux/fiasco on the Intel SCC which does have a pic-8259. The Intel SCC does not have a BIOS and does not have any ACPI tables which I think qemu generates on the fly. It also does not use a Screen or keyboard. > > I obtained a patch from Markus Partheymueller which they used to boot fiasco on the SCC. With it I am able to run hello world both in qemu with no-acpi as well as on the SCC successfully. > > The patch to the best of my knowledge does the following: > > a. Makes the cmdline also parse an argument so that the frequency is an input (533Mhz) > b. Uses the apic timer for scheduling. > c. Disables the pic-8259 because it does not exist. Instead the core in the SCC has two interrupt lines and this patch initializes these lines as interrupts to the core. > d. Disables keyboard and screen and enables a serial line for communication instead > e. Disables super pages because the SCC does not support it. > > So, when I try the patched fiasco/L4linux on qemu, it works when I do not disable acpi. But since the SCC does not have any ACPI/IO-APIC, when I try to run the same thing on qemu with ACPI off, l4linux boots but is not responsive to input. > > In short: > > when I run with I (below) , my l4linux responds to input and with II (below) not. > > qemu-system-i386 -m 256 -serial stdio -kernel bootstrap_l4linux.elf -append "-arg=fiasco,,-serial_esc -freq=533000" > > qemu-system-i386 -no-acpi -m 256 -serial stdio -kernel bootstrap_l4linux.elf -append "-arg=fiasco,,-serial_esc -freq=533000" > > Now the question is: > > a. Is the IO-APIC a must for the serial line? > b. Are ACPI tables just a matter of writing data at the right memory locations (e..g, qemu lets you give the acpi-table as input I noticed)? Or is there more to it? > > Thanks for your patience, > ramya > > > ________________________________________ > From: l4-hackers [l4-hackers-bounces(a)os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroeder(a)openlimit.com] > Sent: 29 August 2014 16:29 > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: Minimal requirements to run L4linux using only a serial console > > Hi Ramya, > > Why did you disable the PIC? > What is your aim with ACPI and why should this lead to a change in the UART driver? > And what has the serial console to do with ACPI tables? > > For me the topics have at the moment very little in common or I am missing something. > > Best regards, > Martin > > > Am 29.08.2014 um 15:58 schrieb Masti Ramya Jayaram: >> Also, given that the thing works with ACPI on, wouldn't it be better to include ACPI information in the boot instead of changing the driver? Or is this impossible? >> >> Best, >> Ramya >> >> >> ________________________________________ >> From: Masti Ramya Jayaram >> Sent: 29 August 2014 15:55 >> To: Martin Schröder; l4-hackers(a)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. So would I have to change the l4ser driver in Linux or the main driver in under pkg/l4/bootstrap or under fiasco in vkey.cpp? :) >> >> Thanks, >> ramya >> ________________________________________ >> From: Masti Ramya Jayaram >> Sent: 29 August 2014 12:15 >> To: Martin Schröder; l4-hackers(a)os.inf.tu-dresden.de >> Subject: RE: Minimal requirements to run L4linux using only a serial console >> >> Hey Martin, >> >> I cleaned up my build and it worked - the mistake was mine. I had a question regarding ACPI. The target machine I am using has no BIOS/ACPi support. So, when I boot linux on it my console input does not work.This is similar to booting in qemu with the -no-acpi option. Serial console output works (I can see the prompt of L4Linux) but input does not. >> >> Is there something special to do when booting with a serial console but no ACPI tables? >> >> Thanks, >> ramya >> ________________________________________ >> From: Martin Schröder [martin.schroeder(a)openlimit.com] >> Sent: 27 August 2014 18:32 >> To: Masti Ramya Jayaram; l4-hackers(a)os.inf.tu-dresden.de >> Subject: Re: Minimal requirements to run L4linux using only a serial console >> >> Hi Masti, >> >> you have all of them already! I did not alter any other file beside the files you already sent. I inserted them into a fresh >> snapshot (http://l4re.org/download/snapshots-oc/l4re-snapshot-2014053111.tar.xz) and started building. Since "drops-rd.rd" was not >> found in the snapshot, I just renamed "ramdisk-x86.rd" to "drops-rd.rd". Nothing more. >> >> Martin >> >> >> >> Am 27.08.2014 um 18:02 schrieb Masti Ramya Jayaram: >>> Hey Martin, >>> >>> thanks for the quick response. Could you send me your configs (l4linux, fiasco, l4re) so that I can try it with that? >>> >>> Thanks, >>> Ramya >>> ________________________________________ >>> From: l4-hackers [l4-hackers-bounces(a)os.inf.tu-dresden.de] on behalf of Martin Schröder [martin.schroeder(a)openlimit.com] >>> Sent: 27 August 2014 16:28 >>> To: l4-hackers(a)os.inf.tu-dresden.de >>> Subject: 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 regards, >>> Martin >>> >>> >>> Am 27.08.2014 um 15:18 schrieb Masti Ramya Jayaram: >>>> Sorry, a couple of typos in the l4linux.cfg >>>> --vim:set ft=lua: >>>> >>>> >>>> L4.default_loader:start({ caps = { >>>> log = L4.Env.log:m("rws"), >>>> }, >>>> l4re_dbg = L4.Dbg.Warn, >>>> log = { "l4linux", "yellow" }, >>>> }, "rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=4000 l4ser.vkey_enable=1"); >>>> >>>> Thanks in advance, >>>> ramya >>>> >>>> ________________________________________ >>>> From: l4-hackers [l4-hackers-bounces(a)os.inf.tu-dresden.de] on behalf of Masti Ramya Jayaram [rmasti(a)inf.ethz.ch] >>>> Sent: 27 August 2014 14:07 >>>> To: l4-hackers(a)os.inf.tu-dresden.de >>>> Subject: Minimal requirements to run L4linux using only a serial console >>>> >>>> Dear all, >>>> >>>> I am trying to run L4linux on fiasco/l4re but with the keyboard and VGA disabled. I can get all the way to the command prompt (of the shell) in the initramfs but then, on pressing a key, I get a page fault and I cannot debug the system anymore using the serial_esc. I suspect it is my configuration which I have provided below. I was wondering what the minimal packages are to achieve this. >>>> >>>> modules.list: >>>> entry l4linux >>>> kernel fiasco -serial_esc -freq=533000 >>>> roottask moe rom/l4linux.cfg >>>> module l4re >>>> module ned >>>> module l4linux.cfg >>>> module io >>>> module vmlinuz >>>> module drops-rd.rd >>>> >>>> I have disabled the framebuffer and input server in the L4linux stub drivers configuration and enabled the serial console. >>>> >>>> l4linux.cfg: >>>> >>>> --vim:set ft=lua: >>>> >>>> L4.default_loader:start({ caps = { >>>> log = L4.Env.log:m("rws"), >>>> }, >>>> l4re_dbg = L4.Dbg.Warn, >>>> log = { "l4linux", "yellow" }, >>>> }, "rom/io -vvvv rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk$ >>>> >>>> >>>> I also specify a custom frequency for my board to fiasco.oc, do I have to make similar modifications to l4linux (e.g., Timer frequency)? >>>> >>>> Thanks, >>>> Ramya _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0

Re: Minimal requirements to run L4linux using only a serial console
by Martin Schröder 29 Aug '14

29 Aug '14

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 PIC you won't get any character into your system since UART reception is normally interrupt based. If you want to change this you have to poll the UART FIFO in the driver every second or so if there is any character available. Best regards, Martin.

1 0

Re: advice on using ddelinux
by Björn Döbel 28 Aug '14

28 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28.08.2014 12:14, Korbinian Ederer wrote: > Yes the symlinks are build properly, but you're right with the > CFlags. The include dir is not listed. How do I tell the make > process to do so? My bad, the variable is called PRIVATE_INCDIR as you can see in all the example Makefiles around the l4/pkg/dde subdirectory. Cheers, Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany WWW: http://www.tudos.org/~doebel - -- "When the seagulls follow the trawler, it's because they think sardines will be thrown into the sea." (Eric Cantona) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlP/E0sACgkQP5ijxgQLUNmhTgCfbaw/Y+IIysCiwasxjvuVSxEP BdkAoJWEcSHWRfTedvXj0VotJv+1zVvn =o8Pq -----END PGP SIGNATURE-----

1 0