* [HP6xx] - Detection of 16MB / 32MB - Questions
@ 2008-03-16 16:27 Kristoffer Ericson
2008-03-18 3:20 ` Paul Mundt
2008-03-19 1:12 ` Kristoffer Ericson
0 siblings, 2 replies; 3+ messages in thread
From: Kristoffer Ericson @ 2008-03-16 16:27 UTC (permalink / raw)
To: linux-sh
Paul,
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.
Basicly try to write a value and check if it is stored. Would this be possible and if so
is the arch/boards/hp6xx/setup.c a good place for that?
--
Kristoffer Ericson <Kristoffer.Ericson@Gmail.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [HP6xx] - Detection of 16MB / 32MB - Questions
2008-03-16 16:27 [HP6xx] - Detection of 16MB / 32MB - Questions Kristoffer Ericson
@ 2008-03-18 3:20 ` Paul Mundt
2008-03-19 1:12 ` Kristoffer Ericson
1 sibling, 0 replies; 3+ messages in thread
From: Paul Mundt @ 2008-03-18 3:20 UTC (permalink / raw)
To: linux-sh
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [HP6xx] - Detection of 16MB / 32MB - Questions
2008-03-16 16:27 [HP6xx] - Detection of 16MB / 32MB - Questions Kristoffer Ericson
2008-03-18 3:20 ` Paul Mundt
@ 2008-03-19 1:12 ` Kristoffer Ericson
1 sibling, 0 replies; 3+ messages in thread
From: Kristoffer Ericson @ 2008-03-19 1:12 UTC (permalink / raw)
To: linux-sh
On Tue, 18 Mar 2008 12:20:14 +0900
Paul Mundt <lethal@linux-sh.org> wrote:
> 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.
Oki, sounds like a good idea. Thanks
--
Kristoffer Ericson <Kristoffer.Ericson@Gmail.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-03-19 1:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-16 16:27 [HP6xx] - Detection of 16MB / 32MB - Questions Kristoffer Ericson
2008-03-18 3:20 ` Paul Mundt
2008-03-19 1:12 ` Kristoffer Ericson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox