From: Daniel Kiper <daniel.kiper@oracle.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: andrew.cooper3@citrix.com, xen-devel@lists.xen.org,
pgnet.dev@gmail.com, wei.liu2@citrix.com
Subject: Re: Status of multiboot2 support on EFI?
Date: Fri, 12 Feb 2016 20:08:58 +0100 [thread overview]
Message-ID: <20160212190858.GM3482@olila.local.net-space.pl> (raw)
In-Reply-To: <20160203170350.GE20613@olila.local.net-space.pl>
On Wed, Feb 03, 2016 at 06:03:50PM +0100, Daniel Kiper wrote:
> On Wed, Feb 03, 2016 at 05:08:44PM +0100, Daniel Kiper wrote:
> > On Tue, Feb 02, 2016 at 03:50:17PM -0600, Doug Goldstein wrote:
> > > On 2/2/16 3:20 PM, Daniel Kiper wrote:
> > > > 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?
> > > >
> > > > Sadly I am not able to devote 100% of my time to this project right now.
> > > > Maybe it will happen when I finish our internal work. However, I think
> > > > that there is another option. You can help with some stuff on this issue.
> > > > This way we may finish whole project a bit earlier.
> > > >
> > > > Daniel
> > > >
> > > > PS I can post latest patchset (it does not contain all suggested fixes)
> > > > rebased on latest master. This way you can continue your work in
> > > > more friendly environment. Is it sufficient for you?
> > >
> > > Can you make a branch available somewhere? You don't even have to rebase
> > > it. That way others will be able to rebase and hopefully move it forward.
> >
> > Xen stuff is rebased because we needed it internally. I will rebase GRUB2
> > patches for convenience too. I hope that I will post them somewhere by the
> > end of this week.
> >
> > Daniel
> >
> > PS If you want to work on any part of this project please coordinate
> > all stuff with me. However, as I said earlier I am going to restart
> > work on it in 2-3 weeks.
>
> Fortunately I was able to reschedule less important stuff and it looks that
> I will be able to restart work on this project next week (100% of my time).
> I am going to release GRUB2 v3 patches first and then Xen v3 patches will
> follow. I hope that helps. If you have any questions please drop me a line.
I am restarting work on GRUB2 stuff. Expect new version in week or two.
Xen v3 patches will follow.
Daniel
next prev parent reply other threads:[~2016-02-12 19:08 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 [this message]
2016-03-10 10:28 ` Daniel Kiper
2016-02-03 11:16 ` Wei Liu
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=20160212190858.GM3482@olila.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=pgnet.dev@gmail.com \
--cc=wei.liu2@citrix.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 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).