All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ruiz Ramos, Daniel Norberto" <drramos@indra.es>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>,
	"meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>
Subject: Re: running qemu on x86 to emulate t2080 (e6500 cores)
Date: Mon, 11 May 2015 15:15:38 +0200	[thread overview]
Message-ID: <5BA00E0F7591B04FB7D7BE67EEB85FDFC1FB87@MADARRMAILBOX03.indra.es> (raw)
In-Reply-To: <BN3PR03MB13679AF26ABAD744666DED1BE4DB0@BN3PR03MB1367.namprd03.prod.outlook.com>

Thank you for your quick answer Zhenhua,
Please correct me if I'm wrong, but the qemu-system-ppc64 compiled to x86 can support  the previous e5500 core through -cpu e5500 option.
¿Does it mean that there are some partial QorIQ hardware  emulation on x86 host QEMU?
¿Or we are talking about all qemus in Freescale SDK is only focused to let powerpc hardware emulates it-self?

Best regards,
Daniel.

-----Mensaje original-----
De: zhenhua.luo@freescale.com [mailto:zhenhua.luo@freescale.com]
Enviado el: lunes, 11 de mayo de 2015 14:42
Para: Ruiz Ramos, Daniel Norberto; meta-freescale@yoctoproject.org
Asunto: RE: running qemu on x86 to emulate t2080 (e6500 cores)

Hello Daniel,

Currently the x86 host QEMU emulation of QorIQ targets are not supported. QorIQ SDK can support the QorIQ boards QEMU emulation on target boards.


Best Regards,

Zhenhua

> -----Original Message-----
> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
> bounces@yoctoproject.org] On Behalf Of Ruiz Ramos, Daniel Norberto
> Sent: Monday, May 11, 2015 7:43 PM
> To: meta-freescale@yoctoproject.org
> Subject: [meta-freescale] running qemu on x86 to emulate t2080 (e6500 cores)
>
> Hello All,
> My name is Daniel and this is my first post here.
>
> Im trying to emulate a T2080RDB for testing images generated with bitbake, but
> I have not luck with it. I couldn't find any qemu that support -cpu e6500 option.
> I've tried compiling qemu from source, and even all qemus that there are in my
> yocto project build.
> All qemu says the same:
>
> $ ./qemu-system-ppc64 -machine ppce500 -cpu e6500 Unable to initialize CPU!
>
>
> ¿Does anybody knows if the new cpu of Freescale is not supported?
>
> Daniel.
>
>
> Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
> contiene información de carácter confidencial exclusivamente dirigida a su
> destinatario o destinatarios. Si no es vd. el destinatario indicado, queda
> notificado que la lectura, utilización, divulgación y/o copia sin autorización está
> prohibida en virtud de la legislación vigente. En el caso de haber recibido este
> correo electrónico por error, se ruega notificar inmediatamente esta
> circunstancia mediante reenvío a la dirección electrónica del remitente.
> Evite imprimir este mensaje si no es estrictamente necesario.
>
> This email and any file attached to it (when applicable) contain(s) confidential
> information that is exclusively addressed to its recipient(s). If you are not the
> indicated recipient, you are informed that reading, using, disseminating and/or
> copying it without authorisation is forbidden in accordance with the legislation
> in effect. If you have received this email by mistake, please immediately notify
> the sender of the situation by resending it to their email address.
> Avoid printing this message if it is not absolutely necessary.
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Si no es vd. el destinatario indicado, queda notificado que la lectura, utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente.
Evite imprimir este mensaje si no es estrictamente necesario.

This email and any file attached to it (when applicable) contain(s) confidential information that is exclusively addressed to its recipient(s). If you are not the indicated recipient, you are informed that reading, using, disseminating and/or copying it without authorisation is forbidden in accordance with the legislation in effect. If you have received this email by mistake, please immediately notify the sender of the situation by resending it to their email address.
Avoid printing this message if it is not absolutely necessary.


  parent reply	other threads:[~2015-05-11 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 11:43 running qemu on x86 to emulate t2080 (e6500 cores) Ruiz Ramos, Daniel Norberto
2015-05-11 12:41 ` zhenhua.luo
2015-05-11 12:44   ` Otavio Salvador
2015-05-12  6:22     ` Luo Zhenhua
2015-05-11 13:15   ` Ruiz Ramos, Daniel Norberto [this message]
2015-05-12  6:24     ` Luo Zhenhua

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=5BA00E0F7591B04FB7D7BE67EEB85FDFC1FB87@MADARRMAILBOX03.indra.es \
    --to=drramos@indra.es \
    --cc=meta-freescale@yoctoproject.org \
    --cc=zhenhua.luo@freescale.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 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.