From: Russell King <rmk@arm.linux.org.uk>
To: Tosoni <jp.tosoni@acksys.fr>
Cc: 'Andy Parkins' <andyparkins@gmail.com>, linux-serial@vger.kernel.org
Subject: Re: tcdrain / TCSBRK / wait_until_sent delay
Date: Mon, 9 May 2005 09:59:03 +0100 [thread overview]
Message-ID: <20050509095903.A5674@flint.arm.linux.org.uk> (raw)
In-Reply-To: <000a01c5546f$57d83f60$2e01a8c0@acksys.fr>; from jp.tosoni@acksys.fr on Mon, May 09, 2005 at 10:16:03AM +0200
On Mon, May 09, 2005 at 10:16:03AM +0200, Tosoni wrote:
> - Then Mr Russel King suggested to redesign a complete "line discipline"
Please do me the reasonable curtesy of spelling my name correctly.
> just to handle the missing RTS feature. I must note that such "line
> discipline" would duplicate completely the existing default line discipline
> except for the RTS_TOGGLE ioctl.
Interestingly, I've reviewed our discussions back in December, and
they aren't exactly how you recollect them to be. I gave you the
historical position, and suggested both a possible way forward and
someone else for you to talk to about this.
It also appears that you continued to press for _your_ original
implementation, justifying it against the historical position (both
of which I'd already suggested weren't suitable.)
Maybe I didn't explain clearly enough why your implementation wasn't
suitable. Adding an IOCTL for RS485 RTS style vs conventional RTS
style causes problems. Consider what happens when:
1. we get a third (and there are more than two) flow control styles.
2. the port is closed and something else opens it which wants standard
flow control. (or even an overlapping open/close.)
I have also suggested to a third party about adding a feature by which
the flow control method could be changed between several different
settings, preferably via the existing control implmentation - termios.
This should resolve both of the above.
Unfortunately, that also went by un-noticed and as such hasn't progressed.
Therefore, there has been no progress on different flow control styles.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-05-09 8:59 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 [this message]
2005-05-09 10:03 ` Tosoni
2005-05-09 10:13 ` Russell King
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=20050509095903.A5674@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=andyparkins@gmail.com \
--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.