All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: PGNet Dev <pgnet.dev@gmail.com>
Cc: andrew.cooper3@citrix.com, daniel.kiper@oracle.com,
	wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: Status of multiboot2 support on EFI?
Date: Wed, 3 Feb 2016 11:16:07 +0000	[thread overview]
Message-ID: <20160203111607.GH10990@citrix.com> (raw)
In-Reply-To: <56B11980.4070103@gmail.com>

On Tue, Feb 02, 2016 at 01:02:56PM -0800, PGNet Dev wrote:
> Here http://wiki.xenproject.org/wiki/Xen_EFI#Xen_as_gz_binary refers to
> original discussion in 2013 (work has been deferred to Xen 4.6. )
> 
> and says "work has been deferred to Xen 4.6."
> 
> >I think that this should be Xen 4.8 target.
> 
> That's roughly another year+ from now for EFI support?
> 
> Per, http://wiki.xenproject.org/wiki/Xen_Roadmap, there's no 4.8 info at
> all.
> 
> But 8months plus 4.7 release =~ Feb 2017?
> 

We now have 6 months cycle.

The release after 4.7 will freeze in October and hopefully release in
December.

Wei.

> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-02-03 11:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 17:01 Status of multiboot2 support on EFI? PGNet Dev
2016-02-02 17:10 ` Konrad Rzeszutek Wilk
2016-02-02 17:10 ` Andrew Cooper
2016-02-02 20:49   ` Daniel Kiper
2016-02-02 21:02     ` PGNet Dev
2016-02-02 21:20       ` Daniel Kiper
2016-02-02 21:24         ` Andrew Cooper
2016-02-02 21:50         ` Doug Goldstein
2016-02-03 16:08           ` Daniel Kiper
2016-02-03 17:03             ` Daniel Kiper
2016-02-12 19:08               ` Daniel Kiper
2016-03-10 10:28                 ` Daniel Kiper
2016-02-03 11:16       ` Wei Liu [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=20160203111607.GH10990@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=pgnet.dev@gmail.com \
    --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 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.