Peter Maydell [](mailto:peter.mayd...@linaro.org)
writes:
>> On Thu, 18 Jul 2024 at 07:15, Markus Armbruster
>> [](mailto:arm...@redhat.com)
>> wrote:
>>
>>> Looks like this one fell through the cracks.
>>>
>>> Octavian Purdila
>>> [](mailto:ta...@google.com)
>>> writes:
>>>
Add path option
Really happy somebody found the patch useful. I forgot to look at the
review comments at the time
and never got it merged.
@Octavian thanks for bringing it up to shape.
Cheers
Paulo Neves
On 04/06/2024 07:50, Marc-André Lureau wrote:
> On Tue, Jun 4, 2024 at 1:22 AM Octavian Purdila wr
the pty device will be, removing the
need for 2 way communication or smarts.
Signed-off-by: Paulo Neves
---
chardev/char-pty.c | 41 -
chardev/char.c | 6 +-
qapi/char.json | 4 ++--
3 files changed, 47 insertions(+), 4 deletions(-)
diff --git
On Wed, Jan 2, 2019 at 9:24 AM Marc-André Lureau
wrote:
>
> Hi
>
> On Sat, Dec 29, 2018 at 2:34 PM Paulo Neves wrote:
> >
> > If a user requires a virtual serial device like provided
> > by the pty char device, the user needs to accept the
> > returned device
the pty device will be, removing the
need for 2 way communication or smarts.
Signed-off-by: Paulo Neves
---
chardev/char-pty.c | 39 ++-
chardev/char.c | 6 +-
qapi/char.json | 2 +-
3 files changed, 44 insertions(+), 3 deletions(-)
diff --git a
If a user requires a virtual serial device like provided
by the pty char device, the user needs to accept the
returned device name. This makes the program need to
have smarts to parse or communicate with qemu to get the
pty device.
With this patch the program can pass the path where
a symlink to th
Hello all.
I am trying to get qemu to spawn a pty terminal in a location
which I control without needing to retrieve information of the PTY device
a-posteriori from qemu. To this end i inspired myself in the functionality
of socat, which allows PTY terminals to be spawned in a location
specified by
