linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Nicolas Pitre <nico@fluxnic.net>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Jeremy Kerr <jeremy.kerr@canonical.com>
Subject: Re: [RFC] arm: Defer lookup of machine_type and vet of atags to setup.c
Date: Mon, 7 Feb 2011 07:55:32 -0800	[thread overview]
Message-ID: <20110207155532.GD20795@atomide.com> (raw)
In-Reply-To: <AANLkTi=dNaOF0wxU+OYEKiWfoGeVKGnqvF3gK8-mQjo5@mail.gmail.com>

* Grant Likely <grant.likely@secretlab.ca> [110112 09:48]:
> On Wed, Jan 12, 2011 at 10:25 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> 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 <nico@fluxnic.net> 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 <grant.likely@secretlab.ca>

Tested-by: Tony Lindgren <tony@atomide.com>

      reply	other threads:[~2011-02-07 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  2:15 [RFC] arm: Defer lookup of machine_type and vet of atags to setup.c Grant Likely
2011-01-11  3:19 ` Nicolas Pitre
2011-01-11  5:21   ` Grant Likely
2011-01-11 10:40 ` Russell King - ARM Linux
2011-01-11 15:36   ` Grant Likely
2011-01-11 15:48     ` Russell King - ARM Linux
2011-01-12 15:46       ` Grant Likely
2011-01-12 15:52         ` Russell King - ARM Linux
2011-01-12 16:24           ` Grant Likely
2011-01-12 16:32             ` Russell King - ARM Linux
2011-01-12 16:53             ` Nicolas Pitre
2011-01-12 17:16               ` Grant Likely
2011-01-12 17:25                 ` Russell King - ARM Linux
2011-01-12 17:49                   ` Grant Likely
2011-02-07 15:55                     ` Tony Lindgren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110207155532.GD20795@atomide.com \
    --to=tony@atomide.com \
    --cc=catalin.marinas@arm.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jeremy.kerr@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).