From: Alien <alien999999999@users.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Cc: Lee Revell <rlrevell@joe-job.com>
Subject: Re: OSS/ALSA issue
Date: Tue, 6 Jun 2006 23:29:06 +0200 [thread overview]
Message-ID: <200606062329.09662.alien999999999@users.sourceforge.net> (raw)
In-Reply-To: <1149626271.4072.60.camel@mindpipe>
[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]
Op dinsdag 6 juni 2006 22:37, schreef Lee Revell:
> On Tue, 2006-06-06 at 21:57 +0200, Alien wrote:
> > as a result, the sound was played, all sound looped (also flash), and
> > a few
> > hours later, my /var/log/kernel/warnings was > 600MB (kernel
> > warnings).
> >
> >
> > Now, we all know that:
> >
> > 1. ALSA has hardware mixing if the chipset/driver supports it (i know
> > mine does).
> >
> > 2. OSS does not do any multiple sounds
>
> It should work. ALSA's OSS emulation supports mixing if the card has
> hardware mixing. It is only in the case of software mixing that OSS
> emulation cannot support multiple open.
>
> Sounds like a driver bug. What do the kernel warnings say?
>
> Lee
these are the kernel warnings
[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2006-06-06 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 19:57 OSS/ALSA issue Alien
2006-06-06 20:37 ` Lee Revell
2006-06-06 21:29 ` Alien [this message]
2006-06-06 21:31 ` Lee Revell
[not found] ` <200606062332.55293.alien999999999@users.sourceforge.net>
2006-06-06 21:40 ` Lee Revell
2006-06-07 6:56 ` Alien
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=200606062329.09662.alien999999999@users.sourceforge.net \
--to=alien999999999@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/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