From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: Jacob Sparre Andersen <jacob@jacob-sparre.dk>
Newsgroups: comp.lang.ada
Subject: Re: GNAT.Serial_Communications
Date: Mon, 20 Mar 2017 16:20:50 +0100
Organization: JSA Research & Innovation
Message-ID: <87a88g2cvh.fsf@jacob-sparre.dk>
References: 
 <d79ca03a-af82-410f-9add-6f6a817b9512@l30g2000vbn.googlegroups.com>
	<b365473f-e4c7-4ea4-93d0-dc93c80e2948@googlegroups.com>
NNTP-Posting-Host: 109.57.25.61.mobile.3.dk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: franka.jacob-sparre.dk 1490023251 25782 109.57.25.61 (20 Mar 2017
 15:20:51 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Mon, 20 Mar 2017 15:20:51 +0000 (UTC)
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Cancel-Lock: sha1:N2fJextm+Q3aN5bhy0StjWkbs7o=
Xref: news.eternal-september.org comp.lang.ada:46433
Date: 2017-03-20T16:20:50+01:00
List-Id: <comp.lang.ada>

mario.blunk.gplus@gmail.com writes:

> The serial communication with /dev/ttyxxxx does not work if hardware
> flow control is enabled (CRTSCTS). Since s-oscons.ads dictates a wrong
> integer for this value, all bits in variable Current.c_cflag (in
> g-sercom.adb) flip to "one" when hardware flow control enabled, thus
> making all other bits in this "register" turn on.
>
> I found the correct number 16#80000000# by counter-checking with a
> C-program which also confirmed the octal ! number specified in
> termbits.h (line 161).
>
> The file s-oscons.ads has a wrong number in line 157 (see attached).

> The os where I found the bug is Open Suse 42.xx Leap (64bit) (not
> older than 1 year). In later distros OpenSuse 13.2 (32bit) also.
>
> What can I do to fix the bug in my run time libraries?

You report the bug to OpenSuse, so their packager can correct the
problem.  It may be a configuration error in the build of the OpenSuse
package.

Greetings,

Jacob
-- 
"Can we feel bad for the universe later?"