From: David Woodhouse <dwmw2@infradead.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
nhorman@redhat.com, cbe-oss-dev <cbe-oss-dev@ozlabs.org>
Subject: Re: [Cbe-oss-dev] [PATCH] Ignore memory listed in PS3 device tree
Date: Tue, 03 Apr 2007 10:45:38 -0400 [thread overview]
Message-ID: <1175611539.2665.30.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1175570169.30552.3.camel@shinybook.infradead.org>
On Mon, 2007-04-02 at 23:16 -0400, David Woodhouse wrote:
> > > My question remains: shouldn't Linux get that
> > > information from the device tree, instead? The
> > > bootwrapper or bootloader can put it there.
> >
> > Yes it _should_, but it doesn't.
>
> It _used_ to. The 2.6.16 kernel just used the memory listed in the
> device tree. That's _why_ we need this hack -- because when we boot
> from
> 2.6.16 with the memory listed in the device tree, it ends up getting
> registered twice by the new kernel.
Why _did_ we make this change? It makes /sbin/kexec unhappy too, since
it doesn't like the apparent lack of _any_ memory.
It's not as if anyone's going to be expanding the amount of memory in
their PS3, so it really needs to be dynamically detected.
If we were to put the memory back in the device-tree, and start with a
single region up to 0x07c00000 followed by another region with the rest
of it, then we wouldn't need the rmo_top hack to /sbin/kexec either.
--
dwmw2
next prev parent reply other threads:[~2007-04-03 14:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 22:43 [PATCH] Ignore memory listed in PS3 device tree David Woodhouse
2007-03-29 23:23 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
2007-03-30 0:27 ` David Woodhouse
2007-03-30 13:25 ` Segher Boessenkool
2007-04-02 0:20 ` Michael Ellerman
2007-04-02 17:36 ` Segher Boessenkool
2007-04-03 2:42 ` Michael Ellerman
2007-04-03 3:16 ` David Woodhouse
2007-04-03 14:45 ` David Woodhouse [this message]
2007-04-03 21:18 ` Geoff Levand
2007-04-03 21:48 ` David Woodhouse
2007-04-03 22:45 ` Geoff Levand
2007-04-03 22:55 ` Arnd Bergmann
2007-04-03 23:58 ` Geoff Levand
2007-04-04 0:10 ` David Woodhouse
2007-04-04 11:43 ` Segher Boessenkool
2007-04-04 1:30 ` Benjamin Herrenschmidt
2007-04-04 1:28 ` Benjamin Herrenschmidt
2007-04-04 1:26 ` Benjamin Herrenschmidt
2007-03-30 17:41 ` Geoff Levand
2007-03-30 17:45 ` David Woodhouse
2007-03-30 18:11 ` Segher Boessenkool
2007-03-30 18:13 ` David Woodhouse
2007-03-31 15:27 ` Segher Boessenkool
2007-03-31 22:34 ` Benjamin Herrenschmidt
2007-03-31 22:42 ` David Woodhouse
2007-04-06 21:22 ` Geoff Levand
2007-04-06 22:34 ` Benjamin Herrenschmidt
2007-04-06 22:43 ` David Woodhouse
2007-04-06 23:15 ` Geoff Levand
2007-04-06 23:35 ` Benjamin Herrenschmidt
2007-04-06 23:44 ` David Woodhouse
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=1175611539.2665.30.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=nhorman@redhat.com \
/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).