On 11/22/2017 03:48 AM, Nathan Rossi wrote:
On 22 November 2017 at 05:32, Manjukumar Harthikote Matha
<[email protected]> wrote:


On 11/21/2017 11:03 AM, Alistair Francis wrote:

[This sender failed our fraud detection checks and may not be who they
appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

On Tue, Nov 21, 2017 at 7:04 AM, Nathan Rossi <[email protected]>
wrote:

On 21 November 2017 at 07:33, Alistair Francis
<[email protected]> wrote:

This series adds QEMU support to all Zynq-7000 machines.


I guess you mean all eval board Zynq-7000 machines.


Yes, good point.


The changes work well, I suspect the intention here is to setup these
targets for QEMU support so as to remove the qemu-zynq7 machine? If so
that sounds like a good plan :).


I wasn't intending on removing the qemu-zynq7 machine, but I'm not
opposed to removing it.

I would like to ensure we have something that boots on mainline at all
times. If we are happy that the ZC702 and/or ZC706 can do that
removing the QEMU machine makes sense.


I would not remove the existing qemu-zynq7 machine.

Just curious, any particular reason?

Since the zc702 machine does work fine with mainline QEMU (at least as
good as the qemu-zynq7 machine does).


The main reason is upstream works having a seperate QEMU machine like qemu-zynq7 and I don't want our layer to deviate from this.

With zynqmp our QEMU took some deviation including devicetrees, multi-arch qemu etc, these things haven't been upstreamed yet. To support our existing product flow including PetaLinux, the best way is to have the QEMU in our machines just like this patch.

Thanks,
Manju
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to