Re: L4-based microkernel on Intel SCC

2014-06-05 Thread Ramya Masti
Markus Partheymueller mpartheym at os.inf.tu-dresden.de writes:

 
 The changes to the kernel have not been merged into upstream because
 they were very specific to the SCC and of little more generic use. But
 I can send you the patch if you want.
 
 That would be great! Also, do let me know the version of the compiler, 
fiasco and l4re you used just to be sure. Alternatively, the source tree 
will also work.

 Yes, you should be able to run almost every ELF binary (conditions may
 apply...) produced by the L4Re build system (make elfimage
 E=yourmoduleentry), including L4Linux. But I have to say that we did
 not have the time for looking into larger deployments at the time. In
 order to load and start ELF binaries on the SCC, I wrote an extension
 to the sccKit that was available then. The way it worked was like this:
 
 1) Extract ELF according to the ELF headers and copy it to the SCC's
 memory
 
 2) Place protected mode boot code and the reset vector in memory
 
 3) Set up multiboot information structure (for memory maps)
 
 4) Set up an I/O connection for providing serial connection with the core
 

1,2,3 are possible but 4 depends on the OS I guess. Send me this as well in 
any case and I will get back to you if I have problems.

 Now, if I remember correctly, a lot of improvement has been made to
 the sccKit and the whole interaction with the chip after I finished
 this project (virtual framebuffers, serial output, etc.). So I tend to
 doubt that this part of my (fairly outdated) work will be of any
 practical use to you. But you could of course have a look at it.
 

No problem. I will get back to you if I have problems.

Thanks,
Ramya




___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: l4re compilation

2014-06-04 Thread Ramya Masti
Adam Lackorzynski adam at os.inf.tu-dresden.de writes:

 
 Yes, please stick with 4.8 for now.
 
 Adam

Thanks Adam! I will try that then. 


___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


l4re compilation

2014-06-03 Thread Ramya Masti
Hi all,

I am trying to compile l4re run time from the snapshot (l4re-snapshot-
2014053111) using GCC 4.9 on an x86-64 machine with multilib. The 
compilation fails with not being able to find cstdio header file. I followed 
the instructions in http://os.inf.tu-dresden.de/L4Re/build.html.

I note that the fiasco kernel itself builds fine from the same snapshot.


Some debug information:

Output of gcc -v 

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/gcc-multilib/src/gcc-4.9-20140507/configure --
prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man 
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --
enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --
enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-
libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-
libssp --enable-gnu-unique-object --enable-linker-build-id --enable-cloog-
backend=isl --disable-cloog-version-check --enable-lto --enable-plugin --
enable-install-libiberty --with-linker-hash-style=gnu --enable-multilib --
disable-werror --enable-checking=release
Thread model: posix
gcc version 4.9.0 20140507 (prerelease) (GCC)

--

Output of make O=build in the src/l4 directory (of what I think maybe 
relevant parts)

=== Building package libstdc++-headers ===
bash: line 0: cd: /home/ramya/Downloads/fiasco/l4re-snapshot-
2014053111/src/l4/pkg/libstdc++-headers/../libstdc++-v3/contrib/libstdc++-
v3-/include: No such file or directory
...
...
...
...
...
...

=== Building package cxx_libc_io ===
  ... Compiling io_backend.o
/home/ramya/Downloads/fiasco/l4re-snapshot-
2014053111/src/l4/pkg/cxx_libc_io/lib/src/io_backend.cc:9:18: fatal error: 
cstdio: No such file or directory
 #include cstdio
  ^
compilation terminated.

Is this a problem with the GCC version? Any help is much appreciated.

Best,
Ramya
 


___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers