From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Tim Abbott <tabbott@ksplice.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: "m68k: Cleanup linker scripts using new linker script macros." and old binutils (was: Re: [PATCH] m68k: Atari EtherNAT - Nicolas Pitre has a new email address)
Date: Sun, 10 Jan 2010 21:29:23 +0100 [thread overview]
Message-ID: <m21vhxln4s.fsf@igel.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1001102020420.19754@zirkon.biophys.uni-duesseldorf.de> (Michael Schmitz's message of "Sun, 10 Jan 2010 21:12:59 +0100 (CET)")
Michael Schmitz <schmitz@biophys.uni-duesseldorf.de> writes:
> And indeed, the old script places the init task data between .init_end and _end.
This is exactly your problem. The bootloader puts the bootinfo
structure at _end, and the kernel reads it from there. But in your
non-working kernel that overlaps the init task structure.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-01-10 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 9:28 "m68k: Cleanup linker scripts using new linker script macros." and old binutils (was: Re: [PATCH] m68k: Atari EtherNAT - Nicolas Pitre has a new email address) Geert Uytterhoeven
2010-01-10 12:44 ` Andreas Schwab
2010-01-10 16:05 ` Tim Abbott
2010-01-10 20:12 ` Michael Schmitz
2010-01-10 20:29 ` Andreas Schwab [this message]
2010-01-10 20:40 ` Andreas Schwab
2010-01-11 2:28 ` Michael Schmitz
2010-01-11 20:08 ` Michael Schmitz
2010-03-07 18:38 ` Tim Abbott
2010-03-27 7:13 ` Michael Schmitz
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=m21vhxln4s.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitz@biophys.uni-duesseldorf.de \
--cc=tabbott@ksplice.com \
/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