public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Andres Freund <andres@anarazel.de>
Cc: keithp@keithp.com, Dave Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org
Subject: Re: [git pull] agp patches for 2.6.28-rc1.
Date: Sun, 19 Oct 2008 18:35:21 -0700	[thread overview]
Message-ID: <1224466521.5303.41.camel@koto.keithp.com> (raw)
In-Reply-To: <200810200300.01411.andres@anarazel.de>

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

On Mon, 2008-10-20 at 03:00 +0200, Andres Freund wrote:

> Hm. But still, there is at least one distribution (ubuntu intrepid) which will 
> propably will ship 2.4.1 in its stable version soon (it seems unlikely that 
> they will update to an unstable version just before an release).

We can backport the fix (it's tiny) to the 2.4 2D driver.

> Which means, that this driver will get quite some spread...
> Is it accepted that the kernel abi breaks that radically/fast?

We tested a pile of hardware and didn't find any GM45s that worked, so
we assumed they were all broken and that fixing the bug wouldn't cause
any working configurations to stop working.

We can hack up the kernel so the old X server just gets a WARN_ON
instead of breaking. This is a bit worrying though; the "fix" would let
user space continue to mis-program the hardware.

My concern here is that a common failure mode with this bug was to lock
up the graphics hardware and require a reboot. Having the X server fail
to start and leave the system in text mode where new packages can be
installed seems like a better mode than making the system hang during
boot.

-- 
keith.packard@intel.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-10-20  1:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  6:59 [git pull] agp patches for 2.6.28-rc1 Dave Airlie
2008-10-19 23:11 ` Andres Freund
2008-10-19 23:25   ` Dave Airlie
2008-10-19 23:44     ` Andres Freund
2008-10-20  0:19       ` Keith Packard
2008-10-20  0:34         ` Andres Freund
2008-10-20  1:00         ` Andres Freund
2008-10-20  1:04           ` Dave Airlie
2008-10-20  1:18             ` Andres Freund
2008-10-20  1:35           ` Keith Packard [this message]
2008-10-20  1:58             ` Andres Freund
2008-10-20  2:19               ` Keith Packard
2008-10-20  2:27                 ` Andres Freund
2008-10-20  9:50                 ` Andres Freund
2008-10-20 10:29                   ` Andres Freund

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=1224466521.5303.41.camel@koto.keithp.com \
    --to=keithp@keithp.com \
    --cc=airlied@linux.ie \
    --cc=andres@anarazel.de \
    --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