Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Qais Yousef <qais.yousef@imgtec.com>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [ALSA-UTILS][PATCH] Add support for cplay and crecord
Date: Thu, 5 Mar 2015 12:30:18 +0530	[thread overview]
Message-ID: <20150305070018.GW2613@intel.com> (raw)
In-Reply-To: <54F73421.3000108@imgtec.com>

On Wed, Mar 04, 2015 at 04:34:41PM +0000, Qais Yousef wrote:
> On 03/04/2015 04:10 PM, Vinod Koul wrote:
> >On Wed, Mar 04, 2015 at 03:36:00PM +0000, Qais Yousef wrote:
> >>cplay and crecord use compress offload API to play and record compressed audio.
> >>
> >>They're based on cplay and crec from tinycompress library using LGPL license.
> >>
> >>For now cplay only supports playing mp3 files.
> >>
> >>Signed-off-by: Qais Yousef <qais.yousef@imgtec.com>
> >>Cc: Takashi Iwai <tiwai@suse.de>
> >>Cc: Vinod Koul <vinod.koul@intel.com>
> >>Cc: Mark Brown <broonie@kernel.org>
> >>---
> >>I renamed crec to crecord also to match aplay and arecord, hopefully
> >>you don't mind Vinod.
> >No thats fine..
> >
> >>This patch is dependent on my other patch that adds support for compress offload
> >>to alsa-lib.
> >And where is that, should have preceded this
> 
> Hmm not sure what went wrong. I resent it. Seems I have some emailer
> issues as I had this problem before.
> Hopefully you received it now.
> 
> >>I needed to include <sound/compress_params.h> in cplay.c and crec.c
> >>but I couldn't find an example of any C file which directly includes <sound/*.h>
> >>The norm seems to be to just include <alsa/asoundlib.h>. Do I need to
> >>redefine structs from <sound/compress_params.h> to newly added <alsa/compress.h>?
> >><alsa/pcm.h> seems to redefine structs from <sound/asound.h>.
> >These are kernel headers and should be in your include path if you have
> >those installed
> >>I could only test cplay but have no means to test crecord at the moment.
> >>
> >>  Makefile.am       |   3 +
> >>  configure.ac      |   6 +-
> >>  cplay/Makefile.am |  14 ++
> >>  cplay/cplay.c     | 294 +++++++++++++++++++++++++++++++++++
> >>  cplay/crec.c      | 449 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>  cplay/tinymp3.h   |  72 +++++++++
> >>  6 files changed, 837 insertions(+), 1 deletion(-)
> >>  create mode 100644 cplay/Makefile.am
> >>  create mode 100644 cplay/cplay.c
> >>  create mode 100644 cplay/crec.c
> >>  create mode 100644 cplay/tinymp3.h
> >Okay here is where we need discussion on the future course. If we do this
> >then we end up in two code bases, something I would not encourage!
> >
> >On the other hand if we add the make file changes to tinycompress or if
> >required split this into two, lib and tools and then package lib part into
> >alsa-lib and players into tools, that way we can have single code base. That
> >was my intent behind ensuring that this is dual licensed.
> 
> I'm not sure I follow you completely here. You mean keep cplay and
> crec in tinycompress with the dual licensing but only merge the lib
> part (which my other patch does) into alsa-lib? For me having this
> lib part into alsa-lib is the important bit. Moving crec and cplay
> to alsa-utils was something I thought would be useful but maybe not.
Not that

Since alsa splits lib and tools, in order to take this into alsa-libs we
need to split tinycompress, to something like lib and tool part.

Then alsa-lib can import the lib part of tinycompress. Please note I am not
saying we should copy or move code into alsa-lib.
The reason for that is
1. copying code will cause more maintaince of same code in two places :(
2. moving into alsa-lib is not an option as existing users like android will
suffer as they dont use alsa-lib

So I think, while building and packaging alsa-library and tools we can
import the tinycompress using LGPL license and use that to give complete
library on Linux to users

Takashi, can we get you blessing for this approach before we embark on this,
or any other better ideas?

-- 
~Vinod

  reply	other threads:[~2015-03-05  7:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 15:36 [ALSA-UTILS][PATCH] Add support for cplay and crecord Qais Yousef
2015-03-04 16:10 ` Vinod Koul
2015-03-04 16:21   ` Takashi Iwai
2015-03-04 16:34   ` Qais Yousef
2015-03-05  7:00     ` Vinod Koul [this message]
2015-03-05  7:43       ` Jaroslav Kysela
2015-03-05  8:30         ` Vinod Koul
2015-03-05  8:52           ` Takashi Iwai
2015-03-05 12:37             ` Qais Yousef
2015-03-05 13:39               ` Jaroslav Kysela
2015-03-05 13:45                 ` snd-aloop not working in linux-3.12.10 Srinivasan S
2015-03-05 14:13                   ` Jaroslav Kysela
2015-03-05 16:42                     ` Srinivasan S
2015-03-05 18:51                       ` Jaroslav Kysela
2015-03-06 10:35                         ` Srinivasan S
2015-03-06 10:58                           ` Takashi Iwai
2015-03-06 11:28                           ` Jaroslav Kysela
2015-03-06 17:43                             ` Srinivasan S
2015-03-09  5:09                               ` Srinivasan S
2015-06-03  6:10                                 ` Srinivasan S

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=20150305070018.GW2613@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=qais.yousef@imgtec.com \
    --cc=tiwai@suse.de \
    /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