From: Clemens Ladisch <clemens@ladisch.de>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Grant Diffey <gdiffey@gmail.com>,
Daniel Mack <zonque@gmail.com>
Subject: Re: A plea for help on mixer support for Fast Track Ultra (8R)
Date: Thu, 19 May 2011 09:15:22 +0200 [thread overview]
Message-ID: <4DD4C38A.2070209@ladisch.de> (raw)
In-Reply-To: <4DD4BC97.5090702@showlabor.de>
Felix Homann wrote:
> Am 19.05.2011 07:42, schrieb Takashi Iwai:
> > I see no big reason to make things more complex. If you want to avoid
> > the standard audio parsing after quirk but only parse mixer, just call
> > snd_usb_create_mixer() in your quirk function.
>
> Maybe I'm misunderstanding your point. But I think your suggestion is
> making things more complex.
>
> I don't want to avoid the standard audio parsing. I want to use standard
> quirks if possible and still would like a means to call
> snd_usb_create_mixer(). That's all.
The quirks-table.h framework handles only quirks that attach to a USB
interface. So create a FTU mixer quirk for intf 0 (or a generic quirk
with a separate table of mixer controls).
> Moreover, I can't believe that the Fast Track Ultra devices are the only
> ones in the world which have a standard USB mixer without exposing it
> through the descriptors.
So far, they are the only ones where somebody bothered to find out what
the controls are.
(Many vendor-specific controls don't implement the complex class-
compliant mixer protocol.)
> I knew it wasn't ready for submission. After generating the patch I send
> I had already corrected the whitespaces and those lines with over 80
> characters that weren't just copies from other locations. The remaining
> issues like "! cval" and "ERROR: do not use assignment in if condition"
> were all taken literally from other locations inside the respective
> files.
"Do as I say, not as I do." ;-)
Regards,
Clemens
next prev parent reply other threads:[~2011-05-19 7:13 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 [this message]
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
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=4DD4C38A.2070209@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=gdiffey@gmail.com \
--cc=linuxaudio@showlabor.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).