Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161980AbWKVI4y (ORCPT ); Wed, 22 Nov 2006 03:56:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161991AbWKVI4x (ORCPT ); Wed, 22 Nov 2006 03:56:53 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:10980 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1161980AbWKVI4w (ORCPT ); Wed, 22 Nov 2006 03:56:52 -0500 Subject: Re: [PATCH 4/5] e1000 : Make Intel e1000 driver legacy I/O port free From: Arjan van de Ven To: Hidetoshi Seto Cc: Linux Kernel list , linux-pci@atrey.karlin.mff.cuni.cz, Greg KH , Grant Grundler , Andrew Morton , e1000-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org, Kenji Kaneshige In-Reply-To: <4564050C.70607@jp.fujitsu.com> References: <4564050C.70607@jp.fujitsu.com> Content-Type: text/plain Organization: Intel International BV Date: Wed, 22 Nov 2006 09:56:49 +0100 Message-Id: <1164185809.31358.714.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 (2.8.1.1-3.fc6) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 772 Lines: 21 On Wed, 2006-11-22 at 17:06 +0900, Hidetoshi Seto wrote: > static struct pci_device_id e1000_pci_tbl[] = { > + INTEL_E1000_ETHERNET_DEVICE(0x1004, 0), > + INTEL_E1000_ETHERNET_DEVICE(0x1008, E1000_USE_IOPORT), Hi, this has the unfortunate effect that it's now a lot harder to add PCI ID's to this driver at runtime via sysfs ;( Greetings, Arjan van de Ven -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - 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/