From: Rusty Russell <rusty@rustcorp.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: Why is virtio_console not a tty?
Date: Fri, 13 Jun 2014 10:36:10 +0930 [thread overview]
Message-ID: <877g4lpqil.fsf@rustcorp.com.au> (raw)
In-Reply-To: <539A004F.20906@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> I have gotten scattered reports of strange problems caused by the fact
> that virtio_console doesn't behave like a normal tty (support termios
> and so on.) This seems to be an odd restriction -- is there any
> fundamental reason for this design choice?
Not that I know. I tacked it into hvc_console which provided the glue
to make it a console. Avoided me digging into console implementation,
which is pretty horrible.
Given my ignorance, how much change do we need to make it behave like a
TTY?
Cheers,
Rusty.
next prev parent reply other threads:[~2014-06-13 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 19:32 Why is virtio_console not a tty? H. Peter Anvin
2014-06-13 1:06 ` Rusty Russell [this message]
2014-06-13 1:26 ` H. Peter Anvin
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=877g4lpqil.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=amit.shah@redhat.com \
--cc=hpa@zytor.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox