public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 built-in command line
Date: Mon, 12 Jun 2006 10:14:24 -0700 (PDT)	[thread overview]
Message-ID: <e6k7dg$gtg$1@terminus.zytor.com> (raw)
In-Reply-To: 20060611234746.GJ24227@waste.org

Followup to:  <20060611234746.GJ24227@waste.org>
By author:    Matt Mackall <mpm@selenic.com>
In newsgroup: linux.dev.kernel
>
> On Mon, Jun 12, 2006 at 01:30:27AM +0200, Jan Engelhardt wrote:
> > >
> > >This patch allows building in a kernel command line on x86 as is
> > >possible on several other arches.
> > >
> > >+config CMDLINE
> > >+	  On some systems, there is no way for the boot loader to pass
> > >+	  arguments to the kernel. For these platforms, you can supply
> > >+	  some command-line options at build time by entering them
> > >+	  here. In most cases you will need to specify the root device
> > >+	  here.
> > 
> > Thank God x86 does not have that limitation. Or am I missing some exotic 
> > bootloader that fails to pass in arguments?
> 
> Yes. Note that this depends on CONFIG_EMBEDDED. It's quite common for
> embedded apps to roll their own trivial ROM-based boot loaders. It's
> also quite common for embedded boxen to run up against the command
> line length limit that's hardcoded in the boot protocol.
> 

There is no command line length limit hard-coded in the boot protocol
per se (at least not for version 2.02 or higher.)  The length limit is
hard-coded in the *kernel*, not in the protocol.

	-hpa


  reply	other threads:[~2006-06-12 17:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 21:55 [PATCH] x86 built-in command line Matt Mackall
2006-06-11 22:54 ` Jesper Juhl
2006-06-11 23:30 ` Jan Engelhardt
2006-06-11 23:47   ` Matt Mackall
2006-06-12 17:14     ` H. Peter Anvin [this message]
2006-06-11 23:40 ` Arjan van de Ven
2006-06-11 23:51   ` Matt Mackall
2006-06-12  0:08     ` Arjan van de Ven
2006-06-12  1:38       ` Matt Mackall
2006-06-12  5:13         ` Willy Tarreau
2006-06-12 17:15     ` H. Peter Anvin
2006-06-12  8:11 ` Andi Kleen
2006-06-12 14:37   ` Matt Mackall
2006-06-12 17:18     ` H. Peter Anvin
2006-06-12 17:12 ` H. Peter Anvin
2006-06-12 17:36   ` Michael Buesch
2006-06-12 17:52     ` H. Peter Anvin
2006-06-12 17:59   ` Tim Bird
     [not found] ` <200606121712.k5CHClUE017185@terminus.zytor.com>
2006-06-12 20:49   ` Matt Mackall
2006-06-12 21:19     ` Thomas Gleixner
2006-06-12 21:36       ` Tim Bird
2006-06-12 21:45         ` Thomas Gleixner
2006-06-12 22:03           ` Tim Bird
2006-06-12 21:45     ` Randy.Dunlap
2006-06-12 22:00       ` Tim Bird
2006-06-12 22:10         ` Randy.Dunlap

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='e6k7dg$gtg$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox