Thanks Ronald, I appreciate it.
-----Original Message----- From: l4-hackers-bounces@os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Ronald Aigner Sent: Wednesday, January 16, 2008 16:20 To: l4-hackers@os.inf.tu-dresden.de Subject: Re: Problems creating IDL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Lucyantie, you still can directly invoke the kernel using assembler. In this case stick with the Fiasco ABI description. I cannot cite a manual here, because the Fiasco ABI evolved rapidly from the L4 Version 2 specification (http://os.inf.tu-dresden.de/L4/l4refx86.ps.gz). The only "documentation" that exists are the L4 IPC syscall bindings.
If you really want to use the Fiasco kernel without getting "infected" by the user level sources, study the Fiasco source to see how the registers have to be filled to initiate an IPC.
Greetings, Ron.
BTW: If you can spare a moment or two you could contribute the lessons you learn into our public wiki at http://wiki.tudos.org .
Lucyantie Mazalan wrote on 01/16/2008 03:24 AM this:
Hi Bjoern, thanks for the quick reply. I actually following the BID tutorial in a way to omit the L4 IPC syscall bindings and all :) looks like I don't have any choice here, do I? I'll appreciate it. Thanks though ;)
Lucille.
-----Original Message----- From: Bjoern Doebel [mailto:doebel@os.inf.tu-dresden.de] Sent: Wednesday, January 16, 2008 10:01 To: Lucyantie Mazalan Cc: l4-hackers@os.inf.tu-dresden.de Subject: Re: Problems creating IDL
Hi,
I have been creating a package which implements a server invoked by a
client. I understand from the tutorial that I have to create an IDL
file
listing all my public function there. Problem here is that, I would
like
to know whether I really need to do the IDL file or can there be
other
way that I can actually skip the IDL and how do I do that, since my intention here is just to create a simple communication with purpose between my server and client using 1 same language, C. Please advice
me
in this.
Of course you can skip the IDL part completely. Have a look at the documentation of the L4 IPC syscall bindings (http://os.inf.tu-dresden.de/l4env/doc/html/l4sys-l4v2/index.html) and
or at the L4v2 reference manual (http://i30www.ira.uka.de/research/documents/l4ka/Ln-86-21.pdf) to
learn
about how to implement a server without IDL.
DISCLAIMER:
This e-mail contains no confidential information because it was posted
on a public mailing list.
Regards, Bjoern
DISCLAIMER:
This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law.
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
- -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
------------------------------------------------------------------ - - - DISCLAIMER:
This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law.