> >
> > 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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
