From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANNOUNCE] Kconfig support
Date: Mon, 20 Apr 2009 14:02:39 +0200 [thread overview]
Message-ID: <20090420120239.GC19818@game.jcrosoft.org> (raw)
In-Reply-To: <04E5C169-DA06-45C6-9502-4DD16CAF19D1@kernel.crashing.org>
On 11:38 Sun 19 Apr , Kumar Gala wrote:
>
> On Apr 18, 2009, at 11:25 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
>> Hi all,
>>
>> I've upload on the u-boot-arm tree in kconfig branch
>> some patch on which I work to all us to use Kconfig
>>
>> It's a dev branch not all patch are perfect
>> but it will be nice if other could help to finish it
>> and help me to create all the Kconfig files
>
> Beyond adding Kconfig's what's left to be done?
I've write a first batch of the generic Kconfig
for commmands, env, fs, disk, lib_generic and drivers
I've start to add the at91 arm arch Kconfig files
currently you can generate a .config and su defconfig
the autoconf.h header is generated
and the Kconfig customisation is started also
I've in mind to start by adding a arm arch with its boards
and merge them to the defconfig instead of the old way
but it's not already integreated
it will be nice to help me by doing the same for other arch
and improve the kconfig integeration and generic file
Best Regards,
J.
next prev parent reply other threads:[~2009-04-20 12:02 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
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 [this message]
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=20090420120239.GC19818@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox