Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 04/10] wavpack: new package
Date: Thu, 20 Jan 2011 13:19:10 +0100	[thread overview]
Message-ID: <87y66fbwe9.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1295369680-24816-5-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Tue, 18 Jan 2011 13:54:34 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

Hi,

 Gustavo> +++ b/package/multimedia/wavpack/Config.in
 Gustavo> @@ -0,0 +1,10 @@
 Gustavo> +config BR2_PACKAGE_WAVPACK
 Gustavo> +	bool "wavpack"
 Gustavo> +	help
 Gustavo> +	  WavPack is a completely open audio compression format providing
 Gustavo> +	  lossless, high-quality lossy, and a unique hybrid compression mode.
 Gustavo> +
 Gustavo> +	  Works on softfloat but it's not recommended since it uses
 Gustavo> +	  a big deal of CPU power.

CPUs without HW FPU are not necessarily low performance for integer
calculations. I don't know anything about wavpack, but from the
wikipedia page it seems like it doesn't use much FPU:

No floating-point arithmetic is used in WavPack's data path because,
according to the author, integer operations are less susceptible to
subtle chip-to-chip variations that could corrupt the lossless nature of
the compression (the Pentium floating point bug being an example). It is
possible that a lossless compressor that used floating-point math could
generate different output when running on that faulty Pentium. Even
disregarding actual bugs, floating-point math is complicated enough that
there could be subtle differences between "correct" implementations that
could cause trouble for this type of application.

So I would just drop this sentence.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2011-01-20 12:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 16:54 [Buildroot] [PATCH 00/10] Add mpd to buildroot Gustavo Zacarias
2011-01-18 16:54 ` [Buildroot] [PATCH 01/10] mpg123: install to staging Gustavo Zacarias
2011-01-19 22:52   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 02/10] libsndfile: bump to version 1.0.23 Gustavo Zacarias
2011-01-19 22:52   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 03/10] libmad: install pkgconfig file Gustavo Zacarias
2011-01-20  8:53   ` Peter Korsgaard
2011-01-20  8:56     ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 04/10] wavpack: new package Gustavo Zacarias
2011-01-20 12:13   ` Peter Korsgaard
2011-01-20 12:19   ` Peter Korsgaard [this message]
2011-01-20 13:15     ` Gustavo Zacarias
2011-01-18 16:54 ` [Buildroot] [PATCH 05/10] libsamplerate: " Gustavo Zacarias
2011-01-20 12:22   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 06/10] libcuefile: " Gustavo Zacarias
2011-01-20 12:46   ` Peter Korsgaard
2011-01-20 12:55     ` Gustavo Zacarias
2011-01-20 16:34       ` Bjørn Forsman
2011-01-20 20:19       ` Peter Korsgaard
2011-01-20 20:29   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 07/10] libreplaygain: " Gustavo Zacarias
2011-01-20 12:51   ` Peter Korsgaard
2011-01-20 12:52     ` Gustavo Zacarias
2011-01-20 14:15       ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 08/10] musepack: " Gustavo Zacarias
2011-01-20 20:32   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 09/10] faad2: " Gustavo Zacarias
2011-01-20 12:55   ` Peter Korsgaard
2011-01-18 16:54 ` [Buildroot] [PATCH 10/10] mpd: " Gustavo Zacarias
2011-01-18 18:29   ` Yoann Sculo
2011-01-20 13:07   ` Peter Korsgaard
2011-01-20 13:23     ` Gustavo Zacarias

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=87y66fbwe9.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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