Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
To:     linux-kernel@vger.kernel.org
From:   Grant Edwards <grant.b.edwards@gmail.com>
Subject: Re: [PATCH v1 0/3] Add virtual serial null modem emulation driver
Date:   Mon, 6 Jan 2020 22:06:50 -0000 (UTC)
Message-ID: <qv0b1p$m0o$1@blaine.gmane.org>
References: <cover.1578235515.git.gupt21@gmail.com>
 <be5b7b29-97e6-41ad-7ae8-cff83dfab95f@zytor.com>
User-Agent: slrn/1.0.3 (Linux)
Cc:     linux-serial@vger.kernel.org
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2020-01-06, H. Peter Anvin <hpa@zytor.com> wrote:
> On 2020-01-05 23:21, Rishi Gupta wrote:

>> The driver named ttyvs creates virtual tty/serial device which
>> emulates behaviour of a real serial port device. Serial port events
>> like parity, frame, overflow errors, ring indications, break
>> assertions, flow controls are also emulated.

Brilliant!  I've wanted that for decades.  It would vastly simplify
the implementation of some network-attached serial ports.

> OK, I believe I have asked this before, at least when this has come up in
> other contexts: any reason not to do this by adding the missing elements to
> the pty interface? For fixed-name nodes, the legacy PTY interface is basically
> what you need.

I proposed doing exactly that many years ago, and I even offered to do
it if there was some indication it would be accepted.  The offer was
ignored, and I never got far enough through the PTY code to determine
if adding the required features would cause any problems for existing
PTY users.

-- 
Grant Edwards               grant.b.edwards        Yow! What PROGRAM are they
                                  at               watching?
                              gmail.com