From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] arm: fix kernel image size
Date: Tue, 21 Jun 2016 03:57:20 -0700 [thread overview]
Message-ID: <20160621105720.GK22406@atomide.com> (raw)
In-Reply-To: <20160621103810.GI22406@atomide.com>
* Tony Lindgren <tony@atomide•com> [160621 03:41]:
> * Russell King - ARM Linux <linux@armlinux•org.uk> [160621 02:50]:
> >
> > There isn't really an answer which will always work for this problem,
> > as I've already detailed in a previous thread discussing the issue.
> > Adding a zImage header don't fix the problem.
>
> Well how about we change both comments and code to use a value
> that works?
Maybe zImage size + MAX_RODATA_SZ + 4x zImage size?
Then the MAX_RODATA_SZ could be 2 or 4 MB or whatever we
think is sufficient to kick the can until we have a better
solution.
Regards,
Tony
next prev parent reply other threads:[~2016-06-21 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 19:44 [PATCH 0/2] Simple fix to the ARM kexec tools implementation Russell King - ARM Linux
2016-06-17 19:44 ` [PATCH 1/2] arm: take account of TEXT_OFFSET for subsequent images Russell King
2016-06-17 19:44 ` [PATCH 2/2] arm: fix kernel image size Russell King
2016-06-21 7:43 ` Tony Lindgren
2016-06-21 9:47 ` Russell King - ARM Linux
2016-06-21 10:38 ` Tony Lindgren
2016-06-21 10:57 ` Tony Lindgren [this message]
2016-06-21 15:44 ` Russell King - ARM Linux
2016-06-21 16:55 ` Tony Lindgren
2016-06-21 21:51 ` Russell King - ARM Linux
2016-06-22 7:36 ` Tony Lindgren
2016-06-22 8:29 ` Russell King - ARM Linux
2016-06-22 8:51 ` Tony Lindgren
2016-06-21 11:02 ` Mason
2016-06-21 6:11 ` [PATCH 0/2] Simple fix to the ARM kexec tools implementation Pratyush Anand
2016-06-21 8:20 ` Russell King - ARM Linux
2016-06-23 0:41 ` Simon Horman
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=20160621105720.GK22406@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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