devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Florian Fainelli <florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Cc: device-tree
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	linux-arm
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: Overriding/concatenating kernel command-line with bootargs from dtb?
Date: Mon, 11 Jun 2012 09:34:33 -0500	[thread overview]
Message-ID: <4FD601F9.8020201@gmail.com> (raw)
In-Reply-To: <2050174.dvvKJHKP0J@flexo>

On 06/08/2012 02:55 AM, Florian Fainelli wrote:
> Hi all,
> 
> I have a specific use case, where two boards using the same SoC have different 
> UART speeds, which is something that I have specified in their corresponding 
> dts files. In order to make sure people don't mess up the configuration, I 
> prefer not to rely on the bootloader-supplied kernel-command line.
> 
> I was kind of expecting that ARM_ATAG_DTB_COMPAT + CMDLINE_EXTEND would 
> actually concatenate the kernel command-line with the bootargs provided from 
> dtb.
> 
> Is this something someone else would need? If so, shall we just make that 
> happen when the two config symbols mentionned above are enabled, or shall we 
> introduce a 4th kernel command line handling strategy?
> 
> Thank you for your answers.

There was a patch to do this:

http://www.mail-archive.com/devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org/msg10448.html

Please comment if this works for you.

Rob

  parent reply	other threads:[~2012-06-11 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  7:55 Overriding/concatenating kernel command-line with bootargs from dtb? Florian Fainelli
2012-06-08 21:49 ` Nicolas Pitre
2012-06-11 14:34 ` Rob Herring [this message]
2012-06-11 17:51   ` Florian Fainelli

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=4FD601F9.8020201@gmail.com \
    --to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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;
as well as URLs for NNTP newsgroup(s).