Re: RTAI fifo opened from LXRT returns 0

Paolo Mantegazza <[email protected]>
Newsgroups gmane.linux.real-time.rtai
Message-ID <[email protected]>
On 03/02/2016 02:05 PM, shreyas pansare wrote:
> Hello Paolo,
> Thanks for your suggestion , but if I want to implement fifos then how 
> do I do it ?
> I have implemented one more fifo in the same application and it works 
> fine.
>
>
What fifo number did you set in kernel space?
Paolo

> -- 
> Thanks & Regards,
>
> *Shreyas B. Pansare*
> +91 9595 052046
> */iASYS/*
> *Product Development Center*
> 401 A/2, Nano Space
> Baner-Pashan link road, Baner
> Pune 411045, India
> Ph. +91 96234 47255 ext. xxx
> www.iasys.co.in
>
> __________________________________________________________________________________________________________________________________________________________
> On 03/02/2016 5:43 PM, Paolo Mantegazza wrote:
>> Use mailboxes, fifo are legacy and for particular specific usages, 
>> e.g patch only based applications and debugging.
>> Paolo
>>
>> On 03/02/2016 01:01 PM, shreyas pansare wrote:
>>> Hello Paolo,
>>>
>>> I am trying to open a fifo */dev/rtf7* in LXRT by using a "*open*" 
>>> system call. *open* returns file descriptor value as 0 .All the data 
>>> written by using this file descriptor gets printed on console.
>>> Why does this happen ? How to solve this problem ? Why does it 
>>> return 0 ?
>>> This is a snippet of my code
>>>
>>> int fd = 0;
>>> fd = open("/dev/rtf7",O_WRONLY);
>>>
>>> The other end of fifo is opened from kernel space module.
>>>
>>> -- 
>>> Thanks & Regards,
>>>
>>> *Shreyas B. Pansare*
>>> +91 9595 052046
>>> */iASYS/*
>>> *Product Development Center*
>>> 401 A/2, Nano Space
>>> Baner-Pashan link road, Baner
>>> Pune 411045, India
>>> Ph. +91 96234 47255 ext. xxx
>>> www.iasys.co.in
>>
>>
>>
>>
>
>

_______________________________________________
Rtai mailing list
[email protected]
https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.