From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
Pawel Moll <pawel.moll@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: introduce a DTS for Xen unprivileged virtual machines
Date: Thu, 20 Sep 2012 11:17:02 +0100 [thread overview]
Message-ID: <1348136222.26501.19.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1348076658-4511-1-git-send-email-stefano.stabellini@eu.citrix.com>
On Wed, 2012-09-19 at 18:44 +0100, Stefano Stabellini wrote:
> +/include/ "skeleton.dtsi"
> +
> +/ {
> + model = "XENVM-4.2";
Why the shouty caps?
Did you mean 4.3 here and throughout?
> + compatible = "xen,xenvm-4.2", "arm,vexpress";
Is this second compatible thing actually true? We don't actually emulate
much (anything?) of what would be on a real vexpress motherboard.
"arm,vexpress" is used only in v2m.c and I don't think we want the
majority of that -- we don't provide any of the peripherals which it
registers.
I think the only things we might want out of that lot are the arch timer
and perhaps the uart0 (as a debug port).
I suspect we should have our own xen machine .c.
[...]
> + gic: interrupt-controller@2c001000 {
> + compatible = "arm,cortex-a9-gic";
Don't we mean "arm,cortex-a15-gic" here? That's what we actually
provide. I'm not sure how the a9 and a15 differ.
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0x2c001000 0x1000>,
> + <0x2c002000 0x100>;
> + };
> +
Ian.
next prev parent reply other threads:[~2012-09-20 10:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 17:44 Stefano Stabellini
2012-09-20 10:06 ` Pawel Moll
2012-09-20 11:18 ` Dave Martin
2012-09-20 12:02 ` Stefano Stabellini
2012-09-20 21:29 ` Konrad Rzeszutek Wilk
2012-09-21 11:17 ` Stefano Stabellini
2012-09-20 11:39 ` Stefano Stabellini
2012-09-20 11:55 ` Pawel Moll
2012-09-20 12:15 ` Stefano Stabellini
2012-09-20 12:28 ` Marc Zyngier
2012-09-20 13:30 ` Ian Campbell
2012-09-20 13:50 ` Marc Zyngier
2012-09-20 10:17 ` Ian Campbell [this message]
2012-09-20 11:56 ` Stefano Stabellini
2012-09-20 12:18 ` Ian Campbell
2012-09-20 12:39 ` Stefano Stabellini
2012-09-20 13:16 ` Ian Campbell
2012-09-20 13:27 ` Arnd Bergmann
2012-09-20 14:11 ` Stefano Stabellini
2012-09-20 14:24 ` Pawel Moll
2012-09-20 10:45 ` [Xen-devel] " David Vrabel
2012-09-20 11:21 ` Dave Martin
2012-09-20 12:04 ` Stefano Stabellini
2012-09-20 12:57 ` Dave Martin
2012-09-20 12:00 ` Stefano Stabellini
2012-09-20 20:26 ` Rob Herring
2012-09-21 11:14 ` Stefano Stabellini
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=1348136222.26501.19.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®