All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Julien Cristau <jcristau@debian.org>
Cc: Dave Airlie <airlied@gmail.com>, 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,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS
Date: Mon, 11 Jan 2010 23:22:14 +0100	[thread overview]
Message-ID: <201001112322.14152.rjw@sisk.pl> (raw)
In-Reply-To: <20100111214355.GA11456@radis.liafa.jussieu.fr>

On Monday 11 January 2010, Julien Cristau wrote:
> On Mon, Jan 11, 2010 at 22:04:36 +0100, Rafael J. Wysocki wrote:
> 
> > Hmm, are you trying to say radeon is better at that?
> > 
> > My experience is quite the opposite to be honest.
> > 
> radeon kms is in staging, doesn't pretend to be stable and force all
> users to the experimental paths.  So yes, I would say radeon is better
> at that.

I guess I should have been more precise.

All of my test boxes with ATI/AMD graphics hardware regressed after upgrading
from openSUSE 11.1 to openSUSE 11.2, in different ways, because of the user
space part of the radeon driver.  Of course, you can argue that the dristro
picked up particularly bad release of the driver, but from the user's point of
view it actually doesn't matter whether the breakage is in the kernel part or
in the user space part of the driver.  The difference is, however, that the
breakage in the kernel is fixed _way_ faster than the breakage in the user
space, so I very much prefer the Intel people pushing new features aggressively
and fixing bugs related to that, then the situation where I need to deal with
the broken user space driver, while the KMS radeon is still not reliable
enough.

IOW, if your user space driver worked 100% of the time, I'd totally agree, but
that's not the case, at least as far as I see it.

Rafael

  reply	other threads:[~2010-01-11 22:21 UTC|newest]

Thread overview: 61+ 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-08 23:45 ` Rafael J. Wysocki
2010-01-09  0:01 ` Linus Torvalds
2010-01-09  0:06   ` Jesse Barnes
2010-01-09  0:21     ` Jesse Barnes
2010-01-09  0:21       ` Jesse Barnes
2010-01-09  0:43       ` Rafael J. Wysocki
2010-01-09  0:43       ` Rafael J. Wysocki
2010-01-09  0:21     ` Jesse Barnes
2010-01-09  0:06   ` Jesse Barnes
2010-01-09  0:21   ` Rafael J. Wysocki
2010-01-09  0:21   ` Rafael J. Wysocki
2010-01-09  0:32   ` Jesse Barnes
2010-01-09  0:46     ` Rafael J. Wysocki
2010-01-09  0:50       ` Linus Torvalds
2010-01-09  1:13         ` Jesse Barnes
2010-01-09  1:13         ` Jesse Barnes
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
2010-01-09 13:35           ` Rafael J. Wysocki
2010-01-09 21:41             ` Dave Airlie
2010-01-09 21:41               ` Dave Airlie
2010-01-09 22:07               ` Rafael J. Wysocki
2010-01-09 22:07               ` Rafael J. Wysocki
2010-01-09 21:41             ` Dave Airlie
2010-01-09  0:50       ` [PATCH] DRM / i915: Fix resume regression on MSI Wind U100 w/o KMS Linus Torvalds
2010-01-09  0:46     ` Rafael J. Wysocki
2010-01-09  0:32   ` Jesse Barnes
2010-01-09  2:15   ` Dave Airlie
2010-01-09  2:50     ` Jesse Barnes
2010-01-09  2:50     ` Jesse Barnes
2010-01-09 12:01       ` Jerome Glisse
2010-01-09 18:17         ` Linus Torvalds
2010-01-09 18:17           ` Linus Torvalds
2010-01-09 21:32           ` Dave Airlie
2010-01-09 21:32           ` Dave Airlie
2010-01-09 21:32             ` Dave Airlie
2010-01-11 16:38             ` Jesse Barnes
2010-01-11 20:12               ` Dave Airlie
2010-01-11 20:12               ` Dave Airlie
2010-01-11 20:12                 ` Dave Airlie
2010-01-11 20:22                 ` Jesse Barnes
2010-01-11 20:22                 ` Jesse Barnes
2010-01-11 21:04                 ` Rafael J. Wysocki
2010-01-11 21:43                   ` Julien Cristau
2010-01-11 21:43                   ` Julien Cristau
2010-01-11 22:22                     ` Rafael J. Wysocki [this message]
2010-01-11 23:05                       ` Dave Airlie
2010-01-11 23:05                         ` Dave Airlie
2010-01-11 23:16                         ` Rafael J. Wysocki
2010-01-11 23:16                         ` Rafael J. Wysocki
2010-01-11 23:05                       ` Dave Airlie
2010-01-11 22:22                     ` Rafael J. Wysocki
2010-01-11 21:04                 ` Rafael J. Wysocki
2010-01-11 16:38             ` Jesse Barnes
2010-01-09 12:01       ` Jerome Glisse
2010-01-09  2:15   ` Dave Airlie
2010-01-09  0:01 ` Linus Torvalds
2010-01-12 22:33 ` Eric Anholt
2010-01-12 22:33 ` Eric Anholt
2010-01-12 22:48   ` Rafael J. Wysocki
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=201001112322.14152.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jcristau@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.