linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jonathan@jonmasters.org (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: ACPI
Date: Fri, 22 Nov 2013 15:59:45 -0500	[thread overview]
Message-ID: <528FC5C1.1080403@jonmasters.org> (raw)
In-Reply-To: <201311222131.08787.arnd@arndb.de>

On 11/22/2013 03:31 PM, Arnd Bergmann wrote:
> On Friday 22 November 2013, Jon Masters wrote:
> 
>> By 64-bit ARM server, I mean a system conformant with a series of
>> specifications that define what such a server system consists of. It
>> might be a physical system featuring an ARM-based SoC containing a core
>> conformant to the v8 Architecture, along with standardized peripherals,
>> or it might be a virtual platform. The boot architecture would include
>> UEFI (specifically a sequential progression from an initial EL3 reset
>> secure ROM on through to a verified Tiano build), and ACPI being used to
>> convey the platform devices, as well as for runtime event delivery.
> 
> Ok, that narrows it down a little, although not in the way I expected.
> 
> It seems there is a secret spec along the lines of the older PREP, CHRP,
> PAPR. Since the group behind this spec has not yet revealed itself, I will
> refer to them as SPECTRE (maybe that should be SPCTR?) for the sake of
> discussion.

That's an *awesome* choice of name. Made my afternoon :) If there were
an organization such as SPECTRE, I really hope that it would come with
those lap cats (I seem to be missing mine - but I do have a stuffed
plush white toy cat in my Amazon wishlist, and a birthday coming..).

But regardless of the existence or otherwise of any organization, I
would expect to see some standards documents appearing in the not too
distant future. I share the concern that this stuff needs to be out in
public, but above all, all else, what I care about above all is that
when there are ARM server systems in market in the next few years that
you can run *any* one-size-fits-all generic Operating System you would
like to choose to run, and freely move from one OS to another. That
includes the ability to run generic Linux distributions, Hypervisors,
non-Unix Operating Systems, and so on. To do that requires that the
underlying server platform be standardized in the same way that it is
elsewhere on other arches, with sensitivity to a wide world of choice.

A few years ago, a strategic direction was chosen by a few industry
players around UEFI and ACPI on ARM. I look forward to seeing standards
published, to seeing more emerging members of this market announced
their intentions, and to an engaging dialog about how support for these
systems will be implemented so that there is one standardized 64-bit ARM
server platform upon which customers can run anything they want. I hope
we can have some really engaging conversation very soon about it.

Thanks,

Jon.

  reply	other threads:[~2013-11-22 20:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:42 ACPI Jon Masters
     [not found] ` < CACRpkdY+6dzs8MpKKtW-3kzsLkZjsit9SeN20k_33TAtVf3NEA@mail.gmail.com>
     [not found]   ` < CACxGe6t_9hUXL_1PHRU=2DYOYfCqZykd7gYRCshZn0XsVoCdRw@mail.gmail.com>
     [not found]     ` < 20131126183344.GA16074@srcf.ucam.org>
     [not found] ` < CACRpkdbNxxNK0GM28H_nDLu6EpbQ-EYAdEeTp5fnXW5mkEPkgw@mail.gmail.com>
     [not found]   ` < CACxGe6uHuWPh7d9NaVuPRBWq0Fh1BmDV190KEN4C4uaq4KjS8g@mail.gmail.com>
     [not found]     ` < CACRpkdaCXJzWXoesjD3Jqpm4XMHLQp3SsHcsDG3veUS+xarqHQ@mail.gmail.com>
     [not found]       ` < CACxGe6vUKzow7QpeX2mU7CiZQzY8aZ+p0jd8Vk0+dqz0B=D0Ew@mail.gmail.com>
2013-11-19 18:15 ` ACPI Arnd Bergmann
2013-11-21 20:03   ` ACPI Mark Brown
2013-11-22  0:29     ` ACPI Arnd Bergmann
2013-11-22  4:05       ` ACPI Jon Masters
2013-11-22 20:31         ` ACPI Arnd Bergmann
2013-11-22 20:59           ` Jon Masters [this message]
2013-11-22 21:37             ` ACPI Jon Masters
2013-11-23  9:11               ` ACPI Arnd Bergmann
2013-11-23 18:39                 ` ACPI Jason Gunthorpe
2013-11-23 23:03                   ` ACPI Matthew Garrett
2013-11-24  3:52                     ` ACPI Jon Masters
2013-11-24  3:56                       ` ACPI Matthew Garrett
2013-11-24 23:21                         ` ACPI Jon Masters
2013-11-24 23:40                           ` ACPI Matthew Garrett
2013-11-22 13:19       ` ACPI Mark Brown
2013-11-19 18:28 ` ACPI Måns Rullgård
2013-11-21 16:56 ` ACPI Matthew Garrett
2013-11-24 17:14 ` ACPI Linus Walleij
2013-11-25  0:42   ` ACPI Grant Likely
2013-11-25  1:28     ` ACPI Matthew Garrett
2013-11-25 11:07     ` ACPI Linus Walleij
2013-11-25 11:33       ` ACPI Grant Likely
2013-11-25 15:41         ` ACPI Matthew Garrett
2013-11-26 12:43           ` ACPI Linus Walleij
2013-11-26 12:55             ` ACPI Grant Likely
2013-11-26 13:43               ` ACPI Jürgen Beisert
2013-11-27 12:25                 ` ACPI Grant Likely
2013-11-28 13:16                   ` ACPI Linus Walleij
2013-11-26 18:33               ` ACPI Matthew Garrett
2013-11-26 23:11                 ` ACPI Matt Sealey
2013-11-26 23:32                   ` ACPI Matthew Garrett
2013-11-27 11:00                     ` ACPI Catalin Marinas
2013-11-27 22:12                       ` ACPI Nicolas Pitre
2013-11-27 20:21                     ` ACPI Matt Sealey
2013-11-28  6:21                       ` ACPI Jon Masters
2013-11-28 18:26                     ` ACPI Stefano Stabellini
2013-11-28 18:48                       ` ACPI Matthew Garrett
2013-11-28 18:51                         ` ACPI Stefano Stabellini
2013-11-27 14:16                   ` ACPI Grant Likely
2013-11-27 22:17                     ` ACPI Matt Sealey
2013-11-28 13:50                       ` ACPI Leif Lindholm
2013-11-28 15:43                       ` ACPI Grant Likely
2013-11-27 12:41                 ` ACPI Grant Likely
2013-11-26 14:45             ` ACPI Matthew Garrett

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=528FC5C1.1080403@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --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).