From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: parsing of some early cmdline options
Date: Fri, 24 Feb 2006 10:19:12 +1100 [thread overview]
Message-ID: <1140736753.8264.55.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0602231658210.16092-100000@gate.crashing.org>
On Thu, 2006-02-23 at 17:02 -0600, Kumar Gala wrote:
> Guys,
>
> I noticed that we have code in arch/powerpc/kernel/prom_init.c to handle
> parsing iommu=, mem=, and crashkernel=.
>
> The problem I have is that we only use/build prom_init.c on MULTIPLATFORM
> (coming from true OF).
MULTIPLATFORM is here to die (or rather be always there, with
ARCH=powerpc we really want to NOT reproduce the old single platform
crap) , but yes, prom_init.c is supposed to only be run on real OFs...
I suppose we woul have to deal with those in early_init_devtree() for
machines that didn't go through prom_init()....
> Any ideas on how to handle this for the !MULTIPLATFORM cases. I'm most
> concerned about mem=.
next prev parent reply other threads:[~2006-02-23 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 23:02 parsing of some early cmdline options Kumar Gala
2006-02-23 23:19 ` Benjamin Herrenschmidt [this message]
2006-02-23 23:40 ` Michael Ellerman
2006-02-24 7:14 ` Kumar Gala
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=1140736753.8264.55.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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