From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Elimination of pow() in SBC code
Date: Sun, 28 Nov 2004 13:15:00 +0100 [thread overview]
Message-ID: <1101644100.18467.47.camel@pegasus> (raw)
In-Reply-To: <20041128025750.00e11da4.henryk@ploetzli.ch>
Hi Henryk,
> > the pow() function is the only reason for linking with -lm and it is
> > only used in one place with a limit range of parameters.
>
> Oh yes, that occurence of pow(2.0, x) is in older code I forgot about.
> (And before -lm was necessary for cos(), too)
>
> > So what is the range of scale_factor[ch][sb]. From a quick testing a
> > saw that it ranges from 0 - 15. Is this always true?
>
> Yes, scale_factor is a 4 bit integer (Table 12.13 of A2DP) and there
> should be no way of getting it bigger. If there was this would be a bug.
>
> > If yes, then I would use a pre-calculated array for 2^x.
>
> Isn't 1<<x good enough for that?
stupid me. Of course power of two is done by bitshifting. I committed
the following to the CVS:
2 << frame->scale_factor[ch][sb]
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-28 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 23:51 [Bluez-devel] Elimination of pow() in SBC code Marcel Holtmann
2004-11-28 1:57 ` Henryk Plötz
2004-11-28 12:15 ` Marcel Holtmann [this message]
2004-11-28 2:38 ` Brad Midgley
2004-11-28 13:32 ` Marcel Holtmann
2004-11-28 15:57 ` Brad Midgley
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=1101644100.18467.47.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.