From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add CMDLINE_EXTEND
Date: Tue, 6 Dec 2016 19:03:59 +0000 [thread overview]
Message-ID: <20161206190358.GY2498@arm.com> (raw)
In-Reply-To: <52e471aa-9ad8-2a6a-efc4-0746b93ab37a@infradead.org>
On Tue, Dec 06, 2016 at 10:28:19AM -0800, Geoff Levand wrote:
> On 12/06/2016 04:20 AM, Will Deacon wrote:
> > On Mon, Dec 05, 2016 at 09:41:06AM -0800, Geoff Levand wrote:
> >> On 12/05/2016 04:08 AM, Catalin Marinas wrote:
> >>> On Fri, Dec 02, 2016 at 02:17:02PM -0800, Geoff Levand wrote:
> >>>> The device tree code already supports CMDLINE_EXTEND,
> >>>> so add the config option to make it available on arm64.
> >>>
> >>> What's your use-case for this patch? Note that both CMDLINE_FORCE and
> >>> CMDLINE_EXTEND (if we introduce it) are ignored by the EFI stub.
> >>> However, we don't seem to have stated this anywhere.
> >>
> >> I use this in CoreOS, where we need to set "acpi=force" for
> >> arm64. CoreOS uses a proper UEFI + grub.
> >
> > So why can't you just set that in grub if you want to boot with ACPI?
>
> That is how I originally did it, but it was suggested I
> do it in the kernel config. See:
>
> https://github.com/coreos/scripts/pull/610
>
> Is there any reason why we don't want arm64 to have
> CMDLINE_EXTEND?
I'm yet to see a good use-case for it.
Will
prev parent reply other threads:[~2016-12-06 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:17 [PATCH] arm64: Add CMDLINE_EXTEND Geoff Levand
2016-12-05 12:08 ` Catalin Marinas
2016-12-05 17:41 ` Geoff Levand
2016-12-06 12:20 ` Will Deacon
2016-12-06 18:28 ` Geoff Levand
2016-12-06 19:03 ` Will Deacon [this message]
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=20161206190358.GY2498@arm.com \
--to=will.deacon@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).