On Nov 07, 2016 12:57, Peter Rosin wrote:
> On 2016-11-07 12:37, Daniel Baluta wrote:
> > On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
> >> From: Jonathan Cameron
> >>
> >> A large number of attributes can only take a limited range of values.
> >>
On Nov 07, 2016 12:57, Peter Rosin wrote:
> On 2016-11-07 12:37, Daniel Baluta wrote:
> > On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
> >> From: Jonathan Cameron
> >>
> >> A large number of attributes can only take a limited range of values.
> >> Currently in IIO this is handled by
On 2016-11-07 12:37, Daniel Baluta wrote:
> On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
>> From: Jonathan Cameron
>>
>> A large number of attributes can only take a limited range of values.
>> Currently in IIO this is handled by directly registering
On 2016-11-07 12:37, Daniel Baluta wrote:
> On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
>> From: Jonathan Cameron
>>
>> A large number of attributes can only take a limited range of values.
>> Currently in IIO this is handled by directly registering additional
>> *_available attributes
On Mon, Nov 7, 2016 at 1:57 PM, Peter Rosin wrote:
> On 2016-11-07 12:37, Daniel Baluta wrote:
>> On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
>>> From: Jonathan Cameron
>>>
>>> A large number of attributes can only take a limited range
On Mon, Nov 7, 2016 at 1:57 PM, Peter Rosin wrote:
> On 2016-11-07 12:37, Daniel Baluta wrote:
>> On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
>>> From: Jonathan Cameron
>>>
>>> A large number of attributes can only take a limited range of values.
>>> Currently in IIO this is handled by
On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
> From: Jonathan Cameron
>
> A large number of attributes can only take a limited range of values.
> Currently in IIO this is handled by directly registering additional
> *_available attributes thus providing
On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin wrote:
> From: Jonathan Cameron
>
> A large number of attributes can only take a limited range of values.
> Currently in IIO this is handled by directly registering additional
> *_available attributes thus providing this information to userspace.
>
>
On 23/10/16 23:39, Peter Rosin wrote:
> From: Jonathan Cameron
>
> A large number of attributes can only take a limited range of values.
> Currently in IIO this is handled by directly registering additional
> *_available attributes thus providing this information to userspace.
On 23/10/16 23:39, Peter Rosin wrote:
> From: Jonathan Cameron
>
> A large number of attributes can only take a limited range of values.
> Currently in IIO this is handled by directly registering additional
> *_available attributes thus providing this information to userspace.
>
> It is
From: Jonathan Cameron
A large number of attributes can only take a limited range of values.
Currently in IIO this is handled by directly registering additional
*_available attributes thus providing this information to userspace.
It is desirable to provide this information via
From: Jonathan Cameron
A large number of attributes can only take a limited range of values.
Currently in IIO this is handled by directly registering additional
*_available attributes thus providing this information to userspace.
It is desirable to provide this information via the core for much
12 matches
Mail list logo