From: Mark Salter <msalter@redhat.com>
To: Ian Campbell <ijc@debian.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Geoff Levand <geoff@infradead.org>,
Riku Voipio <riku.voipio@linaro.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
James Morse <james.morse@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64/acpi: Add fixup for HPE m400 quirks
Date: Tue, 03 Jul 2018 11:20:44 -0400 [thread overview]
Message-ID: <ff46b8ab2786eae798a9a650d24cb20ea1504fd2.camel@redhat.com> (raw)
In-Reply-To: <1530610221.9841.128.camel@debian.org>
On Tue, 2018-07-03 at 10:30 +0100, Ian Campbell wrote:
> On Wed, 2018-06-27 at 08:25 -0400, Mark Salter wrote:
> > On Wed, 2018-06-27 at 10:48 +0200, Ard Biesheuvel wrote:
> > > On 26 June 2018 at 22:20, Mark Salter <msalter@redhat.com> wrote:
> > > > [040h 0064 8] Address : 0000004FF7E9F0E0
> > > >
> > >
> > > This is a reserved region in the memory map. Does that apply to the
> > > other occurrences as well?
> >
> > Yes, they are all in the same reserved region.
>
> I wonder if it corresponds to some actual peripheral on a different X-
> gene based platform (e.g. perhaps a reference design)?
>
> Not sure what one would do with that information, just curious.
>
> Ian.
It's a reserved region of system RAM.
next prev parent reply other threads:[~2018-07-03 15:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 18:22 [PATCH] arm64/acpi: Add fixup for HPE m400 quirks Geoff Levand
2018-06-15 8:47 ` Riku Voipio
2018-06-15 9:51 ` Graeme Gregory
2018-06-15 11:14 ` James Morse
2018-06-15 17:17 ` Geoff Levand
2018-06-15 17:33 ` Mark Salter
2018-06-15 18:15 ` Geoff Levand
2018-06-15 19:14 ` Mark Salter
2018-06-18 16:18 ` James Morse
2018-06-18 18:04 ` Geoff Levand
2018-06-18 22:18 ` Mark Salter
2018-06-19 10:21 ` James Morse
2018-06-22 15:19 ` Mark Salter
2018-06-25 15:34 ` Mark Salter
2018-06-26 14:51 ` James Morse
2018-06-26 20:20 ` Mark Salter
2018-06-27 8:48 ` Ard Biesheuvel
2018-06-27 12:25 ` Mark Salter
2018-07-03 9:30 ` Ian Campbell
2018-07-03 15:20 ` Mark Salter [this message]
2018-06-28 10:06 ` James Morse
2018-06-29 13:05 ` Mark Salter
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=ff46b8ab2786eae798a9a650d24cb20ea1504fd2.camel@redhat.com \
--to=msalter@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=geoff@infradead.org \
--cc=hanjun.guo@linaro.org \
--cc=ijc@debian.org \
--cc=james.morse@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=riku.voipio@linaro.org \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).