From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Kconfig: sync with linux kernel v2.6.35-4771-g1787985
Date: Sun, 8 Aug 2010 14:20:59 +0200 [thread overview]
Message-ID: <20100808122059.GN24069@game.jcrosoft.org> (raw)
In-Reply-To: <20100808120741.GA32022@merkur.ravnborg.org>
> >
> > also a small doc for the mandatory env and symbol will be nice for people to
> > integrate it as not everyone is also a kernel dev or maintainer
>
> I actually take this that integrating kconfig should be simpler.
> So it:
> a) should be documented using a HOW-TO
> b) we sould rely on very little outside scripts/kconfig
>
> The primary 'customer' is the kernel but it would be good
> to generalize stuff a bit more.
> This is by far the biggest task listed.
> I will add it to my mental TODO list - but no promises :-)
for barebox point of view just be able to change the projects name will be enough as most
of us if not all are kernel dev or maintainer
> >
> > and a last thing It will be nice to be able to set a value to a symbol from an
> > other one and not only select it
>
> I am not sure I see how this is usefull.
> Can you give me an example.
>
> Note: We recently had a patch where "select" was extended to
> specify an optional value.
> But my issue with that was that I failed to see the use of it so
> I was not happy with the extension.
>
> But I may have missed something!
ok take a look on arch/arm/mach-at91/Kconfig
as example for the
config BOARDINFO
default "Atmel at91rm9200-ek" if MACH_AT91RM9200EK
default "Atmel 91SAM9260-EK" if MACH_AT91SAM9260EK
default "Atmel at91sam9261-ek" if MACH_AT91SAM9261EK
default "Atmel at91sam9263-ek" if MACH_AT91SAM9263EK
default "Bucyrus MMC-CPU" if MACH_MMCCPU
default "Ronetix PM9261" if MACH_PM9261
default "Ronetix PM9263" if MACH_PM9263
if you change the board via the interface it will not be change and it will the same for
config ARCH_TEXT_BASE in some case
and I'll prefer to do set BOARDINFO="Atmel at91rm9200-ek" from the config MACH_AT91RM9200EK
hope it will be a good example
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-08 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 4:17 Jean-Christophe PLAGNIOL-VILLARD
2010-08-08 6:48 ` Sam Ravnborg
2010-08-08 9:06 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-08 12:07 ` Sam Ravnborg
2010-08-08 12:20 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-08-13 19:26 ` Sam Ravnborg
2010-08-14 4:35 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-14 6:51 ` Sam Ravnborg
2010-08-09 6:49 ` Robert Schwebel
2010-08-22 12:54 ` Peter Korsgaard
2010-08-23 2:51 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-18 15:15 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-21 10:27 ` Sascha Hauer
2010-08-21 11:35 ` Sam Ravnborg
2010-08-22 5:07 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-22 5:55 ` Sam Ravnborg
2010-08-22 13:48 ` Peter Korsgaard
2010-08-24 17:59 ` Uwe Kleine-König
2010-08-22 5:17 ` [PATCH v2] Kconfig: sync with linux kernel v2.6.36-rc1-168-ge36c886 Jean-Christophe PLAGNIOL-VILLARD
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=20100808122059.GN24069@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.org \
/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