Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] support for cortex m3/m4 with newlib
Date: Fri, 16 Jan 2015 09:22:26 +0100	[thread overview]
Message-ID: <20150116092226.0f2859dd@free-electrons.com> (raw)
In-Reply-To: <CAOudHSX=sc7hwE0PObED1jtDp7pOs-=PPVG_Rsh6+di9iYWojA@mail.gmail.com>

Hello,

On Thu, 15 Jan 2015 17:57:32 -0500, Cjw X wrote:

> I've been working on modifying buildroot to support cortex m3/m4 processors
> against the newlib library.
> 
> This way I can use buildroot to build RTOS's for those processors. I've
> been using buildroot for years to build linux systems and I would like to
> expand that for the smaller processors with different operating systems.
> 
> I am making some progress. The toolchain already works. I'm now starting to
> go down the road of supporting RTOS's.
> 
> I'm going to keep going regardless, but I wanted to check to find out if
> this interests the community.
> 
> Does this interest people?

Support for Cortex-M3/M4 based platforms is definitely interesting.
However, I'm wondering if it really makes sense for Buildroot to
support non-Linux operating systems. To me, the main value of Buildroot
is the 1200+ packages that we have, and all of them are based on the
fact that you run a Linux kernel underneath.

What would Buildroot do for a newlib based system, except building the
toolchain? If it's really only about building the toolchain, then maybe
using Crosstool-NG is a better idea, since it already has newlib
support if I remember correctly.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-01-16  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 22:57 [Buildroot] support for cortex m3/m4 with newlib Cjw X
2015-01-16  7:07 ` Fabrice Mousset | GEOCEPT GmbH
2015-01-16  8:23   ` Thomas Petazzoni
2015-01-16  8:35     ` Fabrice Mousset | GEOCEPT GmbH
2015-01-16  8:56       ` Thomas Petazzoni
     [not found] ` <DB3PR04MB108A30595D5D2347E0366E1EA4F0@DB3PR04MB108.eurprd04.prod.outlook.com>
     [not found]   ` <CAOudHSVE_H85gBwZnBkf=_DAzN+XcmcHYRk9SA8s4qZ94+xXKQ@mail.gmail.com>
2015-01-16  7:56     ` Fabrice Mousset | GEOCEPT GmbH
2015-01-16  8:27       ` Thomas Petazzoni
2015-01-17  1:42       ` Cjw X
2015-01-16  8:22 ` Thomas Petazzoni [this message]
2015-01-17  2:06   ` 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=20150116092226.0f2859dd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox