All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] arm: add acpi support for the arm
Date: Mon, 25 Nov 2019 10:13:40 +0800	[thread overview]
Message-ID: <CAEUhbmXM+vQWKkR4Tf8CxJbtEbjUw1TExmA0Z6Cn0Dz0Pv8nSQ@mail.gmail.com> (raw)
In-Reply-To: <HK0PR03MB3953AE6DEA97FF17A2461F36FF4A0@HK0PR03MB3953.apcprd03.prod.outlook.com>

Hi Steven,

On Mon, Nov 25, 2019 at 10:09 AM Steven Hao <steven_hao5189@outlook.com> wrote:
>
> Dear Bin:
>
> Firstly:
> I know that acpi about x86 is existing. And it is usefull for x86 platfporm. If it  is used to arm platform,some modification may have to do. For example,facs table is useless for arm.
>
> In adition,The acpi table is writed statically and then modified dynamically in my patch. It is a new method.
>
> I want to consult that whether my method is helpful or not.
>
> Secondly:
> If i want to reuse the x86-acpi. I will overwrite the write_acpi_tables function. But the definition about acpi strcuture is placed in arch/x86/include/asm directory. It can not be used to arm plateform. If the acpi library need to surport for all platform,i think it should move to /include directory.
>

Yes, we all are aware that modifications are needed to the existing
x86 ACPI support to support ARM. We don't want to create 2 ACP
implementation in U-Boot.

Regards,
Bin

  reply	other threads:[~2019-11-25  2:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  8:41 [U-Boot] [PATCH v3] arm: add acpi support for the arm Steven Hao
2019-11-21 15:18 ` Bin Meng
2019-11-25  2:09   ` Steven Hao
2019-11-25  2:13     ` Bin Meng [this message]
2019-11-25  2:42       ` Steven Hao
2019-11-25 22:42         ` Heinrich Schuchardt
2019-11-25 23:40           ` Simon Glass
2019-11-26  0:58             ` Heinrich Schuchardt
2019-11-27  2:17               ` [U-Boot] 回复: " Steven Hao
2019-11-27  3:42               ` [U-Boot] " Simon Glass
2019-11-27  6:04                 ` Bin Meng
2019-12-16  1:54                   ` 回复: " Steven Hao
2019-12-27 16:41                     ` Simon Glass
2019-12-28  1:42                       ` Steven Hao
     [not found]                       ` <HK0PR03MB3953F7031DEC556C651FB0F9FFF70@HK0PR03MB3953.apcprd03.prod.outlook.com>
2020-03-19 16:18                         ` Simon Glass
     [not found]                           ` <HK0PR03MB3953E7C7A95F80659AEABE95FFF50@HK0PR03MB3953.apcprd03.prod.outlook.com>
2020-03-29  2:13                             ` Simon Glass
2019-11-25  9:14     ` [U-Boot] " Andy Shevchenko

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=CAEUhbmXM+vQWKkR4Tf8CxJbtEbjUw1TExmA0Z6Cn0Dz0Pv8nSQ@mail.gmail.com \
    --to=bmeng.cn@gmail.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.