xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: AP Xen <apxeng@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 4.1 + PVOPS 2.6.32.40 and Sandy Bridge integrated graphics
Date: Tue, 31 May 2011 15:13:50 -0400	[thread overview]
Message-ID: <20110531191350.GA22156@dumpdata.com> (raw)
In-Reply-To: <BANLkTiktJN4dYcYmuASzoCdpkAysoTp3MQ@mail.gmail.com>

> > I was under the impression that SandyBridge support required
> > kernel 2.6.37 or later..? The other issue is, do you have
> > this in your git tree:
> >
> > commit 96587057018b3ac0b11bf34b791aaadfc403fc80
> > Author: Zhang, Fengzhe <fengzhe.zhang@intel.com>
> > Date:   Wed Feb 16 22:26:20 2011 +0800
> 
> I do see this patch when I do "git log" and grep for the commit signature.
> 
> > Does Xorg work when you boot this kernel under baremetal?
> 
> I should have tried this before. No it does not. I see the same
> errors. So you might be right in that I need a kernel > than 2.6.37.
> Is there a tree out there that I can try? Or do I have to wait to for
> Linux 3.0 to come out which I know can work as a Dom0 out of the box
> without external patches?

You can do that.. or use 3.0-rc1 (available now), or you can use this tree:

(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/2.6.39.x)

  reply	other threads:[~2011-05-31 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 22:32 Xen 4.1 + PVOPS 2.6.32.40 and Sandy Bridge integrated graphics AP Xen
2011-05-31 13:59 ` Konrad Rzeszutek Wilk
2011-05-31 19:05   ` AP Xen
2011-05-31 19:13     ` Konrad Rzeszutek Wilk [this message]
2011-06-03 18:57       ` AP Xen
2011-06-03 19:59         ` Konrad Rzeszutek Wilk
2011-06-03 20:22           ` AP Xen

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=20110531191350.GA22156@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=apxeng@gmail.com \
    --cc=xen-devel@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 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).