public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: alsa-devel@lists.sourceforge.net, linux-msdos@vger.kernel.org
Subject: Re: trouble with dosemu and alsa oss emulation (and a fix for alsa)
Date: Sat, 6 Sep 2003 16:56:03 -0500	[thread overview]
Message-ID: <20030906215602.GV21868@dbz.icequake.net> (raw)
In-Reply-To: <20030906200943.GA5128@quark.fsb.hr>


Hi,

On Sat, Sep 06, 2003 at 10:09:43PM +0200, Vedran Rodic wrote:
> Hi. 
> 
> I'm having trouble with latest ALSA and oss emulation. I'm using dosemu to
> play some DOS games and I've noticed that sound in DOS apps stops playing 
> after short time (depending on the app). 
> 
> 
> I'm regulary updating both alsa and dosemu, I suspected dosemu first, since
> I had no problems whatsoever with alsa oss emulation. 
> 
> It turned out that this was not dosemu problem, but alsa oss emulation problem.
> I've tracked it down to a change in  alsa-kernel/core/oss/pcm_oss.c. 
> The change is here:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/alsa/alsa-kernel/core/oss/pcm_oss.c.diff?r1=1.40&r2=1.41
> 
> I'm currently using the latest pcm_oss.c but without this patch and it
> works great again. 
> 
> I think that dosemu code - src/arch/linux/dosext/sound/linux_sound.c is
> correct. 

Yeah, I know I tried dosemu with the ALSA OSS emulation before, and it
worked mostly correct (surprisingly enough!).  I'm glad you spotted this
regression, it might have gone overlooked for some time otherwise.

DOSEMU really needs the native ALSA sound output... one of these days ;)

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

  reply	other threads:[~2003-09-06 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-06 20:09 trouble with dosemu and alsa oss emulation (and a fix for alsa) Vedran Rodic
2003-09-06 21:56 ` Ryan Underwood [this message]
2003-09-08  7:14 ` Jaroslav Kysela
2003-09-08 14:45   ` [Alsa-devel] " Vedran Rodic

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=20030906215602.GV21868@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-msdos@vger.kernel.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