On Wed, May 29, 2013 at 09:47:34AM +0900, Masahiro Yamada wrote: > Hello, Simon. > > Please let me ask some more questions. > > By applying these series of commits, > U-Boot's config file scheme and Kconfig coexist. > > For example, scripts/Makefile.build includes > both auto.conf generated by Kconfig > and autoconf.mk derived from U-boot's config. > > -include include/config/auto.conf > -include $(objtree)/include/config/autoconf.mk > > I think the redundancy and dirtiness do not matter > if they are temporary. > > What I'd like to make clear is our goal. > It is intended to move all U-Boot's config files > to Kconfig over long time and > after that, delete U-Boot's config system. > Is this right?
Yes, long term.
>
> If the answer is yes, there are some macros
> I don't know how to port to Kconfig.
>
> For example,
> CONFIG_SYS_BAUDRATE_TABLE is defined like follows.
>
> #define CONFIG_SYS_BAUDRATE_TABLE {9600, 19200, 38400, 57600, 115200}
>
> To my knowledge this macro can not be described by Kconfig.
We would probably want to change it to something like:
- Do you want the standard baud rate table?
Yes: 9600/19200/38400/57600/115200
No: Prompt for string value of comma sep list of rates
And in the right header:
#ifdef CONFIG_SYS_STD_BAUD_RATE
#define BAUDRATTE_TABLE { 9600, .... }
#else
#define BAUDRATE_TABLE { CONFIG_SYS_PROMPTED_VALUE }
#endif
> And also, some config files still include macros without CONFIG_ prefix.
> For example, LINUX_BOOT_PARAM_ADDR, PHYS_SDRAM_1, PHYS_SDRAM_2, etc.
These don't belong in the config file, and need to be either in the
board or <asm/arch/> or similar construct instead.
--
Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
