Jaco Hofmann

I had the same wish some time ago, but it was rejected for some reason. Can you remind me what it was @lukasmweber?

The question then is: why make the process less comfortable when the same result can be achieved by running just one command? I don't think we gain anything from removing...

Maybe we should separate this discussion into the corresponding rework CLI issue. The question here is, if skipEvaluation should become the default and if it should be a parameter of...

Please read what I wrote above. We should not adhere to some "arcane" teaching, but make TaPaSCo as easy to use as possible. I see the import as part of...

Yes, that would be awesome. However, we actually had exactly this implemented before and it turned out way too pessimistic. For instance, we couldn't build US+ bitstreams on our 32GB...

To be honest, I don't remember. The implementation back then was from Jens and I was just the one that made him delete it again... I just checked for the...

This is all part of the changes in #181. Afterwards it should be very easy to support a variety of memory configurations with different kinds of accessors.

I imagine some functionality such as: Enumerate available FPGAs: ```bash > tapasco-load-bitstream --list-devices 0 -> Zynq MP 1 -> PCIe JTAG XUPVVH 2 -> PCIe Direct VC709 ``` Replace active...

Sure, it remains a Python script with a `if __main__` block. You can simply include that script in your program and use the functionality as desired.

You mean the toolflow or the runtime? We could also include it into the runtime, but that's certainly less convenient considering the languages used. However, certainly possible and worth considering.