linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jeremy.kerr@canonical.com (Jeremy Kerr)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: ARM Boot standard for passing device tree blob
Date: Fri, 26 Mar 2010 08:23:44 +0800	[thread overview]
Message-ID: <201003260823.44829.jeremy.kerr@canonical.com> (raw)
In-Reply-To: <20100325234053.GB26649@yookeroo>


> > > ===Required System State===
> > > *Quiesce all DMA
> > > *CPU register contents
> > > **r0 = 0
> > > **r1 = Linux machine number (as defined in the ARM Linux machine
> > > database) or 0
> >
> > 0 is a valid machine number.  What is your purpose of passing 0?
> 
> Presumably a machine number will need to be allocated to mean "use the
> device tree instead of fixed machine number info".

I've been using 0xffffffff to indicate that this is a 'device-tree' platform. 
The value isn't really important, just that we agree on something.

Cheers,


Jeremy

  reply	other threads:[~2010-03-26  0:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 15:11 RFC: ARM Boot standard for passing device tree blob Grant Likely
2010-03-25 21:04 ` Russell King - ARM Linux
2010-03-25 23:40   ` David Gibson
2010-03-26  0:23     ` Jeremy Kerr [this message]
2010-03-26  3:24   ` Grant Likely
2010-03-26 13:37   ` Catalin Marinas
2010-03-26 17:43     ` Mitch Bradley
2010-03-26 18:13       ` Grant Likely
2010-03-26 19:30         ` Nicolas Pitre
2010-03-26 19:52           ` Grant Likely
2010-03-26 23:03             ` Russell King - ARM Linux
2010-03-29 11:24               ` Dave P. Martin
2010-03-30  0:26                 ` Jamie Lokier
2010-03-30 13:32                   ` Dave P. Martin
2010-03-26 23:00       ` Russell King - ARM Linux
2010-03-31  1:10       ` Ben Dooks

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=201003260823.44829.jeremy.kerr@canonical.com \
    --to=jeremy.kerr@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).