From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: qemu-devel@nongnu.org
Subject: Re: Re : [Qemu-devel] Cursor keys not working?
Date: Sat, 14 Feb 2009 21:01:36 +1100 [thread overview]
Message-ID: <20090214210136.112e7159.mle+tools@mega-nerd.com> (raw)
In-Reply-To: <20090214094855.GA21941@kos.to>
Riku Voipio wrote:
> Here:
>
> http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg00469.html
>
> The main issue is the lack of portability of the patch, the secondary issue
> is inefficiency. Neither should be hard to fix, the main work goes
> into just testing.
Ok, two issues portability and efficiency.
However, the efficiency problem is already fixed in the second version of
the patch in the Redhat bugtracker:
https://bugzilla.redhat.com/attachment.cgi?id=328839
Obviously the portability problem shouldn't be too hard to fix either. I'll
have a look at it.
Of course not fixing the problem leaves qemu's SDL window pretty much
useless under X.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"It seems you are presuming a Waterfall model of development here. We're not
doing the Waterfall, we're doing the Whirlpool." -- Larry Wall on Perl6
"Perl is circling the drain, that's for sure..." -- llimllibon reddit
next prev parent reply other threads:[~2009-02-14 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 11:17 [Qemu-devel] Cursor keys not working? Rob Landley
2009-02-13 15:24 ` Rick Vernam
2009-02-13 20:30 ` Re : " Sylvain Petreolle
2009-02-13 20:57 ` Aurelien Jarno
2009-02-14 0:24 ` Erik de Castro Lopo
2009-02-14 9:38 ` Rob Landley
2009-02-14 9:48 ` Re : " Riku Voipio
2009-02-14 10:01 ` Erik de Castro Lopo [this message]
2009-02-14 11:45 ` Aurelien Jarno
2009-02-14 11:52 ` Erik de Castro Lopo
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=20090214210136.112e7159.mle+tools@mega-nerd.com \
--to=mle+tools@mega-nerd.com \
--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 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.