From: Martin Hicks <mort@bork.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help understanding bd_t passing
Date: Tue, 28 Mar 2006 21:45:23 -0500 [thread overview]
Message-ID: <20060329024523.GR27792@bork.org> (raw)
In-Reply-To: <20060328221633.C39473535F7@atlas.denx.de>
On Wed, Mar 29, 2006 at 12:16:33AM +0200, Wolfgang Denk wrote:
>
> > So what the hacked version of u-boot (hacked by someone else) currently
> > does is declare a simple bd_t in cmd_go and pass the address of that
> > as the only parameter when we jump to addr.
>
> This is plain wrong/ "go" was never designed to bootLinux. Please
> RTFM.
Okay, I'm *glad* that this is wrong. It didn't look like it could work.
I just assumed that the guy who was doing this job before had clue;
obviously a poor assessment.
Thanks for the pointer Wolfgang.
mh
--
Martin Hicks || mort at bork.org || PGP/GnuPG: 0x4C7F2BEE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060328/b9a4666d/attachment.pgp
prev parent reply other threads:[~2006-03-29 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 17:13 [U-Boot-Users] help understanding bd_t passing Martin Hicks
2006-03-28 22:16 ` Wolfgang Denk
2006-03-29 2:45 ` Martin Hicks [this message]
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=20060329024523.GR27792@bork.org \
--to=mort@bork.org \
--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