From: florian@openwrt.org (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: Overriding/concatenating kernel command-line with bootargs from dtb?
Date: Fri, 08 Jun 2012 09:55:11 +0200 [thread overview]
Message-ID: <2050174.dvvKJHKP0J@flexo> (raw)
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.
--
Florian
next reply other threads:[~2012-06-08 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 7:55 Florian Fainelli [this message]
2012-06-08 21:49 ` Overriding/concatenating kernel command-line with bootargs from dtb? Nicolas Pitre
2012-06-11 14:34 ` Rob Herring
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=2050174.dvvKJHKP0J@flexo \
--to=florian@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.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