From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [HP6xx] - Detection of 16MB / 32MB - Questions
Date: Tue, 18 Mar 2008 03:20:14 +0000 [thread overview]
Message-ID: <20080318032014.GB3302@linux-sh.org> (raw)
In-Reply-To: <20080316172833.ce3dbc1d.Kristoffer.Ericson@Gmail.com>
On Sun, Mar 16, 2008 at 05:28:33PM -0700, Kristoffer Ericson wrote:
> Currently we have 2 different configs for 16MB vs 32MB kernels since we cannot
> use mem= as bootparam anymore. Was thinking to add some sort of detection code
> for this inside the arch file.
You can't use mem= to _grow_ beyond CONFIG_MEMORY_SIZE, but you can
truncate. If you want to go that route, always build with
CONFIG_MEMORY_SIZE = 32MB and use mem= for the 16MB cases. We don't
support growing via mem= for a good reason, and dynamically growing from
a probe routine wouldn't avoid any of those issues.
next prev parent reply other threads:[~2008-03-18 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 16:27 [HP6xx] - Detection of 16MB / 32MB - Questions Kristoffer Ericson
2008-03-18 3:20 ` Paul Mundt [this message]
2008-03-19 1:12 ` Kristoffer Ericson
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=20080318032014.GB3302@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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