... | @@ -335,83 +335,22 @@ wrong; there is not error or message to warn you about this. |
... | @@ -335,83 +335,22 @@ wrong; there is not error or message to warn you about this. |
|
The following table shows how the [Requirements](Requirements) list
|
|
The following table shows how the [Requirements](Requirements) list
|
|
items are supported by COMEDI.
|
|
items are supported by COMEDI.
|
|
|
|
|
|
<table>
|
|
|**requirements**|**IIO**|**Note**|
|
|
<tbody>
|
|
|----|----|----|
|
|
<tr class="odd">
|
|
|Digital/Analog I/O|no|There is no output, only analogue signals are explicit support.|
|
|
<td><strong>requirements</strong></td>
|
|
|TDC and DTC|no|There is no explicit support.|
|
|
<td><strong>IIO</strong></td>
|
|
|One-shot, burst, and streaming support|yes||
|
|
<td><strong>Note</strong></td>
|
|
|Layered structure|half|The layer structure is thought for small chips, so it provides only two level: device and channels|
|
|
</tr>
|
|
|No hard limits on the number of bits or channels|no|The numer of devices is limited to 256|
|
|
<tr class="even">
|
|
|High-data rate, little storage overhead|no|IIO buffer interface handles data sample by sample, we need to handle very large amout of samples|
|
|
<td>Digital/Analog I/O</td>
|
|
|Easy and general configuration|half|Only IIO specific applications can handle events; manage trigger instanse it is not clear|
|
|
<td>no</td>
|
|
|Offset, gain, number of bits, ...|no|A different set is considered "common" and does not have always the same name in each devices|
|
|
<td>There is no output, only analogue signals are explicit support.</td>
|
|
|Extensibility|yes||
|
|
</tr>
|
|
|Little code overhead|yes||
|
|
<tr class="odd">
|
|
|Centralized semaphores|no|IIO handle semaphores only for internal use and for standard syfs attribute. Each implementations (driver, buffer, trigger) must handle with semaphores.|
|
|
<td>TDC and DTC</td>
|
|
|Flexible buffer management|no|IIO buffer interface handles data sample by sample, we need to handle very large amout of samples|
|
|
<td>no</td>
|
|
|Device-driven data transfers|yes||
|
|
<td>There is no explicit support.</td>
|
|
|Hardware time stamps|half|IIO make assumption on timestamp; it is a 64bit signed integer which represent nanoseconds|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>One-shot, burst, and streaming support</td>
|
|
|
|
<td>yes</td>
|
|
|
|
<td></td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>Layered structure</td>
|
|
|
|
<td>half</td>
|
|
|
|
<td>The layer structure is thought for small chips, so it provides only two level: device and channels</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>No hard limits on the number of bits or channels</td>
|
|
|
|
<td>no</td>
|
|
|
|
<td>The numer of devices is limited to 256</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>High-data rate, little storage overhead</td>
|
|
|
|
<td>no</td>
|
|
|
|
<td>IIO buffer interface handles data sample by sample, we need to handle very large amout of samples</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>Easy and general configuration</td>
|
|
|
|
<td>half</td>
|
|
|
|
<td>Only IIO specific applications can handle events; manage trigger instanse it is not clear</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>Offset, gain, number of bits, ...</td>
|
|
|
|
<td>no</td>
|
|
|
|
<td>A different set is considered "common" and does not have always the same name in each devices</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>Extensibility</td>
|
|
|
|
<td>yes</td>
|
|
|
|
<td></td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>Little code overhead</td>
|
|
|
|
<td>yes</td>
|
|
|
|
<td></td>
|
|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>Centralized semaphores</td>
|
|
|
|
<td>no</td>
|
|
|
|
<td>IIO handle semaphores only for internal use and for standard syfs attribute. Each implementations (driver, buffer, trigger) must handle with semaphores.</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>Flexible buffer management</td>
|
|
|
|
<td>no</td>
|
|
|
|
<td>IIO buffer interface handles data sample by sample, we need to handle very large amout of samples</td>
|
|
|
|
</tr>
|
|
|
|
<tr class="even">
|
|
|
|
<td>Device-driven data transfers</td>
|
|
|
|
<td>yes</td>
|
|
|
|
<td></td>
|
|
|
|
</tr>
|
|
|
|
<tr class="odd">
|
|
|
|
<td>Hardware time stamps</td>
|
|
|
|
<td>half</td>
|
|
|
|
<td>IIO make assumption on timestamp; it is a 64bit signed integer which represent nanoseconds</td>
|
|
|
|
</tr>
|
|
|
|
</tbody>
|
|
|
|
</table>
|
|
|
|
|
|
|