Paul Osborne

:+1: for publishing a new release for crates.io. Also, please tag all releases in git so it is easy to see what code is in master that is not in...

@arcnmx I did not make that connection -- that would explain a lot of things (I feel a bit dumb for not catching this) :) In an ideal world, would...

@kassane Can you provide source and license information for the SVD? I did not see any license info in the SVD text and we don't have anything in tree already...

@JohnBerg60 Contributions of SVD files with appropriate licenses compatible with the project as described in the README are welcome. We do have some emergent rules we generally try to follow...

Hi @ppannuto, we can move something forward. One items that has been discussed has been removing the SVD from the pypi package and having it just be the python code...

Sorry, quite a lot of time has passed on this @astro. The ST license does not appear to prohibit making changes. To keep the vendor provided ST clear from the...

Thanks @therealprof; I think putting things into the NXP directly would be fine. Hopefully they don't mess with us again by move it over to QCOM or something. The kernel...

Logic of change looks good; if you agree please incorporate the proposed simplification and then squash your commits down to clean up the history. Two commits are fine with the...

I pulled down this file. I believe the SVD provided by ARM does follow the spec but does it in a way that is more than a little obnoxious and...

Unfortunately, due to the license on the SVD files, we don't directly change SVD files as part of this project. We might be able to convince the vendor (in this...