From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANNOUNCE] Kconfig support
Date: Mon, 20 Apr 2009 00:56:53 -0400 [thread overview]
Message-ID: <200904200056.54682.vapier@gentoo.org> (raw)
In-Reply-To: <20090419195046.GV5367@pengutronix.de>
On Sunday 19 April 2009 15:50:46 Robert Schwebel wrote:
> On Sat, Apr 18, 2009 at 03:18:32PM -0400, Mike Frysinger wrote:
> > so, does it make sense to look at the feature set that v2 brings to
> > the table and get it into u-boot v1? ive never personally looked at
> > v2, but if it means i need to redo all of my Blackfin core/board code,
> > that doesnt sound very appealing at all ...
>
> We have even Blackfin support in v2, and that for almost all of the time
> it is actually there. Sure - if you need feature completeness, you'll
> have to stay with v1. Our aim is a sane design, and I'm still not
> convinced that this is even possible with v1 any more.
unless it's the code that ive been committing to mainline via the blackfin git
tree, then it really doesnt matter (and it looks that way) since, as you say,
it is not even close to feature parity.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090420/e38f54be/attachment.pgp
next prev parent reply other threads:[~2009-04-20 4:56 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 [this message]
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
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=200904200056.54682.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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