From: Evan Lloyd <Evan.Lloyd@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Sudeep Holla <Sudeep.Holla@arm.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Matteo Carlini <Matteo.Carlini@arm.com>,
"Stephanie Hughes-Fitt" <Stephanie.Hughes-Fitt@arm.com>,
Dong Wei <Dong.Wei@arm.com>
Subject: HEADLESS flag in ACPI
Date: Wed, 13 Sep 2017 12:23:01 +0000 [thread overview]
Message-ID: <AM4PR0801MB144482280E0E3085829201948B6E0@AM4PR0801MB1444.eurprd08.prod.outlook.com> (raw)
We have a minor conundrum, and would like an element of consensus before we make a commit.
We want to (re-)submit patches adding HDLCD/GOP for some ARM platforms.
We have previously been asked to make this optional, as some people do not want the overhead of GOP (and the frame buffer) in their image/RAM. This is fine, and a build flag called HEADLESS would seem to fit the bill.
The query arises from the ACPI spec which has (in FADT): "
HEADLESS 1 12 System Type Attribute. If set indicates the system cannot detect the monitor or keyboard / mouse devices."
And what we need to confirm is that there is no case of a system with no display still wanting to have keyboard and/or mouse. I can't imagine there is, but thought it best to check.
Any thoughts?
Evan
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next reply other threads:[~2017-09-13 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 12:23 Evan Lloyd [this message]
2017-09-14 9:20 ` HEADLESS flag in ACPI Leif Lindholm
2017-09-14 10:59 ` Zeng, Star
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-list 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=AM4PR0801MB144482280E0E3085829201948B6E0@AM4PR0801MB1444.eurprd08.prod.outlook.com \
--to=devel@edk2.groups.io \
/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