From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: ACPI
Date: Sat, 23 Nov 2013 10:11:45 +0100 [thread overview]
Message-ID: <201311231011.45892.arnd@arndb.de> (raw)
In-Reply-To: <528FCEA6.1060602@jonmasters.org>
On Friday 22 November 2013, Jon Masters wrote:
> The bottom line for me is that for those moving from existing
> architectures into the new world, everything else remains the same. Same
> OEM vendor tooling used to design and build systems and deliver and
> support them, same installation experience, very very boring. This is
> exactly how ARM will succeed in the market. One Platform. Very very
> boring and straightforward installation and management, and so on.
Yes, that part seems fine, but be aware that we still have to deal
with lots of other types of systems that are well outside of the scope
of such a server infrastructure: mobile, industrial, networking,
hobbyist, etc equipment. These will typically have very different
SoCs and not follow the server platform specs, but we still want them
to be as boring when you install a Linux distro on them.
I've talked in the past to people who got your message about ACPI
but not the rest and that are now struggling in a very misguided
attempt to bring ACPI to systems that are anything but boring and
that will cause real headaches for years on both developers and users
if they actually end up shipping.
Arnd
next prev parent reply other threads:[~2013-11-23 9:11 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 ` ACPI Jon Masters
2013-11-22 21:37 ` ACPI Jon Masters
2013-11-23 9:11 ` Arnd Bergmann [this message]
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=201311231011.45892.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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