Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Ronny V. Vindenes" <s864@ii.uib.no>
Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: Re: Re: [Alsa-devel] ALSA 1.0.0pre3 release
Date: Wed, 26 Nov 2003 13:32:04 +0100	[thread overview]
Message-ID: <s5hn0ajxqd7.wl@alsa2.suse.de> (raw)
In-Reply-To: <1069848611.3235.13.camel@localhost.localdomain>

At Wed, 26 Nov 2003 13:10:11 +0100,
Ronny V. Vindenes wrote:
> 
> On Wed, 2003-11-26 at 11:44, Takashi Iwai wrote: 
> > At Wed, 26 Nov 2003 01:11:07 +0100,
> > Ronny V. Vindenes wrote:
> > > 
> > > On Tue, 2003-11-25 at 20:04, Takashi Iwai wrote:
> > > > Hi,
> > > > 
> > > > right now the ALSA 1.0.0pre3 packages are released.
> > > > 
> > > > In this version, alsa-tools package was divided to two several ones,
> > > > alsa-tools and alsa-firmware.  The latter contains only the firmware
> > > > binary files required by loader programs in alsa-tools package.
> > > > Please test them if you have a board requiring the loader (hdsp,
> > > > mixart, vx, usx2y).
> > > > 
> > > > Especially, HDSP users, please test and report whether it works, since
> > > > the hdsploader was modified to load the files dynamically.
> > > > 
> > > > 
> > > 
> > > mmap'ed sound with the cs46xx driver seems to be broken, every other
> > > half second the sound is muted. Non-mmap'ed sound plays normally. This
> > > is under 2.6.0-test9-mm5. The version included in test9-mm5 works as
> > > expected (there was some patches in mm5 against ALSA, but applying those
> > > to 1.0.0pre3 made no difference for this particular problem).
> > 
> > there is no big change in cs46xx driver itself, so the change is
> > either in kernel core or in the config.
> > do you use CONFIG_SND_CS46XX_NEW_DSP ?
> 
> Yes.
> 
> I've tested it with 2.6.0-test10 too now, and I've narrowed it down a
> bit: native alsa mmap'ed or not works, but oss emulation only works
> correctly when not using mmap.
> 
> Things like wine, quake3, Enemy Territory all sound awful. Plain
> 2.6.0-test10 works fine in all cases.

to be sure, try to set direct mode for oss-emulation via writing to
the proc file.  see alsa-kernel/Documentation/OSS-Emulation.txt.

also, please check /proc/asound/card0/pcm0p/sub0/* files in both
cases.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-11-26 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 19:04 ALSA 1.0.0pre3 release Takashi Iwai
2003-11-26  0:11 ` Ronny V. Vindenes
2003-11-26 10:44   ` [Alsa-user] " Takashi Iwai
2003-11-26 12:10     ` Ronny V. Vindenes
2003-11-26 12:32       ` Takashi Iwai [this message]
2003-11-26 14:10         ` Ronny V. Vindenes
2003-11-26 14:15           ` Takashi Iwai
2003-11-26 14:30             ` Ronny V. Vindenes
2003-11-26 16:38 ` [Alsa-devel] " Thomas Charbonnel
2003-11-26 17:08   ` Takashi Iwai
2003-11-27  0:46     ` Thomas Charbonnel
2003-11-27 10:43       ` [Alsa-devel] " Takashi Iwai

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=s5hn0ajxqd7.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=s864@ii.uib.no \
    /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