ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh@kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Linus Walleij <linus.ml.walleij@gmail.com>,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Mon, 19 May 2014 23:41:04 +0100	[thread overview]
Message-ID: <CAFEAcA-1d_47g3Z3R=CNyE8U5+huJ0yDvAMU+BRacajxE5qPXw@mail.gmail.com> (raw)
In-Reply-To: <4931877.zNfKfvcgox@wuerfel>

On 19 May 2014 13:20, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 16 May 2014 23:20:42 Ben Hutchings wrote:
>> Versatile is one of ARM's own development boards, but more importantly
>> it's something QEMU can emulate.
>
> We should really have this in multiplatform soon, I think the last issue
> for versatile is common clock support, but Linus Walleij may have more
> details about what remains here.
>
> We should also make it possible to enable ARCH_VIRT for pre-ARMv7 to
> get qemu users to move over to that.

I think the main reason many people still use QEMU's versatilepb
model is that it has PCI. If you want people to move off that then
getting those "generic device-tree driven PCI" patches into the
kernel would probably be a good start :-)  At that point we can
reasonably easily add PCI support to the QEMU 'virt' board.

thanks
-- PMM

  reply	other threads:[~2014-05-19 22:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  3:00 Jason Cooper
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59   ` Alexandre Belloni
2014-05-11 14:22   ` Olof Johansson
2014-05-15 12:15   ` Grant Likely
2014-05-15 13:38     ` Jason Cooper
2014-05-15 18:50     ` Rob Herring
2014-05-15 19:42       ` Jason Cooper
2014-05-16  3:30         ` Olof Johansson
2014-05-16  4:10           ` Jason Cooper
2014-05-16 18:31             ` Ben Hutchings
2014-05-16 18:42               ` Jason Cooper
2014-05-16 22:20                 ` Ben Hutchings
2014-05-19 12:20                   ` Arnd Bergmann
2014-05-19 22:41                     ` Peter Maydell [this message]
2014-05-19 23:06                     ` Rob Herring
2014-05-20  8:08                       ` Arnd Bergmann
2014-05-22 14:44                         ` Rob Herring
2014-05-23 13:48                         ` Linus Walleij
2014-05-23 14:42                           ` Arnd Bergmann
2014-05-23 13:46                       ` Linus Walleij
2014-05-23 13:40       ` Linus Walleij
2014-05-23 13:57         ` Arnd Bergmann
2014-05-16  3:39     ` Olof Johansson

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='CAFEAcA-1d_47g3Z3R=CNyE8U5+huJ0yDvAMU+BRacajxE5qPXw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linus.ml.walleij@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh@kernel.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