devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
To: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: more pedantic proofing of DTSpec version 0.1
Date: Tue, 5 Sep 2017 17:20:12 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1709051719460.5307@localhost.localdomain> (raw)
In-Reply-To: <59AF139B.5090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Tue, 5 Sep 2017, Frank Rowand wrote:

> On 08/31/17 13:56, Rob Herring wrote:
> > On Sat, Aug 26, 2017 at 10:50:46AM -0400, Robert P. J. Day wrote:
> >>
>
> < snip >
>
> >> p. 25: table 3.6, the acronym "PIR" comes out of nowhere, perhaps
> >> explain it the first time?
> >
> > I'm drawing a blank as to what that is.
>
> According to the Mindshare book: PowerPC System Architecture:
>
> "Processor ID Register (PIR)
>
> The PIR is a 32-bit register that can be used by the OS to assign
> an ID to the processor.  Aside from any OS-specific usage of the
> assigned ID, the processor uses the ID when communicating with
> I/O devices."

  whoops, then my patch was wrong. dang.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
--
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

      parent reply	other threads:[~2017-09-05 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26 14:50 more pedantic proofing of DTSpec version 0.1 Robert P. J. Day
     [not found] ` <alpine.LFD.2.20.1708210705090.28188-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-08-31 20:56   ` Rob Herring
2017-08-31 21:09     ` Robert P. J. Day
2017-09-05 21:14     ` Frank Rowand
     [not found]       ` <59AF139B.5090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-05 21:20         ` Robert P. J. Day [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=alpine.LFD.2.21.1709051719460.5307@localhost.localdomain \
    --to=rpjday-l09j2beyid0n/h6p543eqg@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).