From owner-freebsd-net@FreeBSD.ORG Tue Dec 8 22:24:52 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30C20106568B for ; Tue, 8 Dec 2009 22:24:52 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB898FC14 for ; Tue, 8 Dec 2009 22:24:51 +0000 (UTC) Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 08 Dec 2009 14:22:21 -0800 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Tue, 8 Dec 2009 14:23:44 -0800 From: "David Christensen" To: "Julian Elischer" Date: Tue, 8 Dec 2009 14:22:20 -0800 Thread-Topic: bge driver and MSI Thread-Index: Acp3qPCh+RPCskJbT8iOL6CY+k5x9gAq036A Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A31693938@IRVEXCHCCR01.corp.ad.broadcom.com> References: <2f7feda40912010931i3cf7d90dmb2a8d08ecd40589f@mail.gmail.com> <5D267A3F22FD854F8F48B3D2B52381933A3169363C@IRVEXCHCCR01.corp.ad.broadcom.com> <4B1DB10A.5060005@elischer.org> In-Reply-To: <4B1DB10A.5060005@elischer.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 67000E173J827399446-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "freebsd-net@freebsd.org" , Rafael Ganascim Subject: RE: bge driver and MSI 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: Tue, 08 Dec 2009 22:24:52 -0000 > > MSI is broken on this device (actually all PCI/PCI-X devices in the=20 > > 57XX family). The interrupt will be asserted as expected=20 > but masking=20 > > the interrupt does not work. For those newer 1Gb PCIe=20 > devices that do=20 > > work correctly with MSI, only a single message is actually=20 > supported. >=20 > Might be a good thing of someone would work up a man page=20 > paragraph to this effect. >=20 As a more general question, what would be the right medium to document such device errata as it relates to a driver? Is the=20 man page the best location or would it be better to add a table near the top of the driver file which summarizes the bugs and the workarounds? Is there a general consensus? Dave=