From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "John P. McDermott (USN Civilian)" <john.mcdermott@nrl.navy.mil>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM Hikey 960 - Missing Image Files for Xen
Date: Thu, 28 Sep 2017 09:01:40 -0400 [thread overview]
Message-ID: <20170928130140.GB18695@char.us.oracle.com> (raw)
In-Reply-To: <CB79FF8A-A587-41B0-B529-FBFD85966E8A@nrl.navy.mil>
On Thu, Sep 28, 2017 at 08:29:27AM -0400, John P. McDermott (USN Civilian) wrote:
> Xen Developers,
>
> The guidance for running Xen on a HiKey 960 identifies files that should be flashed onto the board, as part of the process for installing Xen.
>
> https://wiki.xen.org/wiki/HiKey960
>
> All but 2 of the files are available from 96 Boards or can be created by following the guidance. The 2 I have not been able to find are
>
> cache.img
> userdata.img
>
> I have found all sorts of guidance and source code that copies these files, assuming they exist. I have nothing on how these 2 files are generated or where copies might be found. Does anyone know how to get them or if they are even needed for Xen on the HiKey 960?
They are not needed.
>
> Sincerely,
>
> John
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-28 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 12:29 ARM Hikey 960 - Missing Image Files for Xen John P. McDermott (USN Civilian)
2017-09-28 13:01 ` Konrad Rzeszutek Wilk [this message]
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=20170928130140.GB18695@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=john.mcdermott@nrl.navy.mil \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).