All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Tosoni <jp.tosoni@acksys.fr>
Cc: linux-serial@vger.kernel.org
Subject: Re: tcdrain / TCSBRK / wait_until_sent delay
Date: Mon, 9 May 2005 11:13:38 +0100	[thread overview]
Message-ID: <20050509111338.C5674@flint.arm.linux.org.uk> (raw)
In-Reply-To: <001701c5547e$5bd9cca0$2e01a8c0@acksys.fr>; from jp.tosoni@acksys.fr on Mon, May 09, 2005 at 12:03:32PM +0200

On Mon, May 09, 2005 at 12:03:32PM +0200, Tosoni wrote:
> I did not understand well your motivations before. I'm not sure I get all
> the implications you suggest. But did you consider theses points:
> 
> b) The change we are seeking is *exclusive* with other uses of RTS
>    (that is how it is done in Windows)

There are many different styles of use of RTS.  The conventional one
and your one are only two.  There are more than two, and all of them
are exclusive.  I don't see why you made the above comment, since we
obviously agree.

> c) With RS485 we are talking about, e.g., a computer installed in a
>    factory and connected to an automaton. There is no purpose for someone
>    to reopen the port for another kind of use (I know this argument is weak)

Consider a brail device which requires non-standard RTS behaviour,
which may be replaced by a modem.

> d) We could define (since the functionality is not yet defined) that in
>    the last close the standard RTS behaviour is reinstated. But still,
>    there are differences between some UNIXes and LINUX regarding what state
>    is kept between close and open.

As I tried to point out (and you missed) there is no clear point at which
the port is closed.  Consider the following scenario:

	1. program A has the port open.
	2. program B tries to open the port, but blocks in the open,
	   waiting for program A to free up the port.
	3. program A closes the port.
	4. program B finally returns from the open call.

Compare this with:

	1. program A (eg, terminal program) has the port open.
	2. program B (eg, file upload utility) opens the port and
	   sends its data.
	3. program B closes the port.

With the second scenario, it's clear that step 3 shouldn't reset the
behaviour.  However, what about the first scenario?

> When I talked to Allan Cox as you suggested, there was no answer from him.
> Maybe too busy?

I can't talk for Alan.  However, Alan has taken on the task of looking
after the tty layer, and so Alan needs to comment.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-05-09 10:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 15:50 tcdrain / TCSBRK / wait_until_sent delay Andy Parkins
2005-05-05 17:51 ` rich+ml
2005-05-06  8:01   ` Andy Parkins
2005-05-06 19:14     ` rich+ml
2005-05-07  9:35       ` Andy Parkins
2005-05-07 18:09         ` rich+ml
2005-05-09  8:01           ` Andy Parkins
     [not found]             ` <Pine.LNX.4.58.0505090825470.750@deadrat.localdomain>
2005-05-10  7:44               ` Andy Parkins
2005-05-09  8:16         ` Tosoni
2005-05-09  8:59           ` Russell King
2005-05-09 10:03             ` Tosoni
2005-05-09 10:13               ` Russell King [this message]
2005-05-09 15:43                 ` Theodore Ts'o
2005-05-07 10:32       ` Gerald Emig
2005-05-09  9:15 ` Christer Weinigel
2005-05-09  9:22   ` Christer Weinigel
2005-05-09 11:05     ` Andy Parkins
2005-05-09 15:53     ` Andy Parkins
2005-05-09 19:45     ` rich+ml

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=20050509111338.C5674@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jp.tosoni@acksys.fr \
    --cc=linux-serial@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.