From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Sbc encode optimization
Date: Thu, 26 Jun 2008 08:26:03 -0600 [thread overview]
Message-ID: <d89ddf300806260726w7582e5b4lba29322f5ea2b9cd@mail.gmail.com> (raw)
In-Reply-To: <a1c657a80806252303p2563497fs70b548dbbe4f3388@mail.gmail.com>
Paul
> I see "There are a couple of optimizations the codec could see but it
> performs reasonably on 200MHz+ devices. " on the wiki.bluez.org site.
> Would you tell me how to optimise the sbc encode for arm926ejs? Thanks.
The input data is copied a couple of times inside the encoder. It
would be faster if it was not being copied.
There are places, like the precomputed tables, that could be
represented in 16 bits. There was no advantage to doing this on the TI
arm chip but it might be a different result for other chips.
--
Brad
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-06-26 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 6:03 [Bluez-users] Sbc encode optimization salyer
2008-06-26 13:22 ` [Bluez-devel] adding PDU and debbugging sdp daemon Carlo Giuseppe Monaco
2008-06-26 13:27 ` Carlo Giuseppe Monaco
2008-06-26 14:26 ` Brad Midgley [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=d89ddf300806260726w7582e5b4lba29322f5ea2b9cd@mail.gmail.com \
--to=bmidgley@gmail.com \
--cc=bluez-users@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