From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm: document "mach-virt" platform.
Date: Thu, 30 Jan 2014 18:28:59 +0100 [thread overview]
Message-ID: <201401301828.59294.arnd@arndb.de> (raw)
In-Reply-To: <1391098262-15944-1-git-send-email-ian.campbell@citrix.com>
On Thursday 30 January 2014, Ian Campbell wrote:
> mach-virt has existed for a while but it is not written down what it actually
> consists of. Although it seems a bit unusual to document a binding for an
> entire platform since mach-virt is entirely virtual it is helpful to have
> something to refer to in the absence of a single concrete implementation.
>
> I've done my best to capture the requirements based on the git log and my
> memory/understanding.
>
> While here remove the xenvm dts example, the Xen tools will now build a
> suitable mach-virt compatible dts when launching the guest.
It might be worth noting in the changeset comment that the 'compatible'
string is actually no longer needed on newer kernels: All the members
of the machine descriptor are now the defaults (we should remove the
virt_init() function as well), and the fallback machine descriptor should
work just fine if any other string gets passed.
Arnd
next prev parent reply other threads:[~2014-01-30 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:11 [PATCH] arm: document "mach-virt" platform Ian Campbell
2014-01-30 16:54 ` Christopher Covington
2014-01-30 17:12 ` Stefano Stabellini
2014-01-30 17:15 ` Ian Campbell
2014-01-30 17:43 ` Christopher Covington
2014-02-03 4:56 ` Christoffer Dall
2014-02-03 11:14 ` Ian Campbell
2014-02-03 13:46 ` Christopher Covington
2014-02-03 17:41 ` Christoffer Dall
2014-01-30 17:13 ` Marc Zyngier
2014-01-30 17:21 ` Ian Campbell
2014-01-30 17:24 ` Marc Zyngier
2014-01-30 17:29 ` Ian Campbell
2014-01-30 17:28 ` Arnd Bergmann [this message]
2014-01-30 17:33 ` Marc Zyngier
2014-01-31 17:48 ` Rob Herring
2014-01-30 17:33 ` Ian Campbell
2014-02-03 4:54 ` Christoffer Dall
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=201401301828.59294.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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