From: Oliver Fuchs <olivers.lists@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] relocate_code problem
Date: Tue, 06 Jul 2004 17:19:28 +0200 [thread overview]
Message-ID: <40EADF20.20424.AE0466@localhost> (raw)
In-Reply-To: <20040706080626.6309BC109F@atlas.denx.de>
From: Wolfgang Denk <wd@denx.de>
Date sent: Tue, 06 Jul 2004 10:06:21 +0200
> > of in_ram correctly, but the copied code is somehow shifted.
>
> Maybe it just looks shifted or repeated?
You are right. It was hard to accept the idea that the seen code was not within the RAM.
>
> You don't need much knowledge about assembler code. "grep" will just
> do fine (hint: search for "relocate_code", and probably you want to
> searchin the relevant directory with CPU specific code, i. e.
> "cpu/mpc8260/").
It was not the problem to find relocate_code. I was not smart enough to recognize
the nice little loop. Because the destination content did not change during relocate_code,
I thought it was done elsewhere.
> Best regards,
>
> Wolfgang Denk
Thanks,
Oliver Fuchs
next prev parent reply other threads:[~2004-07-06 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 7:52 [U-Boot-Users] relocate_code problem Oliver Fuchs
2004-07-06 8:06 ` Wolfgang Denk
2004-07-06 15:19 ` Oliver Fuchs [this message]
2004-07-06 21:10 ` 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=40EADF20.20424.AE0466@localhost \
--to=olivers.lists@gmx.net \
--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.