On Wed, Aug 10, 2011 at 10:05 AM, Christian Robottom Reis
wrote:
> On Wed, Aug 10, 2011 at 09:18:04AM -0500, Tom Gall wrote:
>> On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack wrote:
>> > Does this involve adding easy/automatic benchmarks so we can track a)
>> > improvements turbo gives over plai
On Wed, Aug 10, 2011 at 09:18:04AM -0500, Tom Gall wrote:
> On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack wrote:
> > Does this involve adding easy/automatic benchmarks so we can track a)
> > improvements turbo gives over plain and b) improvements we do to turbo
> > over time? If not, I would ver
On Wed, Aug 10, 2011 at 4:18 PM, Tom Gall wrote:
> On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack wrote:
>> On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall wrote:
>>> Hi All,
>>>
>>> I thought I would clarify what is in store for the next few linaro
>>> cycles from a libjpeg-turbo perspective.
>>>
>>
On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack wrote:
> On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall wrote:
>> Hi All,
>>
>> I thought I would clarify what is in store for the next few linaro
>> cycles from a libjpeg-turbo perspective.
>>
>> 11.08
>> 1.1.2 libjpeg-turbo (featuring cleaned up patche
On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall wrote:
> Hi All,
>
> I thought I would clarify what is in store for the next few linaro
> cycles from a libjpeg-turbo perspective.
>
> 11.08
> 1.1.2 libjpeg-turbo (featuring cleaned up patches)
> upstreaming and support of what could be a late august upstr
Hi All,
I thought I would clarify what is in store for the next few linaro
cycles from a libjpeg-turbo perspective.
11.08
1.1.2 libjpeg-turbo (featuring cleaned up patches)
upstreaming and support of what could be a late august upstream 1.2 release
11.09
1.2 upstream based linaro release (presum
