Catherine
Catherine
> How would passing arguments / config to the internal/hard block work ? Depends. Some hard blocks are singletons, but it is actually (counterintuitively) better to instantiate them as many...
> One thing that the RFC doesn't mention (but might be obvious) is, how the `@`-prefixed pins interact with the `conn` argument? Excellent question. I have actually spent a good...
> I don't know if we can "_lock_" a device, or determine if it is already use, but this may be worth investigating. We can, by claiming an interface. But......
Per IRC discussion, it's an edge case that we probably can't do much with.
I actually think we *can* introduce this feature without significant disruption. But it would need to be carefully considered how.
> Can't we just make sure we don't reload firmware on Glasgows already exposing this interface? That's what API levels are already for! And we still have the problem, because...
> wasn't using an interface, otherwise we would just try to claim it, fail, and not touch that device any more. The firmware is reloaded before any interfaces are claimed.
Well... yes, that's what I suggested above? Except we don't have an interface that can be used for this purpose yet.
Yep, I was also confused when I closed this issue, which is why I reopened it!
Actually, I think I came up with a way that is somewhat simpler and works with every firmware version we have: just try to claim every interface that is already...