All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_CMD_.... configuration space running out!!
Date: Thu, 18 Dec 2003 12:08:15 +1300	[thread overview]
Message-ID: <3FE0E1DF.208@tait.co.nz> (raw)

Greetings

The number of commands being added to U-Boot seems in danger of 
overflowing the selection mechanism. Are there any plans to expand the 
process to more than 64 bits/commands that are agregated into 
CONFIG_COMMANDS or should there be individual defines to turn commands 
on/off.

The reason I ask is that I've just implemented a bash style 'test' 
command so I can check the values of memory locations with conditional 
code during boot and I note there are only 2 bits left!!

Note:
test syntax as per binary integer comparisons with the option of a unary 
indirection operator on either expression.
eg. 'test *40000 -eq 12345678'
checks location 40000 for the value 12345678. I've only implemented 32 
bit word indirection - does anyone think it useful to provide half-word 
and byte as well - in which case what should the syntax look like?


-- 
Robin Gilks
Senior Design Engineer          Phone: (+64)(3) 357 1569
Tait Electronics                Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks at tait.co.nz
New Zealand

             reply	other threads:[~2003-12-17 23:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 23:08 Robin Gilks [this message]
2003-12-18  2:07 ` [U-Boot-Users] CFG_CMD_.... configuration space running out!! Jon Diekema
2003-12-18  4:20   ` Robin Gilks
2003-12-19 20:49     ` Wolfgang Denk
2004-01-04 22:21       ` Robin Gilks
2004-01-04 23:03         ` Wolfgang Denk
2003-12-19 20:46   ` Wolfgang Denk

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=3FE0E1DF.208@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.