From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 24 Mar 2014 20:12:18 -0400
To: 9fans@9fans.net
Message-ID: <918827792a854c7ff851bc9b3cc115a3@brasstown.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] more serial questions
Topicbox-Message-UUID: cf24ed9c-ead8-11e9-9d60-3106f5b1d025

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