public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ACPI in general
Date: Wed, 5 Oct 2016 21:45:40 -0400	[thread overview]
Message-ID: <20161006014540.GJ4884@bill-the-cat> (raw)
In-Reply-To: <AM4PR0401MB1732BB898EC986F51154BFCA9AC40@AM4PR0401MB1732.eurprd04.prod.outlook.com>

On Wed, Oct 05, 2016 at 11:33:14PM +0000, york sun wrote:
> On 10/05/2016 04:15 PM, Timur Tabi wrote:
> > On Wed, Oct 5, 2016 at 9:46 AM, Simon Glass <sjg@chromium.org> wrote:
> >>> Is there any activity to bring ACPI to other than x86 arch? If not, do
> >>> we have a plan to do so?
> >>
> >> Not that I know of, sorry.
> >
> > Note that ACPI for ARM exists on Linux already, and as far as I know,
> > all ARM ACPI systems use UEFI, not U-Boot.
> 
> Exactly the reason I asked. Wondering if U-Boot is going down this path.

Well, I wouldn't phrase it quite like that.  I would ask, do we want to
go down this path?  How far down would we want to go, if so?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161005/ecb261ce/attachment.sig>

  reply	other threads:[~2016-10-06  1:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 16:38 [U-Boot] ACPI in general york sun
2016-10-05  5:22 ` Bin Meng
2016-10-05 14:46 ` Simon Glass
2016-10-05 14:55   ` york sun
2016-10-05 23:15   ` Timur Tabi
2016-10-05 23:33     ` york sun
2016-10-06  1:45       ` Tom Rini [this message]
2016-10-06  1:48         ` Timur Tabi
2016-10-06  1:58           ` Tom Rini
2016-10-06 11:50             ` Timur Tabi
2016-10-06 12:50               ` Bin Meng
2016-10-06 13:01                 ` Timur Tabi
2016-10-06 19:57                   ` Olof Johansson

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=20161006014540.GJ4884@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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