From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Add CONFIG_PARAM_* to set boot parameters.
Date: Wed, 02 Dec 2009 01:35:46 +0000 [thread overview]
Message-ID: <20091202013545.GA11047@linux-sh.org> (raw)
In-Reply-To: <20091130170254.65d2a0ab.yoshii.takashi@renesas.com>
On Mon, Nov 30, 2009 at 05:02:54PM +0900, yoshii.takashi@renesas.com wrote:
> You can set boot parameters by config, ignoring data at the top of empty_zero_page.
> This and CONFIG_CMDLINE make zImage to be simple "load and go" capable binary,
> same as vmlinux (which has default boot parameters inside of it).
>
> ---
>
> I think people who already have "Linux aware" boot loader don't find anything interesting,
> but this was helpful when I was debugging with a monitor with serial file transfer only.
> IMHO, it might be a good to forget about parameters on the top of empty_zero_page.
>
But this breaks the entire boot ABI, and probably only for the reason
that new bootloaders don't set up the argument page correctly. How about
just fixing the bootloaders to comply with the ABI rather than layering
more hacks in the kernel to make up for lazy bootloader developers?
While I don't have any objections to making the argument page optional in
itself, we still require some hints for things like whether we are using
32-bit boot mode and so on that need to be reflected somewhere. If you
wish to propose a new boot ABI and move away from overloading of the zero
page, that's fine with me, but we're not going to be breaking the ABI to
work around bootloader laziness.
next prev parent reply other threads:[~2009-12-02 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 8:02 [PATCH] sh: Add CONFIG_PARAM_* to set boot parameters yoshii.takashi
2009-12-02 1:35 ` Paul Mundt [this message]
2009-12-08 5:01 ` yoshii.takashi
2009-12-08 8:18 ` Paul Mundt
2009-12-08 13:14 ` Stuart MENEFY
2009-12-09 12:00 ` Magnus Damm
2009-12-10 5:00 ` yoshii.takashi
2009-12-10 7:01 ` yoshii.takashi
2009-12-10 8:48 ` yoshii.takashi
2009-12-14 2:10 ` Paul Mundt
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=20091202013545.GA11047@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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.