From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: head-common.S: relocate atags area if necessary
Date: Sat, 19 Oct 2013 18:19:34 +0200 [thread overview]
Message-ID: <5262B116.50807@gmail.com> (raw)
In-Reply-To: <20131019161314.GK25034@n2100.arm.linux.org.uk>
On 10/19/2013 06:13 PM, Russell King - ARM Linux wrote:
> On Sat, Oct 19, 2013 at 06:10:16PM +0200, Daniel Mack wrote:
>> Well, I totally see your point. However, we have machines out there that
>> won't update via kexec due to this, and fixing kexec is unfortunately
>> not an option, as updating anything would involve kexec'ing into an
>> update kernel again. So out only chance is to fix up the dtb location in
>> early boot code.
>>
>> You might say my case is special, and you're most probably right. I see
>> that trying to fix things is opening a can of worms.
>>
>> So - no worries, we'll just keep that patch around locally as it 'works
>> for me' (tm) :)
>
> How about fixing kexec to work properly anyway, so that at a later date
> you can drop that patch?
I'll have a look on how to properly fix this in kexec, yes.
However, new images have to stay compatible to old versions to update
from, so we'll not be able to drop the patch any time soon :(
Daniel
prev parent reply other threads:[~2013-10-19 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 16:12 [PATCH v2] ARM: head-common.S: relocate atags area if necessary Daniel Mack
2013-10-18 16:29 ` Russell King - ARM Linux
2013-10-18 17:09 ` Daniel Mack
2013-10-18 17:54 ` Russell King - ARM Linux
2013-10-19 15:15 ` Nicolas Pitre
2013-10-19 16:10 ` Daniel Mack
2013-10-19 16:13 ` Russell King - ARM Linux
2013-10-19 16:19 ` Daniel Mack [this message]
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=5262B116.50807@gmail.com \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).