From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Proposed patches for Linux 3.1 kernel.
Date: Thu, 21 Jul 2011 13:59:56 -0400 [thread overview]
Message-ID: <20110721175956.GA19609@dumpdata.com> (raw)
In-Reply-To: <182250971.20110721164359@eikelenboom.it>
On Thu, Jul 21, 2011 at 04:43:59PM +0200, Sander Eikelenboom wrote:
> Thursday, July 21, 2011, 4:17:15 PM, you wrote:
>
> > The 3.0 is suppose to be released today, or perhaps tomorrow.
>
> > For 3.1 kernel we have this long list of features and bug-fixes that we are going
> > to ask Linus to pick up:
>
> > - VGA text support. Since Xen is the first payload on the bootloader it gets the
> > screen information - now with this patch we can copy it from the hypervisor
> > and enjoy 80x25 old-school text output.
>
> I assume this one will be proposed for 3.0.1 stable as well ?
Sadly no - it is considered a feature - and those (as I understand, maybe I am
incorrect?) don't go on the stable wagon.
The vga patch is self-contained in here: http://darnok.org/xen/vga.patch if you would
like to patch your 3.0 kernel. Keep in mind - that you can still run stock 3.0 - with Xorg,
frame-buffer support (KMS), or with serial output.
next prev parent reply other threads:[~2011-07-21 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 14:17 Proposed patches for Linux 3.1 kernel Konrad Rzeszutek Wilk
2011-07-21 14:43 ` [Xen-devel] " Sander Eikelenboom
2011-07-21 17:59 ` Konrad Rzeszutek Wilk [this message]
2011-07-21 19:04 ` Jeremy Fitzhardinge
2011-07-22 3:30 ` Konrad Rzeszutek Wilk
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=20110721175956.GA19609@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.