public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulfs@dof.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Adding new commands
Date: Mon, 16 Oct 2006 20:09:39 +0200	[thread overview]
Message-ID: <011e01c6f14e$44fe56e0$01c4af0a@atmel.com> (raw)
In-Reply-To: 45337173.2070801@schweigstill.de

Andreas Schweigstill wrote:
> Dear llandre!
>
> llandre schrieb:
>> #define CFG_CMD_NEW1 0x8000000000000000ULL
>> #define CFG_CMD_NEW2 ???
>>
>> IIUC we have 64 bits available for the commands and 63 commands are
>> already defined. So how to define more than 64 commands?
>
> This is indeed a big problem which will occur to nearly every
> developer who implements new commands. CFG_CMD_* and CONFIG_COMMANDS
> are only used for preprocessor evaluation; they don't seem to be used
> in object code. But they rely on the ULL (unsigned long long int)
> type; I don't think that there is something like a 128bit type which
> can be used directly for logical AND operations.
>
> For new command there could be used another macro like
> CONFIG_COMMANDS2 and CFG_CMD2_* for the configuration values.
>


The number of options is growing all the time.
Maybe it would be a good idea to adopt the Kconfig system.
Wolfgang does not like to have a lot of files like they do in the kernel
but you do not have to split it up like they do it in the kernel.
You could have a single Config.in file.


Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM:  +46 (706) 22 44 57
Tel:     +46  (8) 441 54 22
Fax:     +46 (8) 441 54 29
Mail: Box 2033  174 02 Sundbyberg
Visit: Kavalleriv?gen 24
          174 58 Sundbyberg'
Sweden

  reply	other threads:[~2006-10-16 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 11:10 [U-Boot-Users] Adding new commands llandre
2006-10-16 11:48 ` Andreas Schweigstill
2006-10-16 18:09   ` Ulf Samuelsson [this message]
2006-10-16 20:06 ` Wolfgang Denk
2006-10-16 20:24   ` Ulf Samuelsson
2006-10-16 21:19     ` Wolfgang Denk
2006-10-16 20:45   ` Tolunay Orkun
2006-10-17  7:19   ` llandre
2006-10-17  9:57     ` Brent Cook
2006-10-17 10:35       ` llandre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='011e01c6f14e$44fe56e0$01c4af0a@atmel.com' \
    --to=ulfs@dof.se \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox