From: Clemens Ladisch <clemens@ladisch.de>
To: Brent Weatherall <brentweatherall@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Possible message repeat
Date: Mon, 25 Jun 2012 11:49:12 +0200 [thread overview]
Message-ID: <4FE83418.7090401@ladisch.de> (raw)
In-Reply-To: <CAAo96ZA3=A2cxTPR5Yegoaru88fKAJx277kdSqS+i9vJ8JA=tg@mail.gmail.com>
Brent Weatherall wrote:
> our goal is to specify a special XU that WOULD require vendors
> supporting it to modify their firmware. We fully expect a vendor to
> modify their firmware to support our specification. That being said,
> is there a simple way to use ALSA to communicate with a vendor
> specific XU as long as the software understands the XU? For example,
> in the video4linux2 world, we can specify a UVC XU with a set of
> controls for special processing, then vendors that want to support it
> modify their firmware to support it. Then anyone can use our custom
> user-space drivers to easily talk to the video device. V4L2 has
> controls made for using XUs in this manner.
The audio class specification does not define any mechanism for a device
to specify what those controls would be. And because nobody has ever
needed to use XUs so far, the current ALSA driver has no other way to
create such controls.
If you insist on not changing ALSA, you must bypass it.
Regards,
Clemens
next parent reply other threads:[~2012-06-25 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAo96ZA3=A2cxTPR5Yegoaru88fKAJx277kdSqS+i9vJ8JA=tg@mail.gmail.com>
2012-06-25 9:49 ` Clemens Ladisch [this message]
2012-06-25 15:02 ` Possible message repeat Brent Weatherall
2012-06-13 14:13 Brent Weatherall
2012-06-13 14:48 ` Clemens Ladisch
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=4FE83418.7090401@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=brentweatherall@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.