All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Simon Dunn" <sdunn@mpc-data.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: softvol plug-in dependancies?
Date: Sat, 17 May 2008 11:53:39 +0100	[thread overview]
Message-ID: <op.ubaojrs7hpbl6d@derby> (raw)
In-Reply-To: <s5hbq36e2gs.wl%tiwai@suse.de>

> Which ALSA version, which driver and how is your configuration setup?
> The softvol itself is known to work in most cases, but of course,
> there could be remaining bugs.  But, I suspect it's rather specific to
> your use-case...
>

Hi Takashi,

Thanks for your reply.

The version of ALSA lib and utils I'm mainly using is 1.0.10, though I've
tried version 1.0.16 and get the same results.

The Linux kernel I'm using is version 2.6.10, which includes the ALSA
driver architecture version 1.0.6.

I'm running this on a freescale mcf5475, Coldfire based platform.

I've reverted to using the dummy driver and a very basic asound.conf file,
see below, but still no joy with the plug-in.

It's the output from running amixer, once the softvol control is enabled,
that I find most curious.  Listing its contents just seems to produce an
uninitialised device.  Given the big endian nature of the cpu I'm
suspicious that this may be an endian bug, though after spending a couple
of days examining the alsa-lib code I've failed to find anything wrong up
to now, obviously ;)

Has the softvol plug-in been used on a big endian system to your knowledge?

Running amixer shows the controls implemented in the Dummy driver perfectly
well, and these can be adjusted using amixer or alsamixer.

The DMIX plug-in works just fine so if it is a bug, endian or otherwise,
then it is probably limited to the softvol plug-in rather than alsa-lib in
general.

Any help or suggestions you can provide is greatly appreciated.

Regards
Simon

.
asound.conf
.

pcm.globalvol {
     type            softvol
     slave.pcm       "hw:0,0"
     control.name    "GLOBAL Vol"
     control.card    0
}


-- 

Simon Dunn, Software Engineer
MPC Data Limited
e-mail: sdunn@mpc-data.co.uk
web: www.mpc-data.co.uk
tel: +44 (0) 1225 710600
fax: +44 (0) 1225 710601
ddi: +44 (0) 1225 710631

MPC Data Limited is a company registered in England and Wales with company  
number 05507446
Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14  
7FJ
VAT no: 850625238

The information in this email and in the attached documents is  
confidential and may be legally privileged. Any unauthorized review,  
copying, disclosure or distribution is prohibited and may be unlawful. It  
is intended solely for the addressee. Access to this email by anyone else  
is unauthorized. If you are not the intended recipient, please contact the  
sender by reply email and destroy all copies of the original message. When  
addressed to our clients any opinions or advice contained in this email is  
subject to the terms and conditions expressed in the governing contract.

  reply	other threads:[~2008-05-17 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 19:59 softvol plug-in dependancies? Simon Dunn
2008-05-16 14:41 ` Takashi Iwai
2008-05-17 10:53   ` Simon Dunn [this message]
2008-05-23  8:24     ` softvol plug-in dependancies? - [SOLVED] Simon Dunn

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=op.ubaojrs7hpbl6d@derby \
    --to=sdunn@mpc-data.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.