From: Adrian Bunk <bunk@stusta.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Userspace visible of 3 include/asm/ headers
Date: Thu, 3 Aug 2006 23:52:31 +0200 [thread overview]
Message-ID: <20060803215230.GI25692@stusta.de> (raw)
In-Reply-To: <44D26A8B.9040907@zytor.com>
On Thu, Aug 03, 2006 at 02:28:43PM -0700, H. Peter Anvin wrote:
> Dave Jones wrote:
> >
> > > Header : setup.h
> > > Architectures : i386, ia64, x86_64
> > > Contents:
> > > - COMMAND_LINE_SIZE on ia64, x86_64
> > > - much more on i386
> > > Should COMMAND_LINE_SIZE be visible to userspace?
> >
> >Bootloaders probably need to know this.
> >
>
> COMMAND_LINE_SIZE should be moved to a different header and be made
> common between all architectures.
On different architectures, we have the following values for
COMMAND_LINE_SIZE:
- 256
- 512
- 896
- 1024
- 4096
What should be the common value?
4096?
And I have a rough memory of some dependencies of COMMAND_LINE_SIZE and
boot loaders. What exactly must be taken care of when increasing
COMMAND_LINE_SIZE?
> -hpa
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-08-03 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 19:39 Userspace visible of 3 include/asm/ headers Adrian Bunk
2006-08-03 19:44 ` Dave Jones
2006-08-03 20:14 ` Alexey Dobriyan
2006-08-03 20:17 ` Dave Jones
2006-08-03 21:28 ` H. Peter Anvin
2006-08-03 21:52 ` Adrian Bunk [this message]
2006-08-03 23:51 ` H. Peter Anvin
2006-08-04 0:12 ` Adrian Bunk
2006-08-04 0:59 ` H. Peter Anvin
2006-08-04 1:00 ` H. Peter Anvin
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=20060803215230.GI25692@stusta.de \
--to=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=dwmw2@infradead.org \
--cc=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 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.