Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932244AbWBMS2o (ORCPT ); Mon, 13 Feb 2006 13:28:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932299AbWBMS2o (ORCPT ); Mon, 13 Feb 2006 13:28:44 -0500 Received: from mx1.redhat.com ([66.187.233.31]:29662 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932244AbWBMS2o (ORCPT ); Mon, 13 Feb 2006 13:28:44 -0500 Date: Mon, 13 Feb 2006 13:27:12 -0500 From: Dave Jones To: Linus Torvalds Cc: Adrian Bunk , Andrew Morton , Linux Kernel Mailing List , Mauro Tassinari , airlied@linux.ie Subject: Re: 2.6.16-rc3: more regressions Message-ID: <20060213182712.GA32350@redhat.com> Mail-Followup-To: Dave Jones , Linus Torvalds , Adrian Bunk , Andrew Morton , Linux Kernel Mailing List , Mauro Tassinari , airlied@linux.ie References: <20060213170945.GB6137@stusta.de> <20060213174658.GC23048@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1431 Lines: 34 On Mon, Feb 13, 2006 at 10:16:59AM -0800, Linus Torvalds wrote: > > > On Mon, 13 Feb 2006, Linus Torvalds wrote: > > > > DaveA, I'll apply this for now. Comments? > > Btw, the fact that Mauro has the same exact PCI ID (well, lspci stupidly > suppresses the ID entirely, but the string seems to match the one that > Dave Jones reports) may be unrelated. > > DaveJ (or Mauro): since you can test this, can you test having that ID > there but _without_ the other changes to drm in -rc1? > > Ie was it the addition of that particular ID, or are the other radeon > driver changes (which haven't had as much testing) perhaps the culprit? > > I realize that without the ID, that card would never have been tested > anyway, but the point being that plain 2.6.15 with _just_ that ID added > has at least gotten more testing on other (similar) chips. So before I > revert that particular ID, it would be nice to know that it was broken > even with the previous radeon driver state. r300 is unlike the other chips though. Adding that ID on its own doesn't make any sense, as the rest of the radeon driver won't have a clue how to drive the new hardware. Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/