Re: [Xenomai-help] writing from user space through fifo problems

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

NZG wrote:
>> Are you sure it is EINTR? A first glance at the possible code path,
>> specifically at xnpipe_recv, suggests that you cannot reach the line
>> returning this error code if TM_NONBLOCK was passed.
> Your right, my mistake sorry.
> It's returning EAGAIN , which is the same thing as  EWOULDBLOCK in my kernel 
> headers, which corresponds to the correct value when data i s not available, 
> but doesn't explain why data is never received.

OK, that makes more sense.

> 
>> What Xenomai version are we talking about BTW? 
> 2.3.1 (blackfin 537 build)
> 
>> And, as usual: 
>> self-contained simple test cases are always appreciated. :)
> I'll try to put something together tonight.

That's good. This test will also allow you to check it against
 - more recent Xenomai (please check the Changelog for pipe-related
   changes since 2.3.1, I bet there are a few)
 - some other arch, specifically x86 (IIRC, there is still some Linux
   scheduling artifact left in the I-pipe patch for blackfin, but it
   shouldn't make a difference here - well, who knows...)

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux