From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issue with running commands
Date: Mon, 02 Jul 2012 23:07:00 +0200 [thread overview]
Message-ID: <20120702210700.0393D2026C1@gemini.denx.de> (raw)
In-Reply-To: <CAM6zRufYHPfuSNxEAtOaoCTyKpYRGFn0U6+YxkNCtD6_cL2j6g@mail.gmail.com>
Dear Sughosh Ganu,
In message <CAM6zRufYHPfuSNxEAtOaoCTyKpYRGFn0U6+YxkNCtD6_cL2j6g@mail.gmail.com> you wrote:
>
> While testing on hawkboard with the latest commit, i hit an issue of
> commands not being accepted.
>
> hawkboard > reset
> Unknown command '?????' - try 'help> '
> hawkboard >
>
> Running git bisect showed that this is caused due to commit 054ea170f271:
> cmd_mem: cmp: unify size code paths. Has anyone seen this issue -- i don't
> think this is board/arch specific.
You must have a different kind of problem with your board. Commit
054ea170f271 is only changing the code of common/cmd_mem.c, which is
not used in any way by the reset command or by the command handler or
so - this cannot be causing such an effect; it could only trigger
another problem by changing code size or alignment or such.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It is easier to write an incorrect program than understand a correct
one.
next prev parent reply other threads:[~2012-07-02 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 19:24 [U-Boot] Issue with running commands Sughosh Ganu
2012-07-02 21:07 ` Wolfgang Denk [this message]
2012-07-03 6:22 ` Christian Riesch
2012-07-03 18:35 ` Sughosh Ganu
2012-07-03 23:28 ` Graeme Russ
2012-07-05 6:48 ` Sughosh Ganu
2012-07-05 8:01 ` Prabhakar Lad
2012-07-10 13:53 ` Sughosh Ganu
2012-07-27 7:18 ` Sughosh Ganu
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=20120702210700.0393D2026C1@gemini.denx.de \
--to=wd@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