linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	Dale Farnsworth <dfarnsworth@mvista.com>
Subject: RE: [RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800 platform
Date: Wed, 28 Mar 2007 13:11:19 -0500	[thread overview]
Message-ID: <1175105479.7553.75.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA302BDAB3E@az33exm25.fsl.freescale.net>

On Wed, 2007-03-28 at 09:43 -0700, Yoder Stuart-B08248 wrote:
> Biggest concern is that I see a lot of undocumented device
> types and properties...

Yes, but that is a problem in general.

> > +		virtual-reg = <f1000000>;
> 
> What is virtual-reg for?  I gather it is related to the bootwrapper
> needed virtual addresses for devices reg blocks.  But, I counted
> 12 instances of the property in this file.  Are all needed by the
> bootwrapper??
> 
> Does anyone where this property came from historically?  If it's
> specifically for a Linux bootwrapper the name should reflect 
> that-- linux,bootwrapper-reg-vaddr -- or something...

It came from a discussion Mark, I, and a few others had on this list a
few months ago about the requirement for reusing the virtual address set
up by the firmware for the bootwrapper.  You cannot assume a 1:1
physical to virtual mapping for things, so the bootwrapper console code
looks for virtual-reg first and uses that address for it's operations.

> Based on some offline dicussions I think I know what block-index
> is, but I'd like to see this property documented in
> booting-without-of.txt.

As an aside, there's a lot of stuff that needs updating in
booting-without-of.txt.  The interrupt mapping it suggests is incorrect,
some of the entry point stuff is invalid, etc.  There's now several
properties that are being introduced that aren't in there as well.

josh

  reply	other threads:[~2007-03-28 18:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28  1:19 [RFC 0/3] powerpc: Add Motorola PrPMC2800 platform support Mark A. Greer
2007-03-28  1:20 ` [RFC 1/3] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Mark A. Greer
2007-03-28  1:21 ` [RFC 2/3] powerpc: Add arch/powerpc support for the " Mark A. Greer
2007-03-28  1:22 ` [RFC 3/3] powerpc: Add DTS file " Mark A. Greer
2007-03-28 16:43   ` Yoder Stuart-B08248
2007-03-28 18:11     ` Josh Boyer [this message]
2007-03-28 19:49       ` [RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800platform Yoder Stuart-B08248
2007-03-29  0:35     ` [RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800 platform David Gibson
2007-03-29  0:48       ` Segher Boessenkool
2007-03-29  1:56         ` David Gibson
2007-03-29 22:21         ` Dale Farnsworth
2007-04-02 18:26         ` Mark A. Greer
2007-04-04 11:28           ` Segher Boessenkool
2007-04-04 16:27             ` Mark A. Greer
2007-04-04 17:44               ` Segher Boessenkool
2007-04-02 18:15       ` Mark A. Greer
2007-04-03  0:55         ` David Gibson
2007-04-03 18:50           ` Mark A. Greer
2007-04-04 11:18         ` Segher Boessenkool
2007-04-04 16:29           ` Mark A. Greer
2007-04-04 17:51             ` Yoder Stuart-B08248
2007-04-05 17:48               ` Segher Boessenkool
2007-03-29 22:18     ` Dale Farnsworth
2007-04-02 18:06     ` Mark A. Greer

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=1175105479.7553.75.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=dfarnsworth@mvista.com \
    --cc=stuart.yoder@freescale.com \
    /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).