From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] [RFC PATCH 2/2] serial console, input
Date: Mon, 04 Jul 2016 22:03:09 +0200 [thread overview]
Message-ID: <1467662589.15123.194.camel@redhat.com> (raw)
In-Reply-To: <20160704153448.GB2039@morn.lan>
Hi,
> Does the original code flush the multi-byte sequence on a timeout? I
> suspect it is important that one can hit ESC without having to type
> another key. Also, I'd prefer to avoid backwards gotos if possible.
Yes, sort of. If it didn't match an escape sequence and hasn't seen
additional data on this particular sercon_handle_event call it goes on
interpret the buffer content as single byte. So, effectively the
timeout is the clock_update() call interval.
cheers,
Gerd
next prev parent reply other threads:[~2016-07-04 20:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 10:54 [Qemu-devel] [RFC PATCH 0/2] seabios: add serial console support Gerd Hoffmann
2016-07-01 10:54 ` [Qemu-devel] [RFC PATCH 1/2] serial console, output Gerd Hoffmann
2016-07-01 15:47 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2016-07-04 8:16 ` Gerd Hoffmann
2016-07-04 9:11 ` [Qemu-devel] " Paolo Bonzini
2016-07-04 12:46 ` Gerd Hoffmann
2016-07-04 12:48 ` Paolo Bonzini
2016-07-04 15:26 ` Kevin O'Connor
2016-07-04 15:45 ` Paolo Bonzini
2016-07-04 20:10 ` Gerd Hoffmann
2016-07-04 16:00 ` Kevin O'Connor
2016-07-04 16:03 ` Paolo Bonzini
2016-07-04 17:28 ` Kevin O'Connor
2016-07-04 20:18 ` Gerd Hoffmann
2016-07-04 20:23 ` Gerd Hoffmann
2016-07-01 10:54 ` [Qemu-devel] [RFC PATCH 2/2] serial console, input Gerd Hoffmann
2016-07-01 17:07 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2016-07-01 18:07 ` Kevin O'Connor
2016-07-04 9:16 ` Gerd Hoffmann
2016-07-04 15:34 ` Kevin O'Connor
2016-07-04 20:03 ` Gerd Hoffmann [this message]
2016-07-01 15:47 ` [Qemu-devel] [RFC PATCH 0/2] seabios: add serial console support Gerd Hoffmann
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=1467662589.15123.194.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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.