Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 3 Jul 2005 10:30:25 +0200	[thread overview]
Message-ID: <2fbbde67cbfffadbb109a38869960a59@bugtrack.alsa-project.org> (raw)


The following issue has been RESOLVED.
======================================================================
<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:                     resolved
Distribution:               
Kernel Version:             2.6.11
Resolution:                 fixed
Fixed in Version:           1.0.9
======================================================================
Date Submitted:             07-01-2005 20:11 CEST
Last Modified:              07-03-2005 10:30 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-03-05 10:26 
----------------------------------------------------------------------
"While debuggin my guess was that running 64-bits caused the port space to
be positioned at an 8 byte boundary"

The values you're modifying are offsets in the iomapped card memory. They
are correct wherever the memory is mapped. This has nothing to do with the
platform.

What's happening is that you're mixing data belonging to different
channels. On those 8 bytes values, you get the most significant ones right
(somehow compensating for the bug in the alsa version you're using) but
the least significant have a one channels offset. For channel one, what
you're reading for the least significant bytes is undefined. So it looks
right, but you're loosing precision. I invite you to do some tests
generating sine waves with pure-data at a given level, and comparing the
values read by the card and those calculated by Fons' excellent JAAA. I
also invite you to upgrade to the latest alsa version...

Thomas

----------------------------------------------------------------------
 charbonnel - 07-03-05 10:30 
----------------------------------------------------------------------
This is the same bug as ALSA BUG
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0000801 and has been
fixed in alsa 1.0.9

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                          
07-03-05 05:22 ckg            Note Added: 0005369                          
07-03-05 10:26 charbonnel     Note Added: 0005371                          
07-03-05 10:30 charbonnel     Status                   assigned => resolved
07-03-05 10:30 charbonnel     Fixed in Version          => 1.0.9           
07-03-05 10:30 charbonnel     Resolution               open => fixed       
07-03-05 10:30 charbonnel     Note Added: 0005372                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-07-03  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03  8:30 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-03  8:26 [ALSA - driver 0001225]: RMS hardware input and software plaback levels are incorrectly reported under 64 bit linux bugtrack
2005-07-03  3:22 bugtrack
2005-07-02  6:42 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=2fbbde67cbfffadbb109a38869960a59@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