On Thu, May 03, 2018 at 10:17:51AM +0100, Peter Maydell wrote: > On 3 May 2018 at 10:05, Joel Stanley <j...@jms.id.au> wrote: > I'm a bit reluctant to take these patches until we have an > actual cortex-m0 model, because anything we take into QEMU > master is then something we have to support. My rule of thumb > is that it's ok to have board models that are missing > functionality, but we should avoid models that have wrong > functionality (like the wrong CPU) where we can.
For the purposes of the micro:bit emulation project we're not sure yet how far the M3 model will take us. The M0 is a subset of the M3 and we intend to use it during bring-up...and even afterwards if software runs okay with it. If you don't want to merge this into qemu.git/master we'll have to maintain a "microbit" project branch on which Julia and Steffen (and others) can work during the Google Summer of Code and Outreachy period. My concern about keeping it out-of-tree is that we want Julia and Steffen to participate in the upstream community and get their patches merged. Anything out-of-tree could still be rejected at a later date :(. Can we mark the machine type "experimental" and merge it in qemu.git/master with the understanding that it may be removed if there is no active development? Stefan
signature.asc
Description: PGP signature
