All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "make menuconfig" does not work
Date: Fri, 27 Apr 2012 10:27:16 +0200	[thread overview]
Message-ID: <20120427102716.1e259c53@skate> (raw)
In-Reply-To: <20120426121811.8032C200246@gemini.denx.de>

Le Thu, 26 Apr 2012 14:18:11 +0200,
Wolfgang Denk <wd@denx.de> a ?crit :

> > (it would be great to get U-Boot added to buildroot as well - One
> > build for bootloader + kernel + root filesystem :)
> 
> Buildroot?  Isn't this kind of a dead horse now?  I thought everybody
> is using Yocto now...

Since the last 3 years, the project has seen an increasing activity,
and has been almost entirely rewritten. We are doing stable releases
every 3 months, are doing a lot more quality testing than we have been
doing in the past. We have given talks at the latests ELC, ELCE and
FOSDEM.

So, definitely it's not a dead project. It however doesn't fit the same
segment as Yocto: Yocto is an embedded distribution generator, while
Buildroot is just a root filesystem + kernel + bootloader image
generator. Buildroot is much, much simpler to use and set up, but also
offers less flexibility than Yocto.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-04-27  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 18:21 [U-Boot] "make menuconfig" does not work hong zhang
2012-04-25 22:26 ` Graeme Russ
2012-04-26 12:18   ` Wolfgang Denk
2012-04-26 12:28     ` Graeme Russ
2012-04-27  8:27     ` Thomas Petazzoni [this message]
2012-05-02 23:45     ` Marek Vasut
2012-04-27  8:24   ` Thomas Petazzoni

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=20120427102716.1e259c53@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=u-boot@lists.denx.de \
    /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.