From: Alexandre IOOSS <erdnaxe@crans.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "open list:STM32F100" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] stm32f100: Add the stm32f100 SoC
Date: Tue, 15 Jun 2021 09:56:38 +0200 [thread overview]
Message-ID: <3549092b-5ad0-71f1-a13d-1f84e4cc5c5c@crans.org> (raw)
In-Reply-To: <CAFEAcA_YkqObpY6E8QiL-_+bLn_3xigv=djtRCdPDNvF4VT4kw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 460 bytes --]
On 6/14/21 6:04 PM, Peter Maydell wrote:
> Is this definitely right? The STM32F00 datasheet I found
> thinks it only has 61 external interrupts.
Yes you are right, I don't really known what I have done here. I will
fix this in next patchset version.
To double-check, it is described page 131 of
https://www.st.com/resource/en/reference_manual/cd00246267-stm32f100xx-advanced-arm-based-32-bit-mcus-stmicroelectronics.pdf
Thanks,
-- Alexandre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-06-15 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 16:10 [PATCH 0/2] STM32VLDISCOVERY Machine Model Alexandre Iooss
2021-06-08 16:10 ` [PATCH 1/2] stm32f100: Add the stm32f100 SoC Alexandre Iooss
2021-06-14 16:04 ` Peter Maydell
2021-06-15 7:56 ` Alexandre IOOSS [this message]
2021-06-15 7:41 ` Alistair Francis
2021-06-15 7:49 ` Alexandre IOOSS
2021-06-15 8:04 ` Alistair Francis
2021-06-15 9:15 ` Alexandre IOOSS
2021-06-15 10:40 ` Alistair Francis
2021-06-08 16:10 ` [PATCH 2/2] stm32vldiscovery: Add the STM32VLDISCOVERY Machine Alexandre Iooss
2021-06-14 15:52 ` Peter Maydell
2021-06-15 7:16 ` Alexandre IOOSS
2021-06-15 7:50 ` Alistair Francis
2021-06-15 9:07 ` Peter Maydell
2021-06-14 16:05 ` [PATCH 0/2] STM32VLDISCOVERY Machine Model Peter Maydell
2021-06-14 16:16 ` Philippe Mathieu-Daudé
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=3549092b-5ad0-71f1-a13d-1f84e4cc5c5c@crans.org \
--to=erdnaxe@crans.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.