diff options
| author | Clemens Ladisch <[email protected]> | 2010-05-21 09:15:59 +0200 |
|---|---|---|
| committer | Takashi Iwai <[email protected]> | 2010-05-21 16:33:34 +0200 |
| commit | ead4046b2fdfd69acc4272e693afd249ad3eb689 (patch) | |
| tree | 9dbc91adb9f4c654f6b9eaa245422162f12e8e47 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | 7f06a8b26aba1dc03b42272dc0089a800372c575 (diff) | |
ALSA: pcm: fix the fix of the runtime->boundary calculation
Commit 7910b4a1db63fefc3d291853d33c34c5b6352e8e in 2.6.34 changed the
runtime->boundary calculation to make this value a multiple of both the
buffer_size and the period_size, because the latter is assumed by the
runtime->hw_ptr_interrupt calculation.
However, due to the lack of a ioctl that could read the software
parameters before they are set, the kernel requires that alsa-lib
calculates the boundary value, too. The changed algorithm leads to
a different boundary value used by alsa-lib, which makes, e.g., mplayer
fail to play a 44.1 kHz file because the silence_size parameter is now
invalid; bug report:
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5015>.
This patch reverts the change to the boundary calculation, and instead
fixes the hw_ptr_interrupt calculation to be period-aligned regardless
of the boundary value.
Signed-off-by: Clemens Ladisch <[email protected]>
Cc: <[email protected]>
Signed-off-by: Takashi Iwai <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions