From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001225]: RMS hardware input and software plaback levels are incorrectly reported under 64 bit linux
Date: Sat, 2 Jul 2005 08:42:46 +0200 [thread overview]
Message-ID: <fb85270a929971e92d19d27ba5768df2@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1225>
======================================================================
Reported By: ckg
Assigned To: charbonnel
======================================================================
Project: ALSA - driver
Issue ID: 1225
Category: PCI - RME HDSP
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution:
Kernel Version: 2.6.11
======================================================================
Date Submitted: 07-01-2005 20:11 CEST
Last Modified: 07-02-2005 08:42 CEST
======================================================================
Summary: RMS hardware input and software plaback levels are
incorrectly reported under 64 bit linux
Description:
I'm using the PCI HDSP with a Multiface interface, Everything appears to
be correct with the audio, but the hdspmixer reports bogus valus for
hardware input and software playback RMS levels. The peak leavels are
correct. The problem happens when the driver is compiled into the kernel
and when it is a module.
I think the problem is caused because the rms regesters are positioned at
a 4 byte but not an 8 byte boundary on a 32 bit system, but on a 64 bit
system, they are movd back 4 bytes to an 8 byte alignment
======================================================================
----------------------------------------------------------------------
charbonnel - 07-02-05 08:42
----------------------------------------------------------------------
Hi,
It sounds similar to a bug in the byte swapping code that was fixed some
time ago.
(see ALSA BUG https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0000801)
Do you use the in-kernel alsa driver with 2.6.11 ? If so they may be a
little old.
What's the version reported by cat /proc/asound/version ?
I suspect your patch seems to fix the problem but introduces a one channel
offset in the metering values.
Thomas
Issue History
Date Modified Username Field Change
======================================================================
07-01-05 20:11 ckg New Issue
07-01-05 20:11 ckg File Added: hdsp.patch
07-01-05 20:11 ckg Kernel Version => 2.6.11
07-02-05 08:42 charbonnel Note Added: 0005352
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-02 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 6:42 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-03 8:30 [ALSA - driver 0001225]: RMS hardware input and software plaback levels are incorrectly reported under 64 bit linux bugtrack
2005-07-03 8:26 bugtrack
2005-07-03 3:22 bugtrack
2005-07-01 18:11 bugtrack
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=fb85270a929971e92d19d27ba5768df2@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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