[okl4-developer] Using naming and IPC from within OK-linux

[Jorge Torres]

Hi Geoff,

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

Hope it helps,

Jorge



On Feb 19, 2008 3:36 PM, Geoff White <netengadmin at gmail.com> wrote:

>
>
> On Feb 19, 2008 12:15 PM, Jorge Torres <jorge.torres.maldonado at gmail.com>
> wrote:
>
> > Hi,
> >
> > Write a Linux driver, which searches on the naming service for the
> > thread ID you registered, and sends it back to the linux thread,
> >
> > Cheers,
> >
> > Jorge
> >
>
>
> Jorge,
> Have you written such a driver?
> Is it a char device or block or network?
> I was thinking of trying to make a more universal type of driver interface
> to the L4 IPC mechanism but was thinking that the real way to do it was to
> extend the existing Linux IPC mechanism to accommodate L4 IPC.
>
> What do you think?
>
>
>
>
>
>
>
> >
> >
> > On Feb 19, 2008 1:14 PM, Damien Schulz <damien.schulz at 4xtc.de> wrote:
> >
> > > Hello,
> > >
> > > 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?
> > >
> > > Thank you,
> > >  ~Damien
> > >
> > > _______________________________________________
> > > Developer mailing list
> > > Developer at okl4.org
> > > https://lists.okl4.org/mailman/listinfo/developer
> > >
> >
> >
> > _______________________________________________
> > Developer mailing list
> > Developer at okl4.org
> > https://lists.okl4.org/mailman/listinfo/developer
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080219/e5f62866/attachment.htm