From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/3] docs/s390x: document 3270
Date: Fri, 15 May 2020 11:45:11 +0200 [thread overview]
Message-ID: <20200515114511.2ac852f3.cohuck@redhat.com> (raw)
In-Reply-To: <b6acb966-16f2-605d-6d01-70f6085bfa79@redhat.com>
On Fri, 15 May 2020 11:14:40 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 15/05/2020 11.00, Cornelia Huck wrote:
> > On Fri, 15 May 2020 09:29:42 +0200
> > Thomas Huth <thuth@redhat.com> wrote:
> >
> >> On 05/05/2020 15.50, Cornelia Huck wrote:
> >>> Add some basic info how to use 3270 devices.
> >>>
> >>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> >>> ---
> >>> docs/system/s390x/3270.rst | 32 ++++++++++++++++++++++++++++++++
> >>> docs/system/target-s390x.rst | 1 +
> >>> 2 files changed, 33 insertions(+)
> >>> create mode 100644 docs/system/s390x/3270.rst
> >>>
> >>> diff --git a/docs/system/s390x/3270.rst b/docs/system/s390x/3270.rst
> >>> new file mode 100644
> >>> index 000000000000..e367a457e001
> >>> --- /dev/null
> >>> +++ b/docs/system/s390x/3270.rst
> >>> @@ -0,0 +1,32 @@
> >>> +3270 devices
> >>> +============
> >>> +
> >>> +With the aid of the ``x3270`` emulator, QEMU provides limited support
> >>> +for making a single 3270 device available to a guest. Note that this
> >>> +supports basic features only.
> >>
> >> The first sentence sounds somewhat confusing. Maybe rather something like:
> >>
> >> QEMU can emulate a 3270 device attached to a guest, which then can be
> >> used with a program like ``x3270`` to get a traditional 3270 terminal
> >> for your guest.
> >
> > But QEMU actually relies on x3270 (or a comparable program). It only
> > emulates the basic ccw plumbing; for the actual protocol (beyond
> > negotiating tn3270), it relies on the emulation done by x3270.
>
> Ok, makes sense now. Maybe something like:
>
> QEMU provides the possibility to connect an external 3270 terminal
> emulator (like ``x3270``) to a guest?
Hm...
"QEMU supports connecting an external 3270 terminal emulator (such as
``x3270``) to make a single 3270 device available to a guest. Note that
this supports basic features only."
?
next prev parent reply other threads:[~2020-05-15 9:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:50 [PATCH 0/3] s390x: improve documentation Cornelia Huck
2020-05-05 13:50 ` [PATCH 1/3] docs/s390x: document the virtual css Cornelia Huck
2020-05-15 7:04 ` Thomas Huth
2020-05-15 8:51 ` Cornelia Huck
2020-05-15 8:57 ` Thomas Huth
2020-05-15 9:40 ` Cornelia Huck
2020-05-05 13:50 ` [PATCH 2/3] docs/s390x: document 3270 Cornelia Huck
2020-05-15 7:29 ` Thomas Huth
2020-05-15 9:00 ` Cornelia Huck
2020-05-15 9:14 ` Thomas Huth
2020-05-15 9:45 ` Cornelia Huck [this message]
2020-05-15 10:01 ` Thomas Huth
2020-05-05 13:50 ` [PATCH 3/3] docs/s390x: document vfio-ccw Cornelia Huck
2020-05-15 7:54 ` Thomas Huth
2020-05-15 9:15 ` Cornelia Huck
2020-05-14 6:13 ` [PATCH 0/3] s390x: improve documentation Cornelia Huck
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=20200515114511.2ac852f3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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).