From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] ladspa-sdk: new package
Date: Wed, 6 Aug 2014 09:59:59 +0200 [thread overview]
Message-ID: <20140806095959.7b634542@free-electrons.com> (raw)
In-Reply-To: <53E14394.2030309@barkynet.com>
Dear Martin Bark,
On Tue, 05 Aug 2014 21:50:28 +0100, Martin Bark wrote:
> > Sorry for the lack of feedback until now on these patches. See below
> > for a number of comments.
>
> That's fine, to be honest I forgot I submitted these patches :)
Yeah, it's been a while, but I'm trying to do some clean up of the
patch backlog.
> Originally I started this because I wanted an equaliser for some work i
> was doing with acoustic echo cancellation. alsaeqaul was a quick easy
> way to add a equaliser i could change real time. alsaequal needs caps
> which is an ladsp module hence the 3 patches.
Ok.
> I don't know if ladsp is under active development. Really it's just the
> definition of an API in a C header file so I think it's not meant to
> change. It's the packages like caps which implement the interface which
> i expect to be active.
Ok, makes sense. I was a bit worried about the lack of upstream
activity, but it is indeed just an API definition, so probably it
doesn't make sense for it to move very often.
> caps is self contained (it includes a copy of ladsp.h) and does not need
> this ladsp-sdk package, i added it for completeness.
Ah, ok.
> Is the lack of development activity an issue? I could drop ladsp-sdk if
> you like. Please let me know your thoughts.
Well, if it's not needed for caps, I'd say leave it aside for now.
And for both packages, if you do patches on them to make them work in
Buildroot, we generally prefer when some patches are submitted
upstream. So that one day, maybe, we can drop those patches when
upstream releases a new version.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-08-06 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 21:19 [Buildroot] [PATCH 1/3] ladspa-sdk: new package Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 2/3] caps: " Martin Bark
2014-08-04 20:28 ` Thomas Petazzoni
2014-08-05 20:51 ` Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 3/3] alsaequal: " Martin Bark
2014-08-04 20:32 ` Thomas Petazzoni
2014-08-05 20:52 ` Martin Bark
2014-08-06 8:00 ` Thomas Petazzoni
2014-08-04 20:23 ` [Buildroot] [PATCH 1/3] ladspa-sdk: " Thomas Petazzoni
2014-08-05 20:50 ` Martin Bark
2014-08-06 7:59 ` Thomas Petazzoni [this message]
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=20140806095959.7b634542@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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