From: Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>
To: Julien Grall <julien.grall@arm.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH] xen/arm: platform: additional Raspberry Pi compatible string
Date: Fri, 4 Oct 2019 00:47:20 +0000 [thread overview]
Message-ID: <d3bc1282725e47e38afa26cc4dfb7c95@dornerworks.com> (raw)
In-Reply-To: <aa1b244f-9500-7798-0f2f-a93567a12e2b@arm.com>
On Tuesday, September 17, 2019 7:05 AM, Julien Grall <julien.grall@arm.com> wrote:
>Hi Stewart,
>
>On 9/14/19 2:22 AM, Stewart Hildebrand wrote:
>> On Friday, September 13, 2019 5:42 PM, Julien Grall <julien.grall@arm.com> wrote:
>>> 2) Is the patch [1] merged? If so, which version?
>>
>> No.
>
>I would rather wait until the patch is merged in Linux before adding the
>compatible.
The downstream kernel has changed their compatible to "brcm,bcm2711" [8],
so "brcm,bcm2838" is obsolete now. While the upstream series has not been
merged yet [9], the lack of "brcm,bcm2711" in our compatible list is
preventing us from booting the downstream kernel. I will send a v2 of the
patch.
>This also raise the question on what's going to happen for blacklist
>device? Are they still going to contain "bcm2835"?
The peripherals/devices still have the same "brcm,bcm2835" prefix. No change.
[8] https://github.com/raspberrypi/linux/commit/53fdd7b8c8cb9c87190caab4fd459f89e1b4a7f8
[9] v3 https://patchwork.kernel.org/cover/11165395/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-10-04 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 19:11 [Xen-devel] [PATCH] xen/arm: platform: additional Raspberry Pi compatible string Stewart Hildebrand
2019-09-13 21:42 ` Julien Grall
2019-09-14 1:22 ` Stewart Hildebrand
2019-09-17 11:05 ` Julien Grall
2019-10-04 0:47 ` Stewart Hildebrand [this message]
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=d3bc1282725e47e38afa26cc4dfb7c95@dornerworks.com \
--to=stewart.hildebrand@dornerworks.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=julien.grall@arm.com \
--cc=julien@xen.org \
--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).