From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io, nhi@os.amperecomputing.com
Subject: Re: [edk2-devel] [edk2-platforms][PATCH 1/3] Platform/Ampere: Add Readme.md
Date: Thu, 3 Dec 2020 17:20:53 +0000 [thread overview]
Message-ID: <20201203172053.GU1664@vanye> (raw)
In-Reply-To: <31782.1607010279980473846@groups.io>
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?
/
Leif
next prev parent reply other threads:[~2020-12-03 17:20 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 [this message]
2020-12-04 4:50 ` Nhi Pham
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=20201203172053.GU1664@vanye \
--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