-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
track merging onf lpc81x #76
Comments
👍 |
as you want, either you stay sole owner of the pac crate, but that means that every time there is a new version, you would need to publish it, or you add me as an owner, and I do the publish everytime there is a new version. |
Hello! I built lpc81x-hal as part of a specific project and haven't ended up using that platform for subsequent projects and so haven't had reason to work on it further. I believe I do still have at least one development board with an LPC812 chip in my lab somewhere, which I could potentially use for some testing if it's still functional. I expect I'll have only limited time to maintain the HAL crate moving forward and so I would be happy to collaborate with others on it if anyone is interested. I must admit that I don't have the details of this platform at the front of my mind right now so I can't comment on the potential impacts of upgrading the PAC, but I'd be willing to give it a try if I can find my dev board. |
In order to increase the bus-factor, I've invited @allexoll as an owner of |
thanks! I've published the new version, no idea about the lpc-rs team on crates.io, maybe @hannobraun has more insight? |
I don't know what the problem could be. The team definitely exists and is set to "visible". |
after discussing it in #75 , we might be able to include the lpc81x pac in here.
there is a lot of differences between the patched 0.2 SVD (0.3? xml says 0.2), and the v1 SVD that is currently in this repository.
As I don't have a board with that MCU, it would be hard to test, and to see what would need to be fixed for a new version of the lpc81x-hal crate as well. @apparentlymart seems to be the owner of the HAL.
I don't think this would be an issue since both the PAC and the HAL have not been updated for a long time (3 and 2 years respectively). current new LPC pacs are on version 0.2.1, so they would not break current version of the hal, which relies on lpc-81x v0.1.0.
if @lucab is fine with moving the lpc81x pac here, that can be done by just publishing the current release (v0.2.1) that is generated by the current files for LPC81x.
The text was updated successfully, but these errors were encountered: