All of lore.kernel.org
 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:58:09 -0400	[thread overview]
Message-ID: <20161006015809.GK4884@bill-the-cat> (raw)
In-Reply-To: <57F5AD87.6060504@codeaurora.org>

On Wed, Oct 05, 2016 at 08:48:55PM -0500, Timur Tabi wrote:
> Tom Rini wrote:
> >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?
> 
> ACPI is pretty complicated, more so than DT.  UEFI is also open
> source.  I think you need to find a very compelling reason to
> reinvent the wheel.

Yes.  But in brief, we also don't go fully down the ACPI path for x86.
But we can do "something".

I assume you mean EDK II when you say UEFI is open source, and yes
that's true.  But I've said in other places (and other contexts) choices
make all projects stronger.

> ACPI on ARM is reserved for ARM Servers, which is a small market (in
> term of number of units) compared to all other ARM chips.

I think that takes too narrow of a view.  If silicon is sold, someone
will put it somewhere.  And if there's firmware that works, and the
buyer can modify to suit their design, they'll use it.

-- 
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/b7a0d6b9/attachment.sig>

  reply	other threads:[~2016-10-06  1:58 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
2016-10-06  1:48         ` Timur Tabi
2016-10-06  1:58           ` Tom Rini [this message]
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=20161006015809.GK4884@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.