From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] more serial questions
Date: Tue, 25 Mar 2014 08:45:37 +0100 [thread overview]
Message-ID: <1D432047-DD58-4730-9386-F242419B88A0@gmail.com> (raw)
In-Reply-To: <918827792a854c7ff851bc9b3cc115a3@brasstown.quanstro.net>
I didn't add that, your guess is as good as mine.
G.
> On Mar 25, 2014, at 1:12 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> i'm just asking questions, because i don't have the experience the author
> clearly has.
>
> i'm looking at this comment
>
> /*
> * if we encounter a long run of continuous read
> * errors, do something drastic so that our caller
> * doesn't just spin its wheels forever.
> */
>
> long run is defined to be 10000 for the lifetime of all serial ports. i'm thinking
> of making this 5 in a row per call, and checking for a few more cant continue
> type messages. was there a particular device that might spit out hundreds of
> consecutive read timeouts (that's the only error this works for) before returning
> something? could the same thing happen on write?
>
> - erik
>
next prev parent reply other threads:[~2014-03-25 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 0:12 erik quanstrom
2014-03-25 7:45 ` Gorka Guardiola [this message]
2014-03-25 13:46 ` erik quanstrom
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=1D432047-DD58-4730-9386-F242419B88A0@gmail.com \
--to=paurea@gmail.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).