Re: [Adeos-main] Adeos to Linux domain data communication

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

poornima r wrote:
> Hello,
> 
> I am working on PPC boards (MPC 860).
> I have patched
> Adeos(adeos-ipipe-2.6.18-ppc-1.5-01.patch)
> to my vanilla kernel linux-2.6.18.
> My requirement are 
> 1. A domain servicing critical interrupts and 
> 2. Adeos to Linux domain communication
> 
> I could implement the first requirement by creating a 
> test domain where my interrupts are getting serviced
> as provided in the below link
> http://www.captain.at/adeos-ipipe-jitter-latency-test.php
> 
> 
> But for the second requirement I went through all the
> API services provided by Adeos but, dint find any APIs
>  providing data communication services between Adeos
> and Linux domains. Is there any method to implement
> the above similar to pipes in Xenomai (I am not using
> Xenomai in my current implementation).

Adeos/I-pipe is not implementing such services in order to remain lean.
It is considered the job of the Adeos user (like Xenomai or your own
domains) to handle this. What Adeos provides are means to stall as many
domains along the pipeline as required to execute critical sections like
for implementing interdomain communication services.

> 
> But when went through Adeos related papers and
> documents, I found that Adeos is mainly used for
> harware sharing among multiple OSes or domains but
> alone does not provide tasking, communication, etc. So
> do you think     
> can we implement communication mechanism similar to
> xenomai pipes for Adeos domain and Linux domain
> communication or is it worth using Xenomai?     

That depends on how much more high-level services you may want to use
(now or in the future). From a certain point on, re-implementing things
becomes silly. If this is just about a basic pipe-like IPC for a simple
scenario like yours, it could make sense to write your own variant,
skipping all other services of the Xenomai core that may remain
unused on your target anyway (and their overhead).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]