linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ACPI: ARM64 does not have a BIOS add config for BIOS table scan.
Date: Wed, 16 Jul 2014 16:49:12 -0700	[thread overview]
Message-ID: <53C70F78.40206@zytor.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3285FB3C@ORSMSX114.amr.corp.intel.com>

On 07/16/2014 04:46 PM, Luck, Tony wrote:
>> +	select ACPI_LEGACY_TABLES_LOOKUP if ACPI
> 
>> This shouldn't actually be set on IA64, should it?  IA64 doesn't have
>> BIOS, either, it has EFI/UEFI, like ARM64...
> 
> Which ACPI tables are in the "LEGACY" category affected by this option?
> 

That's not what this is about... it is about how you find the root pointer.

On a BIOS system it is found by scanning low memory.  On an EFI system
it is found by querying EFI for a specific UUID.

	-hpa

  reply	other threads:[~2014-07-16 23:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  9:39 [PATCH v2 0/3] Clean up ACPI core to prepare for running ACPI on ARM64 Hanjun Guo
2014-07-09  9:39 ` [PATCH v2 1/3] ACPI: ARM64 does not have a BIOS add config for BIOS table scan Hanjun Guo
2014-07-16 23:37   ` H. Peter Anvin
2014-07-16 23:46     ` Luck, Tony
2014-07-16 23:49       ` H. Peter Anvin [this message]
2014-07-17  3:18         ` Hanjun Guo
2014-07-17 16:58           ` Luck, Tony
2014-07-18  9:22             ` Hanjun Guo
2014-07-09  9:39 ` [PATCH v2 2/3] ACPI: Don't use acpi_lapic in ACPI core code Hanjun Guo
2014-07-09  9:39 ` [PATCH v2 3/3] ACPI / processor: Introduce ARCH_HAS_ACPI_PDC Hanjun Guo
2014-07-16 23:32 ` [PATCH v2 0/3] Clean up ACPI core to prepare for running ACPI on ARM64 Rafael J. Wysocki
2014-07-16 23:28   ` Luck, Tony
2014-07-16 23:39     ` H. Peter Anvin

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=53C70F78.40206@zytor.com \
    --to=hpa@zytor.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).