linux-kernel - Re: [PATCH] ARM: zImage: Allow DTB to override broken ATAG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140614203356.GD3853@xo-6d-61-c0.localdomain>
Date:	Sat, 14 Jun 2014 22:33:56 +0200
From:	Pavel Machek <pavel@....cz>
To:	Andreas F?rber <afaerber@...e.de>
Cc:	Bjorn Andersson <bjorn@...o.se>,
	Uwe Kleine-K?nig <u.kleine-koenig@...gutronix.de>,
	Bjorn Andersson <bjorn.andersson@...ymobile.com>,
	Russell King <linux@....linux.org.uk>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-arm-msm <linux-arm-msm@...r.kernel.org>,
	Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: [PATCH] ARM: zImage: Allow DTB to override broken ATAG_MEM

On Wed 2014-05-07 23:24:18, Andreas F?rber wrote:
> Am 07.05.2014 17:29, schrieb Bjorn Andersson:
> > My problem is that the boot loader on every shipped Qualcomm MSM8x60, MSM8960
> > and APQ8064 based device passes ATAG_MEM with the incorrect start address. There
> > is no way to update the boot loader for these.
> 
> Chaining bootloaders comes to mind. This is being done on the Exynos5
> based Chromebooks, for instance.

You can easily start fixed u-boot from broken u-boot...

But I'm not sure that's the way to go. Perhaps your localised/ugly hack in board
init code is the way to go...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/