On Wednesday, May 16, 2007 11:42 AM Jerry Van Baren wrote:
I think you are missing the fundamental part of the problem: u-boot
uses
a #defined bitmap to enable and disable commands at compile time. The
#defined bitmap can hold, at most, 64 bits and 63 of those bits are used.
I am fully aware of that.
The fundamental limitation stems from the desire to enable/disable commands at compile time in conjunction with how many bits gcc (actually, the preprocessor) supports for #if conditional compilation. There are also implicit desires to use & and | to
combine
the #defined bit flags.
This has come up a couple of times, but no good solution has shaken
out.
At one time I proposed simply creating a second set of 64 bit command enable/disable #defines, but Wolfgang wasn't too keen on that
solution.
I really cannot think of any other way to maintain the current method
of compile-time selection and add expansion. Discussion thread here: http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/24647
I agree.
I personally sidestepped the issue by enabling and disabling my new "fdt" command based on whether CONFIG_OF_LIBFDT was defined or not, thereby not needing to use the last command control bit in the
#define.
That can be another way of doing that.
Leonid.