From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org>
Message-ID: <5262B116.50807@gmail.com>
Date: Sat, 19 Oct 2013 18:19:34 +0200
From: Daniel Mack <zonque@gmail.com>
MIME-Version: 1.0
Subject: Re: [PATCH v2] ARM: head-common.S: relocate atags area if necessary
References: <1382112776-20300-1-git-send-email-zonque@gmail.com>
 <20131018162956.GE25034@n2100.arm.linux.org.uk> <52616B56.10407@gmail.com>
 <20131018175414.GF25034@n2100.arm.linux.org.uk>
 <alpine.LFD.2.03.1310191059290.1951@syhkavp.arg> <5262AEE8.5010505@gmail.com>
 <20131019161314.GK25034@n2100.arm.linux.org.uk>
In-Reply-To: <20131019161314.GK25034@n2100.arm.linux.org.uk>
List-Id: <kexec.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/options/kexec>,
 <mailto:kexec-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/kexec/>
List-Post: <mailto:kexec@lists.infradead.org>
List-Help: <mailto:kexec-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/kexec>,
 <mailto:kexec-request@lists.infradead.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "kexec" <kexec-bounces@lists.infradead.org>
Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: kexec@lists.infradead.org, neumann@teufel.de, linux-arm-kernel@lists.infradead.org, Nicolas Pitre <nico@fluxnic.net>

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


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec