linux-mips
[Top] [All Lists]

Re: [PATCH 6/6] setup.c: use early_param() for early command line parsin

To: vagabon.xyz@gmail.com
Subject: Re: [PATCH 6/6] setup.c: use early_param() for early command line parsing
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 09 Aug 2006 23:25:51 +0900 (JST)
Cc: ths@networkno.de, linux-mips@linux-mips.org, ralf@linux-mips.org, yoichi_yuasa@tripeaks.co.jp
In-reply-to: <44D99B02.1070406@innova-card.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <44D898FE.7080006@innova-card.com> <20060809.010526.18607898.anemo@mba.ocn.ne.jp> <44D99B02.1070406@innova-card.com>
Sender: linux-mips-bounce@linux-mips.org
On Wed, 09 Aug 2006 10:21:22 +0200, Franck Bui-Huu <vagabon.xyz@gmail.com> 
wrote:
> > Maybe you can add something like "initrdmem=xxx@yyy", keeping
> > "rd_start" and "rd_size" for the backward compatibility.  Just a
> > thought.
> 
> Well that what I was planning when writing this patch but I didn't.
> I think that we will end up with two different semantics and the
> old one never replaced by the new one... Except if we mark them as
> deprecated by showing a warning at boot. What do you think ?

While the kernel command line is very limited resource (only 256
chars), I prefer a single short option to specify initrd range, if
available.

But nothing wrong with rd_start and rd_size, and it seems there are
some boot loader expected them already, so removing them would not be
good (especially without some grace period).

I don't care if there were two way to specify initrd range.  It would
be somewhat redundant, but that is usual on "Backword compatibility"
issue, isn't it?  ;-)

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>