On Thu, Jan 21, 2016 at 8:38 AM, NGie Cooper wrote:
...
> I would talk to cem@. He's working on ioat(4) on head for us ($work).
I misunderstood the terms a bit. IoT (Internet of Things) != iaot(4) (
Intel I/O Acceleration Technology ).
Thanks,
-NGie
___
2016-01-21 17:38 GMT+01:00 NGie Cooper :
>
> > On Jan 21, 2016, at 08:34, Jan Bramkamp wrote:
> >
> >> On 21/01/16 17:19, Mathieu Prevot wrote:
> >> Dear all,
> >>
> >> I would like to connect several connected object (with homogeneous or
> >> heterogenous hardare: intel edison, samsung artik, a
2016-01-21 17:38 GMT+01:00 NGie Cooper :
>
> > On Jan 21, 2016, at 08:34, Jan Bramkamp wrote:
> >
> >> On 21/01/16 17:19, Mathieu Prevot wrote:
> >> Dear all,
> >>
> >> I would like to connect several connected object (with homogeneous or
> >> heterogenous hardare: intel edison, samsung artik, a
> On Jan 21, 2016, at 08:34, Jan Bramkamp wrote:
>
>> On 21/01/16 17:19, Mathieu Prevot wrote:
>> Dear all,
>>
>> I would like to connect several connected object (with homogeneous or
>> heterogenous hardare: intel edison, samsung artik, apple AX, intel core,
>> etc) so the calculation needs,
On 21/01/16 17:19, Mathieu Prevot wrote:
Dear all,
I would like to connect several connected object (with homogeneous or
heterogenous hardare: intel edison, samsung artik, apple AX, intel core,
etc) so the calculation needs, the storage/memory, the connection, etc are
decoupled; hence we can re
Dear all,
I would like to connect several connected object (with homogeneous or
heterogenous hardare: intel edison, samsung artik, apple AX, intel core,
etc) so the calculation needs, the storage/memory, the connection, etc are
decoupled; hence we can reach an ecosystem with several clouds.
How
On 11 March 2014 at 20:38, David Chisnall wrote:
> On 12 Mar 2014, at 02:07, Roger Pau Monné wrote:
>
>> I've found out that the value PTHREAD_STACK_MIN is currently set (2048
>> bytes) seems to be way too low
>
> This looks like an error in your code. The spec says:
>
>> PTHREAD_STACK_MIN
>> Mi
## Andriy Gapon (a...@freebsd.org):
> It did not make sense to me that libcrypto would have such a bug and then I
> noticed that libcrypto.so.7 was involved.
Now that you mention libcrypto... There was a similar (the same?) issue
about a year ago in VirtualBox, which ended up being linked against