public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Evan Lloyd <Evan.Lloyd@arm.com>, "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"Carsey, Jaben" <jaben.carsey@intel.com>,
	Sami Mujawar <Sami.Mujawar@arm.com>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>,
	"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables
Date: Fri, 23 Dec 2016 01:31:52 +0000	[thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503A8D46CC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <AM5PR0801MB176242DEFF8B986277E748258B920@AM5PR0801MB1762.eurprd08.prod.outlook.com>

HI Even
Thank you for the response.

*Mike Kinney* is managing staging tree – he may help answer the question on staging. ☺

I am glad to co-work with you on that.

Merry Christmas!


Thank you
Yao Jiewen

From: Evan Lloyd [mailto:Evan.Lloyd@arm.com]
Sent: Friday, December 23, 2016 2:26 AM
To: Yao, Jiewen <jiewen.yao@intel.com>; Ni, Ruiyu <ruiyu.ni@intel.com>; Carsey, Jaben <jaben.carsey@intel.com>; Sami Mujawar <Sami.Mujawar@arm.com>
Cc: Carsey, Jaben <jaben.carsey@intel.com>; edk2-devel@ml01.01.org; Leif Lindholm <leif.lindholm@linaro.org>; ard.biesheuvel@linaro.org
Subject: RE: [edk2] [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables


Hi Jiewen.
I hope I have our forename there, not your surname - it can be difficult to tell :-)
I've trimmed a lot out  of the history below, for clarity.

>
>From: Yao, Jiewen [mailto:jiewen.yao@intel.com]
>Sent: 20 December 2016 16:35
>To: Evan Lloyd; Ni, Ruiyu; Carsey, Jaben; Sami Mujawar
>Cc: Carsey, Jaben; edk2-devel@ml01.01.org<mailto:edk2-devel@ml01.01.org>; Leif Lindholm; ard.biesheuvel@linaro.org<mailto:ard.biesheuvel@linaro.org>
>Subject: RE: [edk2] [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables
>
>Thank you, Lloyd.
>
>Comment inline.
>
...
>[Jiewen] Got it.
>As you mention, I hope it can be in SHELL spec, too.
>
>So that we can have a standard way to dump all table information.
>
>For X86 system, I have written similar tool to dump X86 related info.
>I just check in to https://github.com/jyao1/EdkiiShellTool/tree/master/AcpiToolPkg.
>It is also BSD license code. I tried by best to dump info for *all* the ACPI table.
>But I do not validate ARM system. We complement to each other. ?

Yes, we obviously need to get together over this.

>...
>[Jiewen] Let me summarize current status:
>1)       We know there is strong requirement to dump ACPI table in UEFI shell environment, for debug purposes.
>2)       UEFI shell specification does not contain any ACPI dump command. (Although it has SmbiosDump)
>3)       ACPICA.ORG has sample code to dump ACPI.
>> > >Binary can be downloaded from: https://acpica.org/downloads/uefi-support
>> > >Source can be downloaded from: https://github.com/acpica/acpica
>4)       This patch provides dump ACPI information with consistency check. But limitation is: it only supports the limited table on ARM platform. NO support for X86 platform.
>5)       I have similar code to dump ACPI. But the limitation is: it only validated on X86 platform. It is not validated on ARM platform.
>
>
>So I would like to propose:
>1)       DOCUMENTATION: Can we co-work to submit an ECR for SHELL, to add AcpiDump command? So that people may get standard dump log in the future.

This sounds fine, but I'd suggest getting it into the Shell spec is much lower
priority than making the tool available.  We believe the checking aspect will
help people detect errors at an early stage, so want to "get it out there".

>2)       CODE: It seems both of our code is POC quality and has partial validation only. It might not be suitable to check in EDKII immediately
>I would like to propose we co-work in EDKII staging tree - https://github.com/tianocore/edk2-staging/ (We have 4 features there.)

That sounds excellent.  It will be a great thing to have ARM/Intel (or Intel/ARM if you prefer) cooperation on this.

>We can align our design, then I can help validate X86 and you can help validate ARM.
>Then we can submit a complete patch to EDKII ShellPkg.
>
>What about your idea?

I think this potentially helps everyone in UEFI.
Sadly, we are about to shut down for Christmas, and will not be back until 2017-01-03.  (I'm not really sad about it.)
From looking at your code, I think we will be able to learn a lot about EDK2 programming from you.
I suggest we can discuss the design and code merge aspects off list. (And make details of the results public in condensed form.)

Do I need to ask anyone to give me commit rights to https://github.com/tianocore/edk2-staging?
Or is it pull request based?

Regards, and Merry Christmas,
Evan

>
 Thank you
>> Yao Jiewen
>
>>> > > ...
>> > > >> Guid("CE165669-3EF3-493F-B85D-6190EE5B9759")
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2016-12-23  1:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 18:25 [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables evan.lloyd
2016-12-19  9:48 ` Ni, Ruiyu
2016-12-19 15:57   ` Evan Lloyd
2016-12-19 18:01     ` Carsey, Jaben
2016-12-20  2:59       ` Ni, Ruiyu
2016-12-20  3:56         ` Carsey, Jaben
2016-12-20  4:49           ` Yao, Jiewen
2016-12-20  5:18             ` Ni, Ruiyu
2016-12-20  5:54               ` Yao, Jiewen
2016-12-20 13:20                 ` Evan Lloyd
2016-12-20 16:35                   ` Yao, Jiewen
2016-12-22 18:25                     ` Evan Lloyd
2016-12-23  1:31                       ` Yao, Jiewen [this message]
2017-01-13  8:10                         ` Bhupesh SHARMA
2017-01-13 13:26                           ` Yao, Jiewen
2016-12-23  3:35                     ` How to build commonlib of Basetools in x64 mode wang xiaofeng
     [not found]                       ` <CE7102C6-78B7-4631-8641-AF27FFAB52FE@apple.com>
2016-12-23  4:15                         ` wang xiaofeng
     [not found]                           ` <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C3866@shsmsx102.ccr.corp.intel.com>
2016-12-23  4:54                             ` Andrew Fish
2016-12-23  5:02                               ` wang xiaofeng
2016-12-23  5:09                               ` Gao, Liming
2016-12-20 12:22         ` [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables Evan Lloyd
  -- strict thread matches above, loose matches on Subject: below --
2017-12-15 19:28 evan.lloyd
2017-12-15 19:37 ` Evan Lloyd

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-list 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=74D8A39837DF1E4DA445A8C0B3885C503A8D46CC@shsmsx102.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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