[Xenomai-help] rt_pipe_read returns -ENOBUFS

[Xenomai-help] rt_pipe_read returns -ENOBUFS

[newsgroup]

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

Hello,

ive got an userspace process running in realtime and try to communicate to another process unsing the Pipes.
rt_pipe_write() to the non realtime process works fine. ich can read the /dev/rtp1 without problems.

Now i try to write from this process to the realtime process using the /dev/rtp2.
The rt_pipe_read() returns a -ENOBUFS.

here the call (dirty copy): 

struct struct_FIFO_Header {
 unsigned short ID;
 unsigned short Size;
 };

struct_FIFO_Header _Header;
    
ret = rt_pipe_read(&pipe_read,&_Header,sizeof(_Header),TM_NONBLOCK );

ret is now -ENOBUFS

Ive done similar the same using rtai without problems.
anone an idea why it occours?

Greets
  Maveric



[-- Attachment #2: Type: text/html, Size: 2210 bytes --]

Re: [Xenomai-help] rt_pipe_read returns -ENOBUFS

[Gilles Chanteperdrix]

newsgroup wrote:
> Hello,
> 
> ive got an userspace process running in realtime and try to communicate to another process unsing the Pipes.
> rt_pipe_write() to the non realtime process works fine. ich can read the /dev/rtp1 without problems.
> 
> Now i try to write from this process to the realtime process using the /dev/rtp2.
> The rt_pipe_read() returns a -ENOBUFS.
> 
> here the call (dirty copy): 
> 
> struct struct_FIFO_Header {
>  unsigned short ID;
>  unsigned short Size;
>  };
> 
> struct_FIFO_Header _Header;
>     
> ret = rt_pipe_read(&pipe_read,&_Header,sizeof(_Header),TM_NONBLOCK );
> 
> ret is now -ENOBUFS
> 
> Ive done similar the same using rtai without problems.
> anone an idea why it occours?

The great thing with Xenomai compared to rtai is that it has doc. But if
you do not use it, you are right, you have no reason to use Xenomai
instead of rtai.

-- 
                                                 Gilles.