From: Jeremy Linton <jeremy.linton@arm.com>
To: Haojian Zhuang <haojian.zhuang@linaro.org>,
edk2-devel-01 <edk2-devel@lists.01.org>,
Linaro UEFI Mailman List <linaro-uefi@lists.linaro.org>
Subject: Re: [Linaro-uefi] [issue] Arrow key can't be read on tty terminal in release build
Date: Fri, 9 Feb 2018 09:52:30 -0600 [thread overview]
Message-ID: <6466d400-93d3-9594-c527-0f941d41e312@arm.com> (raw)
In-Reply-To: <CAD6h2NQis=i4UDn4x0Fg4JtdojwAJo0-qzt-5cb+ZKHF82SaHA@mail.gmail.com>
Hi,
On 02/07/2018 09:50 AM, Haojian Zhuang wrote:
> Hi all,
>
> I have an issue on tty terminal. I setup PL011 serial console as the
> tty terminal on HiKey platform. When it's built in debug mode, arrow
> key works well. When it's built in release mode, arrow key can't work.
>
> For example, DOWN key is gotten in terminal with "~[B" value in debug
> build. DOWN key is gotten in terminal with "~" value in release build.
> These values are fetched by GetOneKeyFromSerial().
>
> But I can't find any difference on PL011 serial driver between debug
> and release mode.
>
> Do you have any idea on this?
Just to add an additional data point.
I see arrow key issue on the hikey as well as the ARM models. The
problem seems to have shown up sometime late last year and happens in my
case when the machine directly boots into distro provided grub.
Strangely, exiting to the BDS and then starting the boot from the BDS
seems to clear up the problem and the arrow keys work (or pressing
escape and going to the BDS first, either way poping up the BDS menus
seem to work around the issue).
>
> Best Regards
> Haojian
> _______________________________________________
> Linaro-uefi mailing list
> Linaro-uefi@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-uefi
>
prev parent reply other threads:[~2018-02-09 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 15:50 [issue] Arrow key can't be read on tty terminal in release build Haojian Zhuang
2018-02-07 15:52 ` Ard Biesheuvel
2018-02-07 16:12 ` Haojian Zhuang
2018-02-07 16:13 ` Ard Biesheuvel
2018-02-07 16:43 ` Haojian Zhuang
2018-02-07 16:52 ` Ard Biesheuvel
2018-02-09 15:52 ` Jeremy Linton [this message]
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-list 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=6466d400-93d3-9594-c527-0f941d41e312@arm.com \
--to=devel@edk2.groups.io \
/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