- 17 Aug, 2018 8 commits
-
-
Tristan Gingold authored
-
Tristan Gingold authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
- 15 Aug, 2018 4 commits
-
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
- 14 Aug, 2018 5 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>
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
- 08 Aug, 2018 5 commits
-
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
- 07 Aug, 2018 1 commit
-
-
Dimitris Lampridis authored
-
- 02 Aug, 2018 1 commit
-
-
Dimitris Lampridis authored
-
- 01 Aug, 2018 13 commits
-
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Dimitris Lampridis authored
-
Tristan Gingold authored
-
Tristan Gingold authored
-
Tristan Gingold authored
-
Federico Vaga authored
This code has been ported form the fine-delay-sw as is. Probably it will need some review to reduce code size. Signed-off-by: Tomasz Wlostowski <tomasz.wlostowski@cern.ch> 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 mockturtle-framework initilize consecutive actions, here we are keeping together firmware actions received and generated. To avoid trouble on initialization it is good to have the first actions for reception and the last for generation. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
For convenience the first verison of WRTD assumed that a WRTD node is always in/out. Actually this is not true, we may have only input and only output nodes. for this reason we need to split the firmware loading and validation in two parts 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>
-
- 30 Jul, 2018 3 commits
-
-
Dimitris Lampridis authored
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-