From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12
Date: Sat, 21 Jul 2012 08:04:09 +1000 [thread overview]
Message-ID: <5009D5D9.5090606@gmail.com> (raw)
In-Reply-To: <5009D05C.1000004@freescale.com>
Hi Scott,
On 07/21/2012 07:40 AM, Scott Wood wrote:
> On 07/20/2012 04:34 PM, Graeme Russ wrote:
>> Hi Kim & Marek,
>>
>> On 07/21/2012 07:09 AM, Marek Vasut wrote:
>>> Dear Kim Phillips,
>>>
>>>> On Mon, 16 Jul 2012 23:30:49 +0200
>>>>
>>>> Detlev Zundel <dzu@denx.de> wrote:
>>>>> as promised, here are my expanded notes from the BoF meeting at LSM2012
>>>>> last week. It was a pleasure to get some core developers into one room
>>>>
>>>> Any word on Kconfig support?
>>>>
>>>> Kim
>>>
>>> I was digging in it for a bit, but then Graeme took over.
>>
>> I have started on it - I've ported over the Kbuild infrastructure into a
>> dedicated 'kbuild' makefile which is called from the main makefile. This
>> make modifications to the existing makefile very minimal
>>
>> Now it's just a case of building all the Kconfig files which is, to say the
>> least, a massive task. I have a lot of other things going on, so
>> unfortunately progress is slow
>
> How about a transitional phase, where a symbol can either be a kconfig
> symbol or handled the old way via the board config file? That way,
> custodians/maintainers could handle the conversion of their own symbols
> (with the expectation that this be done within a reasonable timeframe).
Well the plan in to have 'make xyz_config' produce the equivalent .config
file (which it pretty much does anyway) - You can then use Kconfig to tweak
the board config
Or use Kconfig to create a config from scratch
Regards,
Graeme
next prev parent reply other threads:[~2012-07-20 22:04 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:30 [U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12 Detlev Zundel
2012-07-16 23:11 ` Graeme Russ
2012-07-17 10:37 ` Stefan Roese
2012-07-17 12:10 ` Graeme Russ
2012-07-17 12:15 ` Graeme Russ
2012-07-18 7:21 ` Wolfgang Denk
2012-07-18 23:37 ` Graeme Russ
2012-07-21 14:46 ` Marek Vasut
2012-07-23 1:33 ` Graeme Russ
2012-07-23 1:47 ` Marek Vasut
2012-07-23 2:07 ` Graeme Russ
2012-07-23 2:13 ` Marek Vasut
2012-07-23 7:43 ` Andy Pont
2012-07-23 6:27 ` Wolfgang Denk
2012-07-23 6:20 ` Wolfgang Denk
2012-07-23 21:16 ` Tom Rini
2012-07-23 22:15 ` Marek Vasut
[not found] ` <500DD2FA.4060800@boundarydevices.com>
2012-07-23 23:06 ` Marek Vasut
2012-07-23 23:37 ` Eric Nelson
2012-07-23 6:16 ` Wolfgang Denk
2012-07-25 19:47 ` Tom Rini
2012-07-27 14:17 ` Marek Vasut
2012-07-20 22:51 ` Tom Rini
2012-07-21 1:27 ` Marek Vasut
2012-07-21 4:28 ` Graeme Russ
2012-07-23 16:49 ` Tom Rini
2012-07-23 16:44 ` Tom Rini
2012-07-23 17:17 ` Marek Vasut
2012-07-23 17:28 ` Tom Rini
2012-07-23 18:11 ` Marek Vasut
2012-07-23 19:09 ` Tom Rini
2012-07-23 22:16 ` Marek Vasut
2012-07-18 7:41 ` Wolfgang Denk
2012-07-20 3:57 ` Mike Frysinger
2012-07-21 14:40 ` Marek Vasut
2012-07-23 20:53 ` Tom Rini
2012-07-23 22:14 ` Marek Vasut
2012-07-20 16:36 ` Kim Phillips
2012-07-20 21:09 ` Marek Vasut
2012-07-20 21:34 ` Graeme Russ
2012-07-20 21:40 ` Scott Wood
2012-07-20 22:04 ` Graeme Russ [this message]
2012-07-21 14:41 ` Marek Vasut
2013-02-18 6:55 ` Simon Glass
2013-02-18 9:59 ` Wolfgang Denk
2013-02-18 10:40 ` Graeme Russ
2013-02-18 12:39 ` Marek Vasut
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=5009D5D9.5090606@gmail.com \
--to=graeme.russ@gmail.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.