linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	Dale Farnsworth <dfarnsworth@mvista.com>,
	Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [RFC 3/3] powerpc: Add DTS file for the Motorola PrPMC2800 platform
Date: Thu, 29 Mar 2007 11:56:56 +1000	[thread overview]
Message-ID: <20070329015656.GA16270@localhost.localdomain> (raw)
In-Reply-To: <2cd6c2dd69700dd162e90f8b7a83a99d@kernel.crashing.org>

On Thu, Mar 29, 2007 at 02:48:47AM +0200, Segher Boessenkool wrote:
> > That does seem like a lot.  The only thing that should need
> > virtual-reg properties is serial ports.  In fact, specifically, only
> > serial ports that the zImage is actually expected to use.
> >
> > In fact, with Scott's addition of xlate_reg() to the bootwrapper,
> > virtual-reg should only be needed on systems that enter the zImage
> > with MMU on.
> 
> Even then, you can just query the MMU structures to
> find out the currently set up translations for that
> physical address.  Way more robust.
> 
> The only valid reason to use "virtual-reg" is as a
> hack to map some device to get some debug output out.

That's exactly what it's for.  Getting serial output as early as
possible.  It shouldn't be used for anything else.

> If for normal usage you can't be bothered to parse
> the current translations, you probably shouldn't be
> doing anything as "advanced" as device I/O either --
> just boot the kernel and let it handle it ;-)
> 
> That said, I sure hope the kernel isn't using this
> property as well...

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-03-29  1:56 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
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 [this message]
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=20070329015656.GA16270@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=dfarnsworth@mvista.com \
    --cc=segher@kernel.crashing.org \
    --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).