public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nhi Pham" <nhi@os.amperecomputing.com>
To: Leif Lindholm <leif@nuviainc.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH 1/3] Platform/Ampere: Add Readme.md
Date: Fri, 4 Dec 2020 04:50:24 +0000	[thread overview]
Message-ID: <MN2PR01MB5855D6D75595A2F0AF1CCABD96F10@MN2PR01MB5855.prod.exchangelabs.com> (raw)
In-Reply-To: <20201203172053.GU1664@vanye>

[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]

Hi Leif,


________________________________
From: Leif Lindholm <leif@nuviainc.com>
Sent: Friday, December 4, 2020 12:20 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; Nhi Pham OS <nhi@os.amperecomputing.com>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH 1/3] Platform/Ampere: Add Readme.md

Hi Nhi,

On Thu, Dec 03, 2020 at 07:44:39 -0800, Nhi Pham via groups.io wrote:
> >> +
> >> +```bash
> >> +$ wget https://acpica.org/sites/acpica/files/acpica-unix2-20200110.tar.gz
> >>
> >> +$ tar xzf acpica-unix2-20200110.tar.gz
> >> +$ cd acpica-unix2-20200110
> >> +$ make && sudo make install
> >> +$ iasl -v
> >> +```
> >
> > I could well believe a newer version of IASL than shipped with the
> > abovementioned Linux distros would be required. However, Instructions
> > for how to rebuild/install a newer acpica-tools would be better to
> > have in the top-level Readme.md.
>
> The top level README does not mention the IASL compiler. Do you think we should add it?

Yes, that's an omission - ACPI hasn't seen as much churn recently as
it did for a while, but the underlying problems with iasl's lack of
backwards/forwards compatibility has not been resolved.

Would you be happy to do so?

[Nhi] Yes, I would be willing to take a look at this as a different topic.  At this moment, it appears that only version 20200110 would work with our code,so we will need to state so specifically in our README.md.

/
    Leif


[-- Attachment #2: Type: text/html, Size: 2906 bytes --]

  reply	other threads:[~2020-12-04  4:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  4:03 [edk2-platforms][PATCH 0/3] Introduce Ampere Mt. Jade support to edk2-platforms Nhi Pham
2020-12-03  4:04 ` [edk2-platforms][PATCH 1/3] Platform/Ampere: Add Readme.md Nhi Pham
2020-12-03 12:49   ` Leif Lindholm
2020-12-03 15:44     ` [edk2-devel] " Nhi Pham
2020-12-03 17:20       ` Leif Lindholm
2020-12-04  4:50         ` Nhi Pham [this message]
2020-12-03  4:04 ` [edk2-platforms][PATCH 2/3] Update Readme.md Nhi Pham
2020-12-03  4:04 ` [edk2-platforms][PATCH 3/3] Maintainers.txt: Update for Ampere platforms Nhi Pham
2020-12-03 11:46 ` [edk2-platforms][PATCH 0/3] Introduce Ampere Mt. Jade support to edk2-platforms Leif Lindholm
2020-12-03 12:15   ` [edk2-devel] " Nhi Pham
2020-12-03 12:52     ` Leif Lindholm

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=MN2PR01MB5855D6D75595A2F0AF1CCABD96F10@MN2PR01MB5855.prod.exchangelabs.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