From: Tabi Timur-B04825 <B04825@freescale.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Alexander Graf <agraf@suse.de>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Gala Kumar-B11780 <B11780@freescale.com>
Subject: Re: RFC: top level compatibles for virtual platforms
Date: Sat, 9 Jul 2011 01:39:26 +0000 [thread overview]
Message-ID: <CAOZdJXVp5LHqYEMoqpnKEkuWyuE6kwU+Z9VwUYLPcz-+h_gqfw@mail.gmail.com> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150316EAB6@039-SN1MPN1-003.039d.mgd.msft.net>
On Fri, Jul 8, 2011 at 1:43 PM, Yoder Stuart-B08248
<B08248@freescale.com> wrote:
> =A0 "MPC85xxDS" - for a virtual machine for the e500v2 type platforms
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 and would support 85xx targets, plus P202=
0, P1022,etc
>
> =A0 "corenet-32-ds" - for a virtual machine similar to the 32-bit P4080
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 platforms
>
> =A0 "corenet-64-ds" - for a virtual machine based on a 64-bit corenet
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 platform
I think we should drop the "DS" because that's a name applied to
certain Freescale reference boards.
Is being a CoreNet board really something meaningful with respect to
KVM? I don't see the connection.
Also, if these are KVM creations, shouldn't there be a "kvm" in the
compatible string somewhere?
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2011-07-09 1:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 18:43 RFC: top level compatibles for virtual platforms Yoder Stuart-B08248
2011-07-09 1:39 ` Tabi Timur-B04825 [this message]
2011-07-09 2:42 ` Grant Likely
2011-07-11 14:36 ` Yoder Stuart-B08248
2011-07-11 14:34 ` Yoder Stuart-B08248
2011-07-11 15:45 ` Timur Tabi
2011-07-11 16:24 ` Scott Wood
2011-07-11 17:41 ` Yoder Stuart-B08248
2011-07-11 18:04 ` Scott Wood
2011-07-11 20:41 ` Yoder Stuart-B08248
2011-07-11 21:06 ` Scott Wood
2011-07-12 14:20 ` Yoder Stuart-B08248
2011-07-11 17:54 ` Timur Tabi
2011-07-11 19:59 ` Grant Likely
2011-07-11 20:06 ` Scott Wood
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=CAOZdJXVp5LHqYEMoqpnKEkuWyuE6kwU+Z9VwUYLPcz-+h_gqfw@mail.gmail.com \
--to=b04825@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B11780@freescale.com \
--cc=agraf@suse.de \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.