From: maillist@superlative.org
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] Idea: dynamic loading of USB quirks
Date: Thu, 01 Nov 2012 21:20:46 +0000 [thread overview]
Message-ID: <1410076.LzJ0gmvzpA@kamdesktop> (raw)
In-Reply-To: <50923B65.4060304@gmail.com>
On Thursday 01 Nov 2012 10:05:41 Daniel Mack wrote:
> [cc lkml as this might be of broader interest]
>
>
> Then again, if a versatile and clean solution to this problem is found,
> there would be tons of other drivers in Linux to benefit from it, just
> think about the hda driver to begin with. But not only in the ALSA area.
>
I was initially thinking of the more trivial USB quirkes only, and having the
more complex quirks remain as hard coded.
But it does make sense that, if such a capability could be extended, that it
could be used for other drivers too.
Cheers,
Keith
next prev parent reply other threads:[~2012-11-01 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2390628.MpxcLPPhM0@kamdesktop>
2012-11-01 9:05 ` [alsa-devel] Idea: dynamic loading of USB quirks Daniel Mack
2012-11-01 21:20 ` maillist [this message]
2012-11-05 11:44 ` Takashi Iwai
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=1410076.LzJ0gmvzpA@kamdesktop \
--to=maillist@superlative.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--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