X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Thu, 30 Dec 2004 07:09:29 +0200
From: "Eli Zaretskii" <eliz AT gnu DOT org>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-ID: <01c4ee2d$Blat.v2.2.2$e31bb780@zahav.net.il>
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 2.2.2
In-reply-to: <uvfakevla.fsf@fitlinxx.com> (message from David Bolen on 29 Dec
	2004 14:46:25 -0500)
Subject: Re: serial port interaction
References: <Xns95CDC7F0584F6serialport AT 62 DOT 81 DOT 237 DOT 233> <uvfakevla DOT fsf AT fitlinxx DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: David Bolen <db3l AT fitlinxx DOT com>
> Date: 29 Dec 2004 14:46:25 -0500
> 
> We use pmcom for our serial handling and find it works very nicely.
> Unless you use something like this, the odds are very good that you'll
> lose serial data since BIOS won't buffer any information but must be
> polled to ensure you receive all data.  While it doesn't directly
> integrate into the filesystem layer in DJGPP, by and large
> COMPortOpen, COMWriteBuffer and COMReadBuffer are pretty easy
> replacements for open(), write() and read().

One could integrate pmcom into the filesystem layer by using the DJGPP
Filesystem Extensions feature (it is described in the library
reference manual).  Then you could simply use `open', `read', and
`write'.

> You may be getting compilation errors due to some older preprocessor
> string concatenation stuff that was in the source (at least in the 1.0
> version we use).  In our case it was fixable by editing com.c and
> replacing instances of "##x" with just "x" (not including quotation
> marks)

Perhaps a fixed version of pmcom could be uploaded to the DJGPP FTP
site.