From: Thomas Huth <thuth@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SDL2 issues
Date: Fri, 20 Oct 2017 13:06:47 +0200 [thread overview]
Message-ID: <9e4910ab-c841-a814-8cc1-879ddb924b7c@redhat.com> (raw)
In-Reply-To: <1508495342.18146.8.camel@redhat.com>
On 20.10.2017 12:29, Gerd Hoffmann wrote:
> On Fri, 2017-10-20 at 13:05 +0300, Michael Tokarev wrote:
>> Hello
>>
>> After we tried to switch from SDL1 to SDL2 in Debian qemu,
>> we receives quite some reports about various issues.
>>
>> We use 2.10.1 version of qemu.
>>
>> Example of the issues: http://bugs.debian.org/879193
>
> Doesn't reproduce.
>
>> http://bugs.debian.org/870025 - a few patches at the bottom
>
> Those patches should go to the mailing list.
>
>> http://bugs.debian.org/878087
>
> Yes, -k is simply not supported with sdl2.
> Those remappings should be done in the guest instead.
>
>> What's the status of SDL2 support in qemu? I've seen it is
>> the default now if SDL2 is present on the system (it was
>> SDL1 before).
>
> Yep. Long term I want drop SDL1, this is the first step.
>
>> Also, what's the status of SDL _audio_ support, is it needed
>> at all once we have alsa, pa and oss?
>
> Dunno how well mixing sdl display with non-sdl audio works. Feel free
> to send a patch dropping sdl audio to the list to check what people
> think about that ;)
I think we've had that topic before: SDL audio is still required for
some non-Linux systems like Haiku, so please don't remove it, even if
SDL audio still needs some love with SDL2 to get really usable there again.
Thomas
prev parent reply other threads:[~2017-10-20 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 10:05 [Qemu-devel] SDL2 issues Michael Tokarev
2017-10-20 10:29 ` Gerd Hoffmann
2017-10-20 11:06 ` 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=9e4910ab-c841-a814-8cc1-879ddb924b7c@redhat.com \
--to=thuth@redhat.com \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--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).