From: "Guido Martínez" <guido@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/4] Add ARM Cortex-M3 support
Date: Mon, 29 Jun 2015 12:01:51 -0300 [thread overview]
Message-ID: <20150629150151.GA10554@fox> (raw)
In-Reply-To: <20150628143454.2b895956@free-electrons.com>
Hi Thomas,
On Sun, Jun 28, 2015 at 02:34:54PM +0200, Thomas Petazzoni wrote:
> Dear Guido Mart?nez,
>
> On Fri, 26 Jun 2015 14:33:18 -0300, Guido Mart?nez wrote:
> > toolchain: introduce BR2_TOOLCHAIN_HAS_RESOLVER
> > toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain
>
> There have been some comments from Yann on these patches, so I've
> marked them as "Changes Requested" in patchwork. Could you rework them
> as suggested by Yann, and resend updated versions?
Yes, will do! I agree with Yann in removing nslookup from the default
busybox config. I think that's easier for everyone.
> Also, now that there is Cortex-M3 support listed, please make sure it
> works fine with the internal toolchain backend, and if it doesn't work,
> add the appropriate exceptions (for example, glibc and musl cannot be
> built for Cortex-M3, as far as I know). Can you send a follow-up patch
> for this?
Right, it doesn't work right now since there are a few places that force
the selection of ARM instructions where Thumb is not available, and that
won't work on M3. I'll try to fix it and get back.
Thanks!
--
Guido Mart?nez, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2015-06-29 15:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 17:33 [Buildroot] [PATCH v3 0/4] Add ARM Cortex-M3 support Guido Martínez
2015-06-26 17:33 ` [Buildroot] [PATCH 1/4] arm: update processor types Guido Martínez
2015-06-27 10:24 ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 2/4] toolchain: allow for stupid toolchains Guido Martínez
2015-06-27 10:28 ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 3/4] toolchain: introduce BR2_TOOLCHAIN_HAS_RESOLVER Guido Martínez
2015-06-27 10:39 ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 4/4] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-06-27 12:42 ` Yann E. MORIN
2015-06-28 12:34 ` [Buildroot] [PATCH v3 0/4] Add ARM Cortex-M3 support Thomas Petazzoni
2015-06-29 15:01 ` Guido Martínez [this message]
2015-07-14 15:11 ` [Buildroot] [PATCH v4 0/3] " Guido Martínez
2015-07-14 15:11 ` [Buildroot] [PATCH v4 1/3] busybox: disable nslookup applet Guido Martínez
2015-07-14 15:11 ` [Buildroot] [PATCH v4 2/3] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-07-14 15:42 ` Baruch Siach
2015-07-14 15:57 ` Guido Martínez
2015-07-14 15:11 ` [Buildroot] [PATCH v4 3/3] toolchain: disable internal for blackfin Guido Martínez
2015-07-14 15:43 ` Baruch Siach
2015-07-14 15:58 ` Guido Martínez
2015-07-14 19:20 ` Waldemar Brodkorb
2015-07-14 16:09 ` [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet Guido Martínez
2015-07-14 16:09 ` [Buildroot] [PATCH v5 2/3] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-07-14 16:09 ` [Buildroot] [PATCH v5 3/3] toolchain: disable internal for Cortex-M3 Guido Martínez
2015-07-14 16:31 ` [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet Thomas Petazzoni
2015-07-14 16:55 ` Thomas Petazzoni
2015-07-14 17:10 ` Gustavo Zacarias
2015-07-15 17:19 ` Guido Martínez
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=20150629150151.GA10554@fox \
--to=guido@vanguardiasur.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox