From: Mark Brown <broonie@sirena.org.uk>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: alsa-devel@alsa-project.org, Oliver Ford <ipaqlinux@oliford.co.uk>
Subject: Re: Problem setting mixer switch with amixer/alsactl.
Date: Fri, 24 Oct 2008 18:25:34 +0100 [thread overview]
Message-ID: <20081024172533.GA3328@sirena.org.uk> (raw)
In-Reply-To: <87mygvmci7.fsf@free.fr>
On Thu, Oct 23, 2008 at 07:45:20PM +0200, Robert Jarzmik wrote:
> Mark Brown <broonie@sirena.org.uk> writes:
> > This is normal - shouldn't be an issue except in UI terms, ALSA limits
> > the length of names.
> Mark, I don't think that's true.
> I had that problem several monthes ago (remember my patch about alsa controls
> length ?).
> Do you remember that patch, which went into asoc-v2 ? :
All this patch does is change the limit, there is still a limit on the
length of control names in ALSA but as I say it's purely a cosmetic issue.
next prev parent reply other threads:[~2008-10-24 17:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 18:47 Problem setting mixer switch with amixer/alsactl Oliver Ford
2008-10-22 20:57 ` Mark Brown
2008-10-22 22:56 ` Oliver Ford
2008-10-23 14:00 ` Mark Brown
2008-10-23 14:07 ` Oliver Ford
2008-10-23 22:55 ` Oliver Ford
2008-10-27 20:44 ` Mark Brown
[not found] ` <4900F6D2.6030305@oliford.co.uk>
2008-10-23 23:54 ` Mark Brown
2008-10-24 17:26 ` Mark Brown
2008-10-23 13:27 ` Mark Brown
2008-10-23 13:56 ` Oliver Ford
2008-10-23 14:01 ` Mark Brown
2008-10-23 17:45 ` Robert Jarzmik
2008-10-24 17:25 ` Mark Brown [this message]
2008-10-24 19:09 ` Robert Jarzmik
2008-10-24 20:32 ` Mark Brown
2008-10-28 13:10 ` Mark Brown
2008-10-28 15:34 ` Mark Brown
2008-10-28 15:41 ` Takashi Iwai
2008-10-28 15:48 ` Mark Brown
2008-10-28 15:54 ` Takashi Iwai
2008-10-28 21:51 ` Oliver Ford
2008-10-29 14:53 ` Mark Brown
2008-10-29 16:04 ` Mark Brown
2008-10-30 11:40 ` Mark Brown
2008-10-30 17:47 ` Oliver Ford
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=20081024172533.GA3328@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ipaqlinux@oliford.co.uk \
--cc=robert.jarzmik@free.fr \
/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