From: Linus Walleij <linus.walleij@linaro.org>
To: Ludovic Barre <ludovic.Barre@st.com>
Cc: Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/6] ARM: stm32: prepare stm32 family to welcome armv7 architecture
Date: Mon, 11 Dec 2017 11:25:09 +0100 [thread overview]
Message-ID: <CACRpkdaKZk5N9F=_nYSzKWyXgW4xQ9Ltft7-UNM+a-nOpqq2xg@mail.gmail.com> (raw)
In-Reply-To: <1512742277-28205-2-git-send-email-ludovic.Barre@st.com>
On Fri, Dec 8, 2017 at 3:11 PM, Ludovic Barre <ludovic.Barre@st.com> wrote:
> From: Ludovic Barre <ludovic.barre@st.com>
>
> This patch prepares the STM32 machine for the integration of Cortex-A
> based microprocessor (MPU), on top of the existing Cortex-M
> microcontroller family (MCU). Since both MCUs and MPUs are sharing
> common hardware blocks we can keep using ARCH_STM32 flag for most of
> them. If a hardware block is specific to one family we can use either
> ARCH_STM32_MCU or ARCH_STM32_MPU flag.
>
> Signed-off-by: Ludovic Barre <ludovic.barre@st.com>
So yesterdays application processors are todays MCU processors.
I said this on a lecture for control systems a while back and
stated it as a reason I think RTOSes are not really seeing a bright
future compared to Linux.
It happened quicker than I thought though, interesting.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-12-11 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 14:11 [PATCH 0/6] ARM: stm32: add initial STM32MPU support Ludovic Barre
[not found] ` <1512742277-28205-1-git-send-email-ludovic.Barre-qxv4g6HH51o@public.gmane.org>
2017-12-08 14:11 ` [PATCH 1/6] ARM: stm32: prepare stm32 family to welcome armv7 architecture Ludovic Barre
2017-12-11 10:25 ` Linus Walleij [this message]
[not found] ` <CACRpkdaKZk5N9F=_nYSzKWyXgW4xQ9Ltft7-UNM+a-nOpqq2xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-11 13:40 ` Arnd Bergmann
2017-12-11 14:22 ` Ludovic BARRE
2017-12-12 11:03 ` afzal mohammed
2017-12-12 13:32 ` Ludovic BARRE
2017-12-08 14:11 ` [PATCH 2/6] ARM: stm32: add initial support for STM32MP157 Ludovic Barre
2017-12-12 23:24 ` Rob Herring
2017-12-13 9:02 ` Ludovic BARRE
2017-12-08 14:11 ` [PATCH 4/6] ARM: configs: multi_v7: add stm32 support Ludovic Barre
2017-12-08 14:11 ` [PATCH 6/6] ARM: dts: stm32: add initial support of stm32mp157c eval board Ludovic Barre
2017-12-08 14:41 ` [PATCH 0/6] ARM: stm32: add initial STM32MPU support Neil Armstrong
2017-12-08 14:11 ` [PATCH 3/6] pinctrl: stm32: Add STM32MP157 MPU support Ludovic Barre
[not found] ` <1512742277-28205-4-git-send-email-ludovic.Barre-qxv4g6HH51o@public.gmane.org>
2017-12-12 23:25 ` Rob Herring
2017-12-08 14:11 ` [PATCH 5/6] ARM: dts: stm32: add stm32mp157c initial support Ludovic Barre
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='CACRpkdaKZk5N9F=_nYSzKWyXgW4xQ9Ltft7-UNM+a-nOpqq2xg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.Barre@st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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).