From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>,
Greg Ungerer <gerg@kernel.org>,
linux-m68k@lists.linux-m68k.org, geert@linux-m68k.org
Subject: Re: m54418: ELF execution issues
Date: Sat, 08 Jun 2024 09:37:23 +0200 [thread overview]
Message-ID: <878qzfopfw.fsf@linux-m68k.org> (raw)
In-Reply-To: <2f52ce9a-2083-7e4d-21e1-204e13d3e8e3@gmail.com> (Michael Schmitz's message of "Sat, 8 Jun 2024 14:15:22 +1200")
On Jun 08 2024, Michael Schmitz wrote:
> TASK_SIZE, TASK_UNMAPPED_BASE and ELF_ET_DYN_BASE all appear related
> according to rules that I haven't found spelled out anywhere.
There is only one rule: TASK_UNMAPPED_BASE and ELF_ET_DYN_BASE must be
smaller than TASK_SIZE.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-06-08 7:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 19:11 Kernel Image Format Issue - Coldfire mcf54418 CPU Failing to Boot Jean-Michel Hautbois
2024-05-14 20:16 ` Michael Schmitz
2024-05-15 7:56 ` Jean-Michel Hautbois
2024-05-15 10:29 ` Greg Ungerer
2024-05-15 11:10 ` Jean-Michel Hautbois
2024-05-16 12:43 ` Greg Ungerer
2024-05-16 13:31 ` Jean-Michel Hautbois
2024-05-21 13:46 ` Greg Ungerer
2024-05-27 13:19 ` Jean-Michel Hautbois
2024-05-28 6:32 ` Jean-Michel Hautbois
2024-05-28 7:47 ` John Paul Adrian Glaubitz
2024-05-28 8:04 ` Jean-Michel Hautbois
2024-05-28 13:59 ` Greg Ungerer
2024-06-03 10:54 ` m54418: ELF execution issues Jean-Michel Hautbois
2024-06-06 14:33 ` Greg Ungerer
2024-06-07 5:27 ` Jean-Michel Hautbois
2024-06-08 2:15 ` Michael Schmitz
2024-06-08 6:58 ` Jean-Michel Hautbois
2024-06-08 7:37 ` Andreas Schwab [this message]
2024-06-07 6:57 ` Geert Uytterhoeven
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=878qzfopfw.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.org \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.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 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.