linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Haffner <haffner@astro.wisc.edu>
To: DeRobertis <derobert@erols.com>
Cc: Linux/PCC Development Mailing List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: stty crtscts < /dev/ttyS1
Date: Wed, 22 Mar 2000 10:05:42 -0600	[thread overview]
Message-ID: <38D8EF56.17970FBC@astro.wisc.edu> (raw)
In-Reply-To: l03130302b4fd80d3a908@[216.164.130.191]


DeRobertis wrote:
>
> Hardware flow control is broken. The command in the subject line (stty
> crtscts < /dev/ttyS1) freezes linux 2.2.14. Any idea why?

Try this syntax: "stty -F /dev/ttyS1 crtscts". There's a comment in the
info doc for stty that letting the shell open the device may block in
certain situations.

mh
--
Matt Haffner                      /|------|\    University of Wisconsin
Dept. of Astronomy               /|--------|\            Madison
haffner@astro.wisc.edu          /|----------|\
           WHAM project -- http://www.astro.wisc.edu/wham

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-22 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 22:28 limited range of data error Rhys
2000-03-20 23:12 ` Gabriel Paubert
2000-03-21  1:54 ` David A. Gatwood
2000-03-21  2:22   ` Gabriel Paubert
2000-03-21 19:48 ` stty crtscts < /dev/ttyS1 DeRobertis
2000-03-22 16:05   ` Matt Haffner [this message]
     [not found]     ` <l03130300b4ff357b23e8@[216.164.129.33]>
2000-03-23 11:17       ` stty crtscts < /dev/ttyS1 [603ev] ce
2000-03-25  6:06         ` DeRobertis
2000-03-23 13:34     ` communicate with peripherics ? Franck Chionna
     [not found]   ` <l03130304b50c8e1b783f@[216.164.131.253]>
2000-04-08  0:35     ` stty crtscts < /dev/ttyS1 Giuliano Pochini
2000-04-08  4:05       ` DeRobertis
2000-04-08 17:08         ` Greg Noel
2000-04-09  0:02           ` Giuliano Pochini
2000-04-09 17:42           ` DeRobertis
2000-04-09  0:20         ` Giuliano Pochini

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=38D8EF56.17970FBC@astro.wisc.edu \
    --to=haffner@astro.wisc.edu \
    --cc=derobert@erols.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).