On 2014-11-20 13:55, Felipe Sateler wrote:
On Thu, Nov 20, 2014 at 8:30 AM, Sjoerd Simons wrote:
On Thu, 2014-11-20 at 11:58 +0100, David Henningsson wrote:
On 2014-11-20 08:40, Alexander E. Patrakov wrote:
20.11.2014 12:35, David Henningsson wrote:
Crossposting to Debian and upstream lis
On Thu, Nov 20, 2014 at 8:30 AM, Sjoerd Simons wrote:
> On Thu, 2014-11-20 at 11:58 +0100, David Henningsson wrote:
>>
>> On 2014-11-20 08:40, Alexander E. Patrakov wrote:
>> > 20.11.2014 12:35, David Henningsson wrote:
>> >> Crossposting to Debian and upstream lists.
>> >>
>> >> Apparently Debian
On Thu, 2014-11-20 at 11:58 +0100, David Henningsson wrote:
>
> On 2014-11-20 08:40, Alexander E. Patrakov wrote:
> > 20.11.2014 12:35, David Henningsson wrote:
> >> Crossposting to Debian and upstream lists.
> >>
> >> Apparently Debian has a patch that uses fixed point by default on armhf,
> >> s
20.11.2014 15:58, David Henningsson wrote:
On 2014-11-20 08:40, Alexander E. Patrakov wrote:
20.11.2014 12:35, David Henningsson wrote:
Crossposting to Debian and upstream lists.
Apparently Debian has a patch that uses fixed point by default on armhf,
so I'm just echoing Luke's question here
On 2014-11-20 08:40, Alexander E. Patrakov wrote:
20.11.2014 12:35, David Henningsson wrote:
Crossposting to Debian and upstream lists.
Apparently Debian has a patch that uses fixed point by default on armhf,
so I'm just echoing Luke's question here: Has anybody performed any
testing or bench
On Thu, 2014-11-20 at 08:35 +0100, David Henningsson wrote:
> Crossposting to Debian and upstream lists.
>
> Apparently Debian has a patch that uss16 speex-fixed-3 587738 604034 874023
> 421630 543090
es fixed point by default on armhf,
> so I'm just echoing Luke's question here: Has anybody per
20.11.2014 12:35, David Henningsson wrote:
Crossposting to Debian and upstream lists.
Apparently Debian has a patch that uses fixed point by default on armhf,
so I'm just echoing Luke's question here: Has anybody performed any
testing or benchmarks across armhf hardware, w r t fixed point vs
flo
Crossposting to Debian and upstream lists.
Apparently Debian has a patch that uses fixed point by default on armhf,
so I'm just echoing Luke's question here: Has anybody performed any
testing or benchmarks across armhf hardware, w r t fixed point vs
floating point resampling with speex and Pul