From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc-dev@ozlabs.org
Subject: Re: parsing of some early cmdline options
Date: Fri, 24 Feb 2006 10:40:50 +1100 [thread overview]
Message-ID: <200602241040.54060.michael@ellerman.id.au> (raw)
In-Reply-To: <1140736753.8264.55.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Fri, 24 Feb 2006 10:19, Benjamin Herrenschmidt wrote:
> 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).
> > Any ideas on how to handle this for the !MULTIPLATFORM cases. I'm most
> > concerned about mem=.
mem= is a bit tricky because you need to know about it really early, otherwise
your bootloader might violate the limit. But we could certainly check for it
again in prom.c. And you can always just set /chosen/linux,memory-limit.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-23 23:40 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
2006-02-23 23:40 ` Michael Ellerman [this message]
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=200602241040.54060.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--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