From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Qais Yousef <qais.yousef@imgtec.com>, Takashi Iwai <tiwai@suse.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: alsa-lib support for compress offload
Date: Mon, 19 Jan 2015 16:07:50 -0600 [thread overview]
Message-ID: <54BD8036.5070405@linux.intel.com> (raw)
In-Reply-To: <54BD3D7F.6020105@imgtec.com>
On 1/19/15 11:23 AM, Qais Yousef wrote:
> On 01/16/2015 04:50 PM, Pierre-Louis Bossart wrote:
>>
>> Since there is no allowed processing/reformatting/reshuffling of
>> compressed data, all the plugin system needs to be bypassed and you'd
>> be looking at an alsa-lib API that interfaces directly with the
>> ioctls, essentially replicating what tinycompress does. I agree it's
>> not great to have independent packages, the decision to maintain
>> tinycompress separately was driven by licensing concerns, not
>> technical ones.
>> -Pierre
>>
>
> I'm not sure how dual licensing work. Is it ok to base alsa-lib support
> for compress API on tinycompress then?
no idea, and what is the objective really? it's not clear what you are
trying to achieve and what would be the merits of enhancing alsa-lib
with compressed audio support?
-Pierre
next prev parent reply other threads:[~2015-01-19 22:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:52 alsa-lib support for compress offload Qais Yousef
2015-01-16 10:34 ` Takashi Iwai
2015-01-16 11:22 ` Qais Yousef
2015-01-16 16:50 ` Pierre-Louis Bossart
2015-01-16 18:46 ` Mark Brown
2015-01-19 17:23 ` Qais Yousef
2015-01-19 22:07 ` Pierre-Louis Bossart [this message]
2015-01-20 7:21 ` Arun Raghavan
2015-01-20 9:53 ` Qais Yousef
2015-01-21 7:10 ` Vinod Koul
2015-01-21 9:22 ` Qais Yousef
2015-01-21 11:59 ` Takashi Iwai
2015-01-21 14:16 ` Qais Yousef
2015-01-22 21:56 ` Vinod Koul
2015-01-22 22:03 ` Pierre-Louis Bossart
2015-01-23 6:41 ` Takashi Iwai
2015-01-21 15:01 ` Pierre-Louis Bossart
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=54BD8036.5070405@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=qais.yousef@imgtec.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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).