[okl4-developer] new Wombat syscall and others

[Jorge Torres]

Hi okl4.org,

I have a few questions, of which probably many of you know the answers, but
I'm starting to feel a little lost (RTFM answers are welcomed too :)

*Wombat magic relies on the great work of adding arch/l4 and asm-l4 right?,
so what are all the (asm-* and arch/*)!=l4 used for?
*If one wants to add a new wombat syscall, where is it to be registered?
since there is no arch/l4/kernel/entry.S, which is quite obvious if
architecture independent code is wanted, I believe there is this  syscalls.c
instead, but I cant understand completely how it works, and how  can  it
match with include/asm/unistd.h? perhaps it doesn't really have to.  And how
does this { sys_MYINTERRUPT,    {{ .args = ?(QUITE OBVIOUS), .flags = ?,
.ret_type = ??? }} }, works?

*What do I have to do If I want to use iguana's libraries on wombat kernel
code, I've seen this #include <asm/macros.h>
#include INC_SYSTEM2(something), but I'm not sure; there is also
INC_SYSTEM() so, what are they for?

*Are wombat's user threads L4 threads too, meaning they have UTCB entries on
Wombat's address space?
*If I add an  iguana server, how can I communicate with it from a Wombat
user application, naming,IPC?

*Iguana naming service is restricted to threads among their specific
protection domain, or is it a global service, meaning  that threads  on
different  protection domains and AS  can  communicate via  naming service?


Well thank you very much,

Jorge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20070609/9f48fdb0/attachment.htm