From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Enabling the data size parameter for memory commands like "md"?
Date: Tue, 14 Oct 2003 14:02:40 +0200 [thread overview]
Message-ID: <87y8vo10yn.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0310141425340.4900-100000@melkki.cs.Helsinki.FI> (Pasi Huhtiniemi's message of "Tue, 14 Oct 2003 14:33:21 +0300 (EEST)")
Hi Pasi,
> I'm playing around with a day-old cvs snapshot of U-Boot, using it with
> "make at91rm9200dk_config". My problem is the same with 0.4.0.
>
>>From the source (and from the usage help) I understand that at least the
> memory commands like "md" should accept (optional) data size parameter
> (.b/.w/.l) as the first parameter.
>
> How do you enable this? In my environment they don't work: 1) argv[0] is
> the command itself (like "md"), not the data size parameter from where the
> source tries to read it and 2) if I give the data size parameter, the
> upper framework counts the amount of parameters to be illegal and
> therefore certain commands give me an error message (the short usage).
>
> I suppose there is a #define missing? What is it? I could not quickly find
> it grepping the source, googling the net / mailing list archives.
I think you misunderstood the docs. The size specification is not a
parameter but rather a part of the command name - that's why the
source looks at argv[0]. Check out the examples in our
documentation[1].
Cheers
Detlev
[1] https://www.denx.de/twiki/bin/view/DULG/UBootCmdGroupMemory#Section_5.9.2.5.
--
You see, the best way to solve a problem is to rigorously define it in
terms of other people's problems, and then run away quickly.
-- Roland McGrath
next prev parent reply other threads:[~2003-10-14 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 11:33 [U-Boot-Users] Enabling the data size parameter for memory commands like "md"? Pasi Huhtiniemi
2003-10-14 12:02 ` Detlev Zundel [this message]
2003-10-14 12:19 ` 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=87y8vo10yn.fsf@deepthought.outer.space.org \
--to=dzu@denx.de \
--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