Hi,<br><br>I dont see why you couldnt write to your proc driver.<br>On your mp_init_module function<br><br>Our_Proc_File = create_proc_entry(PROC_ENTRY_FILENAME, 0644, NULL);<br>Our_Proc_File->proc_fops = &File_Ops_4_Our_Proc_File;<br>
<br> -----<br>static struct file_operations File_Ops_4_Our_Proc_File = {<br> .read = procfs_read,<br> .write = procfs_write,<br> .open = procfs_open,<br> .release = procfs_close,<br>};<br><br>-------<br>
<br>and you could code somethig at open, write, etc<br><br>int procfs_open(struct inode *inode, struct file *file)<br>{<br> your L4 IPC code<br>}<br><br>Cheers,<br><br>Jorge<br><br><br><br><div class="gmail_quote">On Feb 19, 2008 5:45 PM, Subcommander l0r3zz <<a href="mailto:l0r3zz@gmail.com">l0r3zz@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div class="Ih2E3d">On Feb 19, 2008 2:01 PM, Jorge Torres <<a href="mailto:jorge.torres.maldonado@gmail.com" target="_blank">jorge.torres.maldonado@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Geoff,<br><br>I have done; A Linux syscall that proxies IPC calls
and a proc driver, what I experienced was that the driver is a better
approach, plus syscalls will mess up your compiler and you will have to
port them to every architecture, if you want I will search and post a
code for you, the ideal thing would be to have auto-generated studs for each service you provide on iguana, that is something Ben <br>
<br>Hope it helps,<br><font color="#888888"><br>Jorge</font><div><div></div><div></div></div></blockquote></div><div><br><br>Hmmm, I have a very simple /proc driver that just list out the KIP for now. and I was thinking how to extend it. I could add a char driver implementation, but then doesn't IPC look more like a block device, or really even a network device? I guess one advantage to a char driver is that then you can write userland PERL, Scheme and Ruby programs that could talk to Iguana Servers very easily.<br>
<br><br><br>Did your /proc driver allow userland threads to write into parts of it? I'm just curious how you went about it?<br></div><div><div></div><div class="Wj3C7c"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><br><font color="#888888"><br></font><br><br><div class="gmail_quote">On Feb 19, 2008 3:36 PM, Geoff White <<a href="mailto:netengadmin@gmail.com" target="_blank">netengadmin@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div>On Feb 19, 2008 12:15 PM, Jorge Torres <<a href="mailto:jorge.torres.maldonado@gmail.com" target="_blank">jorge.torres.maldonado@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>Write a Linux driver, which searches on the naming service for the thread ID you registered, and sends it back to the linux thread,<br><br>Cheers,<br><font color="#888888"><br>Jorge</font><div><div></div><div>
</div></div></blockquote></div><div><br><br>Jorge,<br>
Have you written such a driver?<br>
Is it a char device or block or network?<br>
I was thinking of trying to make a more universal type of driver interface to the L4 <span style="background: yellow none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">IPC</span> mechanism but was thinking that the real way to do it was to extend the existing Linux <span style="background: yellow none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">IPC</span> mechanism to accommodate L4 <span style="background: yellow none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">IPC</span>.<br>
<br>
What do you think?<br><br><br><br><br><br> </div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><br><br><div class="gmail_quote">
On Feb 19, 2008 1:14 PM, Damien Schulz <<a href="mailto:damien.schulz@4xtc.de" target="_blank">damien.schulz@4xtc.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br><br>I'm writing a client application for ok-linux that should be able to communicate with a l4 service via IPC. The service registers itself at the naming service to share its thread id with the client application. Unfortunately the linux client isn't able too lookup anything from the naming service and alway crashes with a segmentation fault. So is it poosible to resolve a name from within an OK-linux application? And if yes, how is it possible? Is it futhermore possible to use magpie generated code from within a wombat application to communicate with a l4 based service?<br>
<br>Thank you,<br> ~Damien<br><br>_______________________________________________<br>Developer mailing list<br><a href="mailto:Developer@okl4.org" target="_blank">Developer@okl4.org</a><br><a href="https://lists.okl4.org/mailman/listinfo/developer" target="_blank">https://lists.okl4.org/mailman/listinfo/developer</a><br>
</blockquote></div><br>
</div></div><br>_______________________________________________<br>Developer mailing list<br><a href="mailto:Developer@okl4.org" target="_blank">Developer@okl4.org</a><br><a href="https://lists.okl4.org/mailman/listinfo/developer" target="_blank">https://lists.okl4.org/mailman/listinfo/developer</a><br>
<br></blockquote></div></div><br>
</blockquote></div><br>
</div></div><br>_______________________________________________<br>Developer mailing list<br><a href="mailto:Developer@okl4.org" target="_blank">Developer@okl4.org</a><br><a href="https://lists.okl4.org/mailman/listinfo/developer" target="_blank">https://lists.okl4.org/mailman/listinfo/developer</a><br>
<br></blockquote></div></div></div><br>
</blockquote></div><br>