qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SB16 support
Date: Wed, 5 Nov 2003 02:11:04 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.55.0311050156480.10508@home.oyster.ru> (raw)
In-Reply-To: <3FA8260D.9010101@free.fr>

On Tue, 4 Nov 2003, Fabrice Bellard wrote:

> Thank you for the patch ! This is quite impressive.
>
> I cannot include as is as it needs some modifications to be more
> integrated in QEMU. I would have the following needs:
Never thought it would be, since its couple of hours hack.

> 1) Use SDL for audio rendering.
I steered away from using SDL for audio in Minde(and by extension in sb16
emu). SDL uses callback mechanism for audio mixing. At least under *NIXes
the callback is called either by a thread (do you really want that in
QEMU?) or alarm handler (good bye straight forward host_alarm_handler
welcome headache)

Current `aud.c' requires and expects so little from audio system that it
begs the question: what is simpler to retarget it for a bunch of OS/HW
specific audio systems or maintain SDL abstraction (which btw does not
even provide a way for querying current playing position)

>
> 2) The whole patch should add only two files: dma.c for DMA emulation,
> sb16.c for sb16 emulation and sdlaudio.c for SDL audio driver.

I can try to pull this trick, but again, SDL audio decision needs to be
weighted in. Please e-mail me directly if you have some insights on how
to organize those files.

To all:
http://www.boblycat.org/~malc/code/patches/qemu

Now hosts sb16 and interpreter patches.
Interpreter patch was updated to fix some building issues.

Sincerely,
malc

-- 
mailto:malc@pulsesoft.com

  reply	other threads:[~2003-11-04 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 18:16 [Qemu-devel] SB16 support malc
2003-11-04 22:19 ` Fabrice Bellard
2003-11-04 23:11   ` malc [this message]
2003-11-04 23:46     ` Fabrice Bellard
2003-11-06 17:46       ` Herbert Poetzl

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=Pine.LNX.4.55.0311050156480.10508@home.oyster.ru \
    --to=malc@pulsesoft.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 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).