linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ACPI on arm64 TODO List
Date: Mon, 5 Jan 2015 21:52:27 +0100	[thread overview]
Message-ID: <20150105205227.GA24657@amd> (raw)
In-Reply-To: <548F9668.6080900@linaro.org>

Hi!

> Back in September 2014, a meeting was held at Linaro Connect where we
> discussed what issues remained before the arm64 ACPI core patches could
> be merged into the kernel, creating the TODO list below.  I should have
> published this list sooner; I got focused on trying to resolve some of
> the issues instead.
> 
> We have made some progress on all of these items.  But, I want to make
> sure we haven't missed something.  Since this list was compiled by only
> the people in the room at Connect, it is probable we have.  I, for one,
> do not yet claim omniscience.
> 
> So, I want to ask the ARM and ACPI communities:
> 
>   -- Is this list correct?
> 
>   -- Is this list complete?

I'm not sure this is how kernel development works. Expect new issues
to be raised as patches are being reviewed.

> 7. Why is ACPI required?
>    * Problem:
>      * arm64 maintainers still haven't been convinced that ACPI is
>        necessary.
>      * Why do hardware and OS vendors say ACPI is required?
>    * Status: Al & Grant collecting statements from OEMs to be posted
>      publicly early in the new year; firmware summit for broader
>      discussion planned.

This should be #1 really, right? I still hope the answer is "ACPI not
needed".

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2015-01-05 20:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  2:18 [RFC] ACPI on arm64 TODO List Al Stone
2014-12-16 11:27 ` Arnd Bergmann
2014-12-16 15:27   ` Catalin Marinas
2014-12-17  0:03     ` Al Stone
2014-12-17  9:25       ` Catalin Marinas
2014-12-18  4:57         ` Jon Masters
2014-12-18  9:55           ` Catalin Marinas
2014-12-17 13:43       ` [Linaro-acpi] " Charles Garcia-Tobin
2014-12-16 15:48   ` Mark Rutland
2014-12-17  0:37     ` Al Stone
2014-12-17  9:08       ` G Gregory
2014-12-17 16:02       ` Mark Rutland
2014-12-17 16:52         ` Hurwitz, Sherry
2014-12-17 18:14       ` Lorenzo Pieralisi
2014-12-18  5:04       ` Jon Masters
2014-12-18 14:36         ` Jon Masters
2014-12-16 22:55   ` Al Stone
2014-12-17 17:31     ` Catalin Marinas
2014-12-17 22:26   ` Grant Likely
2015-01-10 14:44     ` Grant Likely
2015-01-12 10:21       ` Arnd Bergmann
2015-01-12 12:00         ` Grant Likely
2015-01-12 19:40           ` [Linaro-acpi] " Arnd Bergmann
2015-01-13 17:22             ` Grant Likely
2015-01-14  0:26               ` Al Stone
2015-01-15  4:07                 ` Hanjun Guo
2015-01-15 17:15                   ` Arnd Bergmann
2015-01-15 17:19                 ` Arnd Bergmann
2015-01-12 14:23       ` Pavel Machek
2015-01-12 14:41         ` Grant Likely
2015-01-12 19:39           ` Pavel Machek
2015-01-12 19:55             ` Arnd Bergmann
2015-01-13 14:12             ` Grant Likely
2015-01-14  1:21             ` Al Stone
2015-01-15 17:45               ` [Linaro-acpi] " Linda Knippers
2015-01-13 17:02         ` Grant Likely
2015-01-05 20:52 ` Pavel Machek [this message]
2015-01-06 11:53   ` Catalin Marinas

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=20150105205227.GA24657@amd \
    --to=pavel@ucw.cz \
    --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).