linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] arm/dt: tegra: Remove /memreserve/ from device-tree files
Date: Wed, 7 Dec 2011 16:22:19 -0800	[thread overview]
Message-ID: <20111208002219.GL12945@quad.lixom.net> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF174F08C3BC@HQMAIL01.nvidia.com>

On Tue, Nov 22, 2011 at 08:25:03AM -0800, Stephen Warren wrote:
> Marc Dietrich wrote at Tuesday, November 22, 2011 3:42 AM:
> > On Monday 21 November 2011 14:44:07 Stephen Warren wrote:
> > > There are no drivers in the kernel at present which can make use of the
> > > memory reserved by /memreserve/, so there is no point reserving it. Remove
> > > /memreserve/ to allow the user more memory. It's also unclear whether any
> > > future driver would actually require /memreserve/, or allocate memory
> > > through some other mechanism.
> > 
> > while this gives 512 MB of usable memory on my AC100, it causes some funny
> > pictures on the screen ;-) I guess our bootloader (fastboot) already setups
> > the frambuffer there (and enables the backlight). I guess it shouldn't be
> > harmful as nothing else writes to this memory area. Otherwise you may add that
> > the bootloader (or the kernel cmdline supplied by the bootloader) is now
> > responsible for the reservation to the description.
> 
> Ah yes, I guess that would happen. I'm only testing with mainline U-Boot...
> 
> I'd suggest this is acceptable fallout for now; I don't believe it will
> cause any active problems, and as you say, you can get the bootloader to
> set a command-line that excludes the frame-buffer if you want to solve
> this. Do you agree?

Agreed. It would make more sense to teach u-boot to reserve the memory.


-Olof

  parent reply	other threads:[~2011-12-08  0:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 21:44 [PATCH 1/5] arm/dt: tegra: Remove /memreserve/ from device-tree files Stephen Warren
2011-11-21 21:44 ` [PATCH 2/5] arm/dt: tegra: Remove /chosen node Stephen Warren
2011-12-08  0:20   ` Olof Johansson
2011-11-21 21:44 ` [PATCH 3/5] arm/dt: tegra: Fix I2C nodes to match board files Stephen Warren
2011-12-08  0:20   ` Olof Johansson
2011-11-21 21:44 ` [PATCH 4/5] arm/dt: tegra: Fix serial " Stephen Warren
2011-12-08  0:21   ` Olof Johansson
2011-11-21 21:44 ` [PATCH 5/5] arm/dt: tegra: Fix SDHCI " Stephen Warren
2011-11-22  8:38   ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-22 16:12     ` Stephen Warren
2011-11-22 16:23       ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-08  0:21   ` Olof Johansson
2011-11-22 10:41 ` [PATCH 1/5] arm/dt: tegra: Remove /memreserve/ from device-tree files Marc Dietrich
2011-11-22 16:25   ` Stephen Warren
2011-11-22 21:36     ` [PATCH 1/5] arm/dt: tegra: Remove /memreserve/ from device-treefiles Marc Dietrich
2011-12-08  0:22     ` Olof Johansson [this message]
2011-12-08  0:19 ` [PATCH 1/5] arm/dt: tegra: Remove /memreserve/ from device-tree files Olof Johansson

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=20111208002219.GL12945@quad.lixom.net \
    --to=olof@lixom.net \
    --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).