linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Daniel J Blueman <daniel@numascale.com>,
	"Zheng, Lv" <lv.zheng@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Steffen Persvold <sp@numascale.com>,
	Myron Stowe <myron.stowe@redhat.com>
Subject: Re: overriding ACPI _CRS method
Date: Mon, 21 Dec 2015 02:59:49 -0500	[thread overview]
Message-ID: <5677B175.6040800@jonmasters.org> (raw)
In-Reply-To: <1448853801.18315.0@outlook-emeawest.office365.com>

On 11/29/15, 10:23 PM, Daniel J Blueman wrote:
> On Mon, Nov 30, 2015 at 11:09 AM, Zheng, Lv <lv.zheng@intel.com> wrote:
>> Hi,
>>
>> IMO, if you want the new _CRS to be applied during the Linux early
>> boot stage, you can override the table using initrd override or DSDT
>> override mechanism.
>> Please see Documentation/acpi/initrd_table_override.txt or
>> Documentation/acpi/dsdt-override.txt.
>>
>> If you want the new _CRS to be applied during Linux runtime, you can
>> override it using method customization mechanism.
>> Please see Documentation/acpi/method-customizing.txt
>
> The reason I'm trying to adjust this in firmware, is to deliver the
> right behaviour with pre-built/distro kernels, so I can't use that
> approach.

The initrd method prepends an override initrd so you can use the stock 
distro one (obviously any such modification might impact whether a 
system vendor will support you in any case). This is in fact why I use 
an initrd override method on ARM servers to test ACPI fixes.

The other option you have is to use the "acpi" command in GRUB to 
provide an override set of tables pre-OS boot. Depending upon your OS, 
you might need to regenerate your (dracut) initramfs with that via the 
GRUB configuration file(s).

Jon.

      reply	other threads:[~2015-12-21  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29 10:58 overriding ACPI _CRS method Daniel J Blueman
2015-11-30  3:09 ` Zheng, Lv
2015-11-30  3:23   ` Daniel J Blueman
2015-12-21  7:59     ` Jon Masters [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=5677B175.6040800@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=daniel@numascale.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=myron.stowe@redhat.com \
    --cc=sp@numascale.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).