public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Geir Thomassen <geirt@powertech.no>
To: Trent Jarvi <trentjarvi@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Serial port latency
Date: Thu, 22 Mar 2001 21:03:38 +0100	[thread overview]
Message-ID: <3ABA5A9A.7B85B5B9@powertech.no> (raw)
In-Reply-To: <Pine.LNX.4.20.0103221219410.3343-100000@linuxtaj.korpivaara.org>

Trent Jarvi wrote:
> 
> Hi,
> 
> I'm not on the kernel list.  I just ran across your email while looking at the
> weekly archive.
> 
> I think you want to enable software flow control.
> 
>         tcgetattr( fd, &ttyset );
>         ttyset.c_iflag |= IXOFF;
>         tcsetattr( fd, TCSANOW, &ttyset );
> 

Just tested it, it didn't change anything. The response from the controller
can contain ^S/^Q, so it would be a bad idea anyway ....

> Someone reported that the Java CommAPI driver at http://www.rxtx.org got
> 150-200ms latency with (9600,N,8,1,XON/XOFF).  Beyond that you may have to
> look at something like the realtime support.  I guess 2 ms is normal on
> win98.

Win98 is the problem I am trying to solve with my program ...

> Since you have the scope hooked up you may look at hardware flow control too.
> 
>         tcgetattr( fd, &ttyset );
>         ttyset.c_cflag |= HARDWARE_FLOW_CONTROL;
>         tcsetattr( fd, TCSANOW, &ttyset );

Do you mean CRTSCTS ? HARDWARE_FLOW_CONTROL is not defined in my header files.
I use CLOCAL, which should make the driver ignore modem control lines.

> Let me know if you find anything out.  I'm the maintainer of rxtx and would
> be interested in documenting this for others.

sure ...

> --
> Trent Jarvi
> TrentJarvi@yahoo.com

Thanks anyway

Geir

       reply	other threads:[~2001-03-22 20:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.20.0103221219410.3343-100000@linuxtaj.korpivaara.org>
2001-03-22 20:03 ` Geir Thomassen [this message]
2001-03-22 20:17   ` Serial port latency Trent Jarvi
     [not found] <000401c0b319517fea9@local>
2001-03-25 23:10 ` Pavel Machek
2001-03-29  7:58   ` Manfred Spraul
2001-03-30 22:36     ` Pavel Machek
2001-03-31 22:09       ` Manfred Spraul
2001-04-10  0:37   ` Andrea Arcangeli
2001-03-22 21:45 Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22 18:21 Geir Thomassen
2001-03-22 20:08 ` Theodore Tso
2001-03-22 20:32   ` Geir Thomassen
2001-03-22 20:55     ` Paul Fulghum
2001-03-22 22:44     ` Theodore Tso
     [not found] ` <20010322141937.C22479@universal-fasteners.com>
2001-03-22 21:02   ` Geir Thomassen
2001-03-22 21:52 ` Jonathan Lundell
2001-03-22 23:25 ` Pavel Machek
2001-03-23 14:43   ` Geir Thomassen

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=3ABA5A9A.7B85B5B9@powertech.no \
    --to=geirt@powertech.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trentjarvi@yahoo.com \
    /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