public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jerome Glisse <glisse@freedesktop.org>
Cc: Dave Airlie <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS
Date: Sat, 9 Jan 2010 10:17:19 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1001091012080.7821@localhost.localdomain> (raw)
In-Reply-To: <20100109120141.GA4319@localhost.localdomain>



On Sat, 9 Jan 2010, Jerome Glisse wrote:

> On Fri, Jan 08, 2010 at 06:50:41PM -0800, Jesse Barnes wrote:
> > 
> > Linus, can we ever drop those old paths?  Maybe after the new bits have
> > been around for awhile?  Users of really old userspace stacks would
> > lose 3D support, but they'd still have 2D, so it wouldn't be a complete
> > break.  The non-KMS paths sometimes break like this anyway without us
> > noticing (especially some of the weirder 3D paths)...
> > 
> > Just thinking out loud, we could really kill a lot of really bad code...
> 
> I among those who would love such things to happen :)

I don't want to drop it _yet_, but "ever"? Sure. When people are sure that 
KMS actually handles all the cases that old X does (maybe that's true 
now), and we've had more than just a couple of kernel releases of _stable_ 
Intel KMS, I suspect we can start thinking about "ok, nobody seriously 
uses 3D on Intel integrated graphics _and_ updates the kernel".

The fact that they'd still have a working X setup would make it generally 
much more palatable, I think. 

But we definitely need more than just a couple of kernel releases. So 
we're talking timescales of "more than a year of stable code". Whether 
that is "six months from now" or "two years from now", I can't judge. 

And people can try to convince me to be more or less aggressive about it, 
so take the above as a more of a personal opinion that is open to 
change than anything definite and final.

		Linus

  parent reply	other threads:[~2010-01-09 18:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 23:45 [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS Rafael J. Wysocki
2010-01-09  0:01 ` Linus Torvalds
     [not found] ` <alpine.LFD.2.00.1001081548320.7821@localhost.localdomain>
2010-01-09  0:06   ` Jesse Barnes
     [not found]   ` <20100108160659.65ac0605@jbarnes-piketon>
2010-01-09  0:21     ` Jesse Barnes
     [not found]     ` <20100108162119.55538b7e@jbarnes-piketon>
2010-01-09  0:43       ` Rafael J. Wysocki
2010-01-09  0:21   ` Rafael J. Wysocki
2010-01-09  0:32   ` Jesse Barnes
     [not found]   ` <20100108163217.341da699@jbarnes-piketon>
2010-01-09  0:46     ` Rafael J. Wysocki
     [not found]     ` <201001090146.17793.rjw@sisk.pl>
2010-01-09  0:50       ` Linus Torvalds
     [not found]       ` <alpine.LFD.2.00.1001081648490.7821@localhost.localdomain>
2010-01-09  1:13         ` Jesse Barnes
     [not found]         ` <20100108171311.128c43d0@jbarnes-piketon>
2010-01-09 13:35           ` [PATCH] i915: Always register as a PCI driver (was: Re: [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS) Rafael J. Wysocki
     [not found]           ` <201001091435.56157.rjw@sisk.pl>
2010-01-09 21:41             ` Dave Airlie
     [not found]             ` <21d7e9971001091341j313e6274vd883c0d5301b2586@mail.gmail.com>
2010-01-09 22:07               ` Rafael J. Wysocki
2010-01-09  2:15   ` [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS Dave Airlie
     [not found]   ` <alpine.DEB.2.00.1001090214220.21286@skynet.skynet.ie>
2010-01-09  2:50     ` Jesse Barnes
     [not found]     ` <20100108185041.7aae6c01@jbarnes-piketon>
2010-01-09 12:01       ` Jerome Glisse
     [not found]       ` <20100109120141.GA4319@localhost.localdomain>
2010-01-09 18:17         ` Linus Torvalds [this message]
2010-01-09 21:32           ` Dave Airlie
     [not found]           ` <21d7e9971001091332v23ac0e28m1b1890cd667aacb8@mail.gmail.com>
2010-01-11 16:38             ` Jesse Barnes
     [not found]             ` <20100111083825.4c2bb7b3@jbarnes-piketon>
2010-01-11 20:12               ` Dave Airlie
     [not found]               ` <21d7e9971001111212h1ded5292l94d514c6f5a47cd4@mail.gmail.com>
2010-01-11 20:22                 ` Jesse Barnes
2010-01-11 21:04                 ` Rafael J. Wysocki
     [not found]                 ` <201001112204.36724.rjw@sisk.pl>
2010-01-11 21:43                   ` Julien Cristau
     [not found]                   ` <20100111214355.GA11456@radis.liafa.jussieu.fr>
2010-01-11 22:22                     ` Rafael J. Wysocki
     [not found]                     ` <201001112322.14152.rjw@sisk.pl>
2010-01-11 23:05                       ` Dave Airlie
     [not found]                       ` <21d7e9971001111505ydf12687nbcb752e38efd493c@mail.gmail.com>
2010-01-11 23:16                         ` Rafael J. Wysocki
2010-01-12 22:33 ` Eric Anholt
     [not found] ` <878wc3j6mm.fsf@pollan.anholt.net>
2010-01-12 22:48   ` Rafael J. Wysocki

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=alpine.LFD.2.00.1001091012080.7821@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=glisse@freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.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