From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Mon, 7 Feb 2011 07:55:32 -0800 Subject: [RFC] arm: Defer lookup of machine_type and vet of atags to setup.c In-Reply-To: References: <20110111104051.GA11039@n2100.arm.linux.org.uk> <20110111153630.GB2707@angua.secretlab.ca> <20110111154833.GF11039@n2100.arm.linux.org.uk> <20110112155215.GB11039@n2100.arm.linux.org.uk> <20110112172552.GF11039@n2100.arm.linux.org.uk> Message-ID: <20110207155532.GD20795@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Grant Likely [110112 09:48]: > On Wed, Jan 12, 2011 at 10:25 AM, Russell King - ARM Linux > wrote: > > On Wed, Jan 12, 2011 at 10:16:44AM -0700, Grant Likely wrote: > >> On Wed, Jan 12, 2011 at 9:53 AM, Nicolas Pitre wrote: > >> > On Wed, 12 Jan 2011, Grant Likely wrote: > >> > > >> >> Actually it looks like the real problem is that the mmu has been > >> >> turned on, but the virtual mappings for devices have not yet been > >> >> established, and so the debug macros aren't using a valid address. > >> > > >> > A temporary virtual mapping should be there -- look for addruart in > >> > head.S. > >> > >> Hi Russell and Nicolas, > >> > >> Oops, yes all the early debug stuff works fine. ?Stupid human trick on > >> my end, but I've sorted it out now. ?Thanks for the help. ?I'll have > >> patches to post later today. > > > > I just hacked this up, and on Versatile (real hardware) it produces > > the below for an invalid r1 value - and of course works for a proper r1 > > value. > > Heh, that look pretty close to identical to what I was just about to send. > > Acked-by: Grant Likely Tested-by: Tony Lindgren