From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] New entry for the Cortex-M4 processor
Date: Sun, 13 Sep 2015 10:21:36 +0200 [thread overview]
Message-ID: <20150913102136.01d94129@free-electrons.com> (raw)
In-Reply-To: <1442127768-26447-2-git-send-email-cjwfirmware@vxmdesign.com>
Chris,
On Sun, 13 Sep 2015 03:02:47 -0400, Chris Wardman wrote:
> I created a new entry for the Cortex-M4 processor in the processor list.
Don't use "personal" formulations in commit log. It should be something
like: "This commit adds a new entry..."
> Right now it is being tested against a STM32F4disovery board.
> This is technically an M4F. I will add that entry with the floating point in the future
Ditto here.
And the title of the commit log should be:
arch: add entry for the ARM Cortex-M4 processor
> diff --git a/arch/Config.in.arm b/arch/Config.in.arm
> index 4d10f4c..2692402 100644
> --- a/arch/Config.in.arm
> +++ b/arch/Config.in.arm
> @@ -156,6 +156,11 @@ config BR2_cortex_m3
> bool "cortex-M3"
> select BR2_ARM_CPU_HAS_THUMB
> select BR2_ARM_CPU_HAS_THUMB2
> +config BR2_cortex_m4
> + bool "cortex-M4"
> + select BR2_ARM_CPU_HAS_THUMB
> + select BR2_ARM_CPU_HAR_THUMB2
> + select BR2_ARM_CPU_ARMV7M
Please use tab for indentation. Also, while Cortex-M3 also does it, I
think selecting both Thumb and Thumb-2 is not correct: Cortex-M3/M4
only support Thumb-2, no? Or at least, gcc only provides a -mthumb
option that will generate Thumb-2 code, so there is no way to generate
classic Thumb code on ARMv7-M platforms. Though since the problem
already exists for Cortex-M3, we can keep it this way for Cortex-M4 as
well for now.
Also, you're selecting the BR2_ARM_CPU_ARMV7M option, but this option
does not exist. Since there is a BR2_ARM_CPU_ARMV7A, I believe it makes
sense to create this option, so probably you should have three patches
here:
* One option that adds BR2_ARM_CPU_ARMV7M
* One patch that makes Cortex-M3 select it
* One patch that adds Cortex-M4
Other than that, looks good to me.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-13 8:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 7:02 [Buildroot] [PATCH 1/3] Experimental addition of the newlib library Chris Wardman
2015-09-13 7:02 ` [Buildroot] [PATCH 2/3] New entry for the Cortex-M4 processor Chris Wardman
2015-09-13 8:21 ` Thomas Petazzoni [this message]
2015-09-15 20:52 ` Yann E. MORIN
2015-09-24 21:02 ` Peter Korsgaard
2015-09-13 7:02 ` [Buildroot] [PATCH 3/3] Adding support for uclibcpp library Chris Wardman
2015-09-13 22:00 ` Thomas Petazzoni
2015-09-17 7:07 ` Cjw X
2015-09-17 7:25 ` Thomas Petazzoni
2015-09-13 8:17 ` [Buildroot] [PATCH 1/3] Experimental addition of the newlib library Thomas Petazzoni
2015-09-15 4:06 ` Cjw X
2015-09-15 7:35 ` Thomas Petazzoni
2015-09-15 17:53 ` Yann E. MORIN
2015-09-15 19:39 ` Thomas Petazzoni
2015-09-24 21:30 ` Peter Korsgaard
2015-09-25 7:30 ` Thomas Petazzoni
2015-09-27 16:40 ` Cjw X
2015-09-15 20:45 ` Yann E. MORIN
[not found] ` <CAOudHSVLKiTwrkv0xBNVW=ry3w1yOv4TJqP8+JMFSJRzw3dASQ@mail.gmail.com>
2015-09-16 17:07 ` Yann E. MORIN
2015-09-16 17:36 ` Cjw X
2015-09-16 17:38 ` Thomas Petazzoni
2015-09-15 20:41 ` Yann E. MORIN
2015-09-17 7:41 ` Cjw X
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=20150913102136.01d94129@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.