From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Yoder Stuart-B08248 <B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
parch-QRwYI7m9GJLYtjvyW6yDsg@public.gmane.org
Subject: Re: [Power.org:parch] ePAPR 1.1 to do list
Date: Mon, 13 Sep 2010 13:17:52 -0500 [thread overview]
Message-ID: <20100913131752.54981fb1@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA306688C2F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
On Mon, 30 Aug 2010 14:34:44 -0700
Yoder Stuart-B08248 <B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
> I've consolidated what I am aware of with respect to errors found in
> 1.0,
> clarifications needed, and new mechanisms to go into ePAPR 1.1 into
> a single list.
>
> Let me know if you are aware of anything else.
>
> ePAPR 1.1 To Do
> ---------------
>
> 1. Fix typos, misc cleanup
>
> -device_type="simple-bus" in 8572 soc node example (p.96)
> -p.51, line 27-- ET_EXEC is 0x2 not 0x1
> -p.41, broken cross reference
> -missing period on virtual reg on ns16550
2.3.11 says device_type should only be present for cpu and memory
nodes, but the example trees in the appendices contain device_type =
"serial", "network", "pci", and "open-pic" (as well as the simple-bus
error mentioned above).
In general the examples should be checked for compliance and current
best practices (e.g. the 8572ds tree has a node named "soc8572") -- and
perhaps should show what the tree looks like after "filled in by
u-boot" has taken place.
-Scott
next prev parent reply other threads:[~2010-09-13 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 21:34 ePAPR 1.1 to do list Yoder Stuart-B08248
[not found] ` <9696D7A991D0824DBA8DFAC74A9C5FA306688C2F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-08-30 22:33 ` [Power.org:parch] " Scott Wood
[not found] ` <20100830173314.446aae02-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-08-31 1:00 ` David Gibson
2010-09-13 18:17 ` Scott Wood [this message]
[not found] ` <20100913131752.54981fb1-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-09-20 2:44 ` David Gibson
2011-01-11 22:14 ` Yoder Stuart-B08248
[not found] ` <9F6FE96B71CF29479FF1CDC8046E150301D94E-TcFNo7jSaXM0vywKSws3iq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2011-01-11 22:26 ` Scott Wood
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=20100913131752.54981fb1@schlenkerla.am.freescale.net \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=parch-QRwYI7m9GJLYtjvyW6yDsg@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).