Hi all,
the verdict is out: We are going to meet on Thursday, April 9th. I
reserved a table under my name in B'liebig, Liebigstraße 24
(http://b-liebig.de/) for 7:30 pm.
See you then,
Bjoern
Am 25.03.2015 um 10:18 schrieb Björn Döbel:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
it is time for another Microkernel Meetup! As many regulars seem to be
travelling mid/late April, I suggest we go to
B'liebig, Liebigstraße 24 http://b-liebig.de/
either on April 7 or on April 9. Please participate in the Dudle so I
can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 24.03.2015 11:35, Gayathri Nagarajan wrote:
Is it possible to run the microkernel Fiasco.oc directly as an
instance in Oracle virtual box (just like other operating systems
like Ubuntu, windows etc that are executed) ?
Yes.
If so, how do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.03.2015 07:53, 水镜 wrote:
hi, where could i find the implemention of l4_ipc_send?
This function is implemented in the architecture-specific system
includes in l4/pkg/l4sys/include/ARCH-*/L4API-l4f/ipc.h.
For example for x86, this is in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To directly answer your question: most people here use either vim or
emacs.
In general, you can work on Fiasco code with any editor you want.
There are two things you need to be aware of:
1. As this is a non-standard project, you will have to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am interested in Checkpoint/Restore-functionality on L4Re. I
found the paper Stay Strong, Stay Safe – Enhancing Reliability of
a Secure Operating System
(http://os.inf.tu-dresden.de/papers_ps/vogtdoebel-IIDS2010.pdf),
where it is written
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Ned, file lua_exec.cc, line 408: '_l.launch(am, rom/l4re,
ldr);': What would happen, if the second argument (rom/l4re) was
replaced by a variable holding the actual binary name that should
be started (e.g. rom/hello), which thus would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
we want to use the ddekit in one of our courses next summer term.
So, to get comfortable with the setup and the toolchain I would
like to ask if a step by step guide to get the ddekit up and
running exists?
There is no general-purpose guide
) and embedded them in Fiasco.OC
without or little changes.
Regards, Daniel
Am 13.03.15 um 09:35 schrieb Björn Döbel: Hi,
we want to use the ddekit in one of our courses next summer
term. So, to get comfortable with the setup and the
toolchain I would like to ask if a step by step guide to get
Hi,
Do i have to generate kernel modules and copy to my ramdisk for
executing any linux application on l4linux? Or is there any other method ?
No, you only have to generate kernel modules if you want to load them
into the L4Linux kernel. If you simply want to run a Linux user
application on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.01.2015 14:55, Sushma Rao wrote:
Sir when I execute the command make O=path/to/builddir while
building l4re I got this error
How to resolve it
This error looks weird. What is the GCC version you are using (gcc
- -v)? What version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22.01.2015 06:52, Sushma Rao wrote:
my objective is client has to get input at client side and send it
to server and server should reply to the message got from the
client during runtime. How to do that?
Please see my previous mail and have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.01.2015 08:05, Sushma Rao wrote:
I successfully executed the client-server application in l4 re pkg
folder. Now,I would like to implement chat server application in
l4re, program does not take the values at run time. So I am unable
to make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Waldo,
please send your questions to the l4-hackers@os.inf.tu-dresden.de
mailing list.
On 19.01.2015 20:59, Waldo Paz Rodriguez wrote:
hello l4hacker, I am working with yse5250 card and I need in
implement a driver for a sensor of this card,
Hi Jason,
Hi maybe this is an overly pedantic point but is there a specific term
for device drivers in L4Re?
We just call them device drivers.
Bjoern
___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
Hi,
is it possible to run a bash-script within a l4re-App? Or do i need
l4Linux for this.
To run the Bash script natively on L4Re you will require a console as
well as a port of the Bash itself.
Let me explain my problem:
I have a l4re-App myServer.
I'm testing myServer with another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jason,
On 15.01.2015 00:28, teclis High Elf wrote:
If I create a new library is there a library include path in the
Fiasco/L4Re build system that I need to add my new library to
before I can link to it?
L4Re uses pkgconfig for that.
Suppose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.2015 12:38, ba_f wrote:
Hello L4-Hackers,
i noticed some wiered behavior when using l4io_request_iomem().
Have a look at this simplified code:
Server::dispatch(l4_umword_t, L4::Ipc::Iostream ios){
ios v1; ios v2;
In src/l4/conf have a look at Makeconf.boot.example. Copy this file to
src/l4/Makeconf.boot and edit it according to your setup.
In the line specifying MODULE_SEARCH_PATH replace the occurence of
/path/to/fiasco-build with the absolute path to your Fiasco build directory.
Hth,
Bjoern
Am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.12.2014 12:36, ba_f wrote:
Hi,
Objdump gives me the following, but i guess that comes from
MODE=shared:
NEEDED libc_be_sig.so NEEDED libpthread.so NEEDED
libld-l4.so NEEDED libdl.so NEEDED
libc_support_misc.so NEEDED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30.11.2014 19:59, ba_f wrote:
Hello,
Debugging quickfix: link your program statically to identify the
faulty location.
Unfortunately, no success neither.
I made libClients.a link with myClient. Still there is some dynamic
linking, i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
But is it possible in JDB to display memory of a certain thread in
it's address space to see the faulty instruction?
'd' - dump memory for task
Bjoern
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now i revisited my project a found something. When i add the faulty
code in myClient, i find the PC with objdump. But, when i put the
faulty code in libClient, i.e. a shared lib which myClient uses,
then i dont find the PC in myClient or libClient
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
And at 15c7a8 there is e12fff37 = blx r7 , which i've
already found in MOE. But that's not what i'm looking for, is
it?
This has nothing to do with MOE. When you objdump the myClient
binary, can you find the address in there? Does the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.11.2014 19:35, teclis High Elf wrote:
what does it mean in the JDB lp command if there is an *asterisk *
*after the name of the thread in the *wait *column ?
id cpu name pr sp waitto state 109 0 cons
a ba77*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.11.2014 23:00, ba_f wrote:
Ideally you now find the faulting address in myClient and figure
out where the access happens. Keep us posted if you need help
with that.
Bjoern
Oh boy...
Looking at the TCB, i see the start address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, let's see:
-
CPU 0 [f002e898]: IRQ ENTRY
CPU(s) 0-1 entered JDB jdb: l id cpuname pr sp
waitto state 6e 0 -2 58
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I only have a pc=115c7a8, but since i start from 0x0100, i
guess that right?
115c7a8: e28cca13add ip, ip, #77824 ;
0x13000
No way. This instruction adds a constant to a register and does
not touch memory at all.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.11.2014 00:11, ba_f wrote:
Hello Hackers,
this is a following to the thread below, but i didnt wanna occupy
it so i start a new one.
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/007049.html
Hi,
i run into an Error in my l4re-App.
Till now, i did printf()-Debugging, but it is at its limit in this case.
The Error message is the following:
L4Re[rm]: unhandled write page fault @7300 pc=15c7a8
This error message tells you that your program is trying to execute an
instruction
One more hint:
The Error message is the following:
L4Re[rm]: unhandled write page fault @7300 pc=15c7a8
This error message tells you that your program is trying to execute an
instruction at PC value 0x15c7a8. This instruction causes a write page
fault at address 0x7300 and L4re does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 05.11.2014 04:18, Kevin wrote:
Thanks for your answer,
please always reply to the mailing list. The answers may also be
interesting to other people.
Maybe my question is confused. I know the concept of class
Thread,It'sa runnable,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
How can you monitor how threads are scheduled for execution in
L4Re? The trace buffer does not seem to offer information about
the criticality of tasks.
if you are purely interested in scheduling events, you might want to
look at the kernel
Dear Reinier,
Am 05.11.2014 um 23:22 schrieb Reinier Millo Sánchez:
Hello Aaron
I'm working in a project to develop an embedded operating system for
real time purposes using Fiasco.OC as microkernel. I have reviewed you
article Capability Wrangling Made Easy: Debugging on a Microkernel with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.11.2014 12:44, Kevin wrote:
Hello, I know the class Task in fiasco is equaled with the word
Domain in VMM, but I can't find some schedule policy about Task
in fiasco, all I find is scheduling about Thread in class Context
and sched_context.
Am 10.10.2014 um 16:45 schrieb teclis High Elf:
From examples/libs/l4re/c++/shared_ds/ds_clnt.cc
line 49 : L4::CapL4::Irq irq = L4Re::Util::cap_alloc.allocL4::Irq();
It seems this template name L4::Cap and the function name
L4Re::Util::cap_alloc are a bit misleading or only designate a
Am 10.10.2014 um 18:00 schrieb teclis High Elf:
I have two threads running in the same server. On thread handles
incoming ipc messages from the clients in different address spaces and
the other thread does the work. The thread handling the incoming ipc
needs to pass an integer value to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.10.2014 00:21, teclis High Elf wrote:
What command in JDB gives me a list of thread IDs I can use with
the other thread commands. I tried the list tasks and didn't see
anything that looked like a thread id.
Assuming you are using a recent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 09.10.2014 18:57, teclis High Elf wrote:
How does L4Re handle contiguous memory blocks?
The dataspace managers (aka the user-level applications that provide
allocation and management of memory) provide the possibility to
allocate physically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.09.2014 09:19, Valentin Hauner wrote:
Hi,
On 09/17/2014 04:31 PM, Björn Döbel wrote:
In the end means, that your stack mapping did not succeed as
intended.
OK, that helped. Indeed, some of the arguments concerning the size
of the area
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/18/2014 09:29 AM, Björn Döbel wrote:
Did you see the printf() output before?
No, that's the only problem I'm struggling with at the moment.
There's no error message or the like, but the output does simply
not appear. What might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.09.2014 17:12, Valentin Hauner wrote:
Hi,
On 09/18/2014 04:51 PM, Björn Döbel wrote:
(another advantage you'd get by using L4Re's default application
loader btw).
OK, I'm aware of the fact that all the things I'm implementing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.09.2014 16:22, Valentin Hauner wrote:
Hi,
On 09/16/2014 03:54 PM, Björn Döbel wrote:
Just to be sure: How large is this per-thread stack? Are you
properly aligning it to page boundaries?
Adam suggested to give it a size of 2000
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.09.2014 09:26, Valentin Hauner wrote:
Hi,
On 09/17/2014 08:02 AM, Björn Döbel wrote:
How is thread_stack declared?
It's declared on line 21 in lib/src/edft.c:
l4_umword_t *thread_stack[THREAD_MAX_NUM];
Currently, THREAD_MAX_NUM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.09.2014 14:30, Valentin Hauner wrote:
Hi,
On 09/17/2014 10:23 AM, Björn Döbel wrote:
An fpage() wants an address and a size. Your malloc() call yields
an address (note: this is probably unaligned, maybe prefer to
use posix_memalign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.09.2014 15:29, Valentin Hauner wrote:
Hi,
was the alignment correct?
I don't know as you didn't tell us about the return value you got from
malloc/memalign.
On 09/17/2014 02:53 PM, Björn Döbel wrote:
* What is thread_stacks[thread.id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Values in decimal notation:
thread_stacks[count]: 12320
In hex that is 0x3020 - This address is certainly not aligned to a
page boundary. That would be something like 0x3000 or 0x4000.
I just saw in your previous email that you are calling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.09.2014 13:15, Valentin Hauner wrote:
Hi,
On 09/16/2014 12:04 AM, Adam Lackorzynski wrote:
Are there any entries?
Yes, there are produced more than thousand identical entries in
less than a second:
pf: 0026 pfa=4f3c ip=01000200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.09.2014 13:40, Valentin Hauner wrote:
Hi,
thanks again for your quick reply!
On 09/16/2014 01:21 PM, Björn Döbel wrote:
* What is this instruction? * What address is this? It does not
seem to be part of the binary as it is far off
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.09.2014 15:26, Valentin Hauner wrote:
Hi,
thanks, I've used addr2line and found out that it was the head of
thread_func (l. 27 in examples/libedft-example/main.c). So it seems
that the stack I'm using for passing arguments to the thread
Hi,
as Marcus already pointed out, newer versions of L4Re actually contain a
package called uclibc_minimal that serves exactly this purpose. Even if
you are using an older snapshot, chances are that backporting this
package (and adapting l4/mk) might be easier than stripping things down
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Besides, I'm getting a huge list of kernel warnings with the new
l4_fpage call that hasn't been there before. I've attached it to
this mail.
The kernel is complaining that you are trying to map memory from the
sender that is not available in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.09.2014 20:06, Yuxin Ren wrote:
Hi All,
Does Fiasco support yield system call? Or other mechanism one
thread can switch to another one without IPC?
$ cd src/l4/pkg
$ find . -name \*.h | xargs grep l4.\*yield
[..]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.09.2014 11:32, Valentin Hauner wrote:
Hi,
On 09/08/2014 12:17 AM, Adam Lackorzynski wrote:
Your threads page-fault all around. The reason is that I was
slightly wrong with my last statement on paging. The pager of the
parent task
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28.08.2014 06:33, Noah Zentzis wrote:
On 08/21/2014 02:14 PM, Adam Lackorzynski wrote:
Yes, you'd need to create a new region mapper for the new task,
one that knows about the virtual address space layout of that
one. Should be possible by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28.08.2014 12:14, Korbinian Ederer wrote:
Yes the symlinks are build properly, but you're right with the
CFlags. The include dir is not listed. How do I tell the make
process to do so?
My bad, the variable is called PRIVATE_INCDIR as you can
this:
l4/pkg/dcan/:
-dcan/:
-driver C Files
-Makefile with the PRIVATE_INC_DIR variable
-include/:
-linux/:
-can/:
- the additional header files
thanks
Korbinian
Am 26.08.2014 um 14:09 schrieb Björn Döbel:
-BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.08.2014 19:06, Valentin Hauner wrote:
Hi,
On 08/19/2014 02:55 PM, Björn Döbel wrote:
2) Use Fiasco's thread primitives. For examples using this, you
might want to grep for l4_thread_control in pkg/examples. There
are a couple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
let us stay on the list - others might be interested in your problems
as well.
Thank you very much, I tried what you said, But met a problem. In
my test case, I have multiple threads within the same task, but
running on different cores,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm using the following example provided by Michael Hohmuth in 2000
to create new tasks and threads:
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2000/000384.html
this example was for a previous version of our system (L4Env). Do not
use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Out of curiosity: What exactly does l4re do, or why doesn't ned
start new tasks directly?
l4re implements the Region Manager -- this is a thread running inside
your application's address space and handling the page faults raised
by all other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also, do not call the allocator twice within the function call,
because then you would obtain two different dataspaces and this
is not what you want here. Better do
L4:CapDataspace x =
L4Re::Util::cap_alloc.allocL4::Dataspace(); long alloc =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.08.2014 18:12, Yuxin Ren wrote:
Hi All,
I want to do cap/mem mapping without IPC to another thread. In
particular, I want a thread to map its own memory or capability to
itself. How can I achieve this?
You need a capability to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
printf(This message is printed\n); task-map(L4Re::This_task,
env-mem_alloc().fpage(), env-mem_alloc().snd_base());
printf(This message is never printed\n);
env-mem_alloc() only gives you the memory allocator. You will have to
call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.08.2014 04:26, Noah Zentzis wrote:
I'm trying to launch a new process (without libloader) and I'm
having trouble mapping memory to it. I've found the prog_attach_ds
and prog_reserve_utcb_area methods in libloader and ned, but I'm
not sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
for a project, I want to be able to load (elf-)binaries not only
from the filesystem, but also from the network (receive binary,
then start it.) For this, I will write a L4 app (let's call it
manager for now) which handles the network part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[..]
If I would link ned and manager to the tmpfs lib and used the
mount call directly instead of an fstab file, I could avoid having
a second ned instance, right?
I'm not entirely sure.
* As you already found out tmpfs is only local to each
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.08.2014 23:51, Yuxin Ren wrote:
I did not measure min value. The avg is around 5000 cycs, and my
machine is 2.8GHz.
Client and server are in different core.
- - And are these cores on the same socket or on different ones?
- - Are the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm searching for some Informations about using the dde-kit. My
goal is to use the SocketCan driver from Linux eith the l4re on an
ARM BeagleBone Black (Omap3x).
In that case you are looking for DDE/Linux. DDEKit provides a generic
layer for
Hi,
I want to write some code to transfer capabilities from server to client.
But I have no idea how to do this as I am not familiar with L4Re and its
interface.
Could anyone give me some example code or some hints?
please have a look at l4/pkg/examples/sys/map_irq
Kind regards,
Bjoern
Am 17.05.2014 17:47, schrieb Marcus Hähnel:
Hi Valentin,
On 2014-05-17 13:00, Valentin Hauner wrote:
I did not change the Makefile, so g++ is used for compiling (and not
gcc). I've added
CXX_FLAGS = -lstdc++
but that doesn't help.
In addition to what Marcus already said, note that in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 08.05.2014 03:29, Yuxin Ren wrote:
I have one client and one server talking to each other, and both of
them have 2 threads. I want thread 1 in client only talk to thread
1 in server, and thread 2 in client only talk to thread 2 in
server.
.
But I want different threads to run different dispatch function, not only one
server thread process all requests using different dispatch functions.Do you
have any ideas about this?Thank you.
On Thu, May 8, 2014 at 2:07 AM, Björn Döbel doe...@os.inf.tu-dresden.de
wrote:
* *ANFANG
different threads to run different dispatch function, not
only one server thread process all requests using different dispatch
functions.Do you have any ideas about this?Thank you.
On Thu, May 8, 2014 at 2:07 AM, Björn Döbel doe...@os.inf.tu-dresden.de
wrote:
* *ANFANG des
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
In term of running hello world in L4Linux, I can run it by passing
-m32 -static in the compilation process. But, now I'm having a
problem in running the mpi-based application on L4Linux which this
apps needs the mpi library to be able to run.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.04.2014 10:24, Irvanda Kurniadi wrote:
On Fri, Apr 25, 2014 at 4:24 PM, Björn Döbel
doe...@os.inf.tu-dresden.de mailto:doe...@os.inf.tu-dresden.de
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Hi,
In term of running hello
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ayad,
Does this mean you also tried non-RTL8139 NICs? Does this happen
in qemu if you use for instance the emulated e1000?
exactly, but with the e1000, the e1000_clean_rx_irq() does not call
netif_receive_skb() because rx_desc-status is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.04.2014 14:42, Ayad Mostafa wrote:
Dear Adam,
So it's looping in the while loop all the time while polling the
NIC? That would be strange as at some point there should be no
more packets to process.
it doesn't process any packets. it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.04.2014 01:02, Emanuel Berg wrote:
Adam Lackorzynski a...@os.inf.tu-dresden.de writes:
I'm not sure where you enter this. For me, the following works
quite fine:
I tried it in xterm and it was the same thing. But after the
assertion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Anyway, as for including header files, I found that you can indeed
make a directory at the base package level, called include - and
put a Makefile in it just like it is done for the other projects
(but I'm unsure what the Makefile actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Suppose we have 2 cores (core 0 and core 1) and we have 2 tasks
(task A and task B). And I assign all threads of task A to run in
core 0 and all threads of task B to run in core 1. How L4 Fiasco's
scheduler manages this? Will the tasks run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Amazing thing is, I didn't do half (actually close to zero) of that
stuff the first time around, so how it still worked is a mystery!
Fact is, it didn't.
This - now modified with new paths -
qhello () { core=~/core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.02.2014 08:52, Irvanda Kurniadi wrote:
On Wed, Feb 19, 2014 at 12:01 AM, Björn Döbel
doe...@os.inf.tu-dresden.dewrote:
In your case, the module seems to be available, there's just
something wrong with it. When you compiled the module
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.02.2014 07:36, Irvanda Kurniadi wrote:
Hi,
Have you tried to build kernel modules and run it on L4linux? I
read [1] and followed the instructions given by that document. 1. I
built a Hello world Kernel module by following [2], then I got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes I did. I just checked the .config file # Stub drivers
CONFIG_L4_BLK_DS_DRV=y
Are you getting any messages about a missing file during Linux bootup?
For the file to be available through l4bdds it needs to be passed as a
module in the respective
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18.02.2014 15:43, Irvanda Kurniadi wrote:
On Tue, Feb 18, 2014 at 11:10 PM, Björn Döbel
doe...@os.inf.tu-dresden.dewrote:
Yes I did. I just checked the .config file # Stub drivers
CONFIG_L4_BLK_DS_DRV=y
Are you getting any messages about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So building (compiling and linking + some extra glue) is that OS
intense even with the same compiler (and associated tools), the
same language, and, not the least, on the same architecture?
When you write an application on Linux, you at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, this makes sense if this problem had to do with building
*Fiasco* (and/or L4Re) - which indeed took a while, but that didn't
surprise me. What surprised me was that it took ages to compile a
hello world *application* when I already had
to Björn
Döbel (doe...@os.inf.tu-dresden.de).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlLY8SgACgkQP5ijxgQLUNk5+ACdHXk4O9fyWtdIkZiAL1sug8xP
8IoAn13iFztObmch50/cp0NImShxpsD6
=MjQ1
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
[..]
Capabilities are passed around through standard IPC. The
difference is that you don't put them into the UTCB's message
registers but instead you out a send flexpage into the UTCB
buffer registers. Note, that the receiver must be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have read some question about adding libraries to l4/fiasco, but
I don't get how to do it exactly. I need to port libtiff and
openmpi to compile my program over l4/fiasco. Do you have any
documentation about it?
in most cases (I would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
I have two tasks running and communicating through an IPC
connection (basically the clntsrv demo). Now I would like to extend
this a bit:
Using an ipc_call(), the client (actually: multiple clients) should
be able to register with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Alexander,
I like to implement two processes(if this is the correct word for
l4). I want to implement two elf binaries, each of them have a
main function.
These two processes should communicate over IPC. Is this possible?
Of course!
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Johannes,
I just noticed that the current snapshot (2013-08-19) doesn't
compile with gcc4.4 anymore, which is apparently due to some C++11
incompatibilities (see below).
Based on the snapshot from April, I got the Fiasco.OC and L4Re port
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Johannes,
Well, I want to provide capabilities for an application by
putting them into a local namespace. Since our system changes
dynamically I want to add capabilities at runtime by registering
them to the corresponding namespace.
please
Hi Thang Tran,
I'm new to Fiasco and L4Re. I want to write a new program in C++ which
will run on L4Re. I'm looking at the simple client server example in the
l4/pkg/examples/clntsrv directory for my reference. I was able to get it
compiled eventually on L4Re, but I have no idea how to run it.
On 11.06.2013 10:57, Rahul Singhal wrote:
I have recently ported l4 fiasco + l4Re on raspberry pi. I tested the
port with the sample hello world program and it works fine.Now I want
to write some of my own programs (C++, C and python) and run it on
this environment. All I have done as of now is
On 03.06.2013 12:46, BogDan wrote:
Hi,
[..]
So far so good! This is exactly what I want to do, to have a way to be
notified
by the kernel about any exception of a thread. Now my problem is that I
get no notification when something bad happens (e.g. division by 0 or a
page
Am 02.06.2013 10:29, schrieb BogDan:
Hello,
I tried to create a very simple application that uses cxx::Thread, but I
have some link problems:
... Compiling main.o
== Linking test_cxx_thread
main.o:(.rodata._ZTI10TestThread[_ZTI10TestThread]+0x8): undefined reference
to `typeinfo
Hi,
[..]
So far so good! This is exactly what I want to do, to have a way to be notified
by the kernel about any exception of a thread. Now my problem is that I
get no notification when something bad happens (e.g. division by 0 or a
page fault), is there any example where I can look to see how
1 - 100 of 217 matches
Mail list logo
