From owner-freebsd-net@FreeBSD.ORG Mon Sep 11 21:02:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F269016A403 for ; Mon, 11 Sep 2006 21:02:59 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4442143D53 for ; Mon, 11 Sep 2006 21:02:59 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so583990nzn for ; Mon, 11 Sep 2006 14:02:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uCsYujiflBPHVvGA3BaaK6corlRA4qKUgT6uqPJ4HPUja/aMu0t7CAVFhHJPY/cPJjHMhgIi22LgkZfCcteiFZAwH16fQstm+rVnr9Xb4sz9TBPUVm/qa0OdC+H7LyOa1zASq74p1bAyxprncYqARtra/DfFR9xOMrnhnSaYNmc= Received: by 10.35.61.17 with SMTP id o17mr9611390pyk; Mon, 11 Sep 2006 14:02:58 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Mon, 11 Sep 2006 14:02:58 -0700 (PDT) Message-ID: <2a41acea0609111402g68741d86ib185e9bb77908658@mail.gmail.com> Date: Mon, 11 Sep 2006 14:02:58 -0700 From: "Jack Vogel" To: freebsd-net , "Prafulla Deuskar" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Stale PCI ID X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 21:03:00 -0000 In the last attempt to merge community CVS with Intel internal code I came across an issue I'd like to bring up. There is an ancient e1000 card, pci id 1000, an 82542, that we don't have in our source, yet community cvs still does. Support for this was removed from Linux long ago because the card did not even work. I just had our test group hunt up one of these and test, and sure enough, the driver recognizes it, but it does NOT pass traffic. Clearly no one is using these, at least not with STABLE :) and as Intel does not want to support this I would recommend removing the ID from the driver. Comments? Jack