- l4-hackers - example.com Site

Re: DDE library
by Björn Döbel 21 Jul '08

21 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, > Hi, Bjoern please use the mailing list. It might give others the opportunity to answer _and_ it might help other people with similar problems to get their work done. :) > Thanks for your reply. I rebuilt dde package and got the library > 'libdde_linux26_sound.a' after downloading sound,c from Linux > 2.6.20.19, but now i have a another question, some sound driver source > files from linux 2.6.20.19/sound/pci/hda were copied to my sound > package directory and do i need to combine these files with main.c > including initialization rountine to generate a sound server? if yes, > how to do that? I've tried to compile these sound driver as a library, > but unfortunately it failed. Sure, you need to incorporate the drivers into your sound server. There is not much magic involved - just link the files as well as your main.c file together and link it with the ddekit, dde_linux26, and dde_linux26_sound libraries. Kind regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIhKLgP5ijxgQLUNkRAr6zAKCRuTS7iYDCfN/jnTVz/bKZsMe4kgCfbqSB W9SYbAmrJ1NZdbldJkeJ/As= =EjGa -----END PGP SIGNATURE-----

1 0

DDE library
by Saya Sheng (盛淑蕙) 09 Jul '08

09 Jul '08

Hi,all Recently, i wrote a simple sound server that only contains DDE initialization routines and tried to compile it with DDE libraries. After checking the Makefile in dde/linux26/lib/src, I guess i need the library 'libdde_linux26_sound.a' to link with, but it seems that i need to write the source code 'sound.c' to map linux functions to DDEKit. How can i implement this? any suggestion or hint? Thank you in advance Saya

2 1

Re: about Conventional Memory Region
by Zhang Yinfei 07 Jul '08

07 Jul '08

Hi Adam, Thanks for the reply. But I cannot find any symbol called find_kip in the fiasco source code. For bootstrap, do you mean those source files in kernel/fiasco/src/boot/ia32/ ？I just want to know where is the source code which start the KIP from scratch . Thanks. Best Regards, Zhang Yinfei On 7/7/08, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de> wrote: > > > Date: Sun, 6 Jul 2008 23:51:46 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: about Conventional Memory Region > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20080706215146.GJ7899(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Sun Jul 06, 2008 at 21:49:03 +0800, Zhang Yinfei wrote: > > As in *Mem_region Kip::last_free() const*, the function try to find the > > highest *Conventional* memory region's physical address. (I guess it gets > > physical memory bottom in the first time?). However in *void > > Kip_init::init(),* I only see one Conventional memory region which stores > > virtual address. Where does last_free() get the physical address?? > > > > And in bootstrap, I see it manipulate KIP. I thought at that time, KIP is > > not initialize, because bootstrap runs before Fiasco Startup, where > > Kip_init::init() is called. > > The KIP data structure is indeed in the kernel binary but it is filled > with memory descriptors by bootstrap. I.e. look for find_kip in > bootstrap which looks for the KIP in the kernel. Kip_init::init() does > setup a few things in the KIP but it does not start from scratch with > the memory descriptors. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 63, Issue 5 > ***************************************** >

2 1

about Conventional Memory Region
by Zhang Yinfei 06 Jul '08

06 Jul '08

Hi all, I've got a question about Fiasco source. As in *Mem_region Kip::last_free() const*, the function try to find the highest *Conventional* memory region's physical address. (I guess it gets physical memory bottom in the first time?). However in *void Kip_init::init(),* I only see one Conventional memory region which stores virtual address. Where does last_free() get the physical address?? And in bootstrap, I see it manipulate KIP. I thought at that time, KIP is not initialize, because bootstrap runs before Fiasco Startup, where Kip_init::init() is called. Thanks & Best Regards, Zhang Yinfei

2 1

multi-core support for fiasco? v.s. multi-processor?
by Zhang Yinfei 04 Jul '08

04 Jul '08

Hi all, I've listened to a lecture by Prof. Hermann Haertig about L4 in my university and I'm quite interested in doing some research on L4/Fiasco. I've reviewed some source code of Fiasco recently and one thing I can think of is to add multi-core support for L4/Fiasco. In my investigation, there are some people wrote papers about adding multi-processor (SMP) support for L4 but no one is talking about multi-core support. Is there a big difference between these two in the aspect of fiasco kernel? I'd be very appreciated if you guys can give me some opinions on this. Thanks. Thanks & Best Regards, Zhang Yinfei

3 2

Problem with compiling Fiasco L4 on Suse
by Stefan Kögel 01 Jul '08

01 Jul '08

>>> Can you build with "make V=1" and show the output where the error >>> happens including 20 or more lines above the error? Maybe I can see >>> something there. >>> >>> >>> >>> Adam >> make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' >> Making all in debug >> make[6]: Entering directory >> `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' >> /bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -module >> -version-number 0:3:0 -o libdice-debug.la -rpath /home/drops/lib/dice >> init.lo BETrace.lo L4BETrace.lo L4V4BETrace.lo >> g++ -shared -nostdlib >> /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o >> /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o .libs/init.o >> .libs/BETrace.o .libs/L4BETrace.o .libs/L4V4BETrace.o >> -L/usr/lib/gcc/i486-linux-gnu/4.2.3 >> -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib -L/lib/../lib >> -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../.. -lstdc++ >> -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o >> /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o -Wl,-soname >> -Wl,libdice-debug.so.0 -o .libs/libdice-debug.so.0.3.0 >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o: No such >> file or directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o: No such file or >> directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o: No such file or directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o: No such >> file or directory >> make[6]: *** [libdice-debug.la] Fehler 1 > > Please delete /home/stefan/Desktop/Fiasco/svn/tudos/dice and check it > out again from svn. That should fix it. > > > > Adam Thank you so much! Worked perfectly. Kind Regards, Stefan

1 0

Problem with compiling Fiasco L4 on Suse
by Stefan Kögel 01 Jul '08

01 Jul '08

> Can you build with "make V=1" and show the output where the error > happens including 20 or more lines above the error? Maybe I can see > something there. > > > > Adam make V=1 PWD=/home/stefan/Desktop/Fiasco/svn/tudos/l4 make -C /home/stefan/Desktop/Fiasco/svn/tudos/l4 O=/home/stefan/Desktop/Fiasco/my-l4-build make[1]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/l4' if [ -r ../dice/Makefile.drops ]; then \ PWD=/home/stefan/Desktop/Fiasco/svn/tudos/l4/../dice make -C ../dice -f Makefile.drops; \ fi make[2]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make all -f GNUmakefile make[3]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make all-recursive make[4]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' Making all in libltdl make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make all-am make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make[6]: Für das Ziel »all-am« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' Making all in src make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' Making all in be make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' Making all in l4 make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' Making all in v2 make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' Making all in ia32 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/ia32' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/ia32' Making all in amd64 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/amd64' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/amd64' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' Making all in v4 make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' Making all in ia32 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4/ia32' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4/ia32' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' Making all in fiasco make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' Making all in amd64 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco/amd64' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco/amd64' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' make[8]: Für das Ziel »all-am« ist nichts zu tun. make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' Making all in sock make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/sock' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/sock' make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' make[7]: Für das Ziel »all-am« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' Making all in fe make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/fe' make[6]: Für das Ziel »all« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/fe' Making all in parser make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' Making all in idl make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/idl' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/idl' Making all in c-c++ make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/c-c++' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/c-c++' make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[7]: Für das Ziel »all-am« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' if [ -d .svn ]; then \ ver=`svnversion -nc . | /bin/sed -e 's/^[^:]*://;s/[A-Za-z]//'`; \ echo "#define SVNVERSION \"svn r$ver\"" > svnversion.h.new; \ elif [ -s SNAPSHOT ]; then \ ver=`/bin/sed -e '/^Revision: */!d;s///;q' SNAPSHOT`; \ echo "#define SVNVERSION \"svn r$ver\"" > svnversion.h.new; \ else \ touch svnversion.h.new; \ fi if [ -e svnversion.h ]; then \ if [ 0 = `diff svnversion.h svnversion.h.new | wc -l` ]; then \ rm svnversion.h.new; \ else \ mv svnversion.h.new svnversion.h; \ fi; \ else \ mv svnversion.h.new svnversion.h; \ fi make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' Making all in include make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' Making all in dice make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include/dice' make[6]: Für das Ziel »all« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include/dice' make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' make[6]: Für das Ziel »all-am« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' Making all in lib make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' Making all in debug make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' /bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -module -version-number 0:3:0 -o libdice-debug.la -rpath /home/drops/lib/dice init.lo BETrace.lo L4BETrace.lo L4V4BETrace.lo g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o .libs/init.o .libs/BETrace.o .libs/L4BETrace.o .libs/L4V4BETrace.o -L/usr/lib/gcc/i486-linux-gnu/4.2.3 -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o -Wl,-soname -Wl,libdice-debug.so.0 -o .libs/libdice-debug.so.0.3.0 g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o: No such file or directory make[6]: *** [libdice-debug.la] Fehler 1 make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' make[5]: *** [all-recursive] Fehler 1 make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' make[4]: *** [all-recursive] Fehler 1 make[4]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[1]: *** [../dice] Fehler 2 make[1]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/l4' make: *** [x] Fehler 2 I appreciate your help. Kind Regards, Stefan

2 1

Problem with compiling Fiasco L4 on Suse...
by Stefan Kögel 27 Jun '08

27 Jun '08

On Wed Jun 25, 2008 at 12:54:13 +0200, Stefan K?gel wrote: > > Here it is... > > All I can see is that "GCCLIB=/usr/lib/gcc/i586-suse-linux/4.3/libgcc.a" > > is set to the right path. > > But I still get the "g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o: > > No such file or directory" errors. Strange... > The output looks ok. The build system is using gcc (not g++) to get all the data. Are you sure that g++ is also working (i.e. is version 4.3)? Can you sucessfully compile a 'int main() { return 0; }' type of program with g++? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ G++ is totally fine. stefan@linux-2gsj:~> g++ -v Es werden eingebaute Spezifikationen verwendet. Ziel: i586-suse-linux Konfiguriert mit: ../configure --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --program-suffix=-4.3 --enable-version-specific-runtime-libs --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=i586-suse-linux Thread-Modell: posix gcc-Version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) Compiling also works without any Problems. Any ideas? I am lost. Is there a way to manually set the paths right? Kind Regards, Stefan

2 1

How to determine if the button is pressed or not in L4 Dope?
by Lynette Lin 26 Jun '08

26 Jun '08

Hi all, I am trying to write an application in L4 Dope. Right now, I face a problem. I need to determine if the button is pressed by user or not. In the dope-users-guide.txt, there is a function: dope_req() . I tried to use it to check the button event, but failed. Is anyone know the way to figure it out? Thanks a lot. Best Regards, Lynette

2 3

Re: Cannot read VHW structure!
by ahmad kamal 26 Jun '08

26 Jun '08

hi, thanks adam, i'm trying to load l4linux on fiasco-ux, hopefully, you guys don't mind if i ask very basics question. Regards Ahmad Kamal ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Thursday, June 26, 2008 2:52:07 PM Subject: Re: Cannot read VHW structure! Hi, On Wed Jun 25, 2008 at 22:09:05 -0700, ahmad kamal wrote: > Fiasco-UX on Linux 2.6.18-6-686 (i686) > Mapped 64 MB Memory + 0 KB Framebuffer + 0 KB Input Area on FD 3 > > l4dope | L4INPUT Fiasco-UX mode activated > l4dope | [B.2] input/lib/src/ux.c:95:init_stuff(): > l4dope | Cannot read VHW structure! > > > I went through related codes, it's look likes the KIP is not the correct KIP > > Do you guys have any idea? > > this is what i try to run. > > ./fiasco -l events -l names -l log -l dm_phys -l simple_ts -l l4io -l l4dope You need to add -G 800x600@16 (or similar) to the command line to get the graphical mode. Also make sure to have "Graphical Console" enabled in the Fiasco configuration. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 1