Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161261AbWALU5P (ORCPT ); Thu, 12 Jan 2006 15:57:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161265AbWALU5P (ORCPT ); Thu, 12 Jan 2006 15:57:15 -0500 Received: from palinux.external.hp.com ([192.25.206.14]:45208 "EHLO palinux.hppa") by vger.kernel.org with ESMTP id S1161261AbWALU5O (ORCPT ); Thu, 12 Jan 2006 15:57:14 -0500 Date: Thu, 12 Jan 2006 13:57:14 -0700 From: Matthew Wilcox To: Daniel Drake Cc: Jon Mason , mulix@mulix.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz Subject: Re: pcnet32 devices with incorrect trident vendor ID Message-ID: <20060112205714.GK19769@parisc-linux.org> References: <20060112175051.GA17539@us.ibm.com> <43C6C0E6.7030705@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C6C0E6.7030705@gentoo.org> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 19 On Thu, Jan 12, 2006 at 08:49:42PM +0000, Daniel Drake wrote: > interesting: > > http://forums.gentoo.org/viewtopic-t-420013-highlight-trident.html > > The user saw the correct vendor ID (AMD) in 2.4, but when upgrading to > 2.6, it changed to Trident. It looks to me like there used to be a quirk that knew about this bug and fixed it. The reason I say this is that the lspci -x dumps are the same -- both featuring the wrong vendor ID. Want to dig through 2.4 and look for this quirk? - 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/