![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| system call problem | zerocool_08 | Linux | 2 | 03-24-2009 10:45 PM |
| Problem with signal handler and interrupted system call | soeckel | High Level Programming | 2 | 01-27-2009 05:14 AM |
| problem in msgctl() system call | ajaysahoo | AIX | 0 | 04-30-2008 10:18 AM |
| Problem in system call | spmlingam | High Level Programming | 1 | 04-03-2006 06:02 AM |
| read system call | Madhu Babu | High Level Programming | 1 | 11-16-2002 07:11 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Problem in read() system call in Xenomai-2.4
Dear All,
I am having problem with read() system call in Blocking Mode. In my driver interrupt intimation done through RT FIFO. so i have created the RT FIFO and open the FIFO using open() system call with O_RDONLY flag and i am waiting for interrupt using read() blocking call.initally its running correctly. While handling the continuous interrupt, the read()system call is not released from blocking mode. But the driver is putting the data into RTFIFO. This problem is happenning continuously. Frequency of the interrupt: 700us & 7.3ms Time Line of interrupt : | Int1 | 700us | Int2 | 7.3ms|| Int1 | 700us | Int2 | 7.3ms| |----------------------------------------------------------| ..... | 8ms || 8ms | Kindly help me in this regards. ![]() |
|
||||
|
I cannot find any information on RT fifo's except that they're considered "legacy" now, replaced by message pipes. One way I've found to unstick pipes and fifos is to write a newline at the end of your data, if it's buffering despite it all a newline can flush them. I have no idea if this applies to an rt-fifo. I might find more if I knew what function calls you were using to create the rt-fifo.
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|