So there won't be "simple" master/satellite? What about the board I've been testing it on, is it with a backplane?
Is this just a matter of reordering rtio channels added for nist clock/qc2, and adding missing channels, or am I missing something else?
Good question, actually. It's just something I wasn't really thinking about as long as it could compile. A bit of an online search only says "it resolves the dependencies" somehow, I haven't went…
Well, with it, it tries to built satman with pl/mem files obviously not prepared, failing the build. And makes a circular dependency.
Calling make for master runtime throws a warning, and then…
zc706 doesn't use JSONs, though. Now that I think about it I could make it a bit better still by having the fwtype specified in the list of targets at the bottom, passed to the build function instead.
You mean in the name of the rule? Fair point, no particular reason for it, I'll revert it.
No, it doesn't from what I saw. Cargo must do the checks on its own. And with find . it would also try to build satman at the same time as runtime.