From: baccala@freesoft.org
To: linuxppc-dev@lists.linuxppc.org
Subject: zimage relocation
Date: Thu, 11 Feb 1999 01:03:01 -0500 (EST) [thread overview]
Message-ID: <199902110602.AAA23709@lists.linuxppc.org> (raw)
Hi -
I'm having trouble with the recent (~ 1.5 weeks ago) changes to
arch/ppc/boot/misc.c, relating to MBX image relocation. On my IBM 860
laptop, the relocation never used to run ('cause I wasn't using
ramdisks), but now it does, and the image doesn't decompress properly.
If I comment out this section of code in misc.c, everything works fine:
if ( (( (unsigned long)zimage_start <= 0x01000000 ) && initrd_start)
|| needs_reloc)
{
memcpy ((void *)PAGE_ALIGN(-PAGE_SIZE+(unsigned long)end_avail-zimage_size),
(void *)zimage_start, zimage_size );
zimage_start = (char *)PAGE_ALIGN(-PAGE_SIZE+(unsigned long)end_avail-zimage_size);
end_avail = (char *)zimage_start;
puts("relocated to: "); puthex((unsigned long)zimage_start);
puts(" ");
puthex((unsigned long)zimage_size+(unsigned long)zimage_start);
puts("\n");
}
Clearly, the machine is responding to
needs_reloc, since my initrd_start is 0, no ramdisk. needs_reloc was
set by the Motorola detect code. So what does the Motorola detect
actually do, why would it be triggered on my IBM 860, and what should
be done about it?
--
-bwb
Brent Baccala
baccala@freesoft.org
-------------------------------------------------------------------------
To receive periodic news about what's happening at freesoft.org, send
email to "announce@freesoft.org", with "SUBSCRIBE" as the message, i.e:
echo SUBSCRIBE | mail announce@freesoft.org
-------------------------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-02-11 6:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199902110602.AAA23709@lists.linuxppc.org \
--to=baccala@freesoft.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).