From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANNOUNCE] Kconfig support
Date: Sun, 19 Apr 2009 21:48:02 +0200 [thread overview]
Message-ID: <20090419194802.GU5367@pengutronix.de> (raw)
In-Reply-To: <20090418185441.7D6BB83420E8@gemini.denx.de>
On Sat, Apr 18, 2009 at 08:54:41PM +0200, Wolfgang Denk wrote:
> u-boot-v2 is an interesting approach in several aspects, but since it
> was made publicly visible nearly two years ago it did not collect much
> of a community around it.
Right; part of the reason is it was always something we used to solve
our problems, and we didn't do much marketing around it. Nevertheless,
it *does* solve our problems very well, and each time we have to work
with v1 again it's weaknesses show up again and again.
> From my (strictly personal) point of view, one show stopper is that
> there is no migration path - if you want to go u-boot-v2, you have to
> throw away all what is in mainline.
That was one of the design criteria - starting with a clean code base,
in order to get rid of all the old ugglyness.
> And there is a lot of things that are not available in v2.
Right; from what we need in our daytime projects, the most important
feature which is currently missing is PCI support. There are several
others which are surely also important (like i2c) but could be added
with very low effort if needed.
> So it does make perfect sense to me to add features like Kconfig
> support to mainline.
Right; if v2 inspires someone to take the ideas and bring them into v1,
it's perfectly fine - in the end, it's one of the reasons we started the
whole thing.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2009-04-19 19:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 16:25 [U-Boot] [ANNOUNCE] Kconfig support Jean-Christophe PLAGNIOL-VILLARD
2009-04-18 18:29 ` Mike Frysinger
2009-04-18 18:54 ` Wolfgang Denk
2009-04-18 19:18 ` Mike Frysinger
2009-04-18 20:01 ` Wolfgang Denk
2009-04-19 19:50 ` Robert Schwebel
2009-04-20 4:56 ` Mike Frysinger
2009-04-20 6:52 ` Robert Schwebel
2009-04-20 13:49 ` Mike Frysinger
2009-04-20 14:04 ` Robert Schwebel
2009-04-20 14:42 ` Mike Frysinger
2009-04-20 14:53 ` Robert Schwebel
2009-04-20 15:04 ` Jerry Van Baren
2009-04-20 15:20 ` Mike Frysinger
2009-04-20 15:34 ` Sascha Hauer
2009-04-20 18:29 ` Mike Frysinger
2009-04-21 7:04 ` Robert Schwebel
2009-04-21 7:13 ` Daniel Stenberg
2009-04-21 14:40 ` Wolfgang Denk
2009-04-21 14:54 ` Robert Schwebel
2009-04-21 18:21 ` Sascha Hauer
2009-04-21 20:08 ` Wolfgang Denk
2009-04-21 22:30 ` Sascha Hauer
2009-04-21 23:12 ` Wolfgang Denk
2009-04-22 7:17 ` Robert Schwebel
2009-04-22 13:58 ` Wolfgang Denk
2009-04-22 10:27 ` Ladislav Michl
2009-04-22 8:53 ` Heiko Schocher
2009-04-22 13:25 ` Ladislav Michl
2009-04-22 14:11 ` Wolfgang Denk
2009-04-22 14:26 ` Jerry Van Baren
2009-04-23 9:13 ` Ladislav Michl
2009-04-21 23:34 ` Ladislav Michl
2009-04-20 19:17 ` Wolfgang Denk
2009-04-20 19:12 ` Wolfgang Denk
2009-04-19 19:48 ` Robert Schwebel [this message]
2009-04-19 21:59 ` Kumar Gala
2009-04-19 23:21 ` Sascha Hauer
2009-04-20 6:50 ` Robert Schwebel
2009-04-18 18:41 ` Wolfgang Denk
2009-04-19 16:38 ` Kumar Gala
2009-04-20 12:02 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 15:26 ` [U-Boot] Kconfig support - menuconfig broken? Kumar Gala
2009-04-20 16:25 ` Kumar Gala
2009-04-20 19:08 ` [U-Boot] [ANNOUNCE] Kconfig support Wolfgang Denk
2009-04-20 19:58 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2009-04-20 15:39 Grant Likely
2009-04-20 18:22 ` Mike Frysinger
2009-04-20 18:42 ` Scott Wood
2009-04-20 19:23 ` Mike Frysinger
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=20090419194802.GU5367@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox