Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jon Fraser" <jfraser@broadcom.com>
To: unlisted-recipients:; (no To-header on input)
Cc: jfraser@broadcom.com, "David VomLehn" <dvomlehn@cisco.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH 2/3] mips:powertv: Make kernel command line size configurable (resend)
Date: Wed, 6 May 2009 12:44:00 -0400	[thread overview]
Message-ID: <1241628240.10498.4.camel@chaos.ne.broadcom.com> (raw)
In-Reply-To: <20090506163518.GA19624@linux-mips.org>



David,

We found huge command lines to be awkward.  In our platform support
code, we can pass environment variables from our bootstrap (CFE) to the
kernel.  Would something like this work for you?

I have no objection to making the command line buffer size bigger.

Jon



On Wed, 2009-05-06 at 09:35 -0700, Ralf Baechle wrote:
> On Mon, May 04, 2009 at 03:57:19PM -0700, David VomLehn wrote:
> 
> > Most platforms can get by perfectly well with the default command line size,
> > but some platforms need more. This patch allows the command line size to
> > be configured for those platforms that need it. The default remains 256
> > characters.
> > 
> > Signed-off-by: David VomLehn <dvomlehn@cisco.com>
> 
> How big of a command line do you need?  For no scientific reason other
> than there not being any obvious need for a larger size MIPS is using 256
> and I think unless you're asking for a huge number it will be better to
> just raise that constant.
> 
>   Ralf
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Jon Fraser" <jfraser@broadcom.com>
Cc: jfraser@broadcom.com, David VomLehn <dvomlehn@cisco.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH 2/3] mips:powertv: Make kernel command line size configurable (resend)
Date: Wed, 6 May 2009 12:44:00 -0400	[thread overview]
Message-ID: <1241628240.10498.4.camel@chaos.ne.broadcom.com> (raw)
Message-ID: <20090506164400.etjWexzvRX3V_HvgfD73nYY6PqrhPewLEfbv6Ph9JUU@z> (raw)
In-Reply-To: <20090506163518.GA19624@linux-mips.org>



David,

We found huge command lines to be awkward.  In our platform support
code, we can pass environment variables from our bootstrap (CFE) to the
kernel.  Would something like this work for you?

I have no objection to making the command line buffer size bigger.

Jon



On Wed, 2009-05-06 at 09:35 -0700, Ralf Baechle wrote:
> On Mon, May 04, 2009 at 03:57:19PM -0700, David VomLehn wrote:
> 
> > Most platforms can get by perfectly well with the default command line size,
> > but some platforms need more. This patch allows the command line size to
> > be configured for those platforms that need it. The default remains 256
> > characters.
> > 
> > Signed-off-by: David VomLehn <dvomlehn@cisco.com>
> 
> How big of a command line do you need?  For no scientific reason other
> than there not being any obvious need for a larger size MIPS is using 256
> and I think unless you're asking for a huge number it will be better to
> just raise that constant.
> 
>   Ralf
> 
> 

  reply	other threads:[~2009-05-06 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 22:57 [PATCH 2/3] mips:powertv: Make kernel command line size configurable (resend) David VomLehn
2009-05-06 16:35 ` Ralf Baechle
2009-05-06 16:44   ` Jon Fraser [this message]
2009-05-06 16:44     ` Jon Fraser
2009-05-06 18:28     ` David VomLehn
2009-05-06 17:13   ` Manuel Lauss
2009-05-06 18:19   ` David VomLehn
2009-05-06 18:24     ` David Daney
2009-05-06 18:27       ` Jon Fraser
2009-05-06 18:29         ` David Daney
2009-05-06 18:33         ` David VomLehn
2009-05-08 15:25 ` Paul Gortmaker
2009-05-08 15:25   ` Paul Gortmaker
2009-05-08 16:34   ` David VomLehn
2009-05-11 21:29     ` Paul Gortmaker
  -- strict thread matches above, loose matches on Subject: below --
2009-05-29 18:30 David VomLehn

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=1241628240.10498.4.camel@chaos.ne.broadcom.com \
    --to=jfraser@broadcom.com \
    --cc=dvomlehn@cisco.com \
    --cc=linux-mips@linux-mips.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