From: Alien <alien999999999@users.sourceforge.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: OSS/ALSA issue
Date: Wed, 7 Jun 2006 08:56:44 +0200 [thread overview]
Message-ID: <200606070856.45040.alien999999999@users.sourceforge.net> (raw)
In-Reply-To: <1149630010.4072.81.camel@mindpipe>
BTW: i still have a spare au88x0 card... any devel want it?
I'd prefer it to be used to fix x86_64 issues with it.
mvg,
On Tuesday 06 June 2006 23:40, Lee Revell wrote:
> On Tue, 2006-06-06 at 23:32 +0200, Alien wrote:
> > 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
> >
> > forgot attachments
>
> It's a driver bug, please file a bug report if you can reproduce it with
> the latest ALSA sources from the Hg repository.
>
> Lee
--
Alien is my name and head-biting is my game
prev parent reply other threads:[~2006-06-07 6:56 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
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 [this message]
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=200606070856.45040.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