Displaying 4 results from an estimated 4 matches for "_bfin".
Did you mean:
bfin
2006 May 16
1
new assembler port
...ask about guidelines for assembly optimization, and if you do some
> searching, you will find some tips from Jean-Marc on where to start. Also,
> if you look in the source tree for references to Blackfin or bfin, you will
> find an example port done by Jean-Marc.
Yes, have a look at the _bfin.h, _sse.h and _arm.h files to get an idea of
what's useful. Also, note that most calls to *_mem2() functions have been (and
are being) converted to the _mem16() version.
> You should make sure that you run the latest code from Subversion, which has
> some speed improvements from 1.1.12....
2006 May 16
2
new assembler port
Hello,
I'm trying to use speex for implementing a VoIP demo application using
linphone
on an embedded system. At the moment I'm not really able to do real time
encoding,
and thinking about making an assembler port for speex to the AVR32
architecture.
The AVR32 is a new hybrid MCU/DSP fixed point processor running at
120Mhz in
my application.
Does anyone have experiences/info about the
2005 Aug 15
2
Updated MIPs and memory requirements for TI c54x or c55 DSPs
Hi,
I can see that there has been some effort to compile the SPEEX codec to
operate on the TI c54x and c55x DSPs and I am wondering if anyone would
be able to update the mailing list with their current MIPs and Memory
resource requirements for their c54x and/or c55x compilation? The only
estimate I was able to find in the mailing list archive was 42MIPs but
I'm not sure if this is an
2005 Aug 17
2
Updated MIPs and memory requirements for TI c54x or c55DSPs
...39;s not done already).
This (very) slightly reduces quality, but means you convert a lot of
"emulated" 16x32 multiplications into 16x16. There are also several
routines that would benefit from platform-specific optimizations. There
are already optimizations for ARM (*_arm4.h), Blackfin (*_bfin.h) and
SSE (*_sse.h), so you can see what functions are worth optimizing.
For a DSP, there are also two specific things I would watch. First,
there is at least one CPU-intensive place (inner_prod) where I have to
use many shifts in a loop to prevent overflows, but those could be
replaced by a sin...