From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] package/spandsp: new package
Date: Fri, 12 Oct 2018 18:56:02 +0200 [thread overview]
Message-ID: <20181012165602.GC31509@scaer> (raw)
In-Reply-To: <20181009151421.396cb25a@windsurf>
Thomas, All,
On 2018-10-09 15:14 +0200, Thomas Petazzoni spake thusly:
> On Wed, 3 Oct 2018 15:13:57 +0200, Bernd Kuhls wrote:
> > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >
> > [Bernd:
> > - bumped version to 20180108
> > - removed 0001-fix-msse4.x.patch, applied upstream
> > - removed autoreconf after patch removal
> > - added license hash (Arnout)
> > - added SPDX license codes (Arnout)]
> >
> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> > ---
> > package/Config.in | 1 +
> > package/spandsp/Config.in | 9 +++++++++
> > package/spandsp/spandsp.hash | 3 +++
> > package/spandsp/spandsp.mk | 27 +++++++++++++++++++++++++++
> > 4 files changed, 40 insertions(+)
> > create mode 100644 package/spandsp/Config.in
> > create mode 100644 package/spandsp/spandsp.hash
> > create mode 100644 package/spandsp/spandsp.mk
>
> I am wondering why a signal processing library for telephony needs the
> TIFF library, but OK, it seems to be the case.
Because it is more than a simple 'DSP' library: it specialises in
telephony DSP, including FAX generation/recognition.
So, you give it a tiff file, and it generates the sounds to send on the
line. Conversely, when receiving a FAX, you feed it the sound from the
line, and it generates a tiff file. More or less... ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-10-12 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 13:13 [Buildroot] [PATCH 1/4] package/asterisk: bump version to 14.7.8 Bernd Kuhls
2018-10-03 13:13 ` [Buildroot] [PATCH 2/4] package/asterisk: enable for non-glibc toolchains Bernd Kuhls
2018-10-08 17:19 ` Arnout Vandecappelle
2018-10-08 19:45 ` Yann E. MORIN
2018-10-09 13:09 ` Thomas Petazzoni
2018-10-03 13:13 ` [Buildroot] [PATCH 3/4] package/spandsp: new package Bernd Kuhls
2018-10-09 13:14 ` Thomas Petazzoni
2018-10-12 16:56 ` Yann E. MORIN [this message]
2018-10-03 13:13 ` [Buildroot] [PATCH 4/4] package/asterisk: add optional spandsp support Bernd Kuhls
2018-10-09 13:14 ` Thomas Petazzoni
2018-10-09 13:08 ` [Buildroot] [PATCH 1/4] package/asterisk: bump version to 14.7.8 Thomas Petazzoni
2018-12-23 21:33 ` Peter Korsgaard
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=20181012165602.GC31509@scaer \
--to=yann.morin.1998@free.fr \
--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