From: Daniel Walker <danielwa@cisco.com>
To: Rob Herring <robh@kernel.org>
Cc: Daniel Walker <dwalker@fifo99.com>,
xe-kernel@external.cisco.com,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-RFC 6/7] drivers: of: ifdef out cmdline section
Date: Wed, 14 Oct 2015 07:48:02 -0700 [thread overview]
Message-ID: <561E6B22.1030204@cisco.com> (raw)
In-Reply-To: <CAL_JsqK5qymGdMaayK61WKPw1-Ws9K+Lxi5w6rO2CEg08Aq60A@mail.gmail.com>
There's one last little wrinkle .. In the current setup the defconfig
CONFIG_CMDLINE="" is used as a default in case the device tree has
nothing in it. In my changes, there is no identical functionality. The
only similar thing I have is the the CONFIG_CMDLINE_APPEND="" . The main
difference is that in the current implementation CONFIG_CMDLINE=""
doesn't get added at all if there is a device tree bootargs, but with my
implementation this line would be added unconditionally. It would
represent a subtle change where people would have to add into the DT
bootargs something to override what might be in the default command line.
For example,
if a config has CONFIG_CMDLINE_APPEND="debug" then they would have to
add a "loglevel=7" into the DT bootargs to get back to normal. I
wouldn't think people would want "debug" as the default, but oddly
enough some of the configs do have this. Some of them also have default
ip address setting, nfsroot= settings, and loglevel= settings.
What are your thoughts on this ? I think using the append type default
makes more sense because it's actually setting up global defaults. The
current complete replacement scheme seems to set the stage for people to
make an entirely custom default for a single development machine, which
IMO doesn't make sense. However, I'm not sure what the intent is with
the current setup.
Daniel
next prev parent reply other threads:[~2015-10-14 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 15:47 [PATCH-RFC 6/7] drivers: of: ifdef out cmdline section Daniel Walker
2015-10-06 17:14 ` Rob Herring
2015-10-07 16:27 ` dwalker
[not found] ` <20151007162755.GA23283-zu3NM2574RrQT0dZR+AlfA@public.gmane.org>
2015-10-07 21:48 ` Rob Herring
2015-10-13 20:13 ` Daniel Walker
[not found] ` <561D6603.4060006-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2015-10-13 21:17 ` Rob Herring
2015-10-14 14:48 ` Daniel Walker [this message]
2015-10-14 17:57 ` Rob Herring
2015-10-14 19:16 ` Daniel Walker
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=561E6B22.1030204@cisco.com \
--to=danielwa@cisco.com \
--cc=devicetree@vger.kernel.org \
--cc=dwalker@fifo99.com \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xe-kernel@external.cisco.com \
/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).