William D. Jones

(Drive-by comment while I'm trying to prepare another PR) Would [`cargo-dist`](https://github.com/axodotdev/cargo-dist) be useful here?

Current status is: * Custom bitbang commands that can set voltages, assign pins to voltages, and read/write ZIF pins are implemented. * I need to write documentation on how to...

I have a proof-of-concept driver that's not client code that shows what I want to do. Is it possible you could create a branch with these changes on top of...

>I think the point of the peripheral taking ownership of the pins is to be able to guaranty that the pins will remain in a valid state for the peripheral...

I finally got around to testing this... I don't think it's going to be enough; ultimately what I need is "a way to pass in `DynPin`s to e.g. the I2C...

For more context: the idea is that the C code provides a header that defines the pin layout. I will parse this on the Rust side to create structs for...

I'm quite happy with this PR at this point. But I don't want it merged before other people have tested it. Any chance we could bring it up at the...

>In your case you'd need to specify a .MEMORYMAP where ROM and _RAM_ banks share partially the same address space. Yes, that is correct. Right now, I'm [just plain assuming](https://github.com/cr1901/W65C02SXB/blob/main/common/header.inc#L2-L14)...

>A question regarding having .RAMSECTIONs sharing the same SLOT with normal .SECTIONs: Why not mimick a .RAMSECTION with a .SECTION? I also tried another approach that works sometimes but not...

`OCCUPYROM` is technically correct for my specific board. But note that it's possible to have initialized RAM due to a [loader](https://en.wikipedia.org/wiki/Loader_(computing)) _without the need for RAM/ROM collisions_. Actually, that's kinda...