* Tim Bird <[EMAIL PROTECTED]> wrote:
> + To compile command line arguments into the kernel,
> + set this option to 'Y', then fill in the
FYI, this tab-to-space whitespace error caused this build failure in
-tip testing:
arch/x86/Kconfig:1500: unknown option "set"
arch/x86/Kconfi
* Tim Bird <[EMAIL PROTECTED]> wrote:
> Allow x86 to support a built-in kernel command line. The built-in
> command line can override the one provided by the boot loader, for
> those cases where the boot loader is broken or it is difficult to
> change the command line in the the boot loader.
Allow x86 to support a built-in kernel command line. The built-in
command line can override the one provided by the boot loader, for
those cases where the boot loader is broken or it is difficult
to change the command line in the the boot loader.
Signed-off-by: Tim Bird <[EMAIL PROTECTED]>
---
a
H. Peter Anvin wrote:
> Ingo Molnar wrote:
>> * Tim Bird <[EMAIL PROTECTED]> wrote:
>>
>>> Add support for a built-in command line for x86 architectures. The
>>> Kconfig help gives the major rationale for this addition.
>>
>> i have actually used a local hack quite similar to this to inject boot
>>
Ingo Molnar wrote:
* Tim Bird <[EMAIL PROTECTED]> wrote:
Add support for a built-in command line for x86 architectures. The
Kconfig help gives the major rationale for this addition.
i have actually used a local hack quite similar to this to inject boot
options into bzImages via randconfig -
* Tim Bird <[EMAIL PROTECTED]> wrote:
> Add support for a built-in command line for x86 architectures. The
> Kconfig help gives the major rationale for this addition.
i have actually used a local hack quite similar to this to inject boot
options into bzImages via randconfig - so i would find t
Tim Bird wrote:
CONFIG_CMDLINE_OVERRIDE is probably more palatable to other architectures.
I'd be OK implementing it with an option, rather than a magic char.
I was trying to avoid adding too many options, since many kernel
developers prefer fewer options where possible. But the magic
char m
Matt Mackall wrote:
On Wed, 2008-08-06 at 15:48 -0700, H. Peter Anvin wrote:
Tim Bird wrote:
One difficulty is that the other arches' command lines
are not currently "broken", so there's no real incentive
to change them.
The only thing novel thing I'm adding here is the addition of
the leading
H. Peter Anvin wrote:
> Tim Bird wrote:
>> The only thing novel thing I'm adding here is the addition of
>> the leading '!' to allow for an override. This is needed
>> in some x86 cases I'm familiar with, but I've haven't seen
>> any cases where it would be useful for other arches.
>> (not to say
On Wed, 2008-08-06 at 15:48 -0700, H. Peter Anvin wrote:
> Tim Bird wrote:
> >
> > One difficulty is that the other arches' command lines
> > are not currently "broken", so there's no real incentive
> > to change them.
> >
> > The only thing novel thing I'm adding here is the addition of
> > the
On Wed, 2008-08-06 at 15:31 -0700, Tim Bird wrote:
> Matt Mackall wrote:
> > On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
> >> The default behavior is to append the boot loader string
> >> to this one. However, there is a mechanism (leading '!')
> >> to force the built-in string to override
Tim Bird wrote:
One difficulty is that the other arches' command lines
are not currently "broken", so there's no real incentive
to change them.
The only thing novel thing I'm adding here is the addition of
the leading '!' to allow for an override. This is needed
in some x86 cases I'm familiar
Matt Mackall wrote:
> On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
>> The default behavior is to append the boot loader string
>> to this one. However, there is a mechanism (leading '!')
>> to force the built-in string to override the boot loader
>> string.
>
> Nice solution.
>
> Where is
Robert Schwebel wrote:
> On Wed, Aug 06, 2008 at 02:31:48PM -0700, Tim Bird wrote:
>> Add support for a built-in command line for x86 architectures.
>> The Kconfig help gives the major rationale for this addition.
>
> If this feature is desired on all architectures, shouldn't it go out of
> arch/?
On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
> The default behavior is to append the boot loader string
> to this one. However, there is a mechanism (leading '!')
> to force the built-in string to override the boot loader
> string.
Nice solution.
Where is this relative to early boot optio
On Wed, Aug 06, 2008 at 02:31:48PM -0700, Tim Bird wrote:
> Add support for a built-in command line for x86 architectures.
> The Kconfig help gives the major rationale for this addition.
If this feature is desired on all architectures, shouldn't it go out of
arch/?
rsc
--
Dipl.-Ing. Robert Schw
Add support for a built-in command line for x86 architectures.
The Kconfig help gives the major rationale for this addition.
Note that this option is available for many other arches, and
its use is widespread in embedded projects.
This patch addresses concerns that were raised with an
earlier ver
17 matches
Mail list logo
