tapasco issueshttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues2019-01-22T16:25:45Zhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/164Properly unregister the driver if a device is removed2019-01-22T16:25:45ZJaco HofmannProperly unregister the driver if a device is removedFix errors occurring because the tlkm driver does not react properly on device remove requests.Fix errors occurring because the tlkm driver does not react properly on device remove requests.2018.2Jaco HofmannJaco Hofmannhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/160Local memory slots not considered in area estimation, causing DSE to fail2019-12-18T09:54:11ZJens KorinthLocal memory slots not considered in area estimation, causing DSE to failIf a PE has local memories (or more than one slave interface, for that matter), DSE will still try to build more instances than will fit in the current 128 slots limit. There are several possible solutions:
1. Have separate enumerati...If a PE has local memories (or more than one slave interface, for that matter), DSE will still try to build more instances than will fit in the current 128 slots limit. There are several possible solutions:
1. Have separate enumeration for memory slots (affects status core, `platform_info` and potentially requires a more sophisticated way to determine accessibility for each PE).
2. Fix the algorithms to account for each slave interface instead of just assuming one.
Need to think about it some more; I guess, each PE will always have exactly _one_ control slave interface. We could require a naming convention to identify it if more than one candidate is present on a PE, e.g., `S_AXI_CTRL` or similar. All other slave interfaces could be assigned a base address from a different pool, e.g., using the upper 64 base addresses already reserved for platform addresses. But we'd have to come up with some O(k) or at least O(n) scheme to find the base addresses of all slaves on a PE. :thinking:2018.2https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/19Cleanup: Kernels, Examples2018-07-01T15:08:25ZJens KorinthCleanup: Kernels, Examples* [x] remove broken kernels
* [x] check that all kernels work in HLS
* [ ] check that all kernels have example programs
* [ ] check that example programs *actually work*
* [x] move through all directories, sift files* [x] remove broken kernels
* [x] check that all kernels work in HLS
* [ ] check that all kernels have example programs
* [ ] check that example programs *actually work*
* [x] move through all directories, sift files2018.2