From: Willy Tarreau <w@1wt.eu>
To: Dave Airlie <airlied@gmail.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org
Subject: Re: 3.5 regression on i915
Date: Sat, 6 Oct 2012 09:27:04 +0200 [thread overview]
Message-ID: <20121006072704.GA22465@1wt.eu> (raw)
In-Reply-To: <20121005235845.GE21163@1wt.eu>
On Sat, Oct 06, 2012 at 01:58:45AM +0200, Willy Tarreau wrote:
> On Sat, Oct 06, 2012 at 09:48:57AM +1000, Dave Airlie wrote:
> > Any reason you don't have KMS, you'll keep hitting these non-kms bugs
> > since it has no users anymore really.
> >
> > Granted they'll get fixed, but I suspect its a losing battle over time.
>
> Well, back in old times every time I tried to enable it, I only ran into
> problems so I got used to disable it, which made sense since it didn't
> bring me any benefit.
OK I found why in the end. When I enable KMS, my X server fails to start
and segfaults in intel_drv.so. So I think that the comment in Kconfig
below is quite appropriate :
config DRM_I915_KMS
bool "Enable modesetting on intel by default"
depends on DRM_I915
help
Choose this option if you want kernel modesetting enabled by default,
and you have a new enough userspace to support this. Running old
userspaces with this enabled will cause pain. Note that this causes
the driver to bind to PCI devices, which precludes loading things
like intelfb.
Regards,
Willy
next prev parent reply other threads:[~2012-10-06 7:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 23:42 3.5 regression on i915 Willy Tarreau
2012-10-05 23:48 ` Dave Airlie
2012-10-05 23:58 ` Willy Tarreau
2012-10-06 7:27 ` Willy Tarreau [this message]
2012-10-06 7:43 ` Dave Airlie
2012-10-06 7:59 ` Willy Tarreau
2012-10-06 8:24 ` Chris Wilson
2012-10-06 8:42 ` Willy Tarreau
2012-10-06 9:04 ` Chris Wilson
2012-10-06 9:17 ` Willy Tarreau
2012-10-06 16:10 ` Chris Wilson
2012-10-06 20:43 ` Willy Tarreau
2012-10-06 8:04 ` Chris Wilson
2012-10-06 8:20 ` Willy Tarreau
2012-10-06 8:43 ` Chris Wilson
2012-10-07 21:00 ` Daniel Vetter
2012-10-07 21:07 ` Willy Tarreau
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=20121006072704.GA22465@1wt.eu \
--to=w@1wt.eu \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.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