- l4-hackers - example.com Site

about Fiasco make system
by Zhang Yinfei 10 Jan '09

10 Jan '09

Hi all, I want to add some file to the fiasco source code tree (in my local build). Actually it is a simple assemble file which has some VBE related code to help me debug assembles. It works well in bootstrap module. If I just naively copy the file to "fiasco/src/kern/ia32/", it won't be compiled and other files cannot use it. Any hint about how should I modify the Makefiles to include this file? Thanks a lot. Best Regards, Yinfei Zhang

2 1

Problem on make l4
by Neohtm 09 Jan '09

09 Jan '09

Hi all, I'd followed the guide from the website and the drops tutorial to build the l4env. i go to the l4 dir make oldconfig make but it ends with an error in the uclibc++ Below are the build log, please help on this..thanks make[5]: Entering directory `/home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/OBJ-x86_586' ... Compiling ARCH-all/src/algorithm.o LD_PRELOAD=/home/user/Desktop/tudos/l4/build/tool/gendep/libgendep.so GENDEP_TARGET=ARCH-all/src/algorithm.o GENDEP_BINARY=cc1plus g++ -m32 -c -nostdinc -DGCC_HASCLASSVISIBILITY -DSYSTEM_x86_586 -DARCH_x86 -DCPUTYPE_586 -DL4API_ -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/user/Desktop/tudos/l4/pkg/uclibc++/lib/uclibc++/ARCH-all/include -I/home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/include -I/home/user/Desktop/tudos/l4/build/include/x86/uclibc -I/home/user/Desktop/tudos/l4/build/include/uclibc -I/home/user/Desktop/tudos/l4/build/include -I/home/user/Desktop/tudos/l4/build/include/x86 -I/home/user/Desktop/tudos/l4/build/include -I/home/user/Desktop/tudos/l4/../dice/include -I/home/user/Desktop/tudos/include/x86 -I/home/user/Desktop/tudos/include -I/usr/lib/gcc/i486-linux-gnu/4.1.2/include -I/usr/lib/gcc/i486-linux-gnu/4.1.2/include-fixed -fno-builtin -nostdinc++ -ansi -fpermissive -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -fno-common -fno-stack-protector /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc -o ARCH-all/src/algorithm.o /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1: error: stray '\1' in program /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:10: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:12: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:14: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:16: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:18: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:20: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:22: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:24: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:26: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:28: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:30: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:32: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:34: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:36: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:38: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:40: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:42: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:44: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:46: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:48: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:50: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:52: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:54: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:56: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:58: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:60: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:62: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:64: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:66: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:68: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:70: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:72: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:74: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:76: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:78: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:80: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:82: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:84: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:86: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:88: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:90: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:92: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:94: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:96: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:98: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:100: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:102: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:104: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:106: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:108: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:110: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:112: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:114: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:116: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:118: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:120: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:122: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:124: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:126: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:128: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:130: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:132: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:134: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:136: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:138: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:140: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:142: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:144: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:146: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:148: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:150: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:152: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:154: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:156: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:158: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:160: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:162: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:164: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:166: warning: null character(s) ignored /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1:167: warning: no newline at end of file /home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/ARCH-all/src/algorithm.cc:1: error: expected constructor, destructor, or type conversion before '/' token make[5]: *** [ARCH-all/src/algorithm.o] Error 1 make[5]: Leaving directory `/home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/OBJ-x86_586' make[4]: *** [/home/user/Desktop/tudos/l4/build/pkg/uclibc++/lib/uclibc++/OBJ-x86_586] Error 2 make[4]: Leaving directory `/home/user/Desktop/tudos/l4/pkg/uclibc++/lib/uclibc++' make[3]: *** [uclibc++] Error 2 make[3]: Leaving directory `/home/user/Desktop/tudos/l4/pkg/uclibc++/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/home/user/Desktop/tudos/l4/pkg/uclibc++' make[1]: *** [uclibc++.lib] Error 2 make[1]: Leaving directory `/home/user/Desktop/tudos/l4/pkg' make: *** [pkg] Error 2 -- Best Regards, Neoh Tze Ming Malaysia

2 2

DDEkit for Linux2.6 from svn
by Shakthi Kannan 03 Jan '09

03 Jan '09

Hi, I would like to know from where I can get the DDEKit (Device Driver Environment) for Linux2.6 from svn? http://wiki.tudos.org/DDE/DDEKit >From the svn documentation: http://www.inf.tu-dresden.de/index.php?node_id=1735&ln=en ./repomgr modules lists the following: dice, fiasco, hello, l4env, l4linux-2.6-env. Thanks! SK -- Shakthi Kannan http://www.shakthimaan.com

4 33

Error of building L4 Libraries
by Qmo (Yi-Sheng) 31 Dec '08

31 Dec '08

Dear all: I am trying to build fiasco. My compile environment is Ubuntu 7.1 + gcc 3.4.6 I follow the steps in http://os.inf.tu-dresden.de/fiasco/use.html#install When building L4 system libraries and support servers, there are some error message: install -m 755 bootstrap /home/kashin08/tudos/l4/builddir/bin/x86_586/bootstrap ... Generating bootstrap.stripped objcopy -S bootstrap bootstrap.stripped BFD: bootstrap.stripped: section `.gnu.linkonce.r._ZTVN19_GLOBAL__N__Z4uartv18BootstrapIOBackendE' can't be allocated in segment 0 objcopy: bootstrap.stripped: Bad value BFD: bootstrap.stripped: section `.gnu.linkonce.r._ZTVN19_GLOBAL__N__Z4uartv18BootstrapIOBackendE' can't be allocated in segment 0 objcopy: bootstrap.stripped: Bad value make[5]: *** [bootstrap.stripped] Error 1 make[5]: Leaving directory `/home/kashin08/tudos/l4/builddir/pkg/bootstrap/server/src/OBJ-x86_586' make[4]: *** [/home/kashin08/tudos/l4/builddir/pkg/bootstrap/server/src/OBJ-x86_586] Error 2 make[4]: Leaving directory `/home/kashin08/tudos/l4/pkg/bootstrap/server/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/kashin08/tudos/l4/pkg/bootstrap/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/home/kashin08/tudos/l4/pkg/bootstrap' make[1]: *** [bootstrap.bin] Error 2 make[1]: Leaving directory `/home/kashin08/tudos/l4/pkg' make: *** [pkg] Error 2 Anyone can help me? Thank you very much. Best Regards, Qmo **

2 1

building bootstrap
by Tsai, Tung-Chieh 23 Dec '08

23 Dec '08

Dear All, I'm try to port Fiasco to an ARM platform, and I'm confused by the memory address settup in bootstrap package. What is the relationship between DEFAULT_RELOC_$(ARCH), MOD_ADDR, and RAM_BASE ? In the setting of Integratorcp, they're : DEFAULT_RELOC_arm = 0x0140,0000 RAM_BASE = 0x0 MOD_ADDR = 0x0150,0000 (I wonder if this work on real integratorcp board ? Although QEMU just put 2 memory with the same size on 0x0 and 0x8000,0000, is the real one will remap all it's memory to 0x0 ?) Because I see DEFAULT_RELOC_arm+RAM_BASE is used to be start address and in IMAGE_MODE, RAM_BASE+MOD_ADDR is used to be _mod_addr, So I guess RAM_BASE manes where the physical ram start, and DEFAULT_RELOC_arm, MOD_ADDR are realative to RAM_BASE, which are used to control start address of bootstrap image and specify where modules move to. With these assumption, it will work unitl find_kip(), `fail to find kernel info page.' And then I found the address in regions are strange, only address in bootstrap and multiboot info seems correct, others seems irrelevant to RAM_BASE, looks like started at 0x0. I guess there is some setting I miss. Could anyone give some advice about it ? Best Regards, Tsai, Tung-Chieh

2 3

pxa uart driver bug
by Tsai, Tung-Chieh 23 Dec '08

23 Dec '08

Dear all, The uart driver of pxa in l4/pkg/arm_drivers and l4/pkg/drivers seems forget to add volatile on Uart_pxa::wr and Uart_pxa::rd. This still work on qemu since qemu didn't emulate uart timing, but fail on standard 16550 uart on real board. And I'm confuse on l4/pkg/arm_drivers and l4/pkg/drivers. The uart directory in them are the same, and they all build libarm_uart.a. But while building, it'll first build drivers, then bootstrap, and then arm_drivers, and will override libarm_uart.a. It seems l4/pkg/drivers are redundant. Best Regards, Tsai, Tung-Chieh

2 1

building a toolchian with hard float support
by Gabi Voiculescu 11 Dec '08

11 Dec '08

Hello. I have to create a toolchain with hard fpu support for arm1176's VFPv2. That's because, by looking at the ARM documentation I don't see how I can perform mathematic operations on the FPU (like FABSx, FADDx without using these mnemonics), (as it is the case for fpu load/store operations), so as far as see, I have to build a toolchain that recognized these mnemonics. I dont' know where to start. Has anybody used a script like crosstools for this? I hope by creating a new dat file with proper GCC and GLIBC argumets I could do the job myself, but I have no idea what would those arguments be or where to find them: GCC += ?? --with-float=hard --fpu=vfpv2 --cpu=arm1176jzf ?? GLIBC += ?? Where can I find what gcc version might include support for my hard fpu? I tried the man pages in gcc-4.1.2 and gcc-3.4.4 without success and I can't figure out where to look for this on gnu.org. Can you point me in the right direction to use.

2 2

Problem with Building L4Linux-2.6
by Adam Chang 05 Dec '08

05 Dec '08

Dear all: I'm trying to build L4Linux ,so I followed the tutorial on this website http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml but I have encountered some difficulties. First I got Fiasco, L4Env, L4Linux from SVN, and the following is the steps that I tried to build L4Linux: 1. make -C l4 O=/my-user-build-dir oldconfig 2. make -C l4 O=/my-user-build-dir config unset Compilers and Tools ---> Build doc directories 3. cd l4 make O=/my-user-build-dir 4. Compile Fiasco 5. Go to the l4linux-2.6 directory make menuconfig set L4 tree build directory unset some features like SMP, HPET, highmem, MTRR, MCE, PARAVIRT, KEXEC, APM, HUGETLBFS 6. make Then the following is a error message ERROR: CONFIG_VM86 must not be enabled. But I check the file in l4linux-2.6 directory ./arch/l4/Kconfig, CONFIG_VM86 must be enabled, but the error message said that must be enabled, so I was confused. Then ,I got Fiasco, L4Env, L4Linux from snapshot , http://os.inf.tu-dresden.de/opentc/download.xml then I followed same steps to build, when I did "make O=/my-user-build-dir", there is a error message: /<my-user-build-dir>/pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:321: error: declaration of 'typedef class std::_associative_citer<ValueType, Compare, Allocator> std::_associative_iter<ValueType, Compare, Allocator>::_associative_citer' /<my-user-build-dir>/pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:248: error: changes meaning of '_associative_citer' from 'class std::_associative_citer<ValueType, Compare, Allocator>' I comment typedef _associative_citer<ValueType, Compare, Allocator> _associative_citer; at associative_base:321, and replace _associative_citer by _associative_citer<ValueType, Compare, Allocator>. I continued building, and there is some message: Package dependencies missing: l4con, skipping. Package dependencies missing: dope, skippingg. Compiling L4Linux , unset SMP, HPET, highmem, MTRR, MCE, PARAVIRT, KEXEC, APM, HUGETLBFS , L4_FBDRIVER, but there is still a error message: make[1]: *** No rule to make target `arch/l4/power/arch-i386/../../../i386/power/suspend.o', needed by `arch/l4/power/arch-i386/suspend.o'. Stop. make: *** [arch/l4/power/arch-i386] Error I don't know how to solve these problem, can someone give me some advice about building L4Linux. Thanks!! Best Regards. Adam Chang -- Adam Hung-Hsiang Chang windbread(a)gmail.com +886-987-335398 Wireless Networking and Embedded Systems Lab Graduate Institute of Networking and Multimedia National Taiwan University

2 1

Problem with the configuring user-level code of L4Ka::Pistachio
by Святослав Сидоров 30 Nov '08

30 Nov '08

Hello! I'm trying to configure the user-level code of L4 as written in instruction: http://l4ka.org/projects/pistachio/ia32/gettingstarted.php but there is no configure file in the user directory: debian:/home/svet/l4dev/l4ka-pistachio-081128-01/ia32-user-build# ../user/configure --prefix=../ia32-user-install --with-kerneldir=../x86-kernel-build bash: ../user/configure: No such file or directory debian:/home/svet/l4dev/l4ka-pistachio-081128-01/ia32-user-build# cd ../user; ls apps config.mk.in configure.in contrib include INSTALL install-sh lib Makefile.in Mk README.HG serv util In INSTALL file I read that the configure file should be in the main source directory of L4: <...> The simplest way to compile Pistachio using separate build directories is: 1. Create a directory BUILDDIR to host the build tree. 2. `cd' to the newly created BUILDDIR directory and run the `configure' script located in the main source directory. For example, if you create a directory `SRCDIR/build' and `cd' to this directory, you can run `../configure' to invoke the configure script. <...> but there is no such file too: debian:/home/svet/l4dev/l4ka-pistachio-081128-01/user# cd ..; ls AUTHORS contrib doc ia32-user-build kernel tools user x86-kernel-build What should I do to build the L4? Also this problem is described in message: http://www.mail-archive.com/l4-hackers@os.inf.tu-dresden.de/msg03449.html With the best regards, Svet.

2 1

Re: Problems with l4linux
by Valery V. Sedletski 28 Nov '08

28 Nov '08

On Thu, 20 Nov 2008 19:50:07 +0100, Adam Lackorzynski wrote: > >Those low-level things like GART are not unproblematic, best avoid them >if they seem to make problems (or proper analyse what's going on, much >harder...). > Yes, I'm trying to avoid them by now. On my desktop computer (AMD64) I disabled GART & Co. And on my notebook I disabled iTCO_vendor_support.ko and iTCO_wdt.ko (something watchdog-related) -- they were causing errors with call traces which hang the console. And the most interesting thing -- I found that when adding --isa=0x00800000 to the dm_phys commandline, the panic message disappears and Linux boots OK without errors at all! -- This does something with ISA DMA memory, as I read. It is strange that on AMD64 Linux boots OK without it, but it is needed on the notebook. So, maybe, this panic message is not a problem at all -- this is only configuration problem? Does this make the problem clear or is bootable ISO still needed (I'll trying to make it soon, yet encountered some problems with it -- and I can't reproduce the problem on desktop computer -- must figure out, on what type of hardware it appear. With qemu, all boots OK, so it seems not to be useful, as its emulated hardware does not cause problems, with no regard of --isa=... option) And still no additional messages either on linux console or on log server, only "Kernel Panic, not syncing, out of memory and no killable processes". And also "panic, waiting forever.." on log server. I can make screenshot though, but no useful info here. Maybe, I can recompile with additional debug messages enabled? I added "earlyprintk=1" and "console=ttyLv0" but still no additional messages. >> On my notebook I have ATI Radeon X300 Mobility PCI-express card, so, >> loading AGP drivers have no sense. As with desktop machine, I supposed >> that on notebook kernel panic occurs when loading some driver (maybe, >> video related -- I am not sure, if it makes a sense to load them in >> l4linux), but when I renamed all suspectable drivers, there were no >> errors with call traces, but the single kernel panic message remains, >> without other messages which could tell what causes it. > >Tried earlyprintk=1 on the Linux kernel command line? > Thanks, I added it. >> As I said, the notebook has no comports (I only have PCMCIA serial >> card and USB-to-serial converter); but desktop has them -- when I >> attached a nullmodem cable to the desktop (and connected from the >> notebook with terminal program using usbserial converter), I got debug >> messages from log server, but found nothing suspected (I could post >> logs there, but there are no call traces or other error messages in >> them -- maybe, there is a way to say linux to redirect error messages >> and call traces to log server?) > >There is. In the L4Linux configuration, in the Stub-drivers sub-menu, >enable 'Serial driver' and then use console=ttyLv0 on the kernel command >line. This should do the trick. > Now I got an empty linux console which begin output messages only starting with init process messages. Log server output ends with messages from interrupt service threads attaching to interrupts. But an error appears that linux cannot open /dev/console. I specified console=ttyLv0 but it still tries to open /dev/console. And, maybe, /dev/ttyLv0 must be created, but I don't know its major and minor numbers. >> Maybe, there is something to redirect >> log server messages through network or similar way, not via commport? >> Or, maybe, it's possible to redirect linux messages to log server and >> then from the same machine, to get/view these logs using l4env >> servers, not linux itself (linux is dead but l4env remains alive and >> maybe, I can get some post-mortem info, like logs or task memory dump >> or etc? Or get and save a trace buffer or similar?) (Just an idea -- >> what if include simple http server in l4env and serve log server >> messages, so, they can be viewed from any web browser? Maybe, >> something like this already exist?) > >There's the dmon application which is a DOpE application and a >log-server, i.e. it display log-messages in a window. >The other ideas are nice but do not exist. > Thanks. I also found a logcon application in l4con examples which is a l4con-aware log server. So, viewing log server messages is also possible in l4con environment -- I tried this, it works. Also, 1) with events server I was able to restart l4linux without rebooting -- just do Ctrl-Alt-Del in linux and then "l" option in run application to start it again. 2) by specifying "allow_cli" I was able to reboot computer in "run" application by pressing a tilde ("~") button. But 3) specifying "allow_cli" in run loader script was not sufficient to kill tasks with "run". When I try killing a hung L4Linux, a message appears in log that task F (run) is not allowed to kill tasks. Maybe, some additional option (to the "allow_cli" one) is needed? According the http server -- when I read the log server docs, I found that there is "--net" option that allow to access log server output via telnet! -- So, it appears that my idea is already implemented ;-) But this feature supports only four ethernet cards, unfortunately. I have rtl 8169 Gigabit ethernet and also have NE2000 compatible PCMCIA card on the laptop, but as I understood, PCMCIA is not supported (though, there is NE2000 support in log server) and 8169 is also don't supported. ;( > >I'd like to see the panic message, with the backtrace etc. to be better >able to judge what's going on. A classical screen-shot would also be ok. >Have you considered trying QEmu to play around? This makes all those >issues go away because you get the serial output into your terminal >etc... > As I said, no success with qemu as Linux boots OK with it. The backtrace is possible with calling strace when booting with init=/bin/sh and starting UDEV manually under strace. But here redirecting output to log server is needed, but "console=ttyLv0" still don't work. I can make screenshots then. WBR, valery PS: I forgot to mention -- returning to the problem with GPRS modem card -- this modem is not unique in that it don't work because of not getting high I/O memory area. -- I tried also two dialup PCMCIA modems (detected as ordinary PCMCIA modem/serial card) and one Cardbus serial card -- the same problem -- can't reserve high I/O memory region. So, this problem is not unique to my GPRS card, but it can be reproduced with any standard PCMCIA serial/modem card. (Just to know that this problem is common to all PCMCIA serial devices).

2 1

Re: Problems with l4linux
by Valery V. Sedletski 20 Nov '08

20 Nov '08

On Mon, 27 Oct 2008 01:06:43 +0100, Adam Lackorzynski wrote: > >On Thu Oct 23, 2008 at 21:54:08 +1300, Valery V. Sedletski wrote: >> On Wed, 22 Oct 2008 19:12:59 +0200, Adam Lackorzynski wrote: >> >> ...skipped... >> >> So, this is iret instruction somewhere on return from a syscall, if I understood correctly. >> Maybe, my Fiasco config is wrong? > >Rather not. Can you tell me at which position the f.2 is in user-land? >That would be interesting. > This is the result of executing "tf.2" in kernel debugger: thread: f.02 <001e0801> prio: a0 mcp: ff mode: Con state: 001 ready %dl 001e0804 into wait for: polling: rcv descr: lcked by: ---.-- timeout : cpu time: 2.000 ms timeslice: 4000/10000 ╣s pager : f.00 cap: ---.-- utcb: ffe34200 preemptr: 0.00 not monitored ready lnk: ???.?? 5.00 prsnt lnk: f.04 f.00 EAX=00000000 ESI=001e0801 DS=0023 EBX=a0051454 EDI=00000000 ES=0023 iret ECX=0000000d EBP=afeffe40 GS=0043 lea 0x0(%esi),%esi EDX=afeffe58 ESP=c03c17ec SS=0010 trap 13 (General Protection), error 00000070, from kernel mode CS=0008 EIP=f003622b EFlags=00203246 001e0815 cli c03c17ec f003622b 00000008 00203246 [eacff102] 00000073 00203296 afeffe00 0000007b 001e0818 into the [eacff102] dword was highlighted in backtrace. So, as I understood this, this marks current stack frame. Here we see that previous stack frame is ip=0xf003622b, cs=0x8, eflags=0x00203246 is respectively ip, cs and eflags taken off from the stack by previous iret instruction. Current iret must take off the next frame: eip=0xeacff102, cs=0x73, eflags=0x00203296. Here we can see that selector cs=0x73 is ring3 and eip is 0xeacff102. And also, unassembly at eip=0xeacff102: eacff100 int $0x31 eacff102 ret -- An entering the syscall? <001e0801> -- What is it? If it is an address from where int 0x32 is called then instructions at this point are: 001e07fe dec %dl 001e0800 into 001e0801 cli 001e0802 dec %dl 001e0804 into 001e0805 cli an address 001e0800 (into) is not in CS segment of vmlinux executable (no such address in objdump output) So, what is it? Corrupt stack? Or it is not a return address but something different? >X is very demanding wrt permissions. More recent version should behave >better though. > >> And the question: what does cli instruction do? I guess this must trigger an I/O page fault for I/O >> pages to be mapped? Am I right? > >CLI disables interrupts. Allowing this in user-land is a major security >breach. > I know. But in ioport.c you do CLI and then STI immediately. What it does? >> >I guess not. Which address? Anyway, I guess it should ioremap those... >> > .... > >Some of those addresses are quite low but unfortunately I don't have an >idea what they're used for. > The Cardbus controller uses these addresses, according to windows Device manager: 0xb8008000-0xb8008fff 0xfebff000-0xfebfffff 0xfabff000-0xfebfefff 0x000db000-0x000dbfff and modem itself uses none, only i/o and irq Also, I searched logs and found that piece: Oct 21 04:54:14 localhost kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Oct 21 04:54:14 localhost kernel: cs: memory probe 0xb8000000-0xb80fffff:__l4x_ioremap: Requested region at b8010000 [0x1000 Bytes] Oct 21 04:54:14 localhost kernel: cs: memory probe 0x70000000-0x700fffff: excluding 0x70000000-0x700fffff Oct 21 04:54:14 localhost kernel: cs: warning: no high memory space available! (This was in the log with info level (there are also error and warning levels)), so, as I understood, this is not fatal. Also here are ioremaps, so, they are present. WBR, valery

4 16

Interested with the TUDOS Demo CD's Virtual Linux
by Neohtm 18 Nov '08

18 Nov '08

Hie, I'm new to the L4 kernel. I'd tried on the TUDOS demo cd and i'm quite interest with the linux virtualization on small kernel system. Can someone show me how to achieve that? I'd downloaded the Fiasco kernel and L4linux via SVN but i don't have the idea on how to make it works. Thanks -- Best Regards, Neoh Tze Ming Research Officer Faculty of Engineering and Technology Multimedia University Melaka, Malaysia

3 2

Re: L4 for Openmoko FreeRunner
by Shakthi Kannan 13 Nov '08

13 Nov '08

Hi, --- On Thu, Nov 13, 2008 at 9:44 AM, Gernot Heiser <gernot(a)ok-labs.com> wrote: | I'm not aware of any L4 version officially supporting the FreeRunner | (GTA02). OKL4 has been ported to the GTA01 (see http://okl4.org) As | the two platforms seem to have the same CPU core and a similar SoC, | getting it going on the GTA02 would probably not be too hard. \-- Thanks! SK -- Shakthi Kannan http://www.shakthimaan.com

1 0

nethub and l4linux
by Mikhail Savchenko 10 Nov '08

10 Nov '08

Are there any working samples of nethub with l4linux as it's broken for running with flips? There are interesting the menu.lst configuration issues for nethub and tun/tap infrastructure for l4linux setting up. Thank you.

1 0

question: is there any implementation of fiasco on s2410(samsung arm920tdmi)?
by zhhwu 10 Nov '08

10 Nov '08

hi all: i want to migrate a implementation of fiasco to s2410, is there any already existed? i find that there are implementations on SA1110 and PXA. And i find that the ARM project of Pistachio has status: discontinued. (why ?) best regards! zhhwu

3 2

L4 for Openmoko FreeRunner
by Shakthi Kannan 08 Nov '08

08 Nov '08

Hi, Where can I find documentation on using L4 with the Openmoko FreeRunner? I've seen this post for the Neo1973: http://lists.okl4.org/pipermail/developer/2007-December/000504.html Appreciate any pointers in this regard, Thanks! SK -- Shakthi Kannan http://www.shakthimaan.com

1 0

broken bootstrap, roottask and l4linux with different tools
by Valery V. Sedletski 03 Nov '08

03 Nov '08

hi all, I'm now trying to compile l4env and L4Linux under older Linux distribution (I moved to virtual machine -- VIrtual PC with RedHat 9.0 installed in it). The tools are updated -- I checked that versions of all tools are not lower than those mentioned in dev-overview.txt file. Only gcc is version 3.4.6 (on previous machine I have gcc 4.2.2), but I read it is OK. The problem is that bootstrap, roottask and l4linux kernel are not working. Bootstrap file is about 3 Mb long and is not starting by GRUB, it says "Invalid or unsupported executable format". I opened it under hex editor and it has ELF signature and some data at the beginning (probably, ELF header etc). Then goes a long run of zeroes and code is at the end. I peeked into linker script and saw that bootstrap is linked at addess 0x2d0000, which is also about 3 Mb. Maybe someone already encountered this problem? How to avoid extra zeroes? As I understand it depends on linker script, but why with different tools all is OK? (I have binutils version 2.13 and gcc 3.4.6, with 4.2.2 all is OK). And also roottask is sem-working. The simpliest configuration with pingpong test is working but when I start configuration with dm_phys, for example, DOpE with Nitpicker test: ROOT: task 7.00 at 01505f7a is trying to get page 00000000 which is reserved r --double page fault--------------------------------------IP: 0012804b [root.pager] (4.00) jdb: -- the task 7 is dm_phys. The problem is with roottask, not dm_phys because when I repalce roottassk with version, compiled with gcc 4.2.2 under Mandriva 2008.0 (I don't remember binutils version), it works. As I remember, similar error occures when a program must be started with loader to be fixed up, but was started by roottask, not the loader. But dm_phys is not reuired to be started with the loader server. Also, when I compiled l4linux with these tools, I got a pagefault at zero address with eip == address of LOG_printf() function. -- Linux starts and first tries write something to log server and traps. As I understand, two last errors are because of accessing data by zero pointer. Other binaries seem to work. What can be wrong with tools and how to avoid such effect? (Maybe someone had similar problems?) WBR, valery

2 1

L4 supporting iNotify ??
by Gianfranco Ricci 29 Oct '08

29 Oct '08

Hi at all, I am working on a project that makes it necessary to observe file system events.Therefore I plan to use the inotify subsystem from the kernel. Does L4 support inotify ?? Thanks in advance! Regards, Gianfranco

2 3

Re: Problems with l4linux
by Valery V. Sedletski 27 Oct '08

27 Oct '08

On Wed, 22 Oct 2008 19:12:59 +0200, Adam Lackorzynski wrote: > ...skipped... > >Ok. There's an option in the Fiasco configuration to let you set IOPL3 >(and thus lets you do cli/sti). This is an extra option because if you >enable it Linux can stop the machine. Anyway, that sould fix the X >problem. Now I switched on Fiasco option about IOPL 3 and an error with cli disappeared, but another problem -- GPF somewhere in Fiasco. The serial log is like this: loader | vmlinuz26: Starting application using libld-l4.s.so loader | [36mvmlinuz26,#f: Loading binary[m rtc | Date:23.10.2008 Time:08:17:15 loader | vmlinuz26,#f: Loading ldso loader | vmlinuz26,#f: Starting libld-l4.s.so at 000138e0 via 0000cbe8 l4lx | [34;1m======> L4Linux 2.6 starting... <========[0m l4lx | Linux version 2.6.26-l4-svn120-dirty2 (root@localhost) (gcc version 4 l4lx : .2.2 20071128 (prerelease) (4.2.2-3mdv2008.0)) #7 Thu Oct 23 21:07:12 l4lx : PETST 2008 l4lx | Binary name: vmlinuz26 l4lx | Linux kernel command line (8 args): mem=100M video=l4fb:refreshsleep: l4lx : 200 l4fb.nograb=1 load_ramdisk=1 ramdisk_size=40960 root=/dev/ram l4e l4lx : nv_rd=(nd)/tftpboot/drops/ramdisk/drops-fp.rd panicblink=0 l4lx | Image: 00400000 - 007b9000 [3812 KiB]. l4lx | Areas: Text: 00400000 - 006c3000 [2828kB] (a bit longer) l4lx | Data: 006c3000 - 006e46d8 [133kB] l4lx | Initdata: 006e8000 - 00726000 [248kB] l4lx | BSS: 00728000 - 007b8bb0 [578kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer0) l4lx | Tamer0 is 0f.03 l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0d l4lx | Got 65536 out of 65536 I/O ports l4lx | Running at IOPL 3 l4lx | Connecting to l4io server. l4lx | l4lx_thread_create: Created thread 0f.04 (cpu0) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 006e6000 size = 266240 l4lx | sec-w-init: virt: 0x006e6000 to 0x00726fff [260 KiB] l4lx | sec-w-init: Number of physical regions: 1, 266240 Bytes l4lx | sec-w-init: 1: Phys: 0x012a0000 to 0x012e1000, Size: 266240 l4lx | l4env_linux_startup thread 4. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 100MB l4lx | Main memory: virt: 0x00800000 to 0x06bfffff [102400 KiB] l4lx | Main memory: Number of physical regions: 1, 104857600 Bytes l4lx | Main memory: 1: Phys: 0x06400000 to 0x0c800000, Size: 104857600 l4lx | Filling lower ptabs... l4lx | mainmem = 800000 l4lx | Done (1060 entries). l4lx | l4env_register_pointer_section: addr = 00728000 size = 593920 l4lx | end: virt: 0x00728000 to 0x007b8fff [580 KiB] l4lx | end: Number of physical regions: 1, 593920 Bytes l4lx | end: 1: Phys: 0x006f2000 to 0x00783000, Size: 593920 l4lx | l4env_rd_path: (nd)/tftpboot/drops/ramdisk/drops-fp.rd l4lx | Loading: (nd)/tftpboot/drops/ramdisk/drops-fp.rd l4lx | INITRD: Size of RAMdisk is 40960KiB l4lx | RAMdisk from 10000000 to 12800000 [40960KiB] l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) [1;25r[25;1H [32m ---------------------------------------------------------IP: f003622b[m [32m--[mGeneral Protection [25;1H[32m[l4lx.main] (f.02) jdb: [m[K -- TRAP 000d at 0xf003622b. Here is a disassembly of Fiasco kernel: f0036224 <in_syscall>: f0036224: 59 pop %ecx f0036225: 5a pop %edx f0036226: 5e pop %esi f0036227: 5f pop %edi f0036228: 5b pop %ebx f0036229: 5d pop %ebp f003622a: 58 pop %eax f003622b: cf iret f003622c: 8d 74 26 00 lea 0x0(%esi),%esi f0036230 <entry_sys_id_nearest>: f0036230: 50 push %eax f0036231: b8 c4 37 05 f0 mov $0xf00537c4,%eax f0036236: eb c8 jmp f0036200 <all_syscalls> f0036238 <entry_sys_fpage_unmap>: f0036238: 50 push %eax f0036239: b8 c8 37 05 f0 mov $0xf00537c8,%eax f003623e: eb c0 jmp f0036200 <all_syscalls> So, this is iret instruction somewhere on return from a syscall, if I understood correctly. Maybe, my Fiasco config is wrong? globalconfig.h: /* * Automatically generated C config: don't edit * Fiasco kernel version: SVN * Thu Oct 23 21:11:17 2008 */ #define AUTOCONF_INCLUDED #define CONFIG_WARN_LEVEL 2 #define CONFIG_IA32_TARGET "Intel Pentium" #define CONFIG_POWERSAVE_GETCHAR 1 #define CONFIG_HOST_CC "gcc" #define CONFIG_IO_PROT 1 #define CONFIG_REGPARM3 1 #define CONFIG_BIT32 1 #define CONFIG_LABEL "" #define CONFIG_IO_PROT_IOPL_3 1 #define CONFIG_PERF_CNT 1 #define CONFIG_HANDLE_SEGMENTS 1 #define CONFIG_XARCH "ia32" #define CONFIG_WARN_ANY 1 #define CONFIG_CC "gcc" #define CONFIG_PF_PC 1 #define CONFIG_EXPERIMENTAL 1 #define CONFIG_HOST_CXX "g++" #define CONFIG_SCHED_PIT 1 #define CONFIG_ABI_V2 1 #define CONFIG_NO_FRAME_PTR 1 #define CONFIG_INLINE 1 #define CONFIG_SERIAL 1 #define CONFIG_DECEIT_BIT_DISABLES_SWITCH 1 #define CONFIG_GSTABS 1 #define CONFIG_ABI "v2" #define CONFIG_JDB 1 #define CONFIG_IA32 1 #define CONFIG_IA32_586 1 #define CONFIG_CXX "g++" >(My X version also tries to get ports 0-1024 (or similar) >before doing the iopl thing but AFAIK this has only been added shortly.) > -- so, in normal situation, it should not be (requesting access to some ports before doing iopl(3)), but if it takes the place, then for it to work, the Fiasco option mentioned must be enabled. But in normal situation, this option is not needed? And the question: what does cli instruction do? I guess this must trigger an I/O page fault for I/O pages to be mapped? Am I right? >> >> PS: When I did "modprobe serial_cs" udev created ttyS0..ttyS3 devices but still no comm port access. So, access to video >> >> and comm-ports don't work but network and disks are working. Why could it be? >> > >> >Sorry, no idea with the card. It doesn't say anything strange in dmesg? >> > >> >> Only that serial_cs module prints the message that it could not access >> high memory. I hope this error disappear after linux will get I/O >> privileges > >I guess not. Which address? Anyway, I guess it should ioremap those... > According to scanpci, Cardbus controller and serial (modem) card use these addresses: pci bus 0x0006 cardnum 0x09 function 0x00: vendor 0x104c device 0x8031 Texas Instruments PCIxx21/x515 Cardbus Controller STATUS 0x0210 COMMAND 0x0007 CLASS 0x06 0x07 0x00 REVISION 0x00 BIST 0x00 HEADER 0x82 LATENCY 0xa8 CACHE 0x08 BASE0 0xb8008000 addr 0xb8008000 MEM BASE1 0x020000a0 addr 0x020000a0 MEM BASE2 0xb00a0706 addr 0xb00a0700 MEM BASE3 0x88000000 addr 0x88000000 MEM BASE4 0x8bfff000 addr 0x8bfff000 MEM BASE5 0x90000000 addr 0x90000000 MEM BASEROM 0x000044fc addr 0x00000000 not-decode-enabled MAX_LAT 0x05 MIN_GNT 0xc0 INT_PIN 0x01 INT_LINE 0x0a BYTE_0 0xc0 BYTE_1 0x17 BYTE_2 0x07 BYTE_3 0x30 according to /proc/iomem: 88000000-8bffffff : PCI CardBus #07 90000000-93ffffff : PCI CardBus #07 b8008000-b8008fff : yenta_socket b8010000-b8010fff : pcmcia_socket0 And also it uses these I/O ports (according /proc/ioport): 03f8-0407 : pcmcia_socket0 03f8-03ff : serial 0400-0407 : serial 4400-44ff : PCI CardBus #07 4800-48ff : PCI CardBus #07 here 0x3f8-0x3ff is /dev/ttyS0 and 0x400-0x407 is /dev/ttyS1 WBR, valery

2 1

Problems with l4linux
by Valery V. Sedletski 23 Oct '08

23 Oct '08

>On Tue Oct 14, 2008 at 22:04:49 +1300, Valery V. Sedletski wrote: >> I have Mandriva 2008.0 distribution. >> I compiled l4linux and got some problems with it. Maybe anyone knows >> what's wrong with the configuration? >> First, the problem is with X11 (X.Org), when I'm launching X11 by >> typing startx, there is an error >> >> tal server error: >> xf86EnableIOPorts: failed to set IOPL for I/O (Invalid argument) >> >> I compiled in the L4con/DOpE stubs but X11 don't work. On ordinary >> Linux Kernel it works well. I tried to use a fbdev driver in X.Org. > >fbdev is a driver that will work. The problem is that X wants to have IO >privileges which L4Linux does not have. This is actually feature rather >than a bug. Why should X need IO privileges for just running the fbdev >driver? Anyway, add 'allow_cli' in the loader config script to the >L4Linux load line, and 'task modname "loader" allow_cli' to the roottask >cmdline and it should give L4Linux/X the rights it likes to have. I have these. My bootloader config is like this: title L4Linux 2.6 [console] kernel $(L4)\bootstrap modaddr 0x02000000 module $(L4)\fiasco $(FIASCOARGS) module $(L4)\sigma0 module $(L4)\roottask -symbols -lines task modname "loader" allow_cli task modname "bmodfs" attached 7 modules module $(L4)\fiasco_symbols module $(L4)\fiasco_lines module $(PN)\names module $(PN)\log --prio 0xA1 --buffer 0 module $(PN)\dm_phys module $(PN)\simple_ts -t 380 module $(PN)\rtc module $(PN)\l4io module $(PN)\bmodfs module $(PN)\libloader.s.so module $(PN)\libld-l4.s.so module $(PN)\run module $(CFG)\run.cfg module $(LX)\vmlinuz26 module $(CFG)\l4linux26.cfg module $(LX)\initrd.img module $(PN)\l4con module $(PN)\loader --fprov=BMODFS run.cfg l4linux26.cfg vbeset $(VMODE) and I have the following loader config file: task "vmlinuz26" "mem=1800M no-scroll video=l4fb:refreshsleep:200 l4fb.nograb=1 load_ramdisk=1 ramdisk_size=4096 root=/dev/sda9 l4env_rd=(cd)/lx/initrd.img panicblink=0" allow_cli all_sects_writable priority 0xA0 My system is on /dev/sda9 (a partition on SATA harddisk). I boot it from a CD-ROM with L4 files, linux kernel and initrd on it. Here, removing "all_sects_writable" makes no difference. What interesting, with these settings the system is loading, the only warning a system gives is a warning that can't sync hardware clock with system timer, iopl(3) call failed; and also I cannot start X11. But access to eg. disks works. >> Also, each time I access /dev/null, the message is displayed that >> access is denied. > >How do you try to access it? /dev/null should look like this: >0 crw-rw-rw- 1 root root 1, 3 Jan 1 00:00 /dev/null yes, it appeared that the permissions for /dev/null were crw-r--r--, so users, other than root, have not write permission My fault... but I thought it something related with X11 not starting. >> Third, I got PCMCIA GPRS modem to power up and register in a GSM >> network (power Led is on and Network available Led is flashing). This >> modem appears to an OS like ordinary PCMCIA comm port, but minicom >> does not react to AT commands, though, PCMCIA stack detected the card, >> but did not enabled ttyS0 and ttyS1 ports on the card. It seems I >> loaded all PCMCIA stack modules and hotplug support. Except for >> serial_cs module which warns that "no high memory space available!". >> When I did configuring the linux Kernel, the build system did not give >> me a possibility to specify high memory up to 4 Gb. What should I do >> with it? > >Is the modem really using ttyS0? ttyS0 is used by Fiasco for the serial >console and thus not available to L4Linux (or any other app). You can >specify '-noserial' on the Fiasco command line to disable the usage of >ttyS0. Yes, the modem has two comm ports that could be accessed equally. In normal Linux they are ttyS0 and ttyS1. I removed "-serial" option from bootstrap command line and changed "-serial" to "-noserial" in the command line of fiasco. But still no result. I created /dev/ttyS0 by "mknod /dev/ttyS0 c 4 64" and likewise for ttyS1. When I tried to launch minicom, it says that no such device or address. After I did "modprobe serial_cs", minicom started but it still does not react to AT commands, so it seems that serial driver don't work. Maybe, serial_cs is wrong driver or this is the result of having not all I/O privileges? >> Fourth, I thied a wifi MiniPCI card Intel PRO/Wireless 2200 to get >> working in l4linux. I tried to load all wifi modules like in ordinary >> Linux kernel on the same machine, but when I trying to make the >> network interface up, it says that device does not exists. When I >> check dmesg output, there is a message that a firmware could not be >> loaded. I unchecked the checkbox "Prevent the firmware from being >> built" and "Do not enable drivers which require firmware loading" and >> it seems that firmware must be built. The firmware is in /lib/firmware >> and is called ipw2200-bss.fw. What should I do to get firmware loaded? > >The FW_LOADER config option is not enabled. I guess this needs to be so. I had CONFIG_FW_LOADER enabled but there was "CONFIG_FW_LOADER=m", not "CONFIG_FW_LOADER=y". I changed this option to the latter and recompiled the kernel, but firmware still not loading. So, it won't help. The error is like this: Oct 17 15:10:49 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Oct 17 15:10:49 localhost kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation Oct 17 15:10:49 localhost kernel: __l4x_ioremap: Requested region at b8006000 [0x1000 Bytes] Oct 17 15:10:49 localhost kernel: __l4x_ioremap: Mapping physaddr b8006000 [0x1000 Bytes, b8006000+001000] to 3f58a000+000000 Oct 17 15:10:49 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Oct 17 15:10:49 localhost kernel: firmware: requesting ipw2200-bss.fw Oct 17 15:11:49 localhost kernel: ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 Oct 17 15:11:49 localhost kernel: ipw2200: Unable to load firmware: -2 Oct 17 15:11:49 localhost kernel: ipw2200: failed to register network device Oct 17 15:11:49 localhost kernel: ipw2200: probe of 0000:06:05.0 failed with error -5 -- This is from dmesg output. Maybe, I missed something other? >> And the last, I tried to build l4linux under l4linux itself. The build >> is generally working, except for when doing "make modules_install" >> depmod crashes. Should I report these errors or they are known >> problems? > >Is it depmod or something different? depmod should work as Debian >systems running it on every boot-up. Please report, I'll try to fix as I >can. Yes, I compiled the kernel and did "make modules_install". It copied modules to /lib/modules and started to make files describing the modules. Then a set of messages with call trace appeared and a message that "depmod killed". What is interesting, depmod worked when the number of modules was relatively small. But when it was more than 700 modules, it crashed. What should I do to report the error? The messages are at linux console, not on commport, so is there a way to copy these messages? (The only way I see is to copy the parts of messages from screen using gpm mouse server). WBR, valery

2 8

Boot Fiasco@ARM on QEMU
by Tsai, Tung-Chieh 21 Oct '08

21 Oct '08

Dear All, I'm try to boot fiasco kernel which is compiled to integrator(arm926) on QMEU. I see this thread : http://osdir.com/ml/micro-kernel.l4.devel/2007/msg00303.html So I guess it should be worked. But I got some problem, when I use the following command : qemu-system-arm -kernel fiasco.image -serial stdio -d in_asm there is no output on QEMU. I watch the log of QEMU, find that it fails to go to '_start_kernel' in 0xf0003000 from 'bootstrap_main' because there is nothing in 0xf0003000. As I know, there is no physical memory in QEMU's integratorcp emulation. It only put memory on 0x0 and 0x80000000. So I guess the way I try is wrong, there must be something I lost. Do I have to use some kind of bootloader like grub in ia32 or putting some file by initrd, mtdblock, etc... And couold anyone give some advice about how to run it on QEMU. Best Regards, Tsai, Tung-chieh

3 11

menu.lst
by Mikhail Savchenko 20 Oct '08

20 Oct '08

Hi ,there Can somebody introduce the examples of menu.lst for starting fiasco with working demo configuration of flips and nethub? Thank you

2 1

fiasco boot sequence on arm
by Qmo (Yi-Sheng) 19 Oct '08

19 Oct '08

Dear all, I am working on a project which porting fiasco to a ARM&DSP platform. Now I have questions about the fiasco boot sequence in arm side. First, when doing a workable kernel image, we should use the l4 package *[1]"bootstrap" (l4/pkg/bootstrap)* to encapsulate the needed modules, for example: roottask, sigma0, and the real fiasco kernel(it means the building image in kernel/fiasco/builddir/fiasco.image). And we find the file "l4/pkg/bootstrap/server/src/startup.cc", there are some source code lines like: #elif defined(ARCH_arm) typedef void (*startup_func)(void); * startup_func f = (startup_func)boot_info.kernel_start;* f(); #else the command line says that "setup the L4 kernel info page before booting the L4 microkernel", but we want to know what is the entry point about *boot_info.kernel_start*in the real fiasco kernel(fiasco.image) source codes? And we also find that there is also a file named *[2]bootstrap in kernel/fiasco/src/kern/arm/bootstrap.cpp*, this file seems to steup the memory mapping. So we guess the first bootstrap*[1]* is used to arrange the roottask, sigma0, etc... in the memory space, then jump to the second bootstrap*[2]*in fiasco kernel to setup the needed memory mapping, and finally give the control to the real fiasco kernel. We want to confirm the steps, or something is wrong? And the last question, what is the coding style about *IMPLEMENTATION [arm]: * in kernel/fiasco/src/kern/arm/ directory, is there any effect when compiling them? Thank you very much! Best Regards, Qmo

2 1

Problems with l4linux
by Valery V. Sedletski 15 Oct '08

15 Oct '08

Hi all, I have Mandriva 2008.0 distribution. I compiled l4linux and got some problems with it. Maybe anyone knows what's wrong with the configuration? First, the problem is with X11 (X.Org), when I'm launching X11 by typing startx, there is an error tal server error: xf86EnableIOPorts: failed to set IOPL for I/O (Invalid argument) I compiled in the L4con/DOpE stubs but X11 don't work. On ordinary Linux Kernel it works well. I tried to use a fbdev driver in X.Org. Also, each time I access /dev/null, the message is displayed that access is denied. Third, I got PCMCIA GPRS modem to power up and register in a GSM network (power Led is on and Network available Led is flashing). This modem appears to an OS like ordinary PCMCIA comm port, but minicom does not react to AT commands, though, PCMCIA stack detected the card, but did not enabled ttyS0 and ttyS1 ports on the card. It seems I loaded all PCMCIA stack modules and hotplug support. Except for serial_cs module which warns that "no high memory space available!". When I did configuring the linux Kernel, the build system did not give me a possibility to specify high memory up to 4 Gb. What should I do with it? Fourth, I thied a wifi MiniPCI card Intel PRO/Wireless 2200 to get working in l4linux. I tried to load all wifi modules like in ordinary Linux kernel on the same machine, but when I trying to make the network interface up, it says that device does not exists. When I check dmesg output, there is a message that a firmware could not be loaded. I unchecked the checkbox "Prevent the firmware from being built" and "Do not enable drivers which require firmware loading" and it seems that firmware must be built. The firmware is in /lib/firmware and is called ipw2200-bss.fw. What should I do to get firmware loaded? The question is, does hotplug work in l4linux and does work PCMCIA and wifi support and should I try it and what options I could miss? Also I noticed that CD writing by cdrdao and cdrecord does not work, the console is either hangs until reboot, or the number of call trace messages are displayed. And the last, I tried to build l4linux under l4linux itself. The build is generally working, except for when doing "make modules_install" depmod crashes. Should I report these errors or they are known problems? This is my Linux kernel .config file: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.26-l4 # Tue Oct 14 19:26:11 2008 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/home/valerius/src/tudos/obj" CONFIG_L4_L4ENV=y CONFIG_L4_LDR=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_L4_VMLINUZ_SUFFIX="26" CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # CONFIG_L4_CONS is not set CONFIG_L4_TCG_STPM=y # # Debugging options # # CONFIG_L4_DEBUG is not set # # Advanced options # CONFIG_L4_L4ENV_MEMSIZE=32 CONFIG_L4_TAMED=y # # Priority configuration # CONFIG_L4_PRIO_SERVER_PROC=64 CONFIG_L4_PRIO_IDLER=65 CONFIG_L4_PRIO_IRQ_BASE=66 CONFIG_L4_PRIO_TAMER=85 CONFIG_L4_PRIO_L4FB_INPUT=70 CONFIG_L4_PRIO_L4FB_REFRESH=70 CONFIG_L4_PRIO_L4ORE=70 # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # CONFIG_L4_USE_L4VMM is not set CONFIG_L4_CONFIG_CHECKS=y # CONFIG_L4_SAMPLE_MODULE is not set # # # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" # CONFIG_GENERIC_LOCKBREAK is not set CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y # CONFIG_GENERIC_GPIO is not set CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=15 # CONFIG_CGROUPS is not set CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_RT_GROUP_SCHED is not set CONFIG_USER_SCHED=y # CONFIG_CGROUP_SCHED is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y CONFIG_RELAY=y # CONFIG_NAMESPACES is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_SYSCTL_SYSCALL_CHECK=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_COMPAT_BRK=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set # CONFIG_PROFILING is not set # CONFIG_MARKERS is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y # CONFIG_HAVE_DMA_ATTRS is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_LSF=y # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" CONFIG_CLASSIC_RCU=y # # Processor type and features # # CONFIG_TICK_ONESHOT is not set # CONFIG_NO_HZ is not set # CONFIG_HIGH_RES_TIMERS is not set CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_X86_RDC321X is not set # CONFIG_X86_VSMP is not set CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y CONFIG_PARAVIRT_GUEST=y # CONFIG_VMI is not set # CONFIG_KVM_CLOCK is not set # CONFIG_KVM_GUEST is not set # CONFIG_LGUEST_GUEST is not set # CONFIG_PARAVIRT is not set # CONFIG_PARAVIRT_CLOCK is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_GENERIC=y CONFIG_X86_CPU=y CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_TSC=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 # CONFIG_HPET_TIMER is not set CONFIG_DMI=y # CONFIG_IOMMU_HELPER is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set CONFIG_VM86=y CONFIG_TOSHIBA=m CONFIG_I8K=m # CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_2G_OPT is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0 # CONFIG_X86_PAE is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y # CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set # CONFIG_SCHED_HRTICK is not set # CONFIG_KEXEC is not set # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x100000 CONFIG_COMPAT_VDSO=y # # Power management options # # CONFIG_PM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_IDLE is not set # # Bus options (PCI etc.) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set CONFIG_PCI_GODIRECT=y # CONFIG_PCI_GOOLPC is not set # CONFIG_PCI_GOANY is not set CONFIG_PCI_DIRECT=y CONFIG_PCI_DOMAINS=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=m CONFIG_PCIEAER=y CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set # CONFIG_ARCH_SUPPORTS_MSI is not set CONFIG_PCI_LEGACY=y # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # CONFIG_OLPC is not set CONFIG_K8_NB=y CONFIG_PCCARD=m CONFIG_PCMCIA_DEBUG=y CONFIG_PCMCIA=m CONFIG_PCMCIA_LOAD_CIS=y CONFIG_PCMCIA_IOCTL=y CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_YENTA_O2=y CONFIG_YENTA_RICOH=y CONFIG_YENTA_TI=y CONFIG_YENTA_ENE_TUNE=y CONFIG_YENTA_TOSHIBA=y CONFIG_PD6729=m CONFIG_I82092=m CONFIG_I82365=m CONFIG_TCIC=m CONFIG_PCMCIA_PROBE=y CONFIG_PCCARD_NONSTATIC=m CONFIG_HOTPLUG_PCI=m CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_CPCI=y CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m CONFIG_HOTPLUG_PCI_SHPC=m # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set CONFIG_XFRM_MIGRATE=y # CONFIG_XFRM_STATISTICS is not set CONFIG_NET_KEY=m CONFIG_NET_KEY_MIGRATE=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set CONFIG_INET_TUNNEL=m # CONFIG_INET_XFRM_MODE_TRANSPORT is not set # CONFIG_INET_XFRM_MODE_TUNNEL is not set CONFIG_INET_XFRM_MODE_BEET=y CONFIG_INET_LRO=m CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m # CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=y CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y CONFIG_IPV6_OPTIMISTIC_DAD=y CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m CONFIG_IPV6_MIP6=m CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m # CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y CONFIG_IPV6_MROUTE=y CONFIG_IPV6_PIMSM_V2=y # CONFIG_NETWORK_SECMARK is not set # CONFIG_NETFILTER is not set CONFIG_IP_DCCP=m CONFIG_INET_DCCP_DIAG=m CONFIG_IP_DCCP_ACKVEC=y # # DCCP CCIDs Configuration (EXPERIMENTAL) # CONFIG_IP_DCCP_CCID2=m # CONFIG_IP_DCCP_CCID2_DEBUG is not set CONFIG_IP_DCCP_CCID3=m # CONFIG_IP_DCCP_CCID3_DEBUG is not set CONFIG_IP_DCCP_CCID3_RTO=100 CONFIG_IP_DCCP_TFRC_LIB=m # # DCCP Kernel Hacking # # CONFIG_IP_DCCP_DEBUG is not set CONFIG_IP_SCTP=m CONFIG_SCTP_DBG_MSG=y CONFIG_SCTP_DBG_OBJCNT=y # CONFIG_SCTP_HMAC_NONE is not set # CONFIG_SCTP_HMAC_SHA1 is not set CONFIG_SCTP_HMAC_MD5=y CONFIG_TIPC=m CONFIG_TIPC_ADVANCED=y CONFIG_TIPC_ZONES=3 CONFIG_TIPC_CLUSTERS=1 CONFIG_TIPC_NODES=255 CONFIG_TIPC_SLAVE_NODES=0 CONFIG_TIPC_PORTS=8191 CONFIG_TIPC_LOG=0 # CONFIG_TIPC_DEBUG is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m # CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m CONFIG_ATM_MPOA=m CONFIG_ATM_BR2684=m CONFIG_ATM_BR2684_IPFILTER=y CONFIG_BRIDGE=m CONFIG_VLAN_8021Q=m CONFIG_DECNET=m CONFIG_DECNET_ROUTER=y CONFIG_LLC=y CONFIG_LLC2=m CONFIG_IPX=m CONFIG_IPX_INTERN=y CONFIG_ATALK=m CONFIG_DEV_APPLETALK=m CONFIG_LTPC=m CONFIG_COPS=m CONFIG_COPS_DAYNA=y CONFIG_COPS_TANGENT=y CONFIG_IPDDP=m CONFIG_IPDDP_ENCAP=y CONFIG_IPDDP_DECAP=y CONFIG_X25=m CONFIG_LAPB=m CONFIG_ECONET=m CONFIG_ECONET_AUNUDP=y CONFIG_ECONET_NATIVE=y CONFIG_WAN_ROUTER=m CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_INGRESS=m # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m CONFIG_CLS_U32_PERF=y CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_CLS_IND=y CONFIG_NET_SCH_FIFO=y # # Network testing # CONFIG_NET_PK

2 1

Hardware detection in L4
by Gianfranco Ricci 15 Oct '08

15 Oct '08

Hi at all, I am working on a project that makes it necessary to have some agent application with hardware detection capabilities. Therefore my question is, if there is any L4 library or kernel interface that can be used to get information on detected and hot-plugged hardware in the system. Best would be a solution that provides callbacks to get informed on any change in the hardware automatically. Thanks in advance! Regards, Gianfranco

2 1