public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Dave Airlie <airlied@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kms in defconfig
Date: Tue, 28 Apr 2009 10:04:21 -0700	[thread overview]
Message-ID: <20090428100421.5ea15d67@hobbes> (raw)
In-Reply-To: <1240903942.7620.68.camel@twins>

On Tue, 28 Apr 2009 09:32:22 +0200
Peter Zijlstra <peterz@infradead.org> wrote:

> On Tue, 2009-04-28 at 11:54 +1000, Dave Airlie wrote:
> > On Tue, Apr 28, 2009 at 1:40 AM, Peter Zijlstra
> > <peterz@infradead.org> wrote:
> > > On Mon, 2009-04-27 at 10:39 +0200, Ingo Molnar wrote:
> > >> * Dave Airlie <airlied@gmail.com> wrote:
> > >>
> > >> > Hi guys,
> > >> >
> > >> > I just noticed CONFIG_DRM_I915_KMS is enabled for x86-64.
> > >> >
> > >> > This should never be the case, as anyone who built defconfig
> > >> > kernels before, will now get KMS enabled when really they need
> > >> > to have done userspace upgrades.
> > >>
> > >> I've yet to see such a bugreport.
> > >
> > > Whenever I accidentally enable KMS I get a dead X (happens way
> > > more often that I'd like to), I blame this on the ubuntu Xorg
> > > packages, but can't be arsed to fix it myself -- hopefully the
> > > kinky koala will fix stuff, but who knows.
> > 
> > Well you can't really blame anyone else for it, since you have to
> > put the code upstream
> > in the kernel before you can release drivers that use it for
> > distros to package.
> > 
> > So it would be impossible for any distro to have shipped kms
> > drivers in a useful fashion before KMS is actually in the kernel.
> 
> Can't the driver detect KMS and use it when present? In that case they
> could just ship a KMS capable driver that works either way.
> 
> Anyway, I'm sure it'll all sort itself out.

Yeah Jaunty has such drivers, but Intrepid released with 2.4.x
xf86-video-intel drivers I think, which doesn't have autodetection.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-04-28 17:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27  8:21 kms in defconfig Dave Airlie
2009-04-27  8:39 ` Ingo Molnar
2009-04-27  8:56   ` Dave Airlie
2009-04-28  1:45     ` Tejun Heo
2009-04-28  1:59       ` Linus Torvalds
2009-04-28  6:29         ` Ingo Molnar
2009-04-28 16:54         ` david
2009-04-28 17:13           ` Linus Torvalds
2009-04-28 17:22             ` Ingo Molnar
2009-04-28 17:36               ` Steven Rostedt
2009-04-28 19:18                 ` Ingo Molnar
2009-04-28 21:23                   ` Steven Rostedt
2009-04-28 17:23             ` david
2009-04-28 17:50               ` Linus Torvalds
2009-04-28 21:43                 ` Florian Mickler
2009-04-28 21:50                   ` david
2009-04-28 23:10                     ` Florian Mickler
2009-04-28 23:29                       ` david
2009-04-29  6:55                   ` Giacomo Catenazzi
2009-04-29  5:36     ` Andrew Morton
2009-04-29  5:59       ` Dave Airlie
2009-04-27 15:40   ` Peter Zijlstra
2009-04-28  1:54     ` Dave Airlie
2009-04-28  7:32       ` Peter Zijlstra
2009-04-28 17:04         ` Jesse Barnes [this message]
2009-04-28 23:42         ` Dave Airlie

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=20090428100421.5ea15d67@hobbes \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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