[U-Boot-Users] [PATCH] lkc support for U-Boot
robert at schwebel.de
Wed Nov 6 15:17:56 CET 2002
On Wed, Nov 06, 2002 at 02:03:16PM +0100, Holger Schurig wrote:
> But the bootdelay is NOT an internal definition.
Then I suppose it is incorrect to make it a CONFIG_ variable.
> However, lkc will not easily handle this.
It will - but things have to be ported. The old system had a possible
configuration system in mind, but that doesn't mean that the old config
files can be used without changes...
> This is because LKC can
> * only handle config vars that start with CONFIG_
> * has only types like int, string, bool, but not bitmask
I see no problem with that.
> I'd rather have it like this
> menu "Command selection"
> define CMD_BDI
> bool "bdinfo command (board info)
> default y
> define CMD_LOADS
> bool "loads command (load srec file)
> default n
> define CMD_LOADB
> bool "loadb command (load binary file)
> default n
> and so on.
What's the problem with this variant?
> If we want to use lkc for this, we have to transfer files like cmd_elf.c from
> #if (CONFIG_COMMANDS & CFG_CMD_ELF)
> #ifdef CONFIG_CMD_ELF
The files have to be adapted - I don't understand the problem? As long
as not all board packages are ported just let the old ones use the same
configration files as before and let the new ones use .config.
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Braunschweiger Str. 79, 31134 Hildesheim, Germany
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
Visit us at the SPS/IPC/Drives 2002 in Nuernberg!
Hall 5, Booth 154 +++ Please contact us for details.
More information about the U-Boot