From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florin Malita Subject: [PATCH 15/17] sky2: only disable 88e8056 on some boards Date: Mon, 14 May 2007 00:53:42 -0400 Message-ID: <4647EB56.6080800@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: shemminger@linux-foundation.org Return-path: Received: from an-out-0708.google.com ([209.85.132.241]:25381 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754352AbXENEzK (ORCPT ); Mon, 14 May 2007 00:55:10 -0400 Received: by an-out-0708.google.com with SMTP id d18so385563and for ; Sun, 13 May 2007 21:55:09 -0700 (PDT) References: 20070509035030.939143538@linux-foundation.org Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi Stephen, Stephen Hemminger wrote: > Use DMI to add a blacklist of broken board. For now only one is known > bad. Gentoo users report driver works on other motherboards (strange). [snip] > + .ident = "Gigabyte 965P-S3", > + .matches = { > + DMI_MATCH(DMI_SYS_VENDOR, "Gigabyte Technology Co., > Ltd."), > + DMI_MATCH(DMI_PRODUCT_NAME, "965P-S3"), Actually, I've been using sky2 with a 965P-S3 for a couple of months (x86_64 kernel) and as far as I can tell it works like a charm. Recently I had to hack around the blacklisting but other than that I haven't noticed anything strange. What failures are you trying to prevent? Would a warning (instead of blacklisting) be acceptable? Thanks, Florin 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) Subsystem: Giga-byte Technology Unknown device e000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-