From: Eric Anholt <eric@anholt.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>
Subject: Re: [Regression] X server doesn't start on MSI Wind w/ current mainline
Date: Tue, 06 Jan 2009 20:01:17 -0800 [thread overview]
Message-ID: <1231300877.4690.46.camel@gaiman.anholt.net> (raw)
In-Reply-To: <200901050948.14352.jbarnes@virtuousgeek.org>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Mon, 2009-01-05 at 09:48 -0800, Jesse Barnes wrote:
> On Sunday, January 4, 2009 3:11 pm Rafael J. Wysocki wrote:
> > On Saturday 03 January 2009, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > With the current mainline and the linux-next branch of your pci-2.6 tree
> > > on top, the X server doesn't start any more on MSI Wind (Intel hardware)
> > > w/ openSUSE 11.1 .
> > >
> > > I also tested the linux-next branch of the pci-2.6 tree on top of 2.6.28
> > > and it doesn't cause any problem with the X server to happen.
> >
> > Well, I pulled the mainline from today, unsetted DRM_I915_KMS and it works
> > again.
> >
> > BTW, what user land is necessary for the KMS to work?
>
> Ah yeah defaulting to KMS enabled will probably get you undesirable results at
> this point. You'll need a bleeding edge 2D driver (from xf86-video-intel git)
> and libdrm 2.4.3 to make this all work. Be sure to pass "--enable-kms" when
> you configure your 2D driver.
The --enable-kms requirement is gone now. Hopefully soon we'll have a
release out and can mention a version number in the Kconfig.
--
Eric Anholt
eric@anholt.net eric.anholt@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-07 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 12:28 Rafael J. Wysocki
2009-01-04 23:11 ` Rafael J. Wysocki
2009-01-05 17:48 ` Jesse Barnes
2009-01-07 4:01 ` Eric Anholt [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=1231300877.4690.46.camel@gaiman.anholt.net \
--to=eric@anholt.net \
--cc=airlied@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®