From: Thomas Huth <thuth@redhat.com>
To: Dinar Valeev <k0da@opensuse.org>, slof@lists.ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Dinar Valeev <dvaleev@suse.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [PATCH] Fix function keys sequence on USB
Date: Tue, 1 Sep 2015 17:08:49 +0200 [thread overview]
Message-ID: <55E5BF81.8060707@redhat.com> (raw)
In-Reply-To: <CADqALGQ3xnX75XLWkTpSzqVHhWEmULxjCOEee7=jbU2tpnRiPw@mail.gmail.com>
On 01/09/15 16:48, Dinar Valeev wrote:
> On Tue, Sep 1, 2015 at 4:13 PM, Thomas Huth <thuth@redhat.com> wrote:
>>
>> Hi!
>>
>> May I ask what's the status of this patch? As far as I can see, it has
>> not been included in the repository yet?
> Hi,
> Uhh.. I forgot about this patch, since I run local copy.
>
> No the patch is not included. For me it is unclear why keys don't work
> for me, but they do for Alexey and Nikunj.
At least F12 for the boot menu is currently definitely broken - as the
code in "f12-pressed?" in slof/fs/start-up.fs expects other values than
the libusb code currently generates.
Alexey, Nikunj, could you please check whether the boot menu is working
for you when you run QEMU in graphical mode with "-boot menu=on"?
Thanks,
Thomas
prev parent reply other threads:[~2015-09-01 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 13:30 [PATCH] Fix function keys sequence on USB Dinar valeev
2015-05-30 9:59 ` [PATCH slof] " Alexey Kardashevskiy
2015-05-30 19:21 ` Dinar Valeev
2015-06-02 9:47 ` [PATCH] " Nikunj A Dadhania
2015-06-02 10:05 ` Dinar Valeev
2015-06-02 10:29 ` Nikunj A Dadhania
2015-06-02 10:43 ` Dinar Valeev
2015-06-02 11:12 ` Thomas Huth
2015-06-02 11:17 ` Dinar Valeev
2015-07-06 7:58 ` Nikunj A Dadhania
2015-09-01 14:13 ` Thomas Huth
2015-09-01 14:48 ` Dinar Valeev
2015-09-01 15:08 ` Thomas Huth [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-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=55E5BF81.8060707@redhat.com \
--to=thuth@redhat.com \
--cc=aik@ozlabs.ru \
--cc=dvaleev@suse.com \
--cc=k0da@opensuse.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=slof@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).