From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Subject: Re: [PATCH V2] ARM: dts: bcm283x: Reserve first page for firmware Date: Sun, 14 May 2017 14:50:07 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Phil Elwell , linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Cc: Rob Herring , Mark Rutland , Russell King , Florian Fainelli , bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Stefan Wahren , Eric Anholt List-Id: devicetree@vger.kernel.org Am 09.05.2017 um 11:04 schrieb Phil Elwell: > The Raspberry Pi startup stub files for multi-core BCM27XX processors Curiously, while this V2 was rebased to apply against the bcm283x rather than bcm2710 file, it changed the text from BCM283X to BCM27XX. > make the secondary CPUs spin until the corresponding mailbox is > written. These stubs are loaded at physical address 0x00000xxx (as seen > by the ARMs), but this page will be reused by the kernel unless it is > explicitly reserved, causing the waiting cores to execute random code. > > Use the /memreserve/ Device Tree directive to mark the first page as > off-limits to the kernel. > > See: https://github.com/raspberrypi/linux/issues/1989 > > Signed-off-by: Phil Elwell > --- > > Changes in V2: > - Rebase against linux-next > - Drop downstream-only patch > > arch/arm/boot/dts/bcm283x.dtsi | 2 ++ > 1 file changed, 2 insertions(+) Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html