From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Mark_H_Johnson@raytheon.com, bunk@stusta.de,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <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: Thu, 06 Jan 2005 16:30:27 +0000 [thread overview]
Message-ID: <1105024104.24896.219.camel@localhost.localdomain> (raw)
In-Reply-To: <20050105132711.70f74ecc.akpm@osdl.org>
On Mer, 2005-01-05 at 21:27, Andrew Morton wrote:
> Takashi Iwai <tiwai@suse.de> wrote:
> >
> > 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.
> >
>
> whoa. That's a significant change in user-visible behaviour. Why was this
> done?
It now emulates the later OSS PCI and other devices not 2.2 OSS. As such
its the right thing to have done for emulation of OSS IMHO. It also
works with more apps several of which hang on opening /dev/dsp0
expecting OSS -EBUSY responses.
next prev parent reply other threads:[~2005-01-06 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 19:25 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n 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-05 21:43 ` Lee Revell
2005-01-06 16:30 ` Alan Cox [this message]
2005-01-06 16:30 ` Alan Cox
2005-01-05 21:27 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 14:21 [Alsa-devel] " Mark_H_Johnson
2005-01-05 14:56 ` Alan Cox
2005-01-05 17:23 ` Lee Revell
2005-01-05 16:49 ` Takashi Iwai
2005-01-05 18:04 ` Lee Revell
2005-01-05 18:15 Mark_H_Johnson
2005-01-07 14:41 Mark_H_Johnson
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=1105024104.24896.219.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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 \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.