From owner-svn-src-all@FreeBSD.ORG Mon Aug 23 06:27:38 2010 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03E9A10656A5; Mon, 23 Aug 2010 06:27:38 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 739798FC16; Mon, 23 Aug 2010 06:27:37 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.4/8.14.4) with ESMTP id o7N6RYBk087833; Mon, 23 Aug 2010 00:27:34 -0600 (MDT) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: <201008222126.o7MLQavY016669@svn.freebsd.org> Date: Mon, 23 Aug 2010 00:27:33 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <7C069EE9-33B9-4D57-A6E6-C133F6C47D53@samsco.org> References: <201008222126.o7MLQavY016669@svn.freebsd.org> To: Pyun YongHyeon X-Mailer: Apple Mail (2.1081) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r211648 - head/sys/pci X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2010 06:27:38 -0000 On Aug 22, 2010, at 3:26 PM, Pyun YongHyeon wrote: > Author: yongari > Date: Sun Aug 22 21:26:35 2010 > New Revision: 211648 > URL: http://svn.freebsd.org/changeset/base/211648 >=20 > Log: > It seems some newer RTL8139 controllers provides only memory space > register mapping. Something that I'm seeing more of in recent years is vendors putting = descriptive information into PCI VPD attributes, and having their = Windows and Linux drivers read these attributes and select behavior off = of them instead of selecting based on PCI ID. I don't have any RLT8139 = specs to confirm that this would be the case here, but it might be = something to consider looking into. Scott