Date: Thu, 3 Aug 2006 23:52:31 +0200
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
Message-ID: <20060803215230.GI25692@stusta.de>
References: <20060803193952.GF25692@stusta.de> <20060803194410.GC16927@redhat.com> <44D26A8B.9040907@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44D26A8B.9040907@zytor.com>
User-Agent: Mutt/1.5.12-2006-07-14
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1284
Lines: 48

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

-
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/