Message-ID: <45B8F5FB.6090704@am.sony.com>
Date: Thu, 25 Jan 2007 10:24:59 -0800
From: Tim Bird <tim.bird@am.sony.com>
User-Agent: Thunderbird 1.5.0.4 (X11/20060614)
MIME-Version: 1.0
To: Paul Mundt <lethal@linux-sh.org>, Tim Bird <tim.bird@am.sony.com>,
       linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] init: support preset lpj value as config option
References: <45B7F5E2.4070800@am.sony.com> <20070125021847.GA7609@linux-sh.org>
In-Reply-To: <20070125021847.GA7609@linux-sh.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1452
Lines: 34

Paul Mundt wrote:
> On Wed, Jan 24, 2007 at 04:12:18PM -0800, Tim Bird wrote:
>> This patch provides a config option for preset lpj, which means
>> the value can be easily preserved, and conveyed between developers
>> in a config file.
>>
> This seems excessive, it's already possible to set the preset lpj on the
> kernel command line, and virtually every one of the embedded
> architectures supports setting the kernel command line as a config
> option. Is there any reason why you can't simply set it there as a
> default instead? It's all going to be .config resident in the end
> anyways.

i386 is missing CONFIG_CMDLINE support, and this architecture
is used in embedded.  I think many other x86 derivatives are
also missing .config-based command line support.  CELF has
worked to get patches submitted to fix this, but so far these
haven't been accepted.

For this reason (and IMHO from the standpoint of orthogonality)
I think it's awkward to have options which ONLY have a command-line
representation, and not a way to compile them in separately.

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/