From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4F75C7D1.4020808@domain.hid> Date: Fri, 30 Mar 2012 16:48:49 +0200 From: Wolfgang Grandegger MIME-Version: 1.0 References: <4F7555F7.6010102@domain.hid> <4F75B5BF.8030401@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Cross-link.c ---RTSER_RTIOC_WAIT_EVENT List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Minh GIANG Cc: xenomai-help On 03/30/2012 04:34 PM, Minh GIANG wrote: > hi, > > with option RTSER_RTIOC_WAIT_EVENT in rt_dev_ioctl(), this function returns > un number -110 (Connection timed out) > with option RTSER_RTIOC_GET_STATUS in rt_dev_ioctl(), this function returns > un number 0 (not message) You should call this function *after* the timeout happened. What does the "struct rtser_status" contain? Especially the "line_status" is of interest. > > Anyway, currently it works without rt_dev_ioctl(), i can see rt_dev_read() > wait data event (with debug mode) while giving the period of write > task, for exemple = two seconds. > > so can i remove the funtion rt_dev_ioctl? The rt_dev_ioctl should work. You can remove it, but the problem will remain. To debug the problem you could also add some printk's here: http://www.rts.uni-hannover.de/xenomai/lxr/source/ksrc/drivers/serial/16550A.c#223 Especially the value of "iir" might be interesting. Wolfgang.