From: Bill Paul <wpaul@windriver.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM Cortex-M issues
Date: Mon, 29 Aug 2016 17:12:56 -0700 [thread overview]
Message-ID: <201608291712.56429.wpaul@windriver.com> (raw)
In-Reply-To: <CAFEAcA_PyweooqkvKF2zsTgR-icHsKVUqCRe0HjErpQWVwJw8g@mail.gmail.com>
Of all the gin joints in all the towns in all the world, Peter Maydell had to
walk into mine at 12:51:04 on Monday 29 August 2016 and say:
> On 29 August 2016 at 13:59, Bill Paul <wpaul@windriver.com> wrote:
> > Unfortunately it's been a frustrating experience because there seem to be
> > several key places where QEMU's hardware emulation diverges from reality.
> > The ChibiOS examples often seem to depend on behavior that is valid for
> > actual hardware but which is either broken or just missing in QEMU. Some
> > of these issues are board-specific, but the last one seems a bit more
> > general.
>
> Yes, our Cortex-M support is a bit undermaintained at the moment.
> If you'd like to write patches to fix some of the bugs you're
> encountering I'd be happy to review them, but I'm not aware of anybody
> actively working on M profile right now. We could really use a
> contributor who cares about it and has time to tackle improving it.
> (A-profile ARM emulation is in much better shape.)
I had a feeling you were going to say that. But I already fell for this trick
once when I started using FreeBSD, and then I ended up being a developer for
about 10 years. I'm older and wiser now. (Also I have a day job that consumes
most of my time.)
The best I might be able to do is patch the STM32 SUART driver so that it
supports the TX fifo empty interrupt. I'm really not sure how to fix the STM32
timer driver (like I said, the ST Micro documentation is really hard to
follow) and I'm not sure that any attempt to get the NMI to work would be any
less of a hack then what's there now.
[...]
> The reason for this kind of thing is that the original support was
> done to support a specific RTOS, and so bugs which resulted in that
> RTOS not working were found and fixed. Bugs which weren't exercised
> by that RTOS remain lurking in the code, and if you try to use a
> different RTOS guest then you can run into them. (This is less
> obvious on the A profile cores because to a first approximation
> nobody runs anything but Linux on them, but in the embedded world
> there's still a fairly rich diversity of RTOSes which take different
> approaches to how they prod the hardware.)
In other words it's half-baked. :(
-Bill
> thanks
> -- PMM
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Member of Technical Staff,
wpaul@windriver.com | Master of Unix-Fu - Wind River Systems
=============================================================================
"I put a dollar in a change machine. Nothing changed." - George Carlin
=============================================================================
next prev parent reply other threads:[~2016-08-29 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 17:59 [Qemu-devel] ARM Cortex-M issues Bill Paul
2016-08-29 19:19 ` Liviu Ionescu
2016-08-29 20:30 ` Bill Paul
2016-08-29 20:25 ` Liviu Ionescu
2016-08-30 8:23 ` Fabien Chouteau
2016-08-29 19:51 ` Peter Maydell
2016-08-29 20:26 ` Peter Maydell
2016-08-30 0:12 ` Bill Paul [this message]
2016-08-30 7:38 ` Peter Maydell
2016-08-30 8:50 ` Liviu Ionescu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201608291712.56429.wpaul@windriver.com \
--to=wpaul@windriver.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).