Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: alsa-lib & oss 1.0.3rc1
Date: Fri, 27 Feb 2004 13:38:16 +0100	[thread overview]
Message-ID: <1077885495.13385.32.camel@thor.asgaard.local> (raw)
In-Reply-To: <Pine.LNX.4.58.0402261933560.13076@pnote.perex-int.cz>

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

On Thu, 2004-02-26 at 19:38, Jaroslav Kysela wrote:
> On Thu, 26 Feb 2004, Michel Dänzer wrote:
> 
> > The problem occurs when the ALSA_OSS_WRAPPER environment variable isn't
> > set. initialize() returns early, so the public functions segfault when
> > they try to dereference the uninitialized fds.
> > 
> > Is there a reason why ALSA_OSS_WRAPPER must be set? Even if so, I think
> > it should cope more gracefully otherwise. :)
> 
> No reason. I ommited to remove this hack when I separated the wrapper 
> code from the API emulation code. You can remove the lines without any 
> side effect.

Okay, thanks.

Unfortunately, bzflag now fails doing 

ioctl(5, SNDCTL_DSP_SETFRAGMENT, 0x7ffff308[4000c])

even with the attached patch, which used to be enough to get it working.
Adam's ('small and cosmetic'??? :) patch doesn't help either.

Luckily, bzflag is switching to SDL...


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

[-- Attachment #2: local.diff --]
[-- Type: text/x-patch, Size: 688 bytes --]

? build-arch-stamp
? debian
? local.diff
Index: alsa/pcm.c
===================================================================
RCS file: /cvsroot/alsa/alsa-oss/alsa/pcm.c,v
retrieving revision 1.9
diff -p -u -r1.9 pcm.c
--- alsa/pcm.c	26 Feb 2004 15:31:46 -0000	1.9
+++ alsa/pcm.c	27 Feb 2004 12:13:33 -0000
@@ -261,7 +261,9 @@ static int oss_dsp_hw_params(oss_dsp_t *
 			if (err < 0)
 				return err;
 			if (dsp->maxfrags > 0) {
-				unsigned int periods_max = dsp->maxfrags;
+				unsigned int periods_max = periods_min > dsp->maxfrags
+							 ? periods_min
+							 : dsp->maxfrags;
 				err = snd_pcm_hw_params_set_periods_max(pcm, hw,
 									&periods_max, 0);
 				if (err < 0)

  reply	other threads:[~2004-02-27 12:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21 22:05 alsa-lib & oss 1.0.3rc1 Jaroslav Kysela
2004-02-24 16:59 ` Will
2004-02-25 11:05   ` Jaroslav Kysela
2004-02-25 13:40     ` Will
2004-02-26  0:06 ` Michel Dänzer
2004-02-26 10:30   ` Jaroslav Kysela
2004-02-26 14:13     ` Michel Dänzer
2004-02-26 14:10       ` Jaroslav Kysela
2004-02-26 14:30         ` Michel Dänzer
2004-02-26 14:33           ` Jaroslav Kysela
2004-02-26 17:53             ` Michel Dänzer
2004-02-26 18:38               ` Jaroslav Kysela
2004-02-27 12:38                 ` Michel Dänzer [this message]
2004-02-27 13:49                   ` Adam Tla/lka
2004-02-27 14:18                     ` Adam Tla/lka
2004-02-26 15:55           ` Sergey Vlasov
2004-02-26 17:56             ` Michel Dänzer
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23 21:43 Pawel Rozanski

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=1077885495.13385.32.camel@thor.asgaard.local \
    --to=michel@daenzer.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    /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