Subject: Re: [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with
	CONFIG_PM=n
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark_H_Johnson@raytheon.com
Cc: Takashi Iwai <tiwai@suse.de>, Andrew Morton <akpm@osdl.org>,
       alsa-devel@alsa-project.org, Adrian Bunk <bunk@stusta.de>,
       lkml <linux-kernel@vger.kernel.org>, perex@suse.cz
In-Reply-To: <OFB0B3CD59.F6AC2867-ON86256F80.004CECD3@raytheon.com>
References: <OFB0B3CD59.F6AC2867-ON86256F80.004CECD3@raytheon.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1104936968.24187.180.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Wed, 05 Jan 2005 14:56:09 +0000
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1142
Lines: 22

On Mer, 2005-01-05 at 14:21, Mark_H_Johnson@raytheon.com 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.
> 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)?
> Otherwise - is there some way (other than running lsmod and grep) to find
> out if the interface is busy and which application is using it?

OSS itself changed behaviour over time (2.2 to 2.4) ALSA has merely
caught up with the newer OSS behaviour and the new behaviour is correct.

If you want to find out if the interface is busy open it. If you want to
do it portably open it with O_NDELAY.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/