public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Adrian Bunk <bunk@stusta.de>
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, 03 Aug 2006 17:59:49 -0700	[thread overview]
Message-ID: <44D29C05.4030408@zytor.com> (raw)
In-Reply-To: <20060804001221.GM25692@stusta.de>

Adrian Bunk wrote:
> On Thu, Aug 03, 2006 at 04:51:38PM -0700, H. Peter Anvin wrote:
>> Adrian Bunk wrote:
>>
>>> 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?
>>>
>> It's architecture-dependent; it probably should be defined in something 
>> like <asm/cmdline.h>.
> 
> OK, I did misunderstand you.
> I tought you were saying it should be the same value for all 
> architectures.
> 
> With the exception of frv (in param.h), COMMAND_LINE_SIZE is in setup.h 
> on all architectures.
> 
> Do we want to move it to a different header, or simply make param.h a 
> userspace header on all architectures?
> 

I figure it should be broken out into a separate header, rather than 
exporting all of setup.h.

	-hpa

  reply	other threads:[~2006-08-04  1:02 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
2006-08-03 23:51       ` H. Peter Anvin
2006-08-04  0:12         ` Adrian Bunk
2006-08-04  0:59           ` H. Peter Anvin [this message]
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=44D29C05.4030408@zytor.com \
    --to=hpa@zytor.com \
    --cc=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=dwmw2@infradead.org \
    --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