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?
