Hi Peter, Arun, On Fri, Jul 20, 2012 at 12:43 PM, Peter Meerwald <pmeerw at pmeerw.net> wrote: > Hello, > >> > allow to disable SIMD optimizations with PULSE_NO_SIMD; >> > to give a consistent meaning to that environment variable > >> The SBC code is pulled straight from the BlueZ code, so it's nicer to >> not change that code downstream. If the BlueZ folks would be amenable to >> taking something like this upstream (say BLUEZ_NO_SIMD), we could pull >> then setenv() that early in PA init if PULSE_NO_SIMD is set). >> >> I know it's a bit of a circuitous route to making changes, but this >> split keeps things cleaner/more central. > > I understand your concern; my motivation was to provide a consistent > behaviour of PULSE_NO_SIMD > > not sure if the effort to go upstream is worth it, another env var is > probably not desirable there We are going to have a proper shared library for sbc, we just trying to figure out how to keep the history. -- Luiz Augusto von Dentz
