[U-Boot-Users] [PATCH] lkc support for U-Boot

Holger Schurig h.schurig at mn-logistik.de
Wed Nov 6 14:03:16 CET 2002

> configured by the "user" should be CONFIG_, internal definitions CFG_.

But the bootdelay is NOT an internal definition. And many other CFG_ aren't 
internal, too.   Okay, I can see that CFG_CMD_ are internal definitions and 
that only CONFIG_COMMANDS is user definiable. However, lkc will not easily 
handle this. 

This is because LKC can

* only handle config vars that start with CONFIG_
* has only types like int, string, bool, but not bitmask

and CONFIG_COMMANDS is a bitmask. Of course one could put

define COMMAND
  int "Which commands to allow"
  default <some value>
     This is really a bitmask. Add the following values to get your result:
     1   for bdinfo
     2   for loads
     4   for loadb

but that would be a step backwords. 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.

If we want to use lkc for this, we have to transfer files like cmd_elf.c from




Therefore, I assume that lkc is intrusive. Either change the whole u-boot or 
nothing at all. As in the linux kernel: it's not changed totally,

MN-Logistik GmbH         http://www.mn-logistik.de
Holger Schurig
Dieselstr. 18
61191 Rosbach v.d.Höhe
Tel: 06003/9141-0        Fax: 06003/9141-49

More information about the U-Boot mailing list