From owner-freebsd-net@FreeBSD.ORG Tue Dec 8 23:10:31 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 9B1D71065672 for ; Tue, 8 Dec 2009 23:10:31 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outP.internet-mail-service.net (outp.internet-mail-service.net [216.240.47.239]) by mx1.freebsd.org (Postfix) with ESMTP id 7EEEB8FC13 for ; Tue, 8 Dec 2009 23:10:31 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1EF27ACB80; Tue, 8 Dec 2009 15:10:31 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id B5FC52D6014; Tue, 8 Dec 2009 15:10:30 -0800 (PST) Message-ID: <4B1EDCEA.9060209@elischer.org> Date: Tue, 08 Dec 2009 15:10:34 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: David Christensen References: <2f7feda40912010931i3cf7d90dmb2a8d08ecd40589f@mail.gmail.com> <5D267A3F22FD854F8F48B3D2B52381933A3169363C@IRVEXCHCCR01.corp.ad.broadcom.com> <4B1DB10A.5060005@elischer.org> <5D267A3F22FD854F8F48B3D2B52381933A31693938@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A31693938@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 23:10:31 -0000 David Christensen wrote: >>> MSI is broken on this device (actually all PCI/PCI-X devices in the >>> 57XX family). The interrupt will be asserted as expected >> but masking >>> the interrupt does not work. For those newer 1Gb PCIe >> devices that do >>> work correctly with MSI, only a single message is actually >> supported. >> >> Might be a good thing of someone would work up a man page >> paragraph to this effect. >> > > As a more general question, what would be the right medium to > document such device errata as it relates to a driver? Is the > 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 I think the BUGS section of the man page is correct place.. It could also include problems in the related hardware. It's where people would look when they are having problems. If you sent me a paragraph for the correct man page (it's bce right?) I can commit it for you.