- 17 Oct, 2018 8 commits
-
-
Federico Vaga authored
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
-
Federico Vaga authored
The number of samples should not take into account any interleaving becasue this is already counted by the board-specifc code. A sample size already count any interleaving Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The buffer needs to be released while the device that created it is still open. So this patch revert the order which was wrong. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
``devname`` string allocation needs one extra byte to store the terminator character '\0'. Not doing this works most of the time, but all strings need be terminated properly. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The tools was not release properly ``devmem`` memory. It is true that at process end this get cleared automatically; but it is better to clean everything in the process itself so that if we will do some update where ``free(3)`` become mandatory then we will not forget it. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 02 Aug, 2018 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 27 Jun, 2018 4 commits
-
-
Federico Vaga authored
Today the FmcAdc100m14b4cha is the only supported board, having it optional does not make sense. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 09 Mar, 2018 8 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
In principle, all the operations must be implemented. But in the remote case some special board does not need one of the operation we have foreseen, then we should prevent segfaults and return en error. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
All routing functions are now in ``route.c`` All the board-specific code is in the dedicated board-specific files Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
This re-write the documentation in sphinx. It also adds an example program that can be used to copy and paste code or to quote it in the documentation. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 20 Feb, 2018 7 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
this is not useful anymore Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The complete tool `fald-acq` now is doing it. This tool does not help anymore Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The tools will be completely reviewed so here we just make them compile. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 19 Feb, 2018 12 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
zzero is a true device, why should we call it fake? Of course, this is used for testing but it should be clear which device we are going to use. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
This is useful when the software wants to retrieve all the configuration options without set them one by one Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
It is useful for generic tools which do not know in advance what a device support or not. Signen-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
this will fix g++ warnings and will not affect the gcc and C logic even if `(void *)` is perfectly legal in C Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Having a configuration mask which is 0x0 should not be an error. This is just saying that we do not want to configure anything. Of course, this is weird but legit. The user should be more careful when it does a manual configuration, indeed this does not happen when the user uses the API to build the configuration Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-