public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark_H_Johnson@raytheon.com
Cc: Andrew Morton <akpm@osdl.org>,
	alsa-devel@alsa-project.org, Adrian Bunk <bunk@stusta.de>,
	lkml <linux-kernel@vger.kernel.org>,
	perex@suse.cz
Subject: Re: [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n
Date: Wed, 05 Jan 2005 17:49:17 +0100	[thread overview]
Message-ID: <s5hhdlvyg6q.wl@alsa2.suse.de> (raw)
In-Reply-To: <OFB0B3CD59.F6AC2867-ON86256F80.004CECD3@raytheon.com>

At Wed, 5 Jan 2005 08:21:20 -0600,
Mark_H_Johnson@raytheon.com wrote:
> 
> > At Tue, 4 Jan 2005 13:25:40 -0600,
> > Mark_H_Johnson@raytheon.com wrote:
> > > [snip - how to get to the problem]
> > > At this point, I get the window asking if I heard the sound (I did
> not). If
> > > I repeat the test after waiting a short period, it eventually succeeds.
> >
> > The default blocking behavior of OSS devices was changed recently.
> > When the device is in use, open returns -EBUSY immediately in the
> > latest version while it was blocked until released in the former
> > version.
> I suppose there was a "good reason" for changing the user level
> interface in this way. Could you [or someone else] explain that and
> if you would consider changing it back (to stop breaking old applications)?

It was discussed on alsa-devel in November.  Unfortunately, I can't
find ML archive any longer...

The blocking behavior of OSS is a feature which is nowehre defined.
Some OSS drivers open in the blocking mode and some don't.
So, apps shouldn't depend on this feature.

We had implemented OSS emulation in the blocking manner since we
intepreted the POSIX definition in that way.  But Linus pointed out
that it's a misreading.

BTW, you can enable the blocking mode again via module/boot option.
See OSS-Emulation.txt.


> > > [2] When running latencytest (from
> > > http://www.gardena.net/benno/linux/audio/) the sound is not consistent
> > > (like it was on 2.4 with OSS) and occasionally I hear "rapid playback"
> > > where the repeating audio pattern is much faster than it should be.
> >
> > It's hard to tell.  The cause could be in the general interrupt
> > handling, the difference of HZ, the driver's interrupt setting, or
> > whatever.  This must depend on the hardware, anyway.
> Well, to a certain extent, I agree but let me repeat the symptoms
> I am seeing [repeated below]

Please provide the hardware details (I don't see your original post to
lkml).  Otherwise it'll be a vapor discusson...


Takashi

  parent reply	other threads:[~2005-01-05 17:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 14:21 [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n Mark_H_Johnson
2005-01-05 14:56 ` Alan Cox
2005-01-05 17:23   ` Lee Revell
2005-01-05 16:49 ` Takashi Iwai [this message]
2005-01-05 18:04   ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-01-07 14:41 Mark_H_Johnson
2005-01-05 18:15 Mark_H_Johnson
2005-01-04 19:25 Mark_H_Johnson
2005-01-05 13:41 ` [Alsa-devel] " Takashi Iwai
2005-01-05 21:27   ` Andrew Morton
2005-01-05 21:43     ` Lee Revell
2005-01-06 16:30     ` Alan Cox

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=s5hhdlvyg6q.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Mark_H_Johnson@raytheon.com \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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