On 14/11/2015 19:44, Jonathan Cameron wrote:
On 12/11/15 10:18, Marc Titinger wrote:
On 10/11/2015 19:23, Lars-Peter Clausen wrote:
On 11/10/2015 05:07 PM, Marc Titinger wrote:
Capture the active scan_elements into a kfifo.
The capture thread will compute the remaining time until the next capt
On 12/11/15 10:18, Marc Titinger wrote:
> On 10/11/2015 19:23, Lars-Peter Clausen wrote:
>> On 11/10/2015 05:07 PM, Marc Titinger wrote:
>>> Capture the active scan_elements into a kfifo.
>>> The capture thread will compute the remaining time until the next capture
>>> tick, and do an active wait (
On 11/12/2015 11:18 AM, Marc Titinger wrote:
[...]
>> Slightly OT, but do you already have some Sigrok IIO support? I have this
>> scheduled for end of the month, maybe we can align our strategies here and
>> avoid duplicated work.
>
> How fortunate! I've started some preliminary work like cloning
On 10/11/2015 19:23, Lars-Peter Clausen wrote:
On 11/10/2015 05:07 PM, Marc Titinger wrote:
Capture the active scan_elements into a kfifo.
The capture thread will compute the remaining time until the next capture
tick, and do an active wait (udelay).
This will produce a stream of up to fours ch
On 11/10/2015 05:07 PM, Marc Titinger wrote:
> Capture the active scan_elements into a kfifo.
> The capture thread will compute the remaining time until the next capture
> tick, and do an active wait (udelay).
>
> This will produce a stream of up to fours channels plus a 64bits
> timestamps (ns).
Capture the active scan_elements into a kfifo.
The capture thread will compute the remaining time until the next capture
tick, and do an active wait (udelay).
This will produce a stream of up to fours channels plus a 64bits
timestamps (ns).
# iio_readdev ina226 | od -x
WARNING: High-speed mode n
6 matches
Mail list logo
