From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic SoC updates for v4.15
Date: Mon, 30 Oct 2017 12:12:49 +0100 [thread overview]
Message-ID: <7hy3nsubwu.fsf@baylibre.com> (raw)
In-Reply-To: <CAK8P3a1fLbzp4xzFyTEO1w4vu=X=wwSV74_WBXiuYqTeF1P5ng@mail.gmail.com> (Arnd Bergmann's message of "Mon, 30 Oct 2017 11:26:07 +0100")
[ + Martin ]
Arnd Bergmann <arnd@arndb.de> writes:
> On Sun, Oct 29, 2017 at 5:43 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>
>> ----------------------------------------------------------------
>> Amlogic SoC updates for v4.15
>> - add SMP support to Meson8/8b
>
> Pulled into next/soc. For my understanding, could you clarify what
> this line is needed for on meson?
>
> +textofs-$(CONFIG_ARCH_MESON) := 0x00208000
I belive this is due to the first 2M being reserved for secure memory
on some Meson8 SoCs, but maybe Martin can add more clarification if
needed.
Kevin
next prev parent reply other threads:[~2017-10-30 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 16:43 [GIT PULL] Amlogic SoC updates for v4.15 Kevin Hilman
2017-10-30 10:26 ` Arnd Bergmann
2017-10-30 11:12 ` Kevin Hilman [this message]
2017-10-30 21:52 ` Martin Blumenstingl
2017-11-02 15:49 ` Arnd Bergmann
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=7hy3nsubwu.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).