LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org, benh@kernel.crashing.org
Subject: Re: [PATCH 2/3] dt: Remove obsolete description of powerpc boot interface
Date: Mon, 31 Jan 2011 13:20:48 -0700 [thread overview]
Message-ID: <AANLkTin5s3xLfhERvBCKN9+4ZoRVEGt7Zq_2XFWwn=TR@mail.gmail.com> (raw)
In-Reply-To: <20110131113657.GC13541@zod.rchland.ibm.com>
On Mon, Jan 31, 2011 at 4:36 AM, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> On Mon, Jan 31, 2011 at 12:45:05AM -0700, Grant Likely wrote:
>>32 and 64 bit powerpc support has been merged for a while now, but
>>the booting-without-of.txt document still describes 32 bit as not
>>supporting multiplatform, which is no longer true. This patch fixes
>>the documentation.
>>
>>Also remove references to powerpc-specific details outside of section
>>I in preparation to add details for other architectures.
>
> There's a line around 500 that starts:
>
> "The kernel powerpc generic code does..."
>
> Perhaps the powerpc reference should be dropped there?
Done
>
> Also, there are several mentions of "real Open Firmware", which are
> probably just fine, and prom_init(), which are probably arch specific.
The prom_init() reference is just an example, and so I'm okay with it
staying in. The example is relevant to look at regardless of the
architecture you are working on. Oh, but I should drop the reference
to every node requiring a "device_type" property.
>
> There is a section that talks about ranges that starts with:
>
> "For a new 64-bit powerpc board, I...".
Fixed.
>
> Section III 5) has all kinds of powerpc specific stuff. CHRP,
> pSeries, PAPR in the root node. The references to Apple machines for
> examples are probably OK, but it shouldn't make PowerPC items as
> explicit requirements.
Right, fixed.
>
> Section III 5e) references a file that doesn't exist:
> arch/ppc64/kernel/setup.c
Fixed
>
> Section V, paragraph 2 references a file that doesn't exist:
> arch/ppc64/kernel/prom.c
>
> Hope that helps you...
>
> josh
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2011-01-31 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 7:44 [PATCH 0/3] dt: documentation reorganization Grant Likely
2011-01-31 7:44 ` [PATCH 1/3] dt: Move device tree documentation out of powerpc directory Grant Likely
2011-01-31 11:41 ` Josh Boyer
2011-01-31 7:45 ` [PATCH 2/3] dt: Remove obsolete description of powerpc boot interface Grant Likely
2011-01-31 11:36 ` Josh Boyer
2011-01-31 20:20 ` Grant Likely [this message]
2011-01-31 7:45 ` [PATCH 3/3 RFC] dt: add documentation of ARM dt " Grant Likely
2011-01-31 11:24 ` Josh Boyer
2011-01-31 18:00 ` Stephen Neuendorffer
2011-01-31 18:03 ` Grant Likely
2011-01-31 20:34 ` [PATCH 0/3] dt: documentation reorganization Sam Ravnborg
2011-01-31 21:01 ` Grant Likely
2011-01-31 22:23 ` Sam Ravnborg
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='AANLkTin5s3xLfhERvBCKN9+4ZoRVEGt7Zq_2XFWwn=TR@mail.gmail.com' \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sam@ravnborg.org \
--subject='Re: [PATCH 2/3] dt: Remove obsolete description of powerpc boot interface' \
/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
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).