public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] more encoder stuff
Date: Fri, 26 Nov 2004 01:57:27 +0100	[thread overview]
Message-ID: <41A67F77.3040501@dark-reality.de> (raw)
In-Reply-To: <1101429888.6465.47.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel Holtmann wrote:
| Hi Lars,
|
|
|>| we can optimize at any time if needed, because the SBC API should hide
|>| this stuff. For me this sounds perfect for a diploma thesis for someone
|>| interested in audio codec stuff and Bluetooth.
|>
|>*raising hand*
|>
|>thing is, on modern CPU you won't get much speedup with fixed point
|>stuff, because the main advantage was eliminated by Intel when they
|>build the pseudo-pipes into their FPU's.
|>But of course there are still some cycles to kill in audio processing
|>always. I'll advertise this project to my professor...
|
|
| a non floating point version is interesting for embedded platforms

good argument

| and
| not all desktops are running with a 3 GHz processor. I think what the
| MAD library does is very good and their MP3 decoding is fast.

Depending on the purpose of the calculations fixed point calculations
add an overhead that can - in some situations - eat up the speed gain
compared to true fpu.

But as you said, not all systems run on CPU/FPU combinations with the
specs of a modern desktop computer, and in fact this is important for
bluetooth stuff as many portable devices also use linux nowadays.

So I think we both have a point, but yours matches the BlueZ situation
much better than mine :)

Not used to it. Strange enough, as I program for PalmOS quite a lot...

cu,
~  Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBpn93QWC6DTWkDAoRAhETAJ9dthtjsNEM0Acxt3GSDVmzg8g/kACgg644
eNFC/R0TmjKb9hKu0Y5fR00=
=2HW2
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-11-26  0:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  5:02 [Bluez-devel] more encoder stuff Brad Midgley
2004-11-25  6:02 ` Marcel Holtmann
2004-11-25  6:14 ` Henryk Plötz
2004-11-25  6:51   ` Marcel Holtmann
2004-11-25 14:35     ` Lars Grunewaldt
2004-11-25 23:06     ` Henryk Plötz
2004-11-25 23:23       ` Marcel Holtmann
2004-11-26  0:14         ` Lars Grunewaldt
2004-11-26  0:44           ` Marcel Holtmann
2004-11-26  0:57             ` Lars Grunewaldt [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=41A67F77.3040501@dark-reality.de \
    --to=lgw@dark-reality.de \
    --cc=bluez-devel@lists.sourceforge.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