All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, ondrej drbohlav <ondrej.drbohlav@gmail.com>
Subject: [Qemu-devel] Re: no sound in MusicPal with qemu 0.12.2
Date: Sat, 23 Jan 2010 14:27:16 +0100	[thread overview]
Message-ID: <4B5AF934.9070606@web.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1001231555240.7324@linmac.oyster.ru>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

malc wrote:
> On Sat, 23 Jan 2010, ondrej drbohlav wrote:
> 
>> Hi there,
>>
>> I have compiled qemu 0.12.2 on an x64 ubuntu (8.10) and run MusicPal
>> in it with SDL.
>> MusicPal works OK but there is no sound.
> 
> Confirmed.
> 
>> I have done essentially the same with qemu 0.11.1. The sound is there
>> (thanks jki for suggesting a previous version).
>>
>> Please find below the configs and logs & contact me if additional info
>> is needed.
>>
>> Cheers, Ondrej
>>
>> 1) qemu-0.12.2
> 
> [..snip..]
> 
> Someone would have to bisect it.

Already done: it's b3a219883ebe21f55a8ee5e7e5b38b9eb309e9c0. But that
patch looks sane. I guess it just revealed a hidden bug in Musicpal's
i2c use. Need to dig deeper.

> 
> BTW, Jan, 2e87c5b937444c1155073f7b10d630e0e383e5d8 doesn't quite do
> what i said helps[1] and conseqently musicpal enters an infinite loop
> again...
> 
> [1] http://lists.gnu.org/archive/html/qemu-devel/2009-09/msg00920.html
> 

OK, I will have to look into the Linux driver code to check the loop
termination conditions again.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2010-01-23 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 17:23 [Qemu-devel] no sound in MusicPal with qemu 0.12.2 ondrej drbohlav
2010-01-23 12:21 ` ondrej drbohlav
2010-01-23 13:01   ` malc
2010-01-23 13:27     ` Jan Kiszka [this message]
2010-01-23 17:51       ` [Qemu-devel] " Jan Kiszka
2010-01-23 17:58         ` malc

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=4B5AF934.9070606@web.de \
    --to=jan.kiszka@web.de \
    --cc=av1474@comtv.ru \
    --cc=ondrej.drbohlav@gmail.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.