From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Q] Buildroot vs uCLinux
Date: Wed, 26 Jun 2013 15:35:43 +0200 [thread overview]
Message-ID: <20130626153543.4bf75096@skate> (raw)
In-Reply-To: <CALF0-+UubeQyQPoiQf2y8f30BkbGO+9AzzirCRcfss1sfS724Q@mail.gmail.com>
Dear Ezequiel Garcia,
On Wed, 26 Jun 2013 10:19:07 -0300, Ezequiel Garcia wrote:
> > Which CPU architecture is this platform
> > using?
>
> Nios2
Nice! However, beware that Buildroot has no support for NIOS2. That
said, if you have prebuilt known-working toolchains for NIOS2, adding
support for this architecture in Buildroot is not very complicated.
Patches welcome!
> > There are apparently some not too old releases of uClinux-dist (october
> > 2012), but I'm not sure where the development is happening since the
> > CVS repository reference on the project web site seems to contain only
> > very old stuff.
>
> Well, this is my very same concern: the lack of a healthy community
> on the uCLinux side. I can it's a good choice for MMU-less platforms
> given packages have been heavily patched. But this is not the case,
> and hence my perplexity.
Correct, we don't have as many noMMU fixes in Buildroot as uClibc-dist
has, but we're working on this progressively.
> Since this platforms come in two flavors (MMU and MMU-less) I was almost sure
> the reason is mostly historical.
Most likely yes.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-26 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:57 [Buildroot] [Q] Buildroot vs uCLinux Ezequiel Garcia
2013-06-25 15:26 ` Stephan Hoffmann
2013-06-25 22:01 ` Thomas Petazzoni
2013-06-26 13:19 ` Ezequiel Garcia
2013-06-26 13:35 ` Thomas Petazzoni [this message]
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=20130626153543.4bf75096@skate \
--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.