dt
Cc: Alistair Francis; meta-xilinx@yoctoproject.org
Subject: Re: [meta-xilinx] qemuboot.conf
On 29 January 2018 at 05:51, Martin Siegumfeldt wrote:
>
>
>
>
> From: Nathan Rossi
> Sent: Sunday, January 28, 2018 13:44
> To: Alistair Francis
>
On 29 January 2018 at 05:51, Martin Siegumfeldt wrote:
>
>
>
>
> From: Nathan Rossi
> Sent: Sunday, January 28, 2018 13:44
> To: Alistair Francis
> Cc: Martin Siegumfeldt; meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] qemu
From: Nathan Rossi
Sent: Sunday, January 28, 2018 13:44
To: Alistair Francis
Cc: Martin Siegumfeldt; meta-xilinx@yoctoproject.org
Subject: Re: [meta-xilinx] qemuboot.conf
On 24 January 2018 at 09:04, Alistair Francis wrote:
> On Tue, Jan 23, 2018 at 12:53
On 24 January 2018 at 09:04, Alistair Francis wrote:
> On Tue, Jan 23, 2018 at 12:53 AM, Martin Siegumfeldt
> wrote:
>> Hi,
>>
>> We are rendering a custom piece of HW based on Ultrascale+, and have the
>> Xilinx QEMU successfully running. An extensible SDK (eSDK) is delivered to
>> the applic
On Tue, Jan 23, 2018 at 12:53 AM, Martin Siegumfeldt wrote:
> Hi,
>
> We are rendering a custom piece of HW based on Ultrascale+, and have the
> Xilinx QEMU successfully running. An extensible SDK (eSDK) is delivered to
> the application developers and to close the loop we would like to be capab
Hi,
We are rendering a custom piece of HW based on Ultrascale+, and have the Xilinx
QEMU successfully running. An extensible SDK (eSDK) is delivered to theĀ
application developers and to close the loop we would like to be capable of
delivering also the QEMU instance. The machine image- and qemub