From: u.kleine-koenig@pengutronix.de (Uwe =?iso-8859-1?Q?Kleine-K=F6nig?=) Date: Mon, 11 Oct 2010 11:24:24 +0200 Subject: [PATCH] ARM: allow, but warn, when issuing ioremap() on RAM In-Reply-To: <20101011090212.GA27153@n2100.arm.linux.org.uk> References: <20101008175308.GA10975@n2100.arm.linux.org.uk> <20101008230451.GB10975@n2100.arm.linux.org.uk> <20101008232539.GA28697@kroah.com> <20101008234448.GD10975@n2100.arm.linux.org.uk> <20101009092127.GB20975@n2100.arm.linux.org.uk> <20101011083508.GW29673@pengutronix.de> <20101011090212.GA27153@n2100.arm.linux.org.uk> Message-ID: <20101011092424.GX29673@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 11, 2010 at 10:02:12AM +0100, Russell King - ARM Linux wrote: > On Mon, Oct 11, 2010 at 10:35:08AM +0200, Uwe Kleine-K?nig wrote: > > Alternatively when calling fixup only after parse_tags in setup_arch() > > it worked. But I guess this change is not for discussion. > > OTOH I wonder why fixup gets passed meminfo. It's not very useful if > > it's not yet filled. > > Because, rather than pass in ATAGs or set the memory on the command line, > they instead wanted to hard-code it in C - something which still happens > today: > > arch/arm/mach-msm/board-halibut.c > arch/arm/mach-msm/board-mahimahi.c > arch/arm/mach-msm/board-sapphire.c > arch/arm/mach-msm/board-trout.c > arch/arm/mach-pxa/eseries.c > arch/arm/mach-pxa/spitz.c > arch/arm/mach-s3c2412/mach-smdk2413.c > arch/arm/mach-s3c2412/mach-vstms.c > arch/arm/mach-tegra/board-harmony.c > > This is part of the on-going pain of poor quality boot loaders. Yep, so (at least regarding the memory layout) the name "fixup" is wrong, it's more "initializ"ish. So what now? Do the memory reservation in mdesc->reserve as Felipe suggested? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |