From: Peter Maydell <peter.maydell@linaro.org>
To: Ben Hekster <ben.hekster@foghorn.io>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Booting Raspbian on RPi emulation
Date: Sun, 27 Jan 2019 19:27:54 +0000 [thread overview]
Message-ID: <CAFEAcA9Oc3Rg_NWkeEjYPVz8yQnBbWd0WM5UQSWNRRP9VfjonQ@mail.gmail.com> (raw)
In-Reply-To: <47126B68-3AF7-48AB-B904-4D8EAC854BC7@foghorn.io>
On Wed, 19 Dec 2018 at 19:42, Ben Hekster <ben.hekster@foghorn.io> wrote:
>
> Should have tested a little more:
>
> While the crashing has stopped, the window isn't responsive to
>keystrokes. This includes the frame buffer emulation itself (so
>I can't actually log in) as well as the QEMU Monitor; nothing I
>type has any effect in either.
Yes, I can reproduce this with my "refactor the OSX UI code"
patchset too. The problem is that with the removal of the
code that was in the cocoa_refresh() function that manually
pulled events out of the OSX event queue and called our
QemuCocoaView handleEvent method on them, there's nothing
that does cause that code to be called. (I had mistakenly
assumed handleEvent was an OSX UI method and so the run loop
would call it.)
Unfortunately I'm not sufficiently familiar with how OSX
event handling works to figure out how to plumb it back in
again. It ought to be a fairly simple matter of "implement
whatever method OSX sends events to on whatever of our
various classes is the right one, and make it call handleEvent
with the NSEvent", but I've tried a few things and haven't
been able to actually get any event handling methods to
fire at all :-(
thanks
-- PMM
next prev parent reply other threads:[~2019-01-27 19:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 21:53 [Qemu-devel] Booting Raspbian on RPi emulation Ben Hekster
2018-12-18 22:34 ` BALATON Zoltan
2018-12-19 13:17 ` Peter Maydell
2018-12-19 17:46 ` Ben Hekster
2018-12-19 18:43 ` Peter Maydell
2018-12-19 19:36 ` Ben Hekster
2018-12-19 19:42 ` Ben Hekster
2018-12-20 2:14 ` BALATON Zoltan
2019-01-27 19:27 ` Peter Maydell [this message]
2019-01-27 23:13 ` BALATON Zoltan
2019-01-28 10:24 ` Peter Maydell
2019-01-28 15:30 ` BALATON Zoltan
-- strict thread matches above, loose matches on Subject: below --
2018-11-29 20:29 BALATON Zoltan
2018-11-30 0:43 ` Philippe Mathieu-Daudé
2018-11-30 1:27 ` Guenter Roeck
2018-11-30 2:42 ` BALATON Zoltan
2018-11-30 3:39 ` Guenter Roeck
2018-11-30 12:36 ` BALATON Zoltan
2019-01-15 18:29 ` BALATON Zoltan
2019-01-15 18:54 ` Philippe Mathieu-Daudé
2019-03-04 17:58 ` BALATON Zoltan
2019-08-20 14:50 ` BALATON Zoltan
2019-08-20 15:14 ` Philippe Mathieu-Daudé
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=CAFEAcA9Oc3Rg_NWkeEjYPVz8yQnBbWd0WM5UQSWNRRP9VfjonQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ben.hekster@foghorn.io \
--cc=qemu-devel@nongnu.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).