All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas BLANCHARD" <n.blanchard@domain.hid>
To: Nathan.Lauener@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] error after timeout on serial port
Date: Fri, 23 Feb 2007 16:23:17 +0100	[thread overview]
Message-ID: <s5df14b9.092@domain.hid> (raw)

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



>>>> Jan Kiszka <jan.kiszka@domain.hid> 23.02 15:51 >>>
>Lauener Nathan wrote:
>> Hi,
>> 
>> I am polling on a serial port during an init sequence of a
positioning
>> device. Every once in a while I get a return code indicating that a
>> timeout occured, code -110 (ETIMEDOUT). 
 
In the struct rtser_config you have the event_timeout parameter that
cause 
ETIMEDOUT (if it's different than RTSER_DEF_TIMEOUT).
Have a look on rt_dev_ioctl(uiFd, RTSER_RTIOC_WAIT_EVENT, &rx_event ).
 
>After a timeout occured I can't
>> read the port anymore. Whenever I call rt_dev_read() again the
function
>> returns the error code -14 (EFAULT). Is there a flag I must clear to
get
>> the port operatioanl again?
 
Is your device correctly open (file descriptor>=0) ?

>
>I /tend/ to say it's an application bug, because we are using the
driver
>heavily, and our sluggish devices often cause timeouts during setup.
>Some colleague should have already slapped me otherwise. :)
>
>Are you sure that a valid buffer and a valid size is passed to
>rt_dev_read after the timeout (because those should be the reason for
>EFAULT)? If yes, maybe you can post a simple demo for the effect.
>
>Jan
 
Blanchard nicolas

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

             reply	other threads:[~2007-02-23 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 15:23 Nicolas BLANCHARD [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-23 14:29 [Xenomai-help] error after timeout on serial port Lauener Nathan
2007-02-23 14:51 ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5df14b9.092@domain.hid \
    --to=n.blanchard@domain.hid \
    --cc=Nathan.Lauener@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.