From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Leif Lindholm <leif@nuviainc.com>
Subject: Re: [PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3
Date: Mon, 30 Mar 2020 15:12:11 +0200 [thread overview]
Message-ID: <CAKv+Gu8kr1nzJzPn63HgoU=afn_WZBNRcWzC0=oZ7kUvfkG1UQ@mail.gmail.com> (raw)
In-Reply-To: <adedcac4-a6d9-2332-afe9-f04bf0aa4817@akeo.ie>
On Mon, 30 Mar 2020 at 15:09, Pete Batard <pete@akeo.ie> wrote:
>
> On 2020.03.30 14:06, Ard Biesheuvel wrote:
> > On Fri, 27 Mar 2020 at 14:06, Pete Batard <pete@akeo.ie> wrote:
> >>
> >> Incidentally, this is not an [edk2-platform] patch, as the subject line
> >> from previous mail seemed to indicate, but an [edk2] patch.
> >>
> >
> > Do we have a user for this?
>
> Yes we do. I have a pachset lined up that updates the Raspberry Pi ACPI
> to 6.3, that has a dependency on this.
>
But does the RPi have SPE and the associated overflow interrupt? ACPI
is designed to be backward compatible, so it is perfectly acceptable
to use the 6.2 macros in the context of a firmware implementation that
complies with 6.3. Or is there another reason you want to update the
MADT to 6.3?
next prev parent reply other threads:[~2020-03-30 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:01 [edk2-platforms][PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3 Pete Batard
2020-03-27 13:06 ` [PATCH " Pete Batard
2020-03-30 13:06 ` Ard Biesheuvel
2020-03-30 13:09 ` Pete Batard
2020-03-30 13:12 ` Ard Biesheuvel [this message]
2020-03-30 13:20 ` Ard Biesheuvel
2020-03-30 13:56 ` Pete Batard
2020-03-30 14:01 ` Ard Biesheuvel
2020-03-30 14:06 ` Pete Batard
2020-03-30 14:16 ` Ard Biesheuvel
2020-03-30 14:29 ` Pete Batard
2020-03-30 14:34 ` Ard Biesheuvel
2020-03-30 14:39 ` Pete Batard
2020-03-30 14:42 ` Ard Biesheuvel
2020-03-30 14:50 ` Pete Batard
2020-03-30 14:19 ` Ard Biesheuvel
2020-03-30 14:33 ` Pete Batard
2020-03-30 14:48 ` [edk2-platforms][PATCH " Ard Biesheuvel
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='CAKv+Gu8kr1nzJzPn63HgoU=afn_WZBNRcWzC0=oZ7kUvfkG1UQ@mail.gmail.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