From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Jan Beulich <JBeulich@suse.com>,
shannon.zhao@linaro.org
Cc: hangaohuai@huawei.com, stefano.stabellini@eu.citrix.com,
peter.huangpeng@huawei.com, andrew@fubar.geek.nz,
stefano.stabellini@citrix.com, david.vrabel@citrix.com,
boris.ostrovsky@oracle.com, xen-devel@lists.xen.org,
parth.dixit@linaro.org, christoffer.dall@linaro.org
Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 3
Date: Wed, 2 Sep 2015 12:43:33 +0100 [thread overview]
Message-ID: <1441194213.26292.149.camel@citrix.com> (raw)
In-Reply-To: <55D380BC.9080905@citrix.com>
On Tue, 2015-08-18 at 12:00 -0700, Julien Grall wrote:
> Hi,
>
> On 18/08/2015 02:34, Shannon Zhao wrote:
> > IIUC, this is a requirement for Linux. Because when Linux parses the
> > minimal DT, it uses below dt_params to match the DT properties. If it
> > doesn't match any of them, it will fial.
> > See efi_get_fdt_params in drivers/firmware/efi/efi.c.
>
> This is *not* a requirement for Linux. All those properties are internal
> to Linux so it's not exposed to anyone else. We have room to change it
> while we standardize the property.
This thread is not the correct forum for such standardisation, since we
(Xen) cannot do so in isolation. I've not yet seen any discussion in the
appropriate places and we really should be doing so before we
build/finalise a design based upon it (otherwise we get to the end and the
rest of the world says "no").
AFAICT the correct place to discuss would be the devicetree-spec ML[0], and
perhaps also some or all of:
* Some appropriate UEFI forum?
* Linux (~=devicetree-spec?) since we are building on their internal
spec?
* BSD, since we would like them to support it?
Is someone going to make such a proposal?
Ian.
[0] http://vger.kernel.org/vger-lists.html#devicetree-spec
prev parent reply other threads:[~2015-09-02 11:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 14:59 Design doc of adding ACPI support for arm64 on Xen - version 3 Shannon Zhao
2015-08-14 15:17 ` Julien Grall
2015-08-17 13:01 ` Shannon Zhao
2015-08-17 16:10 ` Julien Grall
2015-08-18 3:19 ` Shannon Zhao
2015-08-18 6:36 ` Julien Grall
2015-08-18 7:23 ` Shannon Zhao
2015-08-18 16:13 ` Julien Grall
2015-08-14 15:59 ` Konrad Rzeszutek Wilk
2015-08-17 15:33 ` Jan Beulich
2015-08-17 16:19 ` Julien Grall
2015-08-18 5:10 ` Jan Beulich
2015-08-18 6:43 ` Julien Grall
2015-08-18 7:01 ` Jan Beulich
2015-08-18 7:46 ` Shannon Zhao
2015-08-18 19:01 ` Julien Grall
2015-08-18 3:41 ` Shannon Zhao
2015-08-18 5:14 ` Jan Beulich
2015-08-18 7:35 ` Shannon Zhao
2015-08-18 8:15 ` Jan Beulich
2015-08-18 8:21 ` Shannon Zhao
2015-08-18 9:11 ` Jan Beulich
2015-08-18 9:34 ` Shannon Zhao
2015-08-18 19:00 ` Julien Grall
2015-09-02 11:43 ` Ian Campbell [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=1441194213.26292.149.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew@fubar.geek.nz \
--cc=boris.ostrovsky@oracle.com \
--cc=christoffer.dall@linaro.org \
--cc=david.vrabel@citrix.com \
--cc=hangaohuai@huawei.com \
--cc=julien.grall@citrix.com \
--cc=parth.dixit@linaro.org \
--cc=peter.huangpeng@huawei.com \
--cc=shannon.zhao@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@huawei.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).