Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail
From: Grant Edwards <invalid@invalid.invalid>
Newsgroups: comp.os.linux.embedded
Subject: Re: When 0x0d become 0x0a
Date: Fri, 14 Feb 2014 04:06:10 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 25
Message-ID: <ldk4ni$hi3$1@reader1.panix.com>
References: <ldjodp$m47$1@dont-email.me>
NNTP-Posting-Host: c-24-118-110-103.hsd1.mn.comcast.net
X-Trace: reader1.panix.com 1392350770 17987 24.118.110.103 (14 Feb 2014 04:06:10 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Fri, 14 Feb 2014 04:06:10 +0000 (UTC)
User-Agent: slrn/1.0.1 (Linux)
Xref: csiph.com comp.os.linux.embedded:636

On 2014-02-14, Les Cargill <lcargill99@comcast.com> wrote:
> I'm porting some code from one Linux to another. It uses serial ports.
>
> As opened, the serial port converts 0x0d characters to 0x0a characters.
>
> I have done some googling to find which *opts() functions

I've no idea what "*opts() functions" mean.

> control setting the file referred to by the handle for the serial
> port to be a pure, binary file. I see the one that turns off this
> conversion, but I want all characters to be received completely
> untrammelled.

http://www.cmrr.umn.edu/~strupp/serial.html

> I also need to use fopen()... fclose(), so ORed together last-argument 
> things in open() are out.

Whatever.

-- 
Grant