From: Robin Murphy <robin.murphy@arm.com>
To: jtoppins@redhat.com, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: prarit@redhat.com, Jon Masters <jcm@redhat.com>,
Bhupesh Sharma <bhsharma@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Will Deacon <will.deacon@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
astone@redhat.com, James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64/acpi: make ACPI boot preference configurable
Date: Tue, 27 Feb 2018 14:55:18 +0000 [thread overview]
Message-ID: <b0f9d2d3-9029-1581-9330-807fab3b2d44@arm.com> (raw)
In-Reply-To: <1454e833-e3b9-780b-c5db-a6f73e799352@redhat.com>
On 27/02/18 14:28, Jonathan Toppins wrote:
>> 'only intended to be booted via ACPI' is a property of the system, not
>> of the OS. If you need this functionality for development, you can
>> append 'acpi=on' to the kernel command line via kconfig.
>
> This is not for development this is for production rate shipping firmware.
Obvious question: if this is "production" firmware on systems which "do
not support DT", what the hell is a non-trivial DT doing in there in the
first place?
Robin.
next prev parent reply other threads:[~2018-02-27 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 6:05 Jonathan Toppins
2018-02-27 7:22 ` Ard Biesheuvel
2018-02-27 14:28 ` Jonathan Toppins
2018-02-27 14:54 ` Ard Biesheuvel
2018-02-27 14:55 ` Robin Murphy [this message]
2018-02-27 12:40 ` Bhupesh Sharma
2018-02-27 14:44 ` Jonathan Toppins
2018-02-27 17:05 ` Mark Rutland
2018-02-27 18:59 ` Bhupesh Sharma
2018-02-28 10:07 ` Andy Shevchenko
2018-02-28 10:10 ` Rafael J. Wysocki
2018-02-28 10:32 ` Bhupesh Sharma
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=b0f9d2d3-9029-1581-9330-807fab3b2d44@arm.com \
--to=robin.murphy@arm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=astone@redhat.com \
--cc=bhsharma@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jcm@redhat.com \
--cc=jtoppins@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®