All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	trini@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/22] Add __early_param for all arches
Date: Fri, 26 Mar 2004 21:03:56 +0000	[thread overview]
Message-ID: <20040326210355.D17638@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1080210253.29835.37.camel@hades.cambridge.redhat.com>; from dwmw2@infradead.org on Fri, Mar 26, 2004 at 11:29:35AM +0000

On Fri, Mar 26, 2004 at 11:29:35AM +0000, David Woodhouse wrote:
> Drivers may require allocation (bootmem not slab). We want to run before
> that's feasible -- before 'mem=', by definition :)

It definitely wants to be after mem= since mem= modifies the memory
layout before bootmem is initialised (and its required to be parsed
before bootmem is initialised, so bootmem knows where the memory is.)

So we require, in order:

- mem= to be parsed
- bootmem to be initialised
- drivers which want to allocate from bootmem to then be
  initialised
- setup rest of the kernel
- final command line parsing

which gives us three stages of command line parsing.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-03-26 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 23:57 [patch 1/22] Add __early_param for all arches trini
2004-03-25  3:55 ` Andrew Morton
2004-03-26 11:29   ` David Woodhouse
2004-03-26 21:03     ` Russell King [this message]
2004-03-26 21:15       ` David Woodhouse
2004-03-31  4:23 ` Rusty Russell
2004-03-31 16:13   ` Tom Rini
2004-04-01  1:51     ` Rusty Russell
2004-04-01  2:24       ` Tom Rini
2004-04-01  2:56         ` Rusty Russell

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=20040326210355.D17638@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.