Catherine
Catherine
I've implemented the RFC in https://github.com/amaranth-lang/amaranth/pull/697. Please try it out; I'm happy to hear any and all feedback!
@Kaucasus > 1. Are the data structure fields meant to be inconsistent? No. > Looking at the examples, it looks like when using `data.Struct` in a class, the order in...
I've updated the RFC to mention `View` accepting `Signal` keyword arguments. I've also updated the implementation. I believe this RFC should be complete now.
We really should just get rid of bitarray at last, it has caused nothing but problems, and the implementation is unsafe and likely unsound.
Thanks for the investigation. My conclusion is the same: we should get rid of bitarray. In the meantime we may need to fix the installation instructions but I'm not entirely...
> The error is that the `Pins` direction (an `inout`?) That's not an `inout`. You're requesting a triple, implicitly. Use `dir="o"` when defining the LED resource, or better, `LEDResources`.
Currently there's no way to do so; it is something on my radar for a while, but also not trivial to add in a backward compatible way. Please see the...
Regarding the port name, you can create a clock domain and then rename the signal using `cd.rst.name = "foobar"`, for example. (nMigen guarantees that it will never mangle names of...
You'd have to write a wrapper module anyway to instantiate a clock domain, wouldn't you?
The reset is synchronous unless you explicitly configure it async. Maybe I'm missing some part of your plan here; could you illustrate what you mean with some code?