[U-Boot-Users] New commands
Leonid at a-k-a.net
Wed May 16 21:17:40 CEST 2007
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
> 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
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
> the #defined bit flags.
> This has come up a couple of times, but no good solution has shaken
> 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
> I really cannot think of any other way to maintain the current method
> of compile-time selection and add expansion. Discussion thread here:
> 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
That can be another way of doing that.
More information about the U-Boot