From: Felix Homann <linuxaudio@showlabor.de>
To: Daniel Mack <zonque@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Grant Diffey <gdiffey@gmail.com>
Subject: Re: A plea for help on mixer support for Fast Track Ultra (8R)
Date: Thu, 19 May 2011 14:23:04 +0200 [thread overview]
Message-ID: <4DD50BA8.4080003@showlabor.de> (raw)
In-Reply-To: <BANLkTi=OsrZKq3ZmC5cdFfuWb7qSOkPitw@mail.gmail.com>
Hi Daniel,
Am 19.05.2011 13:05, schrieb Daniel Mack:
> On Thu, May 19, 2011 at 10:52 AM, Daniel Mack<zonque@gmail.com> wrote:
>> I'll have a look later. I was just under the impression you wanted to
>> try yourself :)
> Attached is a patch which should show how this could work. It won't be
> fully functional though, as there seems to be some sort of confusion
> in your patch.
Thanks! I don't have the device here with me right now. I can try the
patch in an hour or two !
> You're calling build_named_mixer_unit_ctl() with your
> loop variable "in_ch", but you ignore that value in the called
> function. That can't be intentional, can it?
No, this isn't intentional. I wrote this in September, so I don't
remember completely. But a glimpse at the code reveals that this is
inherited from build_mixer_unit_ctl() which doesn't use the in_pin
parameter either.
Back then I wanted both functions to be as closely related as possible,
with the perspective to put them on a common base or let
build_mixer_unit_ctl() actually call build_named_mixer_unit_ctl(). Most
probably I later confused the in_pin parameter's (non-)meaning.
> Anyway, very little tweaking should be needed now to make this work,
> and if you send me back the modified patch, I'll split the work and
> post a patch set here.
I'll send all the needed corrections.
Regards,
Felix
next prev parent reply other threads:[~2011-05-19 12:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:19 A plea for help on mixer support for Fast Track Ultra (8R) Felix Homann
2011-05-18 15:29 ` Felix Homann
2011-05-18 17:51 ` Daniel Mack
2011-05-18 18:46 ` Felix Homann
2011-05-18 21:30 ` Daniel Mack
2011-05-19 0:51 ` Grant Diffey
2011-05-19 5:42 ` Takashi Iwai
2011-05-19 6:45 ` Felix Homann
2011-05-19 7:15 ` Clemens Ladisch
2011-05-19 7:24 ` Takashi Iwai
2011-05-19 8:14 ` Felix Homann
2011-05-19 8:52 ` Daniel Mack
2011-05-19 10:56 ` Felix Homann
2011-05-19 11:05 ` Daniel Mack
2011-05-19 12:23 ` Felix Homann [this message]
2011-05-19 13:36 ` Felix Homann
2011-05-19 13:42 ` Felix Homann
2011-05-19 14:12 ` Daniel Mack
2011-05-20 10:12 ` Felix Homann
2011-05-20 11:12 ` Daniel Mack
2011-05-20 11:14 ` Felix Homann
2011-05-20 11:37 ` Daniel Mack
2011-05-20 15:08 ` Grant Diffey
2011-05-20 15:43 ` Grant Diffey
2011-05-20 15:52 ` Felix Homann
2011-05-20 15:54 ` Daniel Mack
2011-05-20 16:25 ` Grant Diffey
2011-05-20 16:38 ` Daniel Mack
2011-05-20 16:44 ` Felix Homann
2011-05-20 16:52 ` Felix Homann
2011-05-24 10:11 ` Felix Homann
2011-05-24 10:47 ` Daniel Mack
2011-05-24 11:54 ` Takashi Iwai
2011-05-24 23:55 ` Grant Diffey
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=4DD50BA8.4080003@showlabor.de \
--to=linuxaudio@showlabor.de \
--cc=alsa-devel@alsa-project.org \
--cc=gdiffey@gmail.com \
--cc=tiwai@suse.de \
--cc=zonque@gmail.com \
/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.