Daniel Egger

@adamgreig > I agree with your premise, SVD files do kind of suck, are better than nothing, and lots of individual crates, one per device, is a mess It's actually...

@Emilgardis This may work in a few cases but in general the differences are just too big to make it feasible. Even if a peripherals are 1:1 compatible in a...

@jcreedon > I'm not aware of SVD files representing pin mappings of peripherals, or any CSPs providing abstractions for pins. I'm also not aware of any directly expressed mappings, however...

@hannobraun > According to my contact, they provide SVD files to anyone on request though. Yes, you can download them yourself by going to the "MCUXpresso SDK Builder" site and...

I think this has been overtaken by events. There're now multiple alternative solutions to generating chip support crates from SVD files and managing SVD files, including the WGs https://github.com/rust-embedded/svd2rust/ as...

@almindor You mean like https://github.com/hobofan/cargo-nono @TheVova You're not completely off but there's indeed very little we can do here in the EWG. Luckily for us there's another big area where...

@DomonkosSuranyi I absolutely agree. There should be traits which unify the API for working with sensor data so when using the API one can rely on getting the same information...

> I think one of the reasons the Arduino code is able to be so simple is because (in our terminology) it's an automatically selected BSP for your specific board,...

@FlorianUekermann @hannobraun Actually that's a splendid idea. I also have both a huge backlog of things I want to do/get done and a ton (I haven't weighted it but it...

@japaric I think you're numbers are not quite up-to-date anymore. The overhead keeps growing and growing. A simple ``` writeln!(&mut output, "Hello World!"); ``` into a dummy Buffer creates a...