Ivan Dubrov

See RFC 5621

As noted above, being able to have common interface would be useful not only across different devices, but also across different peripherals in the same device. Moreover, some peripherals could...

Is it possible to inherit the whole peripheral and then add an extra field to some inherited register? For example, "basic" timer would not have field CKD (clock division) in...

@djmcgill I tried it on [stm32f103xx](https://github.com/japaric/stm32f103xx) -- works great, thanks a lot! P.S. Just make it official, that will make it stable **really** fast (after you get and fix all...

Adding some context here (as I keep stumbling at ccmr1_input/ccmr1_output registers on STM32 F103 chip). First, unions are in Rust 1.19: https://github.com/rust-lang/rust/pull/42068 However, using them at this point would require...

I like the idea of being able to drive multiple pins separately as a single atomic thing -- for the timing reasons you've mentioned. However, for the purpose of HD44780...

Well, in an ideal world, where you can have a perfect cut & slice on your GPIO (like all pins of GPIOA+GPIOB+GPIOC => Slice1 + Slice2 + Slice3), your interrupt...

Though, if you can have it, I would certainly love the solution that allows me to: 1. Mix multiple GPIO's 2. Split them into individual "slices" of pins/ranges of pins...

Yeah, I've done something similar. This is the workaround I ended up creating: ```rust #[derive(Debug)] pub struct QueryRoot); #[derive(Debug)] pub struct MutationRoot); #[derive(Debug)] pub struct Schema(RootNode, MutationRoot> { let res:...

Our schema is defined through metadata which we read from the database and/or files. And it's big, yes. Takes seconds to build a schema (in debug, in release it is...