Skip to content

Backporting and Upstream Contributions

vintagepc edited this page Mar 2, 2021 · 2 revisions

I realize this project has been built on QEMU which is a popular platform outside of specialty projects like this. As a result, I recognize it may be desirable to have some of the code contributions submitted upstream.

Unfortunately, at this time I have no plans to do so myself as QEMU does not accept pull requests (but rather, mandates all contributions must be submitted as mailing list patches). I just do not have the time nor desire to need to manage/maintain that in addition to the time I spend actually working on this project. I have done my best to keep the simulated STM32 components such that they should be accepted with little or no modification in terms of formatting. If you are interested in taking on this task or are part of the QEMU team and wish to discuss, please open an issue to let me know so we can collaborate on it!

This is an OSS project and of course the license allows you to do what you wish with the code. I do not wish to inhibit that freedom with this request - rather, this is because many of these components are partially implemented or reverse engineered and subject to additional changes that would need to continue being migrated upstream for complete functionality. What's more, if I am in the loop with what is going to be submitted upstream, I can plan ahead for it and switch to using the "native" version of a component once it becomes part of the main project.

Please also note that not all of the work is my own; I have done my best to retain credits and licenses in the headers of the associated files, but the project draws extensively on some of the work done by the Pebble QEMU project (which, in turn, is based on the QEMU STM32 work by Beckus) which served as a basis for STM32 capabilities. I believe the licenses are such that this is not a problem, but I am not an expert on specifics of license compatibility between GPL/MIT/etc.

Clone this wiki locally