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:27:31 +0100	[thread overview]
Message-ID: <20150116092731.0e47d15f@free-electrons.com> (raw)
In-Reply-To: <DB3PR04MB1081BE3A3017D73CFE2F7A2EA4F0@DB3PR04MB108.eurprd04.prod.outlook.com>

Hello,

A couple of mailing list best practices: please keep the messages on
the list (the reply from Cjw was only made to Fabrice), and please
avoid top posting: your replies should be *below* the text you are
replying to. Thanks.

On Fri, 16 Jan 2015 07:56:23 +0000, Fabrice Mousset | GEOCEPT GmbH
wrote:

> I didn?t know ChibiOS, it seems to be interesting, but my interest is more focused on uClinux ;-)
> I don?t have many extra time left, but perhaps I could give you some help.
> Do you have publish your work on a platform like github/sourceforge or something like that?
> What is your next step?
> I have a stm32f4 discovery board, so I could help you on this platform. I?m not an expert, but want to learn more about uClinux and buildroot. I seems to be a good opportunity.

uClinux is not really a different operating system. And in fact,
uClinux doesn't really exist anymore: it used to be a fork of the
Linux kernel to support MMU-less architectures. But this support has
now been merged back in the official Linux kernel.

So for example, on Blackfin (which is an MMU-less architecture), you
can run the official Linux kernel. You can continue to call that
uClinux if you want, but it really has nothing to do anymore with the
original uClinux project.

Buildroot already "supports" uClinux in the sense that it supports the
MMU-less Blackfin architecture, so it should be easily applicable to
other MMU-less architectures such as Cortex-M3/M4 based platforms.

I have a Cortex-M3 platform running Linux, but it has so little RAM
that even the minimal Buildroot filesystem cannot boot on it. I found
this a bit too limited and decided to not really spend more time on
this. But other Cortex-M3 platforms with more RAM are available (8 MB
and more), which should make this more feasible.

Best regards,

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

  reply	other threads:[~2015-01-16  8:27 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 [this message]
2015-01-17  1:42       ` Cjw X
2015-01-16  8:22 ` Thomas Petazzoni
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=20150116092731.0e47d15f@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