All of lore.kernel.org
 help / color / mirror / Atom feed
From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: socfpga: reserve the region at start of phys mem
Date: Wed, 30 Apr 2014 19:01:36 +0200	[thread overview]
Message-ID: <53612C70.6000109@linutronix.de> (raw)
In-Reply-To: <20140430161717.GY5546@joshc.qualcomm.com>

On 04/30/2014 06:17 PM, Josh Cartwright wrote:
> Is there a particular reason why you aren't describing this reservation
> in devicetree using a /memreserve/ node?

Because the kernel is using memory at a specific address it did not
allocate. If the memory address where the second CPU come up could be
set then this node wouldn't be required and a simple kmalloc() would do
it, too.

Sebastian

  reply	other threads:[~2014-04-30 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 17:34 [PATCH] arm: socfpga: reserve the region at start of phys mem Sebastian Andrzej Siewior
2014-03-14 17:01 ` Dinh Nguyen
2014-03-14 17:06   ` Sebastian Andrzej Siewior
2014-04-30 15:27   ` Sebastian Andrzej Siewior
2014-04-30 16:17 ` Josh Cartwright
2014-04-30 17:01   ` Sebastian Andrzej Siewior [this message]
2014-04-30 17:32     ` Josh Cartwright
2014-04-30 22:06       ` Dinh Nguyen

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=53612C70.6000109@linutronix.de \
    --to=bigeasy@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.