linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits
Date: Fri, 22 Mar 2013 09:55:17 +0000	[thread overview]
Message-ID: <201303220955.17821.arnd@arndb.de> (raw)
In-Reply-To: <20130321214132.GB8431@obsidianresearch.com>

On Thursday 21 March 2013, Jason Gunthorpe wrote:
> On Thu, Mar 21, 2013 at 10:15:23PM +0100, Thomas Petazzoni wrote:
> > Dear Jason Gunthorpe,

> > 
> >  *) It only works when LPAE is enabled, so we would have to have
> >     different internal register addresses depending on whether LPAE is
> >     enabled or not. Probably not impossible, but not very
> >     straightforward either.
> 
> Ideally the internal register space address would come from the DT -
> we are getting very close to that on Marvell, I think.. Things like
> earlyprintk should ideally early parse the DT, harder I know :(

Let's not worry about earlyprintk for now. earlyprintk is supposed to be
really really simple, and the solution that we are using now works
well enough: You pick a hardcoded implementation at build time when
you are debugging, but disable debug_ll for a multiplatform release
kernel.

	Arnd

  parent reply	other threads:[~2013-03-22  9:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 16:26 [PATCH 0/5] arm: mvebu: Enable LPAE support for Armada XP SoCs Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 1/5] arm: mvebu: Aligne the internal registers virtual base to support LPAE Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 2/5] arm: mvebu: Select DMA_BOUNCE when LPAE is selected in Kconfig Gregory CLEMENT
2013-03-21 18:19   ` Rob Herring
2013-03-21 19:18   ` Andrew Lunn
2013-03-22 11:32   ` Russell King - ARM Linux
2013-03-21 16:26 ` [PATCH 3/5] arm: mvebu: Enable pj4b on LPAE compilations Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 4/5] arm: dts: Add a 64 bits version of the skeleton device tree Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits Gregory CLEMENT
2013-03-21 17:59   ` Rob Herring
2013-03-21 19:03     ` Arnd Bergmann
2013-03-21 19:18       ` Thomas Petazzoni
2013-03-21 21:31         ` Arnd Bergmann
2013-03-21 22:30           ` Sebastian Hesselbarth
2013-03-21 20:15   ` Andrew Lunn
2013-03-21 20:22     ` Thomas Petazzoni
2013-03-21 20:30       ` Jason Cooper
2013-03-21 20:37       ` Andrew Lunn
2013-03-21 21:08         ` Thomas Petazzoni
2013-03-21 21:16         ` Thomas Petazzoni
2013-03-21 20:55       ` Jason Gunthorpe
2013-03-21 21:15         ` Thomas Petazzoni
2013-03-21 21:35           ` Lior Amsalem
2013-03-21 21:46             ` Jason Gunthorpe
2013-03-21 21:58               ` Lior Amsalem
2013-03-22  6:55                 ` Arnd Bergmann
2013-03-21 21:41           ` Jason Gunthorpe
2013-03-21 22:26             ` Sebastian Hesselbarth
2013-03-22  9:55             ` Arnd Bergmann [this message]
2013-03-21 21:25         ` Andrew Lunn
2013-03-22  6:28         ` Andrew Lunn
2013-03-22 17:43           ` Jason Gunthorpe
2013-03-22 19:33             ` Arnd Bergmann

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=201303220955.17821.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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).