Re: [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n

[Takashi Iwai]

At Wed, 5 Jan 2005 08:21:20 -0600,
Mark_H_Johnson@xxxxxxxxxxxx wrote:
> 
> > At Tue, 4 Jan 2005 13:25:40 -0600,
> > Mark_H_Johnson@xxxxxxxxxxxx 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/