From: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
To: <xen-devel@lists.xenproject.org>
Cc: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: [Xen-devel] [PATCH] xen/arm: platform: additional Raspberry Pi compatible string
Date: Fri, 13 Sep 2019 15:11:47 -0400 [thread overview]
Message-ID: <20190913191147.2323-1-stewart.hildebrand@dornerworks.com> (raw)
Upstream Linux kernel will use "brcm,bcm2711" as the compatible string
for Raspberry Pi 4 [1]. Add this string to our platform compatible list
for compatibility with the upstream kernel.
[1] https://patchwork.kernel.org/patch/11092621/
Signed-off-by: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
---
xen/arch/arm/platforms/brcm-raspberry-pi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/arch/arm/platforms/brcm-raspberry-pi.c b/xen/arch/arm/platforms/brcm-raspberry-pi.c
index e22d2b3184..a95a3db83f 100644
--- a/xen/arch/arm/platforms/brcm-raspberry-pi.c
+++ b/xen/arch/arm/platforms/brcm-raspberry-pi.c
@@ -21,6 +21,7 @@
static const char *const brcm_bcm2838_dt_compat[] __initconst =
{
+ "brcm,bcm2711",
"brcm,bcm2838",
NULL
};
--
2.23.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-09-13 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 19:11 Stewart Hildebrand [this message]
2019-09-13 21:42 ` [Xen-devel] [PATCH] xen/arm: platform: additional Raspberry Pi compatible string Julien Grall
2019-09-14 1:22 ` Stewart Hildebrand
2019-09-17 11:05 ` Julien Grall
2019-10-04 0:47 ` Stewart Hildebrand
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=20190913191147.2323-1-stewart.hildebrand@dornerworks.com \
--to=stewart.hildebrand@dornerworks.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).